DEV Community: Kitwise Studio

How to send polite late-invoice reminders (with a free late-fee check)

Kitwise Studio — Sat, 31 Oct 2026 08:24:44 +0000

Late invoices are normal. What burns the relationship is either silence or a sudden angry email. A better default is a short, staged reminder cadence: same facts every time, tone that steps up only as days pile up, and numbers you can prove.

This is the workflow we use in Kitwise Studio's free Invoice Chaser sample. Full write-up, downloads, and a worked Claude run live on the Invoice Chaser late-fee guide.

1. Collect the facts before you write

You need:

Invoice number, amount, issue date, due date
Client name and what you delivered
Payment terms (especially any late-fee clause). If the contract never said a late fee, do not invent one in the email
Reminders already sent and any replies
Today's date and a payment link (or a clear "reply with how you want to pay" line)

2. Pick a stage from days overdue (and never go backwards)

A simple convention (not a legal rule):

Stage	Rough window	Tone
1 Friendly	1-7 days late	Assume the invoice got lost
2 Firm	8-21 days	Clear ask + a date
3 Final notice	22-44 days	Spell out next step you will actually take
4 Escalate	45+ days	Pause work / formal demand / collections (only if you mean it)

If you already sent stages 1 and 2, do not send "friendly" again just because you restarted the thread. Move forward only.

3. Check the late fee offline (optional, only if your terms allow it)

If your contract states a monthly rate on overdue balances, you can verify the fee with a small Python 3 script (standard library only, no API key, no network). Formula: simple interest, no compounding:

amount × monthly_rate × 12 / 365 × days_overdue

Example (made-up invoice):

python3 late_fee.py --amount 2400 --due 2026-09-15 --today 2026-10-16 --monthly-rate 0.015

Expected for that input: 31 days overdue, late fee $36.69, total $2,436.69, stage 3. The free sample ships late_fee.py, run-script.sh, and expected-script-output.json so you can run bash run-script.sh and get a PASS when the math matches.

If your terms state no late fee, run with --monthly-rate 0 and leave fees out of the email.

4. Draft the email: short, exact, one ask

Keep it under about 150 words. Every draft should include:

Subject with invoice number
Amount and original due date
Days overdue (and late fee only if terms allow)
Payment link or clear next action
One ask with a date ("please confirm payment by Friday")

Tone by stage:

Friendly: "Just checking this landed. Happy to resend the PDF."
Firm: "Still open on my side. Can you confirm a payment date this week?"
Final notice: State the real next step you will take (pause new work, formal letter, etc.). Do not threaten something you will not do.
Escalate: General options only; this is not legal advice and depends on your contract and jurisdiction.

Read every draft before you send it. A drafting helper can write the first pass. You own the send.

5. Put the next reminders on a calendar

Default spacing that works for many solo freelancers: +7, +14, +21 days from today, each at the next stage. When the client replies "we'll pay next week," write the date back. If they ask for installments, offer a short 2-3 part plan with dates instead of a vague "whenever."

Free workflow files

Download the free Invoice Chaser sample (MIT): SKILL.md, late_fee.py, run-script.sh, and the expected JSON. The longer guide (linked at the top) walks through a full Claude.ai run on a made-up packaging invoice, including the status line and follow-up schedule.

Optional related product (list price only)

If you also want fillable invoice and quote PDFs with an invoice log for days overdue, Kitwise's Invoice & Quote Set is $9.99. Not required for the free late-fee check.

I built a Claude skill that flags scope creep before you reply to a client

Kitwise Studio — Fri, 23 Oct 2026 07:33:09 +0000

If you freelance, you know the message: one friendly paragraph that quietly contains four new requests. The easy reply is "sure, no problem". The expensive part is that you answered before checking the message against what you actually agreed.

I wrote a Claude skill that does the checking first. It splits the message into separate asks, compares each one to your scope, and drafts a reply with prices before you say anything.

What a Claude skill is

A skill is a folder with a SKILL.md file. The top of the file tells Claude when to use it, and the body tells Claude how to do the job. You upload the folder in Claude's settings and it kicks in when your message matches the description. No code is needed for the skill itself.

The skill

This is the core of mine, trimmed a bit. The full version also has a rubric file, reply templates and a small pricing script.

