You're my inbox assistant. Go through everything that landed in my inbox in the last 7 days. Sort every email into exactly one of these: REPLY TODAY / REPLY THIS WEEK / READ LATER / SAFE TO UNSUBSCRIBE. For anything in REPLY TODAY or REPLY THIS WEEK, write a draft reply in my voice: warm, direct, short. No "I hope this email finds you well." No paragraph where a sentence does the job. Rules: - If an email needs a decision only I can make, still draft it, but leave a [DECISION: ...] placeholder where my answer goes. Don't guess. - Anything mentioning money, a contract, or a date I could miss gets flagged, regardless of bucket. - Newsletters and notifications go to READ LATER unless they contain a deadline or a payment problem. - Never send anything. Drafts only. Output: one table first - Bucket | From | Two-line summary | Flagged? Then the draft replies underneath, each with its subject line.

Here is the transcript of a call I just ran. Pull the content out of it. Find every moment where I did one of these three things: 1. Explained something in a way that actually landed 2. Gave an opinion, especially an unpopular one 3. Told a story or gave a specific example For each moment, give me: the raw quote, a hook line, a 30-second script, and a caption. Rules: - Skip anything client-confidential. If a moment only works by revealing who the client is or their numbers, leave it out and tell me you did. - Use my actual words wherever they're already good. Don't smooth them into marketing voice. - If a moment is only half-formed, say so rather than inflating it. Output: a numbered list of moments, strongest first, with a one-line note on why each one will land.

Audit every funnel in my business and tell me what's actually running. A funnel is anything that takes a stranger and moves them somewhere: an opt-in, a landing page, a lead magnet, an email sequence, a comment-to-DM trigger, a link in bio. For each one, log: - Where people enter it - What they get immediately - What happens next (which sequence, which page) - Whether it is still live right now - When it was last touched Then flag, in a separate list: - Anything broken (dead links, 404s, sequences that end nowhere) - Anything orphaned (live page, but nothing points at it) - Anything duplicated (two funnels doing the same job) Output: one table of every funnel, then the flagged list with a one-line fix for each. Check the links rather than assuming - tell me which ones you actually tested.

Here is a transcript from a video I filmed. Write the text for every platform. Give me: - Instagram caption - TikTok on-screen text - LinkedIn post - Threads version - Email intro with subject line - YouTube description Rules: - These are not reformats of each other. LinkedIn opens on the business cost. TikTok opens on the sharpest line in the first three words. Email can take its time. Threads is a thought, not a lecture. - Use my words from the transcript. If a line is already good, keep it exactly. - One CTA across all of them so the keyword stays consistent. - Australian spelling. Output: each platform as its own block, labelled, ready to copy.

Every Monday, give me last week's numbers on one page. Pull: sales, email list growth, website visits, and content performance. Then answer three questions, in this order: 1. What made money? Be specific - which offer, which post, which email. 2. What did not work? Name it plainly. Don't soften it. 3. What are the three things to focus on this week, based on the two answers above? Rules: - Compare to the week before, not to my best week ever. - If a number moved more than 20% in either direction, tell me what caused it. - If you can't get a number, say so rather than estimating it. Output: a four-tile summary at the top (the headline numbers with their change), then the three answers underneath. One page. No preamble.

Watch my top three competitors and report back weekly. I'll give you their handles and sites. For each one, log: - What they posted this week and roughly how it performed - Their best performing piece and why you think it worked - What they are charging, if it's public - Anything new they launched or changed Then the part I actually want: three angles they have all missed. Not three things they did well - three gaps. Rules: - I want what they did, not a vibe. Quote the hooks. - If their pricing isn't public, say so. Don't infer it. - Flag if one of them has clearly changed direction. Output: one block per competitor, then the three gaps at the bottom with a one-line pitch for each.

Check my calendar for tomorrow. For every meeting with another human in it (skip focus blocks, travel and reminders), write me a short brief. Open the linked files, notes and past email threads for each one, then give me: - Who I am meeting and their role - What we agreed or discussed last time - What I owe them, and what they owe me - Three good questions to ask Rules: - If I promised something last time and haven't done it, put that at the top in bold. That's the thing I'll be embarrassed about. - If there's no history with this person, say so and give me three openers instead. - Keep each brief to one screen. Output: briefs in calendar order, with the time and the meeting name as the heading.

