TaskbyTask.Practical AI guides for work
Claude · Practical walkthrough

Turn rough notes into a proposal with Claude

The client call ends with “could you send something over by Friday?”, and all you have is half a page of notes. Before Claude turns them into a confident proposal, get it to ask whether the work actually fits the time.

Task by Task13 min read + practice
Rough notes flow into a structured proposal with a question marking an unanswered detail.

What you'll make

a plain-English proposal draft with the work, deliverables and exclusions defined, and every unagreed fee or date marked “to agree”.

What you'll need

Claude on any plan (the text method also works in ChatGPT, Gemini or Copilot), client notes your organisation allows you to use in your work account, and about 20 minutes. You still decide the scope, price and terms before anything is sent.

Example result.

Section What the draft says
Work included Four 20-minute interviews, a 60-minute walkthrough and a 20-minute wrap-up
Deliverables A findings report and a proposed handover checklist
Timing Report target: five working days after the review
Exclusions Implementation and ongoing support
Points to agree Fee, session date, revision allowance

1. Ask Claude for scope questions first

Open a new chat in Claude. Paste your rough notes, covering whatever you have of: the client’s problem, the proposed work and quantities, the deliverables, what the client provides, timing, exclusions, and any fee, date or revision allowance. Write “not agreed” wherever something isn’t. It is useful information, not an embarrassment to be edited away.

Help me prepare a proposal from this brief. First ask up to five
questions needed to define a realistic scope. Pay particular attention
to whether the work fits the proposed time, including preparation,
sessions and follow-up work.

Do not invent a price, client fact, date, guarantee or legal term.
Keep unanswered items visible. Do not draft the proposal yet.

[Paste your rough brief.]

[Paste your rough brief.] means your notes, as they are.

Why this works: asking before drafting surfaces the trade-offs while they are still cheap to fix. A finished proposal makes a workload problem look settled when it isn’t.

What you should see: up to five practical questions, such as how long each session takes or whether report-writing sits inside the time. “What tone would you like?” can probably wait. Get real answers from the client, add them to the brief and check the time arithmetic yourself.

2. Ask for a draft that stays inside the brief

Once the answers are in, ask for the draft in the same chat. Change the length and headings if your normal proposal format differs.

Turn this brief into a plain-English proposal under 400 words.
Use: Purpose, Work included, Deliverables, What the client provides,
Timing, Exclusions and Points to agree.

Use only the brief and answers. Leave prices, dates and revision
allowances that are not agreed as "to agree". Keep targets as targets
and assumptions separate. Do not add guarantees, legal terms,
acceptance language, ongoing support or extra services. Flag
conflicting details rather than fixing them by guessing.

[Paste your checked brief and the client's answers.]

Why this works: the limits stop a tidy draft adding work you haven’t priced. “To agree” keeps a business decision visible, and calling a date a target stops it quietly becoming a promise.

What you should see: a short proposal under the seven headings, with the fee, date and anything else unresolved listed under Points to agree.

3. Audit every commitment in the draft

Search the draft for “all”, “unlimited”, “complete”, “ensure” and “ongoing”. Each might be harmless, or it might be Claude volunteering you for another fortnight. Then ask Claude to list what it has promised.

List every commitment in this draft as a table with two columns:
Commitment and What supports it. For each one, quote the sentence in
my brief or answers that supports it. Flag any promise you added,
scope ambiguity or conflict between workload and proposed time.
Check numbers, exclusions, timing targets and all points left to agree.
Do not fix a gap by inventing an answer.

Why this works: a commitment with nothing in the “What supports it” column is easy to see in a table and easy to miss in fluent prose.

What you should see: one row per commitment, each with a quoted source, and a short list of anything flagged. Use the table as a second check, then read the proposal yourself.

Check the result

  • Every deliverable, quantity and date matches the brief or the client’s answers.
  • Session time adds up on its own, with preparation and report-writing counted separately.
  • The exclusions are still there.
  • The fee, date and revision allowance still say “to agree” unless you have actually agreed them.

The usual failure: the draft promises more than the brief. The original quantity creeps back, a fee appears, or a line says everything will fit in the time. You’ll spot it as a row in the audit table with no supporting quote. Remove it with the repair below. If the work still cannot fit, resolve the scope with the client before polishing.

Remove [unsupported promise]. It is not in the brief or the answers.
Keep the agreed work and the remaining points to agree unchanged.

[unsupported promise] means the sentence you found in the audit.

Copy the checked wording into your usual template and follow your normal sign-off before sending.

Worked example: making a half-day realistic

Fictional example. Acorn Studio wants help with handovers that leave people unclear about the next action. The rough brief:

Client: Acorn Studio.
Problem: handovers leave people unclear about the next action.
Proposed work: one half-day remote review, with up to six staff interviews.
Deliverable: a short findings report and a proposed handover checklist.
Report target: five working days after the review.
No implementation or ongoing support included.
Fee, interview lengths and review date are not agreed.

Six interviews and a review may be a fairly energetic half-day, especially if the interviews include answers. Claude asks how long interviews take, whether preparation sits inside the session and what the client provides. The client answers:

Four 20-minute interviews, a 60-minute walkthrough and a 20-minute
wrap-up. Preparation and report-writing happen outside the session
but are in scope. The client provides its current template and two
redacted examples. Fee, session date and revision allowance: to agree.

The first draft includes this line: “Six interviews and the entire report will fit inside the half-day for a confirmed fee.” The audit table shows it with no supporting quote: the answers say four interviews, the report sits outside the session and the fee is not confirmed. After the repair prompt, the extract reads:

“The proposed remote session includes four 20-minute interviews, a 60-minute walkthrough and a 20-minute wrap-up. Preparation, the findings report and a proposed handover checklist are included. The report target is five working days after the review. Implementation and ongoing support are excluded. The fee, session date and any revision allowance remain to agree.”

What mattered:

  1. The arithmetic. Four 20-minute interviews (80 minutes), the walkthrough (60) and the wrap-up (20) total 160 minutes, leaving the rest of the half-day for breaks and transitions.
  2. The trade-off is explained, not hidden. Don’t quietly turn the original “up to six” into four without telling the client. The point of the questions is to reveal the trade-off, not bury it in better prose.
  3. “Target” stays a target. Five working days is a plan, not a guarantee, and the draft says so.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Explain a scope change to the client

When the questions change the scope, tell the client before they read the proposal and wonder where two interviews went. Ask Claude for a short covering note that names the change and the reason.

Draft a short, friendly note to the client explaining how the scope
changed from the original brief and why. Name each change and its
reason in one sentence. Do not add new work, prices or dates, and do
not apologise for the change.

[Paste the original brief and the agreed answers.]

Check that every change in the note matches the answers, and that nothing new has appeared.

Create a Word document from the checked text

Claude can create a downloadable Word document when Code execution and file creation is switched on. On Free, Pro and Max, find it in Settings › Capabilities. On Team and Enterprise it is on by default, and an owner can turn it off in Organization settings › Capabilities.

Create a simple Word document from this checked text. Keep its wording,
numbers, exclusions and "to agree" items unchanged. Use clear headings
and ordinary readable formatting. Do not add a signature block,
acceptance statement, price or terms.

[Paste the checked text.]

Open the file and check the wording as well as the layout. If you can’t create files, copying into your template works just as well. Keep the questions and answers with the draft so the next edit doesn’t restore the original assumptions.

Sources

Optional analytics

With your permission, Google Analytics uses cookies to measure visits and which guides people read. It stays off until you accept. Use Analytics choices in the footer to change your choice. Rejecting after accepting refreshes this page. Privacy details.