---
name: scope-creep-guard
description: "Checks a client message against the agreed project scope, flags out-of-scope or ambiguous requests, and drafts a friendly change-order reply with pricing and schedule impact. Use when a freelancer pastes a client email or Slack message and asks \"is this in scope?\" or \"how do I say no / charge for this?\""
---

# Scope-Creep Guard

You protect the freelancer's time and the client relationship at the same time.
You never accuse the client; you make the scope visible and give them easy options.

## Inputs
1. The agreed scope (proposal, contract excerpt or bullet list: deliverables,
   revision rounds, exclusions). If missing, ask once. If the user can't provide
   it, mark the verdict "provisional".
2. The client's new message, pasted as-is.
3. The rate and the current deadline.

## Workflow
1. Split the client message into individual asks, one line each. Clients often
   bury 2-3 asks in one message.
2. Classify every ask:
   - IN SCOPE: explicitly covered (cite the scope line).
   - REVISION: a change to an existing deliverable inside the remaining rounds.
   - OUT OF SCOPE: new deliverable, extra round past the limit, or listed under exclusions.
   - AMBIGUOUS: scope is silent. Recommend a clarifying question, never assume.
3. Estimate hours for each out-of-scope item and price them.
4. Draft the reply: say yes to what is in scope, then offer options for the rest:
   (a) add it as a change order at $X and +N days,
   (b) swap it for something of similar size,
   (c) park it for phase 2.

## Rules
- Quote the scope. Never invent contract terms. If the contract is silent, say so.
- Never start out-of-scope work before written approval.
- Put the revision math in the client reply itself, not only in the table.
- This is business communication help, not legal advice.

Two details in there matter more than they look:

"Split into individual asks." Without this step Claude tends to judge the whole message as one thing. Splitting is what catches the third and fourth request hiding after "oh and".
"Put the revision math in the client reply itself." In an earlier dry run of the same example, the scope table was right but the drafted reply never told the client that her revision rounds were used up, so the one-time courtesy had no context. Adding this rule fixed it. In the real Claude run below, the reply opens with the revision math.

A test run

I ran it on a free Claude.ai account with the skill uploaded. Nothing was edited except the chat formatting, which I turned back into plain text. This is one run, and yours will be worded differently.

The setup was a made-up web design project. Agreed scope: 6 pages, a booking embed, polish of existing copy, 2 revision rounds per deliverable, no new copywriting, $75 an hour. The home design was already approved with both rounds used.

The client message:

Hi Sam! Loving it so far. A few things: can you make the hero button orange instead of purple? Also I'd love our Instagram feed on the homepage. And we're launching Pilates in January, could you add a page for that too? Oh and the teachers page text, can you write bios for our 8 teachers? Thanks!!

The skill's scope check:

Ask	Verdict	Why	Hours	Price
Hero button purple to orange	Out of scope (tiny, so a goodwill candidate)	Home design approved, 2 of 2 rounds used	~0.25	$0 if goodwill
Instagram feed on homepage	Out of scope	New integration, not in the 6 pages or the booking embed	2	$150
New Pilates page	Out of scope	The scope fixes 6 pages, so this is a 7th	8	$600
Write bios for 8 teachers	Out of scope	"Not included: new copywriting"	4 to 6	Quote separately

The reply it drafted:

Hi [Client name],

So glad you're loving it! The home design was approved on Nov 14 with both revision rounds used, so changes to it now count as extra. I'm happy to switch the hero button to orange as a one-time courtesy.

The other three fall outside our original 6-page plan, so here are the options:

Instagram feed on the homepage: $150

Pilates page (same layout as Classes): $600

Together that's $750 and adds about 2 days. We'd still launch Dec 15 if you confirm by Nov 25.

For the teacher bios, new copywriting isn't part of the project. If you send me a few lines per teacher, I'll polish them. Or I can quote writing all 8 from scratch. If you'd rather keep the budget fixed, we could also park the Pilates page for after launch.

Reply "approved" for the feed and/or Pilates page and I'll get started.

Sam

Compared with the default "sure, happy to!", this reply says yes to the small thing, puts a price and a date on the big things, and gives the client three ways forward. Nobody is accused of anything.

It also added a note for me that I would have missed: the Pilates page launches in January, so it does not have to ship before the December deadline, and parking it may suit the client better.

What it gets wrong