List every unpaid invoice, then write the chase emails. For each one, show me: client, amount, what it was for, when it was due, how many days overdue. Then draft a chase email for each, with the tone matched to how late it is: - Under 7 days: light. Assume they forgot, because they probably did. - 7 to 30 days: direct. State the amount and the due date. Ask for a payment date. - Over 30 days: firm and short. Reference the earlier emails, state what happens next, give a deadline. Rules: - Never apologise for asking to be paid. No "so sorry to chase." - Always include the invoice number and the amount in the body, not just the attachment. - Leave them all as drafts. Never send. Output: the table first, then the drafts underneath, each labelled with the client name and the tone you used.

You're my inbox assistant. Go through the emails that landed in my inbox in the last 24 hours and do three things with each one. 1. Sort it into exactly one bucket: REPLY TODAY / REPLY THIS WEEK / READ ONLY / ARCHIVE. 2. Summarise it in two lines max - who it's from, what they actually want. 3. For anything in REPLY TODAY or REPLY THIS WEEK, write a draft reply in my voice: warm, direct, short. No "I hope this email finds you well." No paragraph where a sentence works. Rules: - If an email needs a decision only I can make, put it in REPLY TODAY and write the draft with a [DECISION: ...] placeholder where my answer goes. Don't guess the decision. - Newsletters, receipts and notifications go to ARCHIVE unless they contain a deadline or a payment problem. - Flag anything mentioning money, a contract, or a date I could miss. - Never send anything. Drafts only. Give me one table first: Bucket | From | Two-line summary | Flagged? Then the draft replies underneath, each with its subject line so I know which is which. Start by telling me what you need connected to read my inbox.

Look at my calendar for tomorrow. For every meeting that has another human in it (skip focus blocks, reminders and travel time), write me a one-page brief. Each brief has: - WHO: name, company, role, and how we know each other - LAST TIME: what was discussed or agreed at our previous meeting, based on my calendar, notes and email history - WHY THIS MEETING: what the invite says it's for, in plain English - MY THREE GOALS: the three things I should walk out of this call having got - OPEN LOOPS: anything I promised them and haven't delivered - ONE GOOD QUESTION: something worth asking that shows I've paid attention Rules: - Don't invent history. If you can't find a previous meeting, write "No prior meeting found." - Under 200 words per brief. I'm reading this in the car park. - Put them in the order the meetings actually happen, with the start time at the top. - If two meetings are back to back with no gap, say so at the top. Tell me which accounts you need connected before you start.

My Downloads folder is out of control. Sort it out - but don't delete anything. Do this: 1. List everything in my Downloads folder with the file name, type, size and the date it was last opened. 2. Create a folder called "Downloads Review" with these subfolders: Invoices & Receipts, Client Files, Photos & Screenshots, Installers, Documents, Everything Else. 3. Move anything I haven't opened in 60 days into the matching subfolder. 4. Leave anything I've opened in the last 60 days exactly where it is. 5. Find likely duplicates (same name, or same size and same type) and list them - don't act on them. Rules: - Never delete. Never empty the bin. Moving only. - If a file name is meaningless (IMG_4429, Document (7), Untitled-3), tell me what's actually in it so I can rename it. - Don't touch anything that looks like it belongs to an application rather than to me. - When you're done, give me a before/after count, the duplicates list, and the list of files that need renaming.

It's Monday. Build me the brief for this week. Pull from my calendar, my task list and anything I've flagged in the last fortnight, then give me: 1. THE WEEK AT A GLANCE - how many meeting hours, how many free hours, and which day is the worst. Say it plainly: "Wednesday is cooked." 2. THE BIG THREE - the three things that, if they get done, make this a good week. You pick them. Don't give me ten. 3. OPEN LOOPS - things I said I'd do and haven't. Name who's waiting on me. 4. DEADLINES - anything due in the next 14 days, soonest first. 5. WHAT TO MOVE - if my calendar doesn't leave room for the Big Three, tell me which meeting to shift and where to. Rules: - Under 400 words. This is a brief, not a report. - No encouragement, no pep talk. Tell me what's true. - If something has been on the open loops list three weeks running, say so out loud. - If the week is genuinely quiet, say that too and suggest what to pull forward.

