Turn rough notes into a proposal with Claude

A proposal becomes expensive when it promises something you never meant to sell. Claude can turn rough notes into a useful first draft, but it needs boundaries around the price, the scope and the tempting extra services that nobody has agreed.

Start with the job. Then ask questions about what fits. Make it presentable after the scope is right, because a handsome heading has never prevented a paragraph from selling another week of your time.

What you'll make

a proposal draft with a clear scope, explicit exclusions and a visible list of points still to agree. It remains a draft for human review.

What you'll need

a short brief, the answers you actually have and an approved Claude account. The text workflow does not require a connector or paid automation; normal limits apply. Creating a downloadable file is an optional final step.

Use a fictional client first. For real work, check confidentiality requirements and use only information permitted in the approved account. This exercise prepares a draft; it does not send an offer, approve a fee or agree terms.

1. Put the job into plain English

Name the problem, work, deliverables, timing and exclusions. Write “not agreed” where something is not agreed. It is useful information rather than an embarrassment to be edited away.

Use this fictional 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.

There is enough here to start a conversation. There is not enough to pretend the proposal is ready to sign. Six interviews and a review may be a fairly energetic half-day, especially if the interviews include answers.

2. Make Claude ask before it writes

Open a new chat and give it the brief with this prompt:

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,
interviews, review and report-writing.

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

[Paste the brief.]

Useful questions might include how long the interviews take, what the client provides and whether preparation sits inside the session. “What tone would you like?” can probably wait.

Anthropic’s getting-started guide supports ordinary text conversations. You can do the drafting work with typed notes; there is no need to connect a client drive.

3. Answer the scope questions before drafting

These are fictional answers for this walkthrough:

Reduce the session to four 20-minute interviews, a 60-minute
walkthrough and a 20-minute wrap-up: 160 minutes of scheduled activity.
Allow the rest of the half-day for breaks and transitions.

Preparation and report-writing happen outside that session and are
included in the proposed scope. The client provides the current
template and two redacted examples.

The report remains a target of five working days after the review.
Fee and session date remain to agree. Implementation and ongoing
support are excluded. A revision allowance remains to agree and is
not included unless separately approved.

In your own work, use actual answers. Check the time arithmetic and your working definition of a half-day. The session may fit while the preparation and report still require a separate budget of time.

Do not quietly turn the original “up to six” into four without explaining the change to the client. The point of the questions is to reveal the trade-off, not hide it in better prose.

4. Draft with the gaps still showing

Now ask for a bounded draft:

Using the brief and my answers, draft a plain-English proposal under
500 words. Use: Purpose, Work included, Deliverables, What the client
provides, Timing, Exclusions and Points to agree.

State assumptions separately. Leave unapproved prices and dates as
"to agree". Preserve timing as a target where the source calls it a
target. Do not add acceptance language, guarantees, legal terms,
ongoing support or a revision allowance I have not supplied.

[Paste the brief and answers.]

A checked scope might look like this illustrative paragraph, rather than a captured Claude response:

The proposed work includes a half-day remote session with four 20-minute interviews, a 60-minute walkthrough and a 20-minute wrap-up. Preparation and the findings report sit outside that session and are included in the proposed work. A draft handover checklist is included. Implementation and ongoing support are excluded. The report target is five working days after the review; the fee and session date remain to agree. Any revision allowance also remains to agree.

Check the rest of the draft for contradictions. A clear exclusions section does not help if the introduction promises a complete transformation of the client’s handovers.

5. Find the free work hiding in the wording

Search for “all”, “unlimited”, “complete”, “ensure” and “ongoing”. Each might be harmless, or it might be Claude volunteering you for another fortnight.

List every commitment in this draft. 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.

Use the list as a second check, then read the proposal yourself. In this example, the following boundaries matter:

Commitment	What supports it
Four 20-minute interviews	The fictional scope answers, replacing the original six
Findings report and draft checklist	The original brief
Five-working-day report target	The brief; still a target
Implementation and ongoing support excluded	The brief and answers
Fee and session date to agree	Both remain unresolved

If the draft contains a fee, a guaranteed result or unlimited revisions, it has crossed the boundary of the supplied brief. Remove the addition or obtain a real agreement before including it.

6. Format the approved wording and review the file

Copy the checked text into your normal proposal template. Where file creation is enabled, Claude can also create a downloadable Word document. Ask it to use the approved text without changing the scope:

Create a simple Word document from this approved 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 approved text.]

Anthropic’s file-creation documentation describes downloadable Word files; availability depends on enabled capabilities and workspace settings. If you cannot create a file, copying into your template is sufficient.

Open the exported file and check the wording as well as the layout. Review the fee, scope and required terms through your normal approval process before you choose whether to send it. Keep the questions and answers with the draft so the next edit does not restore the original assumptions.

Keep this: A polished proposal still needs to describe work you have actually agreed to do.

Accounts and limits

Use your organisation’s approved account and permitted client material. Anthropic’s commercial-product policy describes training defaults and exceptions; it does not describe Free, Pro or Max consumer accounts and does not grant permission to upload confidential briefs. Account usage limits still apply.

Sources and status

Checked 4 October 2026 against Anthropic’s chat instructions, file-creation guidance and commercial training policy. The client, answers and output are fictional or illustrative. No live Claude test, contractual advice or measured saving is claimed.

When the proposal becomes active work, a short weekly update can keep the next decision visible.