The hour estimates are Claude's guesses. It said so itself and told me to adjust them, especially if the Instagram feed needs a paid widget or API setup. Check them against your own speed.
It only knows the scope you give it. If your contract is vague, you get "provisional" verdicts, which is the honest answer.
It does not read your contract for legal meaning. For large disputes, talk to someone qualified.

Try the idea without the skill

You do not need the full skill to get most of the value. Paste your scope and the client message into any chat and ask for three things: split the message into separate asks, mark each one as in scope, revision, out of scope or unclear with the scope line that proves it, and draft a reply that offers a change order, a swap or a later phase. The order matters: classify first, reply second.

I put a free set of 10 prompts for freelancers together here, in case it is useful: https://kitwisestudio.com/free?utm_source=devto&utm_medium=article&utm_campaign=skill-post

I sell a small pack of Claude skills under Kitwise Studio, this one is from it.

What do you do when a client message has a "quick extra" hiding in it? I would like to hear how others handle the reply.

How to Calculate Your Freelance Rate (Formula + Worked Example)

Kitwise Studio — Fri, 16 Oct 2026 12:23:25 +0000

Most freelancers pick a rate by looking at what others charge, then wonder why they're busy but broke. Here's a better way: work backwards from the life you need to fund, and let the maths tell you your minimum.

Why "market rate" is the wrong starting point

Looking at other freelancers' rates tells you what the market will tolerate. It doesn't tell you what you need. Two designers charging $60 an hour can have completely different outcomes: one lives somewhere cheap, works 35 billable hours a week and has no software costs; the other pays for a studio, an Adobe subscription and health insurance, and spends half the week on admin and sales. Same rate, very different businesses.

So start with your own numbers. Once you know your floor – the rate below which you're effectively paying to work – you can look at the market to decide how far above that floor you can price.

The freelance rate formula

Here's the whole thing in one line:

Minimum hourly rate = (Take-home income goal + Business expenses) ÷ (1 − Tax rate) × (1 + Profit buffer) ÷ Billable hours per year

Each part does a specific job:

Take-home income goal – what you want to pay yourself for the year, after tax. Think of it as your salary.
Business expenses – everything the business pays for: software, hardware, insurance, accounting, coworking, training, website, bank fees.
Tax rate – a realistic blended estimate of income tax plus self-employment or social contributions. Dividing by (1 − tax) "grosses up" your number so the tax comes out of revenue, not your salary.
Profit buffer – a margin for slow months, late payers, equipment that dies and future growth. Employees have an employer absorbing this risk; you don't.
Billable hours – the hours you can actually invoice for. This is where most people get it badly wrong.

Step 1: Set your income goal

Add up your real yearly personal costs – rent, food, transport, debt, family, holidays – then add what you want to save or invest. Don't use a wishful number and don't use a guilty number. If you were previously employed, your old net salary is a sensible baseline, but remember that freelancing usually removes perks like paid leave, pension contributions and equipment.

Step 2: List your business expenses

Go through your bank statements for the last few months and pull out anything business-related. Annualise subscriptions (a $25/month tool is $300 a year). Include things you'll need to replace: if your laptop costs $1,800 and lasts three years, that's $600 a year. If you track income and expenses as you go, this step takes five minutes instead of an afternoon.

Step 3: Estimate tax honestly

Tax rules vary by country, so check with a local accountant, but a blended rate between 20% and 35% is typical for many freelancers once social or self-employment contributions are included. If you're unsure, err slightly high. Over-saving for tax is a pleasant surprise; under-saving is a crisis in April.

Step 4: Count your real billable hours

A year has 52 weeks, but you won't work all of them. Subtract public holidays, vacation and a few sick days – six weeks off is a reasonable starting assumption. Then accept that not every working hour is billable. Emails, proposals, invoicing, marketing, bookkeeping, learning and finding the next client all take time. Many freelancers bill 50–70% of their working hours; newer freelancers who are still building a pipeline are often at the lower end.

A worked example

Let's run the numbers for Maya, a freelance web designer.

Input	Value
Take-home income goal	$60,000
Business expenses (software, laptop, insurance, accountant, coworking)	$6,000
Blended tax rate	25%
Profit buffer	10%
Weeks off (holidays, vacation, sick)	6
Hours worked per week	40
Billable share of time	60%

1. Cover income and costs: $60,000 + $6,000 = $66,000.

