Practical guide

ChatGPT for freelancers: proposals, scope and the admin that eats your week

Freelance work is not lost to the work. It is lost to the wrapper around it: scoping, quoting, chasing, reporting, re-explaining. Those are exactly the jobs that are repetitive and reviewable, which makes them the right ones to hand over first.

By Brooks7 min read

Turn a messy discovery call into a scoped proposal

Type your notes as they are — fragments are fine. The value is in forcing the unknowns to the surface before you quote.

Notes to proposal
Call notes: {paste raw}. Produce: (1) the client's problem in their own words, (2) a deliverable list with one line each, (3) explicit out-of-scope items, (4) assumptions that, if wrong, change the price, (5) three questions I must answer before quoting. Do not estimate hours or price.

Price the scope, not your mood

Quote from the deliverable list you just produced. Two options beats one — it converts a yes/no into a which.

Two-option quote
Deliverables: {paste list}. My minimum acceptable day rate: {rate}. Build two options: a tight version that solves the core problem, and a fuller version. For each: deliverables, timeline, and what the client must supply. State the revision limit explicitly. No discounts, no urgency language.

The scope-creep reply

This is the message freelancers rewrite five times and send late. Have it drafted in thirty seconds and edit it once.

Out-of-scope response
Agreed scope: {paste}. New request: {paste}. Write a reply under 100 words that thanks them, names the request as outside the agreed scope without accusation, gives a price and timeline to add it, and confirms the current work is unaffected. No apology, no hedging.

Chase money without damaging the relationship

Three escalating drafts, written in advance so the tone stays even when you are annoyed.

Invoice follow-ups
Invoice {number}, {amount}, due {date}, now {n} days late. Client relationship: {ongoing / one-off}. Write three follow-ups: a light nudge, a firm reminder that references the payment terms, and a final notice that states what happens next. Keep each under 80 words and neutral.

The weekly client update nobody dreads

Short, factual updates prevent most of the questions that interrupt your deep-work blocks. Send one every week, even when nothing dramatic happened.

Client update
Done this week: {bullets}. In progress: {bullets}. Blocked on client: {bullets}. Write a client update under 150 words: what moved, what is next, and exactly what I need from them with a date. No filler, no status adjectives.

Protect the billable hours

Handing the wrapper to AI only helps if you take the time back deliberately. Book the recovered hour as client work or as your own product work in the same calendar move — otherwise it silently refills with admin.

Questions I get asked

Should I tell clients I use AI?
For internal drafting, it is no more notable than using a template. If a client's contract restricts it, or you are pasting their confidential material, that is a different question and you should ask first.
Can it write the actual deliverable?
Sometimes for first drafts, but that is the part clients pay you for. The reliable win is the wrapper around the work, not the work.
How do I stop proposals sounding identical?
Feed it real call notes rather than a description of the project. Specific client language is what makes a proposal sound like it was written for them.

Where to go next

Insider List

Get the next guide when it's written

Occasional notes on running a one-person business with AI — new guides, new tools, and what actually worked. One click to leave.

No spam. Unsubscribe in one click.