5 AI shortcuts for freelancers and creatives
Five client emails freelancers dread, each with a prompt you can copy into any AI chat. Fill in the blanks and check every line before you send.
Tap a message to open it.
1Chase an overdue invoice politelyTested
Use it when the work is delivered, the amount isn't in dispute and the due date has passed. Don't use this when the client disputes the work or the amount, or when the debt is already with a collections agency or a lawyer.
Don't paste card or bank numbers, passwords, or health, legal or other private details about anyone.
I'm a freelance [designer / writer / photographer / developer]. A client hasn't paid my invoice. Client: [name]. Invoice: [number and date]. Amount: [amount]. Due: [date]. Work delivered: [short description, date delivered]. Reminders so far: [none / dates]. My payment terms: [in your words]. Write a friendly, firm reminder. If I've already sent one, make it firmer and ask for a payment date. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - No legal threats. No late fees or interest unless they are in terms the client agreed to and I listed them. - Don't promise any next step, reply, call or help I didn't list. - If a fact says "not sure" or "not decided yet", write UNCLEAR there instead of working it out. - Don't offer to check, look into or fix anything on my side.
Check before you send
- Invoice number, amount and dates are right.
- Only the terms you really agreed on.
- No legal threats, and any fee or interest is in terms the client saw and agreed to.
- Talk to a professional before any collections or legal step.
Tested once on October 27, 2026 with made-up facts: GPT-6.1 Sol (via Codex) and Claude Sonnet 5.5 (via Claude Code) both followed the rules. One run is not proof, so still check.
See the test: what we pasted and what each model wrote
How we tested: we filled the blanks with made-up facts and ran the prompt once on OpenAI's GPT-6.1 Sol through the Codex command-line tool and once on Anthropic's Claude Sonnet 5.5 through Claude Code, with no other instructions. A separate GPT-6.1 Sol run with no tools judged both answers against the prompt's rules and the checks. The ChatGPT and Claude chat apps can use different models and settings, so your answers may differ.
It uses the supplied facts, marks the due date UNCLEAR, and asks for a payment date without adding promises or fees.
The email preserves the supplied facts, marks the due date UNCLEAR, and requests a payment date without adding prohibited commitments.
What we pasted (made-up facts):
I'm a freelance designer. A client hasn't paid my invoice. Client: Harbor Lane Bakery (contact: Ellen). Invoice: Invoice #1042, dated May 1, 2030. Amount: $850. Due: not sure. Work delivered: logo and brand colors, delivered April 28, 2030. Reminders so far: one reminder on May 20, 2030. My payment terms: Payment within 14 days of the invoice by bank transfer. I don't start new work until earlier invoices are paid.. Write a friendly, firm reminder. If I've already sent one, make it firmer and ask for a payment date. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - No legal threats. No late fees or interest unless they are in terms the client agreed to and I listed them. - Don't promise any next step, reply, call or help I didn't list. - If a fact says "not sure" or "not decided yet", write UNCLEAR there instead of working it out. - Don't offer to check, look into or fix anything on my side.
What GPT-6.1 Sol wrote (exact words, formatting adapted):
Subject: Payment reminder — Invoice #1042
Hi Ellen,
I’m following up on my May 20, 2030 reminder about Invoice #1042, dated May 1, 2030, for $850 for the logo and brand colors delivered April 28, 2030.
Payment remains outstanding. My payment terms are payment within 14 days of the invoice by bank transfer. Invoice due date: UNCLEAR.
Please confirm the date you will make payment. I don’t start new work until earlier invoices are paid.
Thank you,
[Your name — UNCLEAR]
What Claude Sonnet 5.5 wrote (exact words, formatting adapted):
Subject: Invoice #1042 – payment date needed
Hi Ellen,
I'm following up on Invoice #1042 for $850, dated May 1, 2030, for the logo and brand colors delivered on April 28, 2030. I sent a reminder on May 20, 2030, and the invoice is still unpaid.
My payment terms are payment within 14 days of the invoice by bank transfer. The due date for this invoice is UNCLEAR.
Please reply with the date you will make the payment.
I also don't start new work until earlier invoices are paid, so this invoice needs to be settled before any new project begins.
Thank you,
[Your name: UNCLEAR]
Notes for you (not part of the email):
- Due date: UNCLEAR. You said you're not sure, so I didn't calculate it from the 14-day terms. If you confirm it, replace the UNCLEAR in that sentence with the date.
- Your name: you didn't give the name to sign with.
- Bank details: you didn't provide any, so none are included. Add them if Ellen needs them.
- Dates: the invoice dates (2030) are later than today's date (October 27, 2026). I used them exactly as you gave them, so check they're correct before sending.
- Late fees or interest: none included, since you didn't list any agreed terms for them.
Full step-by-step guide: Write payment reminder emails in three tones (friendly, firm, final)
2Say no to extra work that's outside the scopeTested
Use it when a client asks for more than you agreed to, and you want to quote it instead of doing it free. Skip this if your contract is unclear about scope; find the signed proposal or get the contract reviewed first.
Don't paste card or bank numbers, passwords, or health, legal or other private details about anyone.
I'm a freelance [designer / writer / photographer / developer]. A client asked for work outside what we agreed. What we agreed: [scope, from your proposal or contract]. What they asked for now: [the new request]. My price for the extra work: [amount or rate, or "need to work it out"]. Write a short, friendly reply that says what's included, what's extra, and how we can add it. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - Don't agree to the extra work for free. Don't sound annoyed. - Don't promise any next step, reply, call or help I didn't list. - Don't guess numbers or details of the new request; ask the client instead.
Check before you send
- The scope matches your proposal or contract.
- The price for extra work is yours.
- Friendly, not defensive.
Tested once on October 27, 2026 with made-up facts: GPT-6.1 Sol (via Codex) and Claude Sonnet 5.5 (via Claude Code) both followed the rules. One run is not proof, so still check.
See the test: what we pasted and what each model wrote
How we tested: we filled the blanks with made-up facts and ran the prompt once on OpenAI's GPT-6.1 Sol through the Codex command-line tool and once on Anthropic's Claude Sonnet 5.5 through Claude Code, with no other instructions. A separate GPT-6.1 Sol run with no tools judged both answers against the prompt's rules and the checks. The ChatGPT and Claude chat apps can use different models and settings, so your answers may differ.
It states the agreed scope, asks for missing email details, and marks the price as UNCLEAR without inventing terms.
It separates included and extra work, flags the unknown price and process, and asks for missing details without committing to unlisted next steps.
What we pasted (made-up facts):
I'm a freelance writer. A client asked for work outside what we agreed. What we agreed: Four 800-word blog posts for June, with one round of edits each. What they asked for now: They now want me to also write the newsletter emails that promote each post. My price for the extra work: need to work it out. Write a short, friendly reply that says what's included, what's extra, and how we can add it. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - Don't agree to the extra work for free. Don't sound annoyed. - Don't promise any next step, reply, call or help I didn't list. - Don't guess numbers or details of the new request; ask the client instead.
What GPT-6.1 Sol wrote (exact words, formatting adapted):
Hi! Our agreement covers four 800-word blog posts for June, with one round of edits each. The newsletter emails would be extra work.
Could you confirm how many emails you need and what each should include? We can add them once we agree on the scope and price (UNCLEAR—still to be worked out).
What Claude Sonnet 5.5 wrote (exact words, formatting adapted):
Draft reply (not sent)
Subject: Newsletter emails for the June posts
Hi [Client name],
Thanks for asking about the newsletter emails. I'd be glad to help with those.
Included in our current agreement:
- Four 800-word blog posts for June
- One round of edits on each post
Extra:
- The newsletter emails promoting each post. They weren't part of the original scope, so they would be added as separate work with their own price.
- Price: UNCLEAR
To add them, could you tell me:
- How many emails you'd like per post?
- Roughly how long each email should be?
- Whether you'd like edits on the emails, and how many rounds?
- When you'd need them by?
Once the details and price are agreed, we can add the emails to the project. UNCLEAR: how you want to formalize this (e.g., written confirmation, updated agreement).
Thanks,
[Your name]
Notes for you:
- Price: You said you still need to work it out, so I left it as UNCLEAR rather than guessing. Fill it in before sending, or send as is.
- Process: You didn't tell me how extras are normally added, so I kept that vague and flagged it.
- No promises: I didn't commit to a quote date, a call, or a follow-up, since you didn't list any.
- Questions to the client: The number, length, edit rounds, and deadline for the emails are all unknown, so I asked rather than assumed. Cut any you don't need.
Full step-by-step guide: Turn a phone or walk-in inquiry into a written quote draft
3Follow up on a proposal that went quietTested
Use it a week after you send a proposal with no reply. One clear nudge. Skip this if they said no or asked you to stop, or if you're emailing someone who never asked for a proposal.
Don't paste card or bank numbers, passwords, or health, legal or other private details about anyone.
I'm a freelance [designer / writer / photographer / developer]. I sent a proposal and haven't heard back. Client: [name]. Project: [short description]. Sent: [date]. Price: [amount]. Anything real that affects timing: [your availability or start date, or "none"]. Write one short, friendly follow-up email that makes it easy to say yes, no or not now. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - No fake urgency or discounts. Keep it under 100 words. - End the email with these two lines: [your business postal address] and [how to unsubscribe].
Check before you send
- Price and dates match your proposal.
- Any timing note is true.
- It's easy for them to say no.
- If it mainly sells your service, treat it as marketing: honest subject line, your postal address, a way to opt out, and nobody who asked you to stop.
Tested once on October 27, 2026 with made-up facts: GPT-6.1 Sol (via Codex) and Claude Sonnet 5.5 (via Claude Code) both followed the rules. One run is not proof, so still check.
See the test: what we pasted and what each model wrote
How we tested: we filled the blanks with made-up facts and ran the prompt once on OpenAI's GPT-6.1 Sol through the Codex command-line tool and once on Anthropic's Claude Sonnet 5.5 through Claude Code, with no other instructions. A separate GPT-6.1 Sol run with no tools judged both answers against the prompt's rules and the checks. The ChatGPT and Claude chat apps can use different models and settings, so your answers may differ.
It uses the supplied facts, welcomes yes, no or not now, and copies the required footer exactly.
The email stays under 100 words, uses the supplied facts and footer, and leaves missing details for the owner.
What we pasted (made-up facts):
I'm a freelance photographer. I sent a proposal and haven't heard back. Client: Jordan at Pine Street Dental. Project: Team headshots for 8 staff, plus 10 office photos for their website. Sent: Monday, June 3, 2030. Price: $1,400. Anything real that affects timing: I have two open shoot days left in July. Write one short, friendly follow-up email that makes it easy to say yes, no or not now. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - No fake urgency or discounts. Keep it under 100 words. - End the email with these two lines: "Riverside Studio, 14 Mill Road, Riverside, CA 92501" and "To stop getting these emails, use the unsubscribe link below.".
What GPT-6.1 Sol wrote (exact words, formatting adapted):
Hi Jordan,
Just following up on the $1,400 proposal I sent June 3 for Pine Street Dental’s team headshots for 8 staff and 10 office photos for your website.
I have two open shoot days left in July. Would you like to move forward? A quick “yes,” “no,” or “not now” is welcome—whatever works for you.
Thanks!
Riverside Studio, 14 Mill Road, Riverside, CA 92501
To stop getting these emails, use the unsubscribe link below.
What Claude Sonnet 5.5 wrote (exact words, formatting adapted):
Subject: Following up: Pine Street Dental photos
Hi Jordan,
I'm following up on the proposal I sent Monday, June 3: headshots for 8 staff plus 10 office photos for your website, $1,400.
I have two open shoot days left in July. If you'd like to go ahead, reply "yes" and we'll pick a day. If it's a no or not now, just tell me. Either answer is fine.
Thanks,
[Your name: UNCLEAR]
Riverside Studio, 14 Mill Road, Riverside, CA 92501
To stop getting these emails, use the unsubscribe link below.
Flags:
- Your name/sign-off: UNCLEAR
- Specific July dates: UNCLEAR, so I didn't name any
- Jordan's email address: UNCLEAR
- The year of the July shoot days: UNCLEAR. The proposal date is 2030, but today's date on my end is October 2026, so please check the dates.
- The unsubscribe link itself isn't included. Your email tool needs to add it below the final line.
Full step-by-step guide: Write a polite follow-up email when someone hasn't replied
4Reply to vague or harsh feedback on your workTested
Use it when a client's feedback is unclear or upsetting and you need a calm reply that gets clear next steps. Don't use this when the client threatens legal action or refuses to pay; talk to a professional first.
Don't paste card or bank numbers, passwords, or health, legal or other private details about anyone.
I'm a freelance [designer / writer / photographer / developer]. A client sent feedback on my work that's vague or harsh. Their feedback: [paste it]. What we agreed: [the brief, and how many revision rounds are left]. What I think they want: [your best guess, or "not sure"]. Write a calm, professional reply that thanks them, asks two or three questions to make the changes clear, and says how many revision rounds are left. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - Don't argue or get defensive. Don't promise extra rounds I didn't offer. - Don't promise any next step, reply, call or help I didn't list. - Don't say how or when the revision rounds will be used.
Check before you send
- Revision rounds left is right.
- The questions would really make the changes clear.
- Calm, even if the feedback stung.
Tested once on October 27, 2026 with made-up facts: GPT-6.1 Sol (via Codex) and Claude Sonnet 5.5 (via Claude Code) both followed the rules. One run is not proof, so still check.
See the test: what we pasted and what each model wrote
How we tested: we filled the blanks with made-up facts and ran the prompt once on OpenAI's GPT-6.1 Sol through the Codex command-line tool and once on Anthropic's Claude Sonnet 5.5 through Claude Code, with no other instructions. A separate GPT-6.1 Sol run with no tools judged both answers against the prompt's rules and the checks. The ChatGPT and Claude chat apps can use different models and settings, so your answers may differ.
It asks three clarifying questions, marks unknowns UNCLEAR, and correctly states that two revision rounds remain.
It asks three clarifying questions, identifies unknowns in owner notes, and correctly states that neither revision round has been used.
What we pasted (made-up facts):
I'm a freelance developer. A client sent feedback on my work that's vague or harsh. Their feedback: "This doesn't feel right. It's kind of clunky. Can you make it better?". What we agreed: A 5-page website for a florist, built from their approved design; 2 revision rounds included, none used yet. What I think they want: not sure. Write a calm, professional reply that thanks them, asks two or three questions to make the changes clear, and says how many revision rounds are left. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - Don't argue or get defensive. Don't promise extra rounds I didn't offer. - Don't promise any next step, reply, call or help I didn't list. - Don't say how or when the revision rounds will be used.
What GPT-6.1 Sol wrote (exact words, formatting adapted):
Thanks for sharing your feedback. I’d appreciate a little more detail so I can understand what feels off:
- Which pages or elements don’t feel right? UNCLEAR
- What feels clunky—for example, the layout or navigation? UNCLEAR
- What would you like to look or work differently? UNCLEAR
Both of the 2 included revision rounds remain.
What Claude Sonnet 5.5 wrote (exact words, formatting adapted):
Subject: Your feedback on the website
Hi [Client name],
Thank you for taking the time to review the site and share your feedback. I want to make sure the changes I make are the right ones, so I have a few questions:
- What feels "not right"? Is it the overall look, the colors, the layout, the text, or something else? If you can point to a specific page or section, that would help.
- What feels "clunky"? For example, is it how the pages load, how you move between pages, how the menu works, or how it looks on a phone or tablet?
- What would "better" look like to you? If there's a site you like, or a particular change you have in mind, please share it. You can also point out anything that differs from the approved design.
Your agreement includes 2 revision rounds, and neither has been used yet.
Best regards,
[Your name]
Notes for you:
- UNCLEAR: What the client actually wants. I wrote the questions to narrow this down without assuming.
- UNCLEAR: Whether the feedback counts as a revision round. You didn't say, so I left it out of the email, other than stating that none have been used yet.
- UNCLEAR: Client name and your name. Placeholders are in brackets.
- I didn't promise a reply time, a call, or any next step, and I didn't say how or when the revision rounds will be used.
Full step-by-step guide: Write a calm, firm reply to an angry customer email
5Confirm what you agreed after a client callTested
Use it right after a call, so you both have the same plan in writing. Don't use this when you need a final contract, or when the work is in a dispute that may go to a lawyer; write that record yourself.
Don't paste card or bank numbers, passwords, or health, legal or other private details about anyone.
I'm a freelance [designer / writer / photographer / developer]. I just had a call with a client and want to confirm what we agreed. My notes: [what's included, deadlines, price, who does what]. Next step: [what happens next and when]. Write a short recap email with what we agreed, the deadlines and the next step, and ask them to reply if anything is wrong. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - Don't add anything that isn't in my notes.
Check before you send
- Every item is from your notes.
- Deadlines and price are right.
- It asks them to correct anything wrong.
Tested once on October 27, 2026 with made-up facts: GPT-6.1 Sol (via Codex) and Claude Sonnet 5.5 (via Claude Code) both followed the rules. One run is not proof, so still check.
See the test: what we pasted and what each model wrote
How we tested: we filled the blanks with made-up facts and ran the prompt once on OpenAI's GPT-6.1 Sol through the Codex command-line tool and once on Anthropic's Claude Sonnet 5.5 through Claude Code, with no other instructions. A separate GPT-6.1 Sol run with no tools judged both answers against the prompt's rules and the checks. The ChatGPT and Claude chat apps can use different models and settings, so your answers may differ.
It accurately recaps the supplied terms and next step and asks the client to correct anything wrong.
It preserves the supplied terms, correctly calculates the half deposit, marks missing due dates UNCLEAR, and requests corrections.
What we pasted (made-up facts):
I'm a freelance designer. I just had a call with a client and want to confirm what we agreed. My notes: Brochure, 8 pages, print-ready PDF. First draft by Friday, July 12, 2030. Final files by Friday, July 26. Price $1,100, half up front. The client sends all photos and text by Monday, July 8. Two revision rounds.. Next step: I send the deposit invoice today; work starts when the deposit and the photos arrive. Write a short recap email with what we agreed, the deadlines and the next step, and ask them to reply if anything is wrong. Rules: - Use only the facts I give you. Don't send anything. - Don't invent prices, fees, dates, policies or promises. - If anything is missing or unclear, write UNCLEAR next to it. - Don't add anything that isn't in my notes.
What GPT-6.1 Sol wrote (exact words, formatting adapted):
Subject: Brochure project recap
Here’s a recap of what we agreed:
- Deliverable: 8-page brochure as a print-ready PDF.
- Price: $1,100, half up front.
- Photos and text: You’ll send everything by Monday, July 8.
- First draft: Friday, July 12, 2030.
- Final files: Friday, July 26.
- Revisions: Two rounds.
I’ll send the deposit invoice today. Work starts when the deposit and photos arrive.
Please reply if anything is wrong.
What Claude Sonnet 5.5 wrote (exact words, formatting adapted):
Subject: Recap of our call: 8-page brochure
Hi [Client name],
Thanks for the call. Here's what we agreed:
Project
- 8-page brochure, delivered as a print-ready PDF
- Two revision rounds
Price
- $1,100 total, half ($550) up front
- Balance due date: UNCLEAR
Deadlines
- Monday, July 8, 2030: you send me all photos and text
- Friday, July 12, 2030: first draft from me
- Friday, July 26, 2030: final files from me
Next step
- I'm sending the deposit invoice today. Deposit due date: UNCLEAR
- I'll start work once I have both the deposit and your photos.
Please reply if anything here is wrong or missing.
Best,
[Your name]
Notes for you (not part of the email):
- The $550 is just half of $1,100. Delete it if you'd rather not state it.
- The UNCLEAR items are the balance due date and the deposit due date. Fill them in or remove those lines before sending.
- The weekdays match the 2030 dates you gave, so I kept them as written.
Full step-by-step guide: Turn a long phone call into a written recap for the customer
More: questions, earlier tests and how we test
Questions freelancers and small creative studios ask
Can I use ChatGPT to chase unpaid invoices?
Yes, as a draft. Give it the invoice facts and your terms, check every number, and send it yourself.
How do I handle scope creep without losing the client?
Say clearly what was agreed and what the new request costs, in a friendly tone. The scope shortcut above drafts that email.
Is it OK to paste client contracts into AI?
Paste only the lines you need, and leave out anything confidential. For what a contract means, ask a lawyer.
Also as plain Markdown for AI tools.
The Tuesday email
One ready-to-copy shortcut, every Tuesday.
Every Tuesday: one AI shortcut for a message owners put off, right in the email. Copy it, fill the blanks, check it, send. Read it in a minute. Your first week starts with three short welcome emails.
Free. Every Tuesday: one ready-to-copy AI shortcut for a message owners put off, in the email itself. At most one ad, always labeled. Unsubscribe in one click.