2. Gross up for tax: $66,000 ÷ (1 − 0.25) = $66,000 ÷ 0.75 = $88,000.

3. Add the profit buffer: $88,000 × 1.10 = $96,800 revenue target for the year.

4. Work out billable hours: 52 − 6 = 46 working weeks. 46 × 40 = 1,840 working hours. 1,840 × 0.60 = 1,104 billable hours.

5. Divide: $96,800 ÷ 1,104 = $87.68 per hour.

That's Maya's floor. She rounds up to $90/hour. Notice what would have happened if she'd assumed every working hour was billable: $96,800 ÷ 1,840 = $52.61. Charging that, she'd fall almost $39,000 short of her target. The billable-hours assumption is the single biggest lever in the whole calculation.

Turning the hourly rate into day and project prices

Clients often prefer day rates or fixed prices, and so should you – they reward you for getting faster. From the same number:

Day rate: $90 × 7 billable hours = $630/day.
Monthly revenue target: $96,800 ÷ 12 ≈ $8,067. Weekly, across 46 working weeks: ≈ $2,104.
Project price: a landing page estimated at 20 hours, plus a 15% buffer for revisions and back-and-forth = 23 hours × $90 = $2,070. Add a rush fee (say 25%) if the deadline forces you to clear your calendar.

If you'd rather not rebuild this spreadsheet yourself, the Freelance Rate Calculator does exactly this: you enter your goal, expenses, tax estimate, time off and billable percentage, and it gives you minimum and recommended hourly rates, a day rate, revenue targets and a project & retainer pricing sheet with revision buffers and rush fees built in.

Sanity-check against the market

Now look outward. Compare your floor to rates in your niche, region and experience level. Three scenarios:

Your floor is below the market: great – price at market or above it. Your minimum is not your price.
Your floor is close to the market: fine, but find ways to justify a premium: specialisation, faster turnaround, a clear process.
Your floor is well above the market: don't simply drop your rate. Look at the inputs. Can you raise billable hours by systemising admin? Cut expenses? Move to a niche with higher budgets? Package work into fixed-price offers?

Common mistakes to avoid

Forgetting unpaid time. Sales, admin and learning are real work. Price them into your billable hours, not your evenings.
Ignoring late payments. Your buffer exists partly because clients pay late. Clear payment terms on every invoice help a lot.
Never revisiting the rate. Recalculate at least once a year, and whenever your expenses or availability change.
Discounting by default. If you discount, trade it for something: a larger scope, upfront payment or a longer commitment.

Put your rate on paper

A rate only matters once it appears on a quote and an invoice. Quote fixed-price projects with a clear scope, a deposit and a "valid until" date, then invoice with your payment terms spelled out. The Invoice & Quote Template Set handles the totals, tax, discounts and balance due for you, so your new rate goes out looking professional from day one.

FAQ

How much should a beginner freelancer charge?

Run the same formula. Beginners usually have a lower billable percentage (more time spent finding clients), which pushes the floor up, not down. Price at or slightly above your floor and raise rates as your portfolio grows.

Should I charge hourly or per project?

Use your hourly rate as an internal measure, but quote per project or per day where you can. Fixed prices reward efficiency and are easier for clients to approve. Track your actual hours to check your estimates.

What billable percentage should I use?

If you don't know, start with 60%. Track your time for a month to find your real number – many people are surprised how low it is.

How often should I raise my rates?

Review once a year at minimum. Raise rates for new clients first, and give existing clients 30–60 days' notice.

Does this work for retainers?

Yes. Multiply your hourly rate by the hours included each month, then consider a small discount in exchange for a minimum three-month commitment and payment in advance.

Free Freelance Starter Kit: https://shop.kitwisestudio.com/l/freelance-starter-kit

24 ChatGPT Prompts for Freelancers (Fill-in-the-Blank Templates)

Kitwise Studio — Fri, 16 Oct 2026 12:22:24 +0000

Generic prompts produce generic answers. Freelancers need a clear role, task, context, rules and format – plus blanks you actually fill in. Here are 24 copy-paste ChatGPT prompts for freelancers that also work in Claude and Gemini.

If you want more AI kits for business owners and freelancers after this guide, start at the AI kits hub.

The 5-part prompt structure

Every prompt below uses the same five parts. Learn them once and you can adapt any prompt without a blank chat box.