I'm going to give you a folder of receipts and invoices (PDFs, screenshots, photos). Turn them into one expense sheet. For each receipt, pull out: Date | Supplier | Description | Amount (inc GST) | GST amount | Category | Payment method | Source file name Categories: Software & subscriptions, Contractors, Travel, Meals & entertainment, Equipment, Marketing, Professional fees, Other. Rules: - Australian receipts: where GST applies it's 1/11th of the total. If a receipt says no GST, or the supplier is overseas, put 0 and note why. - If you can't read a field confidently, write NEEDS CHECK in that cell instead of guessing. I'd rather fix ten cells than find out in July. - Foreign currency: keep the original amount and currency and flag it for conversion. Don't convert it yourself. - Sort by date, oldest first. - At the end give me the total, the total GST, and a subtotal per category. - List separately any file you couldn't read at all. Output it as a table I can paste straight into Google Sheets.

At the end of each working day, write my work log. Look at what actually happened today - calendar events, files I touched, messages I sent, tasks I ticked off - and give me three short lists: DONE - what got finished today. Be specific: "Sent the Bloom proposal", not "worked on proposals". IN PROGRESS - what I started and didn't finish, and what's blocking it. NEXT - the first three things to pick up tomorrow, in order. Then one line: FRICTION - the thing that ate time today that shouldn't have. Rules: - 12 bullets total, maximum. If it was a big day, pick the 12 that matter. - Write it as if I'm reading it in six months trying to remember what I was doing. Use names, not pronouns. - Don't include anything you're guessing at. If you're not sure a task got finished, put it in IN PROGRESS. - No motivational sign-off.

Here's one piece of content: [PASTE THE ARTICLE, TRANSCRIPT OR LINK] Turn it into eight social posts. Each one makes a DIFFERENT point from the piece. Use a different angle for each: 1. The strongest single claim, stated flatly 2. A story or example from the piece 3. A list of three to five things 4. The thing most people get wrong 5. A contrarian take the piece actually supports 6. A question that makes people argue in the comments 7. A step-by-step someone could do today 8. The whole idea in one sentence For each post give me: the post text, the platform it suits best (Instagram / LinkedIn / Threads / X), and the first line on its own so I can check the hook works cold. Rules: - No hashtag walls. Three maximum, and only real ones. - Every post has to stand on its own without the article. - Write like a person, not a brand account. Short sentences. - Banned: "dive in", "game-changing", "unlock", "in today's fast-paced world", "whether you're X, Y or Z". - Don't use a single fact that isn't in the source piece.

Summarise this Slack thread: [PASTE THE THREAD OR LINK IT] Give me exactly this, in this order: DECIDED - what was actually agreed. One line each. OWNERS - who's doing what, by when. Format: Name - task - due date. If no date was given, write "no date agreed". STILL OPEN - questions somebody raised that nobody answered. MY BIT - anything assigned to me, pulled out separately so I can't miss it. Rules: - Don't summarise the chat. Summarise the outcome. - If two people disagreed and it was never resolved, say so. Don't smooth it over into a fake consensus. - Ignore jokes and emoji reactions, unless a reaction is how somebody agreed to something. - If nothing was actually decided, write "Nothing was decided" rather than inventing a takeaway.

I've got a meeting with [NAME] from [COMPANY] on [DATE]. Research them and give me a one-pager - with a source link for every claim. Cover: - ROLE: what they actually do, not just their job title - COMPANY: what it sells, roughly how big, anything that's changed recently - RECENT: anything they've published, posted or been quoted in over the last 6 months - COMMON GROUND: anything we genuinely have in common - people, places, industries - WATCH OUT: anything awkward I should know before I open my mouth - TWO QUESTIONS: two things worth asking that they haven't been asked a hundred times Rules: - Every claim gets a link. No link, leave it out. - Public information only: published bios, company sites, news, public posts. Nothing scraped from anywhere private. - If you can't verify something, don't hedge it - drop it. - At the end, list what you could NOT find, so I know where the gaps are. - If there are several people with this name, show me the candidates and ask which one before you go deep.

Write this week's newsletter out of the work I actually did. Look at my calendar, notes, finished tasks and published content for the last 7 days and pull out the one thing worth telling people about. Not a roundup. One idea. Structure: - A subject line that says something specific (not "Weekly Update") - An opening hook: the moment, the problem, or the thing that annoyed me this week - The idea: what I worked out or decided, and why it matters to someone running their own business - The proof: the actual example from my week - One thing they can do this week - A sign-off Rules: - 400 to 600 words. Conversational. Short paragraphs. - Australian English. - Banned: "dive in", "game-changing", "unlock your potential", "in today's fast-paced world", "furthermore", "it's important to note that", "whether you're X, Y or Z". - If the week was genuinely boring, say so and pick the smallest true story rather than inflating something. - Give me the subject line three ways so I can pick.

