How to write a client proposal template that wins work

You sent the proposal. You thought it was good. Then you heard nothing. Maybe a "we'll get back to you" that turned into silence. And now you're wondering if it was your price, your timing, or something about how you presented the whole thing.

Nine times out of ten, it's the proposal. Not because you're bad at what you do, but because the document didn't do its job. A strong client proposal template fixes this by giving you a repeatable structure that communicates your value clearly, every single time.

Let me walk you through what goes into a proposal that actually closes projects.

Why most proposals don't work

Most freelancers and small studios treat proposals like quotes. They list what they'll do, slap a price at the bottom, and email it off. That's not a proposal. That's a shopping list.

A proposal is a sales document. Its job is to make the client feel confident that you understand their problem, you have a clear plan to solve it, and you're the right person for the job. If your proposal doesn't do all three of those things, it's working against you.

The other big mistake? Starting from scratch every time. You spend hours writing a new one for each project, tweaking the language, reformatting, second-guessing yourself. That's a massive waste of time and energy. A solid template gives you the bones so you can focus on the parts that matter.

What a good client proposal template includes

Here's the structure I use and recommend. Every section has a specific purpose. Skip one and the whole thing feels incomplete.

1. Cover page

First impressions count. A clean cover page with the project name, client name, your studio name, and the date sets the tone. It tells the client this is a professional document, not something you knocked together in Google Docs at midnight.

Keep it simple. Your logo, their name, the project title. Done.

2. Project overview

This is where you show the client you were actually listening. Write a short summary of their situation, the problem they're trying to solve, and what they're looking for. Use their words where you can. Mirror back what they told you in the discovery call or brief.

This section builds trust fast. When a client reads a description of their own problem written clearly, they immediately feel like you get it.

3. Your approach

Don't list deliverables yet. First, explain how you work and why you work that way. Clients want to know your thinking, not a feature list. Walk them through your process in plain language.

For example: "We start with a strategy session to lock in the direction. Then we move into two rounds of concepts, followed by refinements. You'll have a single point of contact throughout, and we check in weekly."

This is where you stand out from everyone else who's quoting on the same project. Your process is your differentiator.

4. Scope of work

Now you list the deliverables. Be specific. Don't write "branding package" when you mean logo, colour palette, type system, and brand guidelines document. Vague scopes lead to scope creep, and scope creep leads to resentment on both sides.

Use bullet points. One deliverable per line. Make it scannable. The client should be able to read this section in under 30 seconds and know exactly what they're getting.

5. Timeline

Give them a clear picture of how long the project takes and what the key milestones are. Break it into phases if that makes sense. Include when you need things from them, too, like feedback or content.

This does two things. It sets expectations, and it shows the client that delays on their end will push the timeline. That's an important boundary to establish early.

6. Investment

Call it investment, not cost. It's a small language shift but it matters. You're framing the price as something they're putting into their business, not an expense they're losing.

Break the pricing down. If it's a fixed project, show the total and the payment schedule. If it's phased, show the cost per phase. Be transparent. Hidden costs are a trust killer.

Include your payment terms here, too. Deposit amount, payment deadlines, accepted methods. Don't make them guess.

7. About you

A short section on who you are and why you're the right fit. This isn't your life story. A couple of sentences about your experience, a note about the types of clients you work with, and maybe a relevant project you've done before.

If you have testimonials, drop one in here. One good quote from a past client is worth more than five paragraphs about yourself.

8. Next steps

Tell them exactly what to do if they want to move forward. "Reply to this email with your approval and we'll send the contract and deposit invoice within 24 hours." Make it clear and easy. Remove any friction.

A proposal without a clear call to action is a brochure. You're not making brochures. You're closing work.

Design matters more than you think

The way your proposal looks communicates as much as the words on the page. If you're a designer sending a proposal that looks like a tax return, you've got a problem.

You don't need to go overboard. Clean layout, consistent type, your brand colours, and enough white space to let it breathe. That's it. The goal is to look put-together and intentional.

If you're not a designer, don't try to DIY this. Use a template that's already been designed well. It'll save you hours and make a much better impression.

We built the Proposal Framework in Figma for exactly this. It's a ready-to-go proposal template you can customise with your own branding, drop in your content, and send out looking sharp. No fiddling with layout or formatting from scratch.

Common mistakes to avoid

Even with a good structure, there are a few traps that can sink a proposal.

Writing too much. Proposals aren't essays. Every sentence should earn its place. If it doesn't build trust or move the client toward a yes, cut it.

Being vague about scope. "We'll handle the branding" means something different to every person reading it. Spell out the deliverables. Be boring about it. Boring is clear, and clear closes.

Forgetting the client's perspective. Your proposal should be about them, not you. Lead with their problem. Frame everything around how it benefits their business. Save the "about us" stuff for the end.

Sending a PDF with no context. The email you send with the proposal matters. Write a short note that summarises the key points and tells them what to look at first. Don't make them open a 10-page document cold.

No expiry date. Put a validity period on your proposal. 14 or 30 days is standard. This creates gentle urgency and protects you from someone coming back six months later expecting the same price.

How to personalise your template for each client

A template doesn't mean copy-paste. It means you're not starting from zero. Here's what you should customise for every new proposal.

• Project overview. Rewrite this section fresh for each client based on your conversations with them.
• Scope and deliverables. Tailor this to the actual project. Don't leave in deliverables from the last proposal that don't apply.
• Timeline. Adjust based on the project size and your current availability.
• Investment. Price the specific project. Don't use a generic rate card.
• About section. Swap in a testimonial or case study that's relevant to their industry or project type.

Everything else, your cover page layout, your process description, your terms, your next steps section, stays the same. That's the power of a template. It locks in the stuff that doesn't change so you can spend your time on the stuff that does.

Proposals are part of a bigger system

A proposal doesn't exist in isolation. It's one step in the client journey. Before the proposal, there's discovery. After it, there's the contract, the onboarding, the project itself, and the offboarding.

If your proposal is polished but the rest of your process is messy, the client will feel that disconnect. The experience needs to be consistent from first email to final delivery.

That's why I always recommend building your proposal template as part of a bigger system. Your proposal format, contract, invoice, onboarding docs, and offboarding process should all look and feel like they come from the same studio.

If you want the full set, the CBOS Frameworks pack includes all eight Figma frameworks: proposals, contracts, invoices, client onboarding, offboarding, pitch decks, portfolio, and services guide. It's the whole client experience in a box.

When to send it

Timing matters. Send the proposal within 24 to 48 hours of your discovery call while the conversation is still fresh. The longer you wait, the more the client's enthusiasm fades.

If you have a good template ready to go, this is easy. You fill in the custom sections, export, and send. The template does the heavy lifting.

Follow up if you haven't heard back in three to five days. A short, friendly email. "Hey, wanted to check if you had any questions about the proposal." That's it. No pressure, no desperation. People are busy. A nudge is expected.

Build it once, use it forever

The best time to build your client proposal template is before you need it. Sit down on a quiet day, put the structure together, get the design right, and save it somewhere you can grab it fast.

Next time an enquiry comes in, you won't be scrambling. You'll pull up the template, fill in the details, and send something that looks great and reads even better. That speed and consistency is what separates studios that close work from ones that are always chasing it.