Role – who the AI should act as.
Task – the concrete job.
Context – facts only you know (notes, prices, voice sample).
Rules – length, tone, what not to invent.
Format – how the answer should be laid out.

Fill every [BLANK] before you run the prompt.

Give AI your context once: the Context Card

Keep a short Context Card for new threads, ChatGPT custom instructions, a Claude Project, or a Gemini Gem:

Context Card template

I'm a freelance [ROLE] helping [IDEAL CLIENT] with [SERVICES]. Typical project size: [RANGE]. Tone: [PLAIN / WARM / DIRECT]. I never promise [THINGS YOU DON'T PROMISE]. Words I avoid: [LIST]. Proof points I can cite: [2–3 REAL RESULTS].

Update it when your offer or rates change.

Blanks, "use when" lines and why they speed things up

Each prompt has a one-line Use when and [BLANKS] so you know what to add. That beats a wall of vague prompts you never reopen.

AI output can contain mistakes – review every draft, match your voice, and never paste confidential client data without permission. Kitwise Studio is not affiliated with OpenAI, Anthropic or Google. Contract, tax and money prompts are drafting help only – not legal, tax or financial advice.

Prompts for winning clients

Fill the blanks, then edit so it sounds like you.

1. Cold email / LinkedIn outreach

Use when: Reaching out to a business you want to work with.

Role: Senior freelance [YOUR ROLE] writing concise outreach.

Task: Cold email + LinkedIn note to [NAME], [THEIR ROLE] at [COMPANY].

Context: Noticed: [SPECIFIC OBSERVATION]. Offer: [SERVICE] for [RESULT]. Proof: [ONE RESULT OR CLIENT TYPE].

Rules: Email under 90 words; one question CTA; no flattery/links. LinkedIn note max 280 characters.

Format: Email, 3 subject lines (≤6 words), LinkedIn note.

2. Discovery call questions

Use when: First call booked; you want a sharp question list.

Role: Freelance [YOUR ROLE] preparing a discovery call.

Task: 12 questions for [CLIENT NAME], [INDUSTRY], interested in [SERVICE].

Context: Known so far: [NOTES]. Cover goals, situation, decision/budget, timeline, success metrics.

Rules: 2 polite budget questions; 1 on who else decides; star 5 must-asks for a short call.

Format: Numbered list under five headings; must-asks starred.

3. Qualifying a lead

Use when: Lead is interested; you want a clear fit check before a long proposal.

Role: Practical coach helping me qualify freelance leads.

Task: Qualification checklist + reply after [TOUCHPOINT: call / form / email].

Context: Ideal client: [PROFILE]. Red flags: [LIST]. Lead said: [PASTE MESSAGE OR NOTES].

Rules: If weak fit, say so and draft a polite decline. Don't invent budget numbers.

Format: Fit score (strong/maybe/weak) + reasons; 5 clarifying questions; short reply email.

Want freelancer-ready prompts? The AI Prompt Playbook has 105 prompts in 8 workflow areas plus an editable .xlsx/.csv library, Context Card, model tips and 4 worked examples.

Prompts for proposals and pricing

For a rate floor see how to calculate your freelance rate; for layout, the freelance proposal template.

4. Proposal from discovery notes

Use when: Call done; you need a full proposal draft fast.

Role: Senior freelance [YOUR ROLE] writing a client proposal.

Task: From my notes, draft: situation, outcome, 3–5 phase approach, deliverables, timeline, [NUMBER] packages, next steps.

Context: Notes: [PASTE]. Tone: [FORMAL / CONVERSATIONAL]. Max: [WORD COUNT].

Rules: Plain language; list unclear items first; don't invent prices I didn't give.

Format: Unclear items, then full proposal under headings.

5. Good / Better / Best packages

Use when: You're done sending one take-it-or-leave-it price.

Role: Pricing strategist for freelancers.

Task: Quote [CLIENT TYPE] for [PROJECT]; base [PRICE] for [CORE SCOPE]. Three packages; middle = preferred.

Context: Must include/exclude: [NOTES]. Timeline: [NOTES].

Rules: Top tier ~[1.6–2]× middle. Each: name, in/out, timeline, price. Then 2 sentences why middle fits.

Format: Three labelled packages + recommendation.

6. Reply to "that's too expensive"

Use when: Prospect likes the work but pushed on price.

