Go through everything that's arrived in my inbox since yesterday. Sort it into four groups: 1. NEEDS ME — genuinely requires my judgement or my voice 2. DRAFTED — you can write the reply, so write it 3. FILE — useful but no action needed 4. NOISE — newsletters, notifications, nothing to do For everything in DRAFTED, write the reply in my voice: warm, direct, no corporate padding, no "I hope this finds you well". Then give me a one-screen summary at the top: how many in each group, and the three things in NEEDS ME ranked by what happens if I ignore them. Don't send anything. Just draft.

I've just signed a new client. Here's what I know: [who they are, what I'm delivering, the price, the timeline, how we'll work together]. Build me the full onboarding pack: 1. A welcome email in my voice — warm, clear about what happens next, no corporate onboarding language 2. A kickoff call agenda, including the awkward questions I should ask now rather than in week six 3. A prep form: what I need from them before we start, and why each item matters 4. A folder structure and file naming convention for this client 5. A first-week checklist for me Make it feel like a business that's done this before, not a form letter. Keep the client-facing bits short — nobody reads a long welcome email.

Here's the transcript from a client call: [paste it]. Give me: 1. ACTIONS — what was agreed, who owns it, and by when. If a date wasn't said, mark it "no date agreed" rather than inventing one. 2. DECISIONS — what was settled, so nobody relitigates it in three weeks 3. OPEN QUESTIONS — what was raised and left hanging 4. RISKS — anything said in passing that could become a problem 5. A follow-up email to the client summarising the agreed actions, ready to send Quote them directly where the exact wording matters. Don't smooth over disagreement — if something was left unresolved, say it was.

Here's the transcript of my discovery call: [paste it]. Draft a proposal based on what they actually said they needed — not what I could sell them. Include: - A short summary of their situation, in their words, so they feel heard - The outcome we're aiming for - Scope: what's included, and explicitly what isn't - Timeline with milestones - Investment (leave the number blank for me to fill) - What I need from them for this to work Keep it under two pages. Flag anything they said that suggests scope creep is coming, and tell me the boundary I should write in now to prevent it.

Here's the transcript of a video I just filmed: [paste it]. Turn it into: 1. An Instagram caption — hook in the first line, short lines, one clear CTA 2. A LinkedIn post — same idea, more context, professional but not stiff 3. Six carousel slides — one point per slide, short enough to read at a glance 4. A short email to my list Use my actual words and examples wherever you can. Don't add claims I didn't make or polish the personality out of it. Each one should stand on its own — someone who saw the video shouldn't feel like they're reading the same thing again.

Here's what's in my calendar this week and what I'm trying to get done: [paste your calendar and your list]. Tell me honestly whether this week is realistic. Give me: - Where I've over-committed, with the specific days - What to move, and where to move it - Where my genuinely free blocks are, and what deep work should go in them - What I should say no to - The one thing that, if it's the only thing that happens, makes this a good week Assume everything takes longer than I've allowed, because it does. Be blunt about what won't fit.

Here's a recording (or transcript) of me doing a task: [attach or paste]. Turn it into a step-by-step SOP someone else could follow without asking me questions. Include: - What this process is for and when to run it - What they need before starting — access, logins, files - Numbered steps in plain English - The bits where it commonly goes wrong, and what to do - How to know it worked Write it for someone competent who has never seen this task. No jargon, no assumed knowledge. Where I did something without explaining why, flag it so I can fill in the reasoning.

I need to make a decision about: [what you're deciding]. Here's what matters to me: [budget, must-haves, deal-breakers, anything specific to your situation — including that you're in Australia if that affects pricing, tax or availability]. Research it properly and give me: 1. The two or three real options, not a list of ten 2. A comparison against my actual criteria 3. The catch with each one — pricing that scales badly, a missing feature, a lock-in 4. What I'd have missed if I'd only looked at their websites 5. Your recommendation, and what would change your mind Cite where things came from. If something is unclear or you couldn't verify it, say so rather than filling the gap.

Here's a messy export: [upload the CSV or paste the data]. Clean it up: - Remove duplicates, and tell me how many you removed and how you decided - Standardise the formatting — names, dates, phone numbers, capitalisation - Flag rows with missing or clearly wrong data rather than guessing - Tell me any pattern you noticed that I should know about Give me back a clean version I can download, plus a short summary of what changed. Don't delete anything ambiguous. Put it in a separate "check these" list and let me decide.

Set this up as a recurring task every Friday afternoon. Ask me what happened this week, then give me: - SHIPPED — what actually got finished - SLIPPED — what didn't, and whether it still matters - WAITING — what's sitting with someone else, and who needs chasing - MONDAY — the three things to start with Keep it to one screen. Be honest about the slipped items — if something has moved three weeks running, say so and ask whether it's actually happening. End with one line about what went well. I'm bad at noticing that.