The Client Proposal Template Pack (Built With Claude Code)

A client proposal template is the difference between winning a deal in an hour and losing a week. When a prospect is warm, speed matters - the proposal that lands while they still feel the problem closes far more often than the polished one that arrives five days later. A reusable template removes the blank page so you send fast and consistent every time.

The template below is what we call the CCC proposal skeleton. It is seven sections, in order, that walk a prospect from 'you understand my problem' to 'here is exactly what I do next'. You fill it once from your discovery-call notes, and Claude Code does the drafting. The structure does the persuading.

The point is not a prettier document. It is a faster, clearer one that says the right things in the right order. Below, each section comes with a copy-paste Claude Code prompt that turns your raw notes into finished text.

Every proposal we send follows the same seven sections, in this order. The order matters: you earn agreement on the problem and the outcome before you ever talk price, so the price lands as the cost of a result they already want.

The first three sections build trust before you ask for anything. State the problem in the client's own language, name the outcome they actually want, then list the scope so there is no ambiguity about what they are buying. Here are the copy-paste Claude Code prompts that draft each one from your discovery-call notes.

Section 1, the problem in their words. Prompt: 'Here are my notes from a discovery call. Write a short Problem section for a client proposal that restates this client's main problem in their own words, using the phrases they used. Two to three sentences. Make them feel understood, do not pitch anything yet. Notes: [paste your notes].'

Section 2, the outcome. Prompt: 'From these same notes, write an Outcome section that describes the result this client gets when the work is done - in terms of their business, not my tasks. Focus on what changes for them. Three to four sentences. Notes: [paste your notes].'

Section 3, scope and deliverables. Prompt: 'From these notes, write a Scope and Deliverables section as a clear bulleted list of exactly what is included in this engagement. Be specific so there is no ambiguity. Add a short line on what is explicitly out of scope. Notes: [paste your notes].'

The middle two sections turn intent into a plan and a price. The timeline shows the path and the milestones so the client can picture the work happening. The pricing section gives three tiers - good, better, best - so the client chooses how much to buy instead of whether to buy. Here are the prompts.

Section 4, timeline. Prompt: 'From these notes, write a Timeline section for the proposal. Break the work into clear phases with milestones and rough durations. Keep it realistic and easy to scan. Notes: [paste your notes].'

Section 5, three-tier pricing. Prompt: 'From these notes, write a Pricing section with three tiers named good, better, and best. The good tier solves the core problem, the better tier adds clear value, and the best tier is the full result with extras. For each tier list what is included and leave a placeholder for the price. Make the better tier the obvious recommended choice. Notes: [paste your notes].'

Pricing the tiers themselves is its own skill. For how to set the numbers so each tier is profitable and the middle one wins, see [how to price a Claude Code agency project](/blog/how-to-price-a-claude-code-agency-project).

The last two sections close the loop. Terms set the simple ground rules - payment, revisions, timeline expectations - so there are no surprises later. The next step gives the client exactly one action to take to say yes. One action, not three. Here are the prompts.

Section 6, terms. Prompt: 'From these notes, write a short Terms section for the proposal covering payment schedule, number of revisions, what I need from the client, and how either side can end the engagement. Keep it plain and fair, not legalese. Notes: [paste your notes].'

Section 7, the next step. Prompt: 'Write a short closing Next Step section for the proposal that gives the client exactly one clear action to accept and start - for example approve a tier and book a kickoff. Make it confident and frictionless. One action only.'

Once the proposal is accepted, the work starts at onboarding. Hand off cleanly with the prompts in our [Claude Code client onboarding prompt pack](/blog/claude-code-client-onboarding-prompt-pack).

Once you have the skeleton and the seven prompts, a full proposal comes together in minutes. The fastest way is to give Claude Code your whole notes once and ask it to draft every section in order, then refine each one. Here is the single prompt that does it.

Prompt: 'You are drafting a client proposal using the CCC proposal skeleton: problem in their words, outcome, scope and deliverables, timeline, three-tier pricing (good, better, best), terms, and one clear next step. Draft all seven sections in that order from the discovery-call notes below. Keep the language plain and confident, restate the problem in their own words, and make the better pricing tier the recommended choice. Notes: [paste your notes].'

Then read it back, tighten anything that sounds generic, drop in your real prices, and send. The skeleton keeps every proposal consistent, and Claude Code removes the slow part - the blank page. For the broader set of agency workflows that turn drafts into revenue, see [5 Claude Code workflows that get you paid](/blog/5-claude-code-workflows-that-get-you-paid).

Three pricing tiers and one clear next step are not decoration - they change how the client decides. Tiers shift the question from 'should I buy this?' to 'which version do I want?', which is a far easier yes. A single next step removes the friction that lets a warm prospect drift and go cold.

This is also why a repeatable proposal is the first step toward a productized offer - the same skeleton, the same tiers, sent again and again. To take that further, see [how to productize a service with Claude Code](/blog/how-to-productize-a-service-with-claude-code).