Intermediate

Proposal, scope, and the client no.
Anyone can use this page. Copy the prompt and try it today.
$6.99
Everyday AI
Proposal, scope, invoice follow-up.
You stay the editor. The model drafts. You decide.
$6.99 · 20 pages
Intermediate shelf · solo week · you stay the owner
CONTENTS
Read pages 3 through 6. Then copy one cream box.
THE IDEA
Mara ends a client call with six useful notes, two crossed-out dates, and no clean email. A model can arrange that mess. It cannot remember what the client meant, choose Mara’s rate, or promise Tuesday for her.
You own: facts, judgment, rates, scope, availability, relationships, and the final send.
The model can draft: structure, shorter wording, neutral summaries, question lists, and alternative phrasing.
It was not on the call. It did not negotiate the job. A polished sentence can still be false. If a draft supplies a number, promise, result, quote, or client motive absent from your material, remove it.
This booklet handles proposals, scope, declines, invoices, revisions, updates, quiet clients, portfolio notes, and contract questions. The cream boxes produce drafts. They do not make business decisions.
Hard nos: No confidential material you lack permission to share. No invented rates, fees, discounts, dates, metrics, quotes, results, or legal conclusions.
Then do this: Find the next message you already owe. Start there, not with all ten boxes.
WHAT THE LABS FOUND
Freelancers do not need a study claiming a chatbot wins clients. The useful evidence is narrower: these tools are often used to edit text, and clearer instructions make drafts easier to control.
1 · Editing: OpenAI reports that writing is about 40% of work-related messages. About two-thirds of those writing messages modify user text.
2 · Iteration: Anthropic’s AI Fluency Index found that people who iterate and refine also show more goal-clarifying and evaluation behaviors. This is correlational.
3 · Long briefs: Anthropic advises long material first and the question last, reporting gains of up to 30% in some complex long-document tests.
4 · Visible parts: Google names objective, persona, constraints, context, and response format. This booklet uses Role / Task / Details / Format.
Hard nos: These findings do not prove higher freelance win rates, faster payment, better design, or better legal decisions.
Then do this: Put verified source notes before your next drafting instruction.
BEFORE YOU PASTE
Inez is about to paste an entire client folder because a proposal is due tonight. It contains phone numbers, login details, internal comments, and an old budget. The model needs none of that.
Say before you paste: I am sharing only material I own or may use. I removed passwords, private contact details, customer data, and confidential files. I checked every number I want repeated. Brackets mean missing information, not permission to guess. The model may organize and phrase. It may not choose my rate, availability, scope, discount, result, or legal position. I will read the draft before anyone receives it.
Replace full names with labels. Extract relevant lines instead of uploading folders. Mark dates and numbers as verified, proposed, or missing. Keep agreed work separate from ideas.
The distinct danger is source blending: “possible launch: 14 May” becomes an agreed date because it sat near the client’s request.
Hard nos: No passwords, access links, card data, private lists, protected work, or documents you may not share.
Then do this: Make a five-line safe note: ask, scope, dates, numbers, missing facts.
HOW TO USE THIS
Theo needs to answer a revision email before school pickup. He does not need a new system. He needs one controlled draft from facts he can check.
Role: the narrow job.
Task: the draft needed now.
Details: verified facts and limits.
Format: length and shape.
Do not ask the model to choose a rate when you need wording. Do not ask whether a contract is safe when you need questions for a qualified person. If the first reply keeps guessing, start a fresh chat with less material.
Hard nos: No automatic sending. No invented facts. No model-made commitments. No legal, tax, or financial conclusions.
Then do this: Pick one page and replace its brackets before opening a chat.
THE PROPOSAL
Priya has a bakery owner’s email, three call notes, and a blank proposal. The danger is a generic pitch that quietly adds strategy, results, and timing nobody discussed.
COPY THIS
Role: Plain-spoken proposal editor for a solo freelancer.
Task: Turn my source material into a short proposal draft I can verify.
Details: Brief: [paste]. Verified offer: [deliverables]. Outside this job: [items]. Client timing: [timing or missing]. My next action: [true action]. Voice sample: [paste].
Format: Five headings: What I heard; What I will deliver; Outside this proposal; Timing; Next step. Add Missing facts.
Hard nos: Do not invent rates, discounts, hours, deadlines, deliverables, results, testimonials, client problems, or reasons to hire me. Do not turn ideas into scope.
The failure is scope hidden inside impressive verbs. “Manage” is not the same as “draft.”
Then do this: Compare every noun and number with the brief. Reply: “Use verified client wording. Remove unsupported claims and services.”
THE SCOPE SPLIT
Luis agreed to one logo and two revision rounds. On Thursday, the client asks for social templates and a brand film “while you are in there.”
COPY THIS
Role: Scope-sorting assistant. Do not interpret law or make commitments.
Task: Sort requests into Agreed now, New request, Parked question, and Unclear. Draft a short note.
Details: Original items: [paste]. New message: [paste]. Recorded revision limit: [verified or missing]. Decision I made: [state it].
Format: A four-column table, then a 5-sentence note confirming current work without accepting new work.
Hard nos: Do not call this a contract. Do not invent rights, fees, hours, dates, obligations, approval, or consent.
The failure is accidental agreement. Helpful wording can commit Luis before he has decided.
Then do this: Highlight every commitment. Delete any you did not choose. Reply: “Sort only. Do not accept new work for me.”
THE CLEAR DECLINE
Elena likes the lead, but a rush deck by Wednesday would break the week. “I might struggle” invites negotiation she cannot support.
COPY THIS
Role: Concise email editor stating a decision I already made.
Task: Draft a warm, unambiguous decline.
Details: Request: [paste]. Decision: [I cannot take it]. Reason I will share: [true reason or omit]. Real alternative: [later option or none]. Sign-off: [paste].
Format: Subject plus 4–6 sentences. State the no by sentence two. Add an alternative only if supplied.
Hard nos: Do not invent availability, referrals, rates, discounts, excuses, emergencies, or a future slot. Do not use maybe, hopefully, or I’ll try.
The failure is hedging: a polite note can imply that pressure or money will change the answer.
Then do this: Read the first two sentences. If the decision is hidden, reply: “Put the clear no in sentence two. Keep it warm.”
THE INVOICE FOLLOW-UP
Marcus sent invoice 1042 twelve days ago. A drafting tool may escalate with a late fee or due date that was never agreed.
COPY THIS
Role: Calm invoice-correspondence editor, not a collections agent or lawyer.
Task: Ask the recipient to confirm receipt and status.
Details: Invoice: [verified]. Amount: [exact or omit]. Sent: [date]. Agreed terms: [exact wording or missing]. Recipient: [name/address]. Previous follow-ups: [dates or none].
Format: Subject plus 4 sentences: record, receipt check, status question, thanks. If terms are missing, do not discuss lateness.
Hard nos: Do not invent fees, interest, deadlines, amounts, threats, legal status, promises, or reasons for delay. Do not say overdue without verified support.
The failure is false escalation. “Past due” is a factual claim, not merely a firmer tone.
Then do this: Verify the invoice and terms. Reply: “Neutral receipt-and-status check only. Add no consequence.”
THE REVISION ROUND
Jin receives comments on slides 2, 5, and 8. One is vague. One asks for a photo he does not have. A broad rewrite would consume the round.
COPY THIS
Role: Revision triage assistant mapping feedback to existing work.
Task: Create a change plan and reply.
Details: Delivered work: [version]. Current round: [verified]. Comments: [paste]. Accepted changes: [list]. Scope limit: [verified or missing].
Format: Table: Comment; Planned response; Needed input; Affected item. Then a 5-sentence reply.
Hard nos: Do not rewrite untouched items. Do not invent assets, concepts, extra rounds, approval, dates, or interpretations of vague feedback. Do not label work out of scope without records.
The failure is revision sprawl: polishing unmentioned slides creates extra review work.
Then do this: Count affected items. Reply: “Map one response to each comment. Leave everything else unchanged.”
RATE AND AVAILABILITY
Tara receives: “Could you do 15 hours next month?” A model can phrase her answer. It should not choose a market rate or fill her calendar.
COPY THIS
Role: Wording editor for decisions I already made.
Task: Draft a rate-and-availability reply using only verified numbers and dates.
Details: Request: [paste]. My rate/fee: [number and currency or missing]. What it covers: [basis]. Availability: [dates/capacity]. Earliest start: [date or missing]. Questions: [list].
Format: 5–7 sentences. If my rate is missing, return “RATE DECISION NEEDED” instead of a price.
Hard nos: Do not invent or recommend rates, fees, discounts, deposits, tax, expenses, hours, market averages, availability, deadlines, or terms.
The failure is outsourced pricing. A plausible number is still an unsupported guess.
Then do this: Trace every number to your note. Delete any that appeared on its own.
THE WEEKLY UPDATE
Devi has three facts: homepage copy is ready, client photos have not arrived, and Friday’s draft depends on them. She needs clarity, not status theater.
COPY THIS
Role: Status-update editor for a solo freelancer.
Task: Turn verified bullets into a short update.
Details: Completed: [bullets]. Waiting on client: [bullets]. In progress: [bullets]. Next date I can commit to: [fact or missing]. Decision needed: [one or none].
Format: Labels: Done; Waiting on; Next. Maximum 90 words. End with one direct question if needed.
Hard nos: Do not invent progress, dates, blockers, blame, wins, percentages, or reassurance. Do not say “on track” without an established track.
The failure is spin. “Nearly” and “smoothly” can disguise missing input.
Then do this: Remove unsupported adjectives. Reply: “State the dependency plainly. No blame or invented optimism.”
WHEN THEY GO QUIET
Noah sent a draft nine days ago and nudged once. He needs a yes or no on the headline. He does not know why the client is silent.
COPY THIS
Role: Light check-in editor. Describe the record without guessing motives.
Task: Draft a short note asking for one specific response.
Details: Sent item: [item]. Date: [verified]. Promised next step: [exact note or missing]. Follow-ups: [dates/count]. Response needed: [one answer]. Verified scheduling effect: [none or fact].
Format: Subject plus 4 sentences: reference, easy question, optional verified scheduling note, warm close.
Hard nos: Do not invent a reason for silence, guilt the client, create a deadline, threaten closure, add a fee, pitch work, or claim urgency.
The failure is mind-reading. “I know you’re busy” claims knowledge Noah does not have.
Then do this: Keep one answerable question. Reply: “Remove guesses. Ask only for [decision].”
THE PORTFOLIO NOTE
Samira finished bakery packaging. She may show selected images, but she has no measured sales result and no approved client quote.
COPY THIS
Role: Portfolio editor using approved, non-confidential facts.
Task: Draft a compact case note for my review.
Details: Publishable client label: [name/description]. Problem: [verified]. Work: [deliverables]. Choices: [verified]. Proven outcome: [fact or none]. Approved images: [list]. Voice: [paste].
Format: Label “DRAFT — VERIFY BEFORE PUBLISHING.” Three paragraphs: situation, work, observable outcome or what images show. Add Proof needed.
Hard nos: Do not invent metrics, revenue, conversion, praise, quotes, awards, client size, names, confidential details, or causal results.
The failure is fake proof. “Improved shelf impact” claims an effect unless Samira can support it.
Then do this: Attach evidence to every outcome or rewrite it as a design decision.
QUESTIONS BEFORE SIGNING
Cole receives an agreement covering ownership, cancellation, payment, and indemnity. He wants questions, not a chatbot declaring it safe.
COPY THIS
Role: Document question-lister, not a lawyer.
Task: Turn unclear or consequential wording into questions for a qualified human or the other party.
Details: Shareable excerpt: [paste]. My concerns: [list]. Terms I understand: [list].
Format: Sections: Money; Timing and ending; Ownership and use; Responsibilities and risk. Quote triggering words, state what is unclear, ask one neutral question. End “Not legal advice.”
Hard nos: Do not tell me to sign, reject, negotiate, or rely on the document. Do not invent laws, rights, clauses, risks, fees, enforceability, or legal meaning.
The failure is false legal certainty. A summary may omit definitions, linked terms, or interactions between clauses.
Then do this: Take the questions and complete document to a qualified person. Reply: “Questions only. Quote my text. No legal conclusion.”
STUCK
The first reply is not a verdict. Diagnose the failure instead of asking for a vaguely “better” version.
Invented a number: “List each number beside its source. Delete unsupported numbers.”
Accepted work: “Change commitments into discussion points. I have not accepted new scope.”
Softened the no: “State my decision by sentence two. Remove hedges.”
Escalated an invoice: “Use only verified terms. Ask for receipt and status.”
Expanded revisions: “Map one comment to one change. Leave the rest.”
Guessed a motive: “Remove speculation. Ask one factual question.”
Invented success: “Separate observable work from measured outcomes.”
Gave legal advice: “Quote my wording and produce questions only.”
Start a fresh chat when old clients, rates, or instructions leak into the answer. Draft manually when material is sensitive or repair takes longer than writing.
Hard nos: Do not argue a false draft into submission. Do not send because it sounds professional.
Then do this: Name the failure in five words. Use one repair, then verify.
THIS WEEK
Asha has four unfinished conversations and twenty minutes. A seven-day challenge would become another obligation. She chooses the nearest real consequence.
Lead waiting: Proposal or decline.
Job moving sideways: Scope split or revision round.
Money waiting: Invoice follow-up. Open the invoice first.
Delivery active: Weekly update.
Inbox silent: Quiet-client note.
Future work needs proof: Portfolio note.
Document has consequences: Contract questions, then a qualified human.
Keep a private scratch template with your voice sample, sign-off, and factual labels. Do not create a giant client archive in a chat. Start clean when the job changes.
Hard nos: No pressure to use every box. No yesterday-client facts in today’s note. No unfinished placeholders.
Then do this: Set ten minutes: prepare facts, draft, verify, then send—or decide not to send.
BEFORE YOU SEND
Mara’s proposal sounds clean. One line says “launch in May,” though the client only said May was ideal. The final edit matters more than the first draft.
Remove internal notes, hidden comments, unrelated client material, and context not meant for the recipient. For contracts, tax, finances, or disputes, organize questions and seek qualified help.
Hard nos: No automatic send. No “close enough” numbers. No brackets. No accidental commitment.
Then do this: Verify the highest-stakes sentence against its source. Only then choose Send.
SOURCES
Chatterji et al. “How People Use ChatGPT.” NBER Working Paper 34255, September 2025.
Writing is about 40% of work-related messages; about two-thirds of writing messages modify user text.
https://openai.com/index/how-people-are-using-chatgpt/
Anthropic. “The AI Fluency Index.” 2026.
Iteration and refinement coincide with more fluency behaviors. This is correlational.
https://academy.claude.com/tutorials/the-ai-fluency-index
Anthropic Documentation. “Be Clear and Direct.”
Clear roles and instructions; long material first and the query last; up to 30% improvement in some complex long-document tests.
https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/be-clear-and-direct
Google Cloud. “Prompt Design Strategies.”
Objective, persona, context, constraints, and response format.
https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/prompts/prompt-design-strategies
The live booklet’s customer-support RCT is omitted. Its results do not establish freelance proposal, sales, creative, or payment outcomes.
Hard nos: Research does not verify your client facts or make your business decisions.
Then do this: Keep the sources if useful. Keep control of the send either way.