Here's a voice note (or its transcript): [ATTACH OR PASTE] I was thinking out loud. Turn it into something I can act on. Give me: TASKS - every action hiding in there. One line each, starting with a verb. Add a due date if I said one, otherwise "no date". DECISIONS - anything I decided while talking. IDEAS - things worth keeping but not doing yet. QUESTIONS - anything I said I needed to find out, or ask someone. BIN - anything that was just me thinking and doesn't need to exist. List it anyway so I can check you didn't bin something important. Rules: - Don't tidy up my meaning. If I contradicted myself, give me both versions and flag it. - If I named a person, keep the name on the task. - Keep my own words where they're clearer than yours. - Don't add a task I didn't say out loud.

Here's a meeting transcript: [PASTE OR ATTACH] Pull out the commitments. Nothing else. Give me one table: Owner | What they committed to | By when | Quote Rules: - The Quote column is the actual line from the transcript where the commitment was made. This is not optional - it's how I check you got it right. - "By when": use the date if one was said. If someone said "next week", write the real date and mark it (inferred). If there was no timing at all, write "no date agreed". - If a commitment was made and then walked back later in the call, don't put it in the table - list it under WALKED BACK. - Anything agreed but assigned to nobody goes under UNOWNED. Those are the ones that quietly never happen. - Do not add tasks nobody said out loud. If the meeting produced two actions, give me two.

Here's my customer feedback: [PASTE REVIEWS, SURVEY ANSWERS, DMs OR SUPPORT MESSAGES] Group it into themes. Not sentiment - themes. For each theme give me: - THEME: a plain name for it, in the customers' language not mine - HOW OFTEN: how many pieces of feedback mention it, and what share of the total that is - WHAT THEY ACTUALLY SAY: three quotes, word for word - SEVERITY: is this "mildly annoying" or "this is why they left"? - THE FIX: the smallest change that would move it Then rank the themes by how often multiplied by how badly, and tell me which one to fix first. Rules: - Don't merge two different complaints into one nice-sounding theme. Annoyed about price AND annoyed about response time is two themes. - Quotes are verbatim. Don't clean up the spelling or the tone. - If something came up once but it's serious, put it in a separate list: ONE-OFFS BUT SERIOUS. - Say how many pieces of feedback you processed, so I know nothing got skipped.

You're triaging my support inbox. For every message, tag it and tell me what to do. For each one give me: Topic - one of: Billing, Access & login, How-to question, Bug or broken thing, Refund request, Feature request, Not support (sales / spam / other) Urgency - P1 (they can't use the thing, or money is wrong), P2 (blocked but there's a workaround), P3 (question, no rush) Sentiment - Calm / Frustrated / About to leave Suggested action - one line Draft reply - for P3 how-to questions only, write the full reply. For P1 and P2, write the first two lines only and I'll take it from there. Rules: - Anything mentioning a chargeback, a lawyer, a public review, or "cancel my account" is automatically P1, whatever else it says. - Anything where someone has followed up twice with no reply from us gets flagged, whatever the topic. - Order the output P1 first. - Never promise a refund, a fix or a date in a draft. Say we're onto it. - Never send anything. Drafts only.

Here are my notes (or the transcript) from a sales call: [PASTE] Write the follow-up email. It needs: - A subject line referencing something specific they said, not "Great chatting today" - One line that proves I listened - their actual words about their actual problem - What I'm proposing, in plain English, with the price if we discussed one - What happens next and by when - One clear ask (book the next call / say yes / send me X) Rules: - Under 200 words. Nobody reads a long follow-up. - Warm and direct. Banned: "I hope this email finds you well", "circling back", "just following up", "touching base". - Australian English. - Only include things that were actually said on the call. Where I need to fill something in, leave [FILL IN: what's needed] so I can see it. - If they raised an objection, answer it in one sentence. Don't dodge it and don't write three paragraphs about it. - Give me a second version that's shorter and blunter, so I can pick.