Role: Calm freelance [YOUR ROLE] negotiating without undervaluing.

Task: Reply to [CLIENT NAME] on quote [PRICE] for [SCOPE].

Context: Can flex: [TIMELINE / SCOPE / PAYMENT]. Won't cut: [NON-NEGOTIABLES]. Alternatives: [PHASED / MVP / OTHER].

Rules: Acknowledge constraint; offer 2–3 options; no price apology; under 150 words. Drafting help only – not legal/financial advice.

Format: Email draft + which option best protects my rate.

Prompts for client communication

Always review before sending. More scripts: AI prompts for difficult client emails.

7. Scope creep reply

Use when: Client asked for something outside agreed scope.

Role: Professional freelance [YOUR ROLE] protecting scope without defensiveness.

Task: Short reply to [CLIENT NAME] about [NEW REQUEST].

Context: Agreed scope: [SCOPE]. SOW note: [CLAUSE]. Options: [CHANGE ORDER / SWAP / PHASE 2].

Rules: Acknowledge; state out of scope; clear next steps; under 120 words; no guilt language.

Format: Email draft ready to personalise.

8. Missed deadline or delay update

Use when: Something slipped (or will) and you need to tell them first.

Role: Trustworthy freelance [YOUR ROLE] owning a delay.

Task: Update [CLIENT NAME] about [WHAT'S DELAYED].

Context: Reason: [REASON]. New date: [NEW DATE]. Recovery: [ACTIONS]. Other milestones: [NONE / LIST].

Rules: Lead with the new date; no blame; under 100 words.

Format: Subject + body.

9. Late payment reminder

Use when: Invoice overdue; chase without burning the relationship.

Role: Polite but firm freelance business owner.

Task: Reminder for invoice [INVOICE #], [AMOUNT], due [DUE DATE], [DAYS] overdue.

Context: Client: [NAME]. Pay how: [DETAILS]. Tone: [FRIENDLY FIRST / FIRM SECOND].

Rules: Facts + amount + how to pay. Payment plan only if [YES/NO + TERMS]. Drafting help only – not legal advice. Under 90 words.

Format: Subject + body.

Prompts for onboarding

Use these once the deposit clears.

10. Welcome email

Use when: New client signed; need a clear kickoff message.

Role: Freelance [YOUR ROLE] onboarding a client.

Task: Welcome [CLIENT NAME] for [PROJECT NAME].

Context: Next 3 steps: [LIST]. Need from them by [DATE]: [LIST]. Hours/response: [BOUNDARIES]. Kickoff: [DATE OR TBA].

Rules: Warm but structured; bullet the asks; under 160 words.

Format: Subject + email with client action checklist.

11. Client intake questionnaire

Use when: Need a focused intake so you're not chasing details.

Role: Operations-minded freelance [YOUR ROLE].

Task: Intake questionnaire for [SERVICE / PROJECT TYPE].

Context: Cover: [GOALS, AUDIENCE, ASSETS, DEADLINES, BUDGET RANGE, BRAND, SUCCESS METRICS]. Extra: [TOPICS].

Rules: Max [NUMBER] questions; mark required; mix short answer and multiple choice.

Format: Numbered form ready to paste.

12. Kickoff agenda

Use when: Kickoff call coming; keep it on track.

Role: Project lead for a freelance [YOUR ROLE] engagement.

Task: [30/45/60]-minute agenda for [PROJECT] with [CLIENT NAME].

Context: Call goals: [GOALS]. Open questions: [LIST]. Decisions today: [LIST].

Rules: Time-box sections; close with owners/deadlines; 5 minutes for parking lot.

Format: Timed agenda with suggested owners.

Prompts for project delivery

Break work down, turn feedback into actions, hand over cleanly.

13. Task breakdown from a brief

Use when: Messy brief; need an actionable task list.

Role: Delivery-focused freelance [YOUR ROLE].

Task: Phased task list with estimates from: [PASTE BRIEF].

Context: Internal rate: [RATE]. Revision rounds: [NUMBER]. Constraints: [TOOLS / DEPENDENCIES].

Rules: Flag unclear requirements; rough hour ranges; don't invent scope.

Format: Phases → tasks → hours → open questions.

14. Feedback-to-action list

Use when: Pile of comments; need a clear revision plan.

Role: Project manager assisting freelance [YOUR ROLE].

Task: Turn feedback into actions: [PASTE FEEDBACK].

Context: Original scope: [SCOPE]. Deadline this round: [DATE].

Rules: Group must-fix / clarify / out of scope; suggest change-order wording where needed.

Format: Item, category, action, owner.

15. Handover summary

Use when: Project done; need a clean handover doc.

Role: Freelance [YOUR ROLE] writing a client handover.

Task: Handover for [PROJECT NAME] to [CLIENT NAME].

Context: Deliverables: [LIST]. Files/logins: [NOTES]. Maintain how: [CARE]. Out of support: [BOUNDARIES]. Support window: [IF ANY].

Rules: Clear headings; file checklist; optional next steps without hard sell.

Format: Delivered / Where it lives / How to use / Support / Optional next steps.

Prompts for marketing

Paste two or three sentences of your writing so the AI can match your voice.

16. Social post ideas from a project

Use when: Finished work you're proud of; need post angles.

Role: Content partner for freelance [YOUR ROLE].

Task: [NUMBER] post ideas from: [PROJECT SUMMARY / RESULT].

Context: Platforms: [LIST]. Audience: [WHO]. Voice sample: [PASTE 2–3 SENTENCES].

Rules: Each: hook, 2-sentence angle, CTA. No fake metrics or hashtag stuffing.

Format: Numbered ideas with hook / angle / CTA.

17. Portfolio entry

Use when: Need a tight portfolio write-up.

Role: Freelance [YOUR ROLE] writing a portfolio entry.

Task: Entry for [PROJECT] / [CLIENT TYPE OR INDUSTRY].

Context: Problem: [PROBLEM]. Approach: [WHAT I DID]. Result: [ONLY REAL NUMBERS]. Constraints: [TIME / BUDGET / TECH].

Rules: Under [WORD COUNT] words. No invented testimonials/metrics. Anonymise if [YES/NO].

Format: Headline, problem, approach, result, tools.

18. Case study outline

Use when: Want structure before drafting the full case study.

Role: Narrative-minded freelance marketer.

Task: Case study outline for [PROJECT] I can fill later.

Context: Known facts: [FACTS]. Goal: [E.G. ATTRACT SIMILAR CLIENTS].

Rules: Don't invent results; flag every place I need a real number or quote.

Format: Section outline with fill prompts + 'still need' list.

Prompts for admin and money

Track clients long-term with the client CRM and project tracker. Money prompts are drafting help only – not tax or financial advice.

19. Weekly plan

Use when: To-do list is a mess; need a realistic week.

Role: Operations coach for a solo freelancer.

Task: Weekly plan from: [PASTE TASKS / DEADLINES / CAPACITY].

Context: Billable hours: [HOURS]. Personal constraints: [LIST]. Revenue priorities: [LIST].

Rules: Protect deep work; only plan what fits; call out what to defer.

Format: Day-by-day plan, priorities, 'not this week' list.

20. Inbox triage

Use when: Inbox overflowing; need order, not guilt.

Role: Executive assistant for a freelancer.

Task: Triage into reply today / this week / archive: [PASTE SUBJECTS + ONE-LINE CONTEXT, REDACT CONFIDENTIAL DETAILS].

Context: Response-time promise: [E.G. 1 BUSINESS DAY]. Deadlines: [LIST].

Rules: Don't draft full replies unless asked. Flag urgent/money items. Never paste passwords.

Format: Three buckets with one-line actions.

21. Expense sorting notes

Use when: Month of expenses to sort before your accountant.

Role: Bookkeeping assistant (drafting help only – not tax advice).

Task: Categorise expenses + questions for my accountant: [PASTE DESCRIPTION + AMOUNT].

Context: Business type: [SOLE TRADER / LLC / OTHER]. Country: [COUNTRY]. Usual categories: [LIST OR 'SUGGEST'].

Rules: Don't claim deductibility. Flag ambiguous items for professional review.

Format: Item, suggested category, confidence, accountant question.

Refine prompts: shorten, humanise, fact-check

Run these on any draft before it leaves your outbox.

22. Shorten

Use when: Draft is useful but too long.

Role: Ruthless editor for a busy reader.

Task: Shorten to ~[WORD COUNT] words; keep the ask and key facts.

Context: Audience: [WHO]. Channel: [EMAIL / LINKEDIN / PROPOSAL]. Text: [PASTE].

Rules: Cut filler; keep meaning; no new claims.

Format: Shortened version, then bullets of what you cut.

23. Humanise / match my voice

Use when: Draft sounds like generic AI.

Role: Writing coach matching my voice.

Task: Rewrite so it sounds like me.

Context: Voice sample: [PASTE 2–3 SENTENCES]. Draft: [PASTE]. Never use: [LIST]. Prefer: [LIST].

Rules: Keep facts identical; no new metaphors I wouldn't say.

Format: Rewritten draft only.

24. Fact-check and risk scan

Use when: Second pass for mistakes, overclaims, confidential leaks.

Role: Careful reviewer for a freelancer.

Task: Review for factual risks, unclear claims, confidential-looking content.

Context: Text: [PASTE]. Facts I stand behind: [LIST]. Sensitivities: [NOTES].

Rules: List issues by severity; safer rewrites; no invented citations; verify time-sensitive claims.

Format: Issues list, then safer rewrite.

Worked example: one prompt filled in

Prompt 1 filled for a fictional UX writer. Sample output is illustrative.

Filled prompt (excerpt)

Role: senior freelance UX writer.

Task: cold email to Maya Chen, Head of Product at Northline Apps.

Context: noticed their post on week-one drop-off after an onboarding redesign; offer UX writing for activation; proof: cut onboarding support tickets 18% for a B2B SaaS client.

Rules: under 90 words, one question, no flattery.

Illustrative sample output:

Subject: Week-one drop-off on Northline

Maya – saw your note on week-one drop-off after the onboarding redesign. I help product teams tighten activation copy so new users know what to do next. Recently cut onboarding support tickets 18% for a B2B SaaS team. Worth a 15-minute look at one screen together?

Swap in your real proof, check names, and edit anything that doesn't sound like you.

ChatGPT vs Claude vs Gemini: quick tips

ChatGPT – Context Card in custom instructions or a Project; strong for fast drafts and refine loops.
Claude – Context Card + prompts in a Project; strong on long proposals and careful tone.
Gemini – save a Gem with your Context Card; handy if you live in Docs or Gmail.

Same 5-part structure works in all three, plus Copilot. Free tiers are fine to start; paid helps with longer context and files.

Mistakes to avoid

Sending unedited output. Clients notice generic AI. Edit every time.
Skipping context. No notes or prices means filler.
Pasting confidential data. Redact first; get permission.
Trusting invented numbers. If you didn't supply a metric, delete it.
One voice for everyone. Paste a short sample of your writing when tone matters.

FAQ

Do these ChatGPT prompts for freelancers work in Claude, Gemini or Copilot?

Yes. Same role–task–context–rules–format structure works in ChatGPT, Claude, Gemini, Copilot and most chat assistants. Paste your Context Card via custom instructions, Projects or Gems.

Do I need a paid ChatGPT plan?

No. Free tiers work. Paid helps with longer context and file uploads for big proposal drafts.

Will clients know I used AI?

They often notice unedited AI. They rarely notice a draft you edited to match your voice and facts. Review before sending.

How do I make the output sound like me?

Paste two or three sentences of your writing into the humanise prompt or Context Card. List words you never use, then cut anything that still sounds templated.

Where can I get a bigger prompt library?

The AI Prompt Playbook has 105 fill-in-the-blank prompts in 8 workflow areas, 5 agent-style workflows (25 step prompts), a Context Card, tips for ChatGPT/Claude/Gemini, 4 worked examples, and an editable .xlsx + .csv library. PDF US Letter 39 pp / A4 36 pp, $19.

Get the full prompt library

Want the complete set – more outreach, onboarding, negotiation and multi-step workflows? Grab the playbook.

Get the AI Prompt Playbook – $19

Until Sun 18 Oct 2026, 23:59 Berlin, code LAUNCH40 gives 40% off the AI Prompt Playbook and the Business Bundle.

Or start with the free Starter Kit, the AI kits hub, or freelance templates.

Related: ChatGPT prompts for freelance proposals, AI prompts for difficult client emails, AI workflows for freelancers, how to calculate your freelance rate.

Want more? The full AI Prompt Playbook is 40% off with code LAUNCH40 until Sunday: https://shop.kitwisestudio.com/l/sppaht