Here's my approved proposal template: [PASTE THE TEMPLATE] Here are my notes on this client: [PASTE THE CALL NOTES OR BRIEF] Fill the template in for this client. Follow the structure exactly - same sections, same order, same headings. Don't redesign it. Rules: - Use their language for their problem. If they said "our onboarding is a mess", the proposal says onboarding is a mess, not "suboptimal client activation". - Every claim about what I'll deliver has to trace back to something in my notes or my template. Invent nothing. - Where you don't have the information, write [FILL IN: what's needed] instead of guessing. Especially prices, dates and scope. - Keep the scope tight to what we discussed. Don't add deliverables to make it look bigger. - At the end, list separately: (a) everything you had to assume, (b) everything I still need to fill in before this goes out.

Compare these two documents and tell me what changed. Document A (older): [PASTE OR ATTACH] Document B (newer): [PASTE OR ATTACH] Give me: CHANGES THAT MATTER - anything affecting money, dates, scope, obligations, liability, or who's responsible for what. For each: what it said before, what it says now, and why it matters in one line. EVERYTHING ELSE - wording, formatting, reordering. Just list it, don't explain it. ADDED - anything in B that isn't in A. REMOVED - anything in A that's gone from B. This is the one people miss. Rules: - Quote the before and after text exactly. Never paraphrase a contract. - If a number changed, show both numbers. - Sort CHANGES THAT MATTER most significant first, and say why the first one is first. - If you're unsure whether something is a real change or just reformatting, put it in CHANGES THAT MATTER and flag the uncertainty. I'd rather check. - This is not legal advice and you're not my lawyer. Just tell me what moved.

Here's a spreadsheet: [PASTE OR ATTACH] Clean up the labels and find the duplicates. Don't delete anything. Do this: 1. For each text column, show me every distinct value and how many times it appears. Group the ones that are obviously the same thing spelled differently ("NSW", "N.S.W.", "New South Wales", "nsw "). 2. Propose ONE standard spelling per group and show me the mapping BEFORE you apply it. 3. Fix the boring stuff: trailing spaces, inconsistent capitalisation, smart quotes, and dates in mixed formats (standardise to DD/MM/YYYY). 4. Flag likely duplicate ROWS - the same person or company with slightly different details. Show the rows side by side and say exactly what matches. 5. Flag blanks in columns that shouldn't be blank. Rules: - Show me the mapping and wait for my OK before you change a single cell. - Never merge two rows on your own. Flag them and I'll decide. - Give me the cleaned version as a new table, with a column keeping the original value so I can check your work. - Tell me how many rows you processed.

Here are this week's numbers: [PASTE THE DATA, OR CONNECT THE ACCOUNT] Write me the plain-English version. I don't want a dashboard, I want to know what happened. Give me: - THE HEADLINE: one sentence. What's the story of this week? - WHAT MOVED: the three biggest changes against last week. Give the number, the change, and the percentage. Up or down. - WHY, PROBABLY: your best explanation for each, and how confident you are in it. Say "I don't know" when you don't. - WHAT'S FLAT: anything that isn't moving and should be. Flat is information too. - ONE THING TO DO: the single action this week's numbers point at. Rules: - No jargon. If a nine-year-old couldn't follow it, rewrite it. - Never describe a change without the actual numbers next to it. "Up a lot" is useless. - Small numbers: if something went from 2 to 4, say "2 to 4", not "up 100%". - If the sample is too small to mean anything, say so instead of finding a pattern in noise. - Under 300 words.

Here's everything my audience has asked me lately: [PASTE DMs, COMMENTS, EMAILS, SURVEY ANSWERS OR SALES-CALL QUESTIONS] Two jobs. JOB 1 - THE FAQ Group the questions into the real underlying questions (people ask the same thing fifteen different ways). For each one: - The question, phrased the way they ask it - How many times it came up - A clear answer in three to five sentences JOB 2 - THE CONTENT LIST Turn the top 15 into content ideas. For each: the question, the format that suits it (short video / carousel / email / long post), and a hook line built out of their words. Rules: - Use their wording, not industry wording. If they say "how do I get started", the FAQ says that, not "onboarding process". - Rank by how often it's asked, most-asked first. - List separately: QUESTIONS I CAN'T ANSWER YET - the ones needing a decision or information from me. Those are usually the best content. - Don't invent questions. Everything comes from the source.