FROM THE CADDY METHOD
Every proposal starts from a blank page? How to reuse what your studio already sells
You write a design studio proposal without starting from scratch by separating what is reusable (problem you solve, approach, proof, recommended path) from what is specific to this client, then rewriting only the client-specific parts. Price and scope belong in the quote; the proposal makes the case.
A proposal should reuse the case you already make.
What is a design proposal, and how is it different from a quote?
A design proposal is the document that makes the case for the work, and a quote is mainly the price and terms for a defined scope. business.gov.au's guide to preparing quotes covers what a written quote includes and notes that an accepted quote becomes a legally binding contract. Our guide on quoting design work faster walks through that side for a studio.
A proposal is the other half. It sets out the problem as you understand it, the approach you recommend, why this studio fits, proof you have solved a similar problem, and what happens next if they say yes. The Commonwealth's Capability Improvement Grant guidance on requesting a quote for a Capability Improvement Grant project asks applicants for a formal proposal and quote together, and lists outcomes and deliverables, methodology (including previous similar work), references, timing and price among the things to check. That split travels well outside a grant: the proposal carries the case, the quote carries the commercial detail.
A clear, small job with a known deliverable often needs only a quote. A larger or more strategic enquiry usually needs a proposal as well. This guide isn't legal advice; if you're unsure about your terms or how an accepted document binds you, get legal advice.
Why does every proposal feel like a blank page?
Every proposal feels like a blank page when the case you already make isn't written down anywhere the next document can pull from. The last proposal gets copied, the previous client's name half-deleted, and the opening paragraphs rewritten in new words even when the method is the same. Proof lives in someone's head or a forgotten folder. Sections that should be standard (how you work, what happens after they say yes) get reinvented because there is no agreed wording to start from.
The founder is often the only person who can "make the case", so every proposal also waits for a gap in their week. One enquiry arrives as a detailed brief; the next is two lines from a phone. Both still need the same studio case underneath them.
Here's an illustrative moment, the kind of enquiry on the Caddy homepage: a client asks for help launching a new product range under an existing brand. The team knows how they usually approach that work. Opening a blank page still feels easier than finding the last time they wrote it down.
Where does your proposal time go? Trace one proposal
You find where your proposal time goes by taking one recent proposal that took longest to write and noting what was reusable and what was specific. Pick one the team still remembers, and write it down from your own emails and drafts.
For that proposal, note four things:
- What was specific to this client. Their problem in their words, their constraints, their timing, and anything only they could have told you.
- What you have written before in almost the same form. Your approach, how a typical engagement runs, typical phases, proof of a similar problem, and standard next steps.
- What you rewrote anyway, and why. No shared library, no agreed wording, or waiting on the person who "owns" the case.
- Where price and scope sat. Inside the proposal, or as a separate quote attached or linked beside it.
Once it's written down, look for the pattern that tends to show up: most of the time went into rewriting the reusable pieces. The client-specific understanding has to be fresh; the approach, the proof and the next-step wording are usually the ones that keep getting reinvented.
This is how we start at Caddy: we look at what you rewrite every time before suggesting a new template. You can read more about how we approach it.
What should a design proposal cover?
A design proposal should cover the case for the work. The Design Business Council's page on how clients look at your pricing puts it plainly: lead with the client's problem and what needs to change, rather than a list of what you will produce. In studio terms, that usually means:
- The client's problem in their language. What they are trying to change, and what success would look like for them.
- The recommended approach, and what sits in or out of that path.
- Why this studio for this problem. The kind of work you take. The Design Business Council's page on what creatives should say to a client at a pitch calls these pillars of excellence: the field where you are more able to help.
- Proof of a similar problem you have solved. One or two short examples (problem, what you did, what changed), with permission where needed. An illustrative proof line: "a brand launching a new range needed customers to recognise the products as part of the existing brand; we framed the offer around that recognition, then built the communications to match." Use your own real examples when you send.
- Recommended path and next step. What happens if they say yes, and what you need from them to start.
- Where the quote sits. Price, deliverables, revision rounds, terms and acceptance belong with the quoting side. Point there rather than rebuilding that checklist here.
If terms, signatures or contract language sit in your proposal, get legal advice for your own agreements.
How do you reuse what you already sell?
You reuse what you already sell by fixing the pattern your trace pointed to, smallest change first. Write down once the problem types you solve, in plain language. Write down once how a typical engagement runs. Keep a short, approved library of proof (problem, what you did, what changed), with permission where needed, and keep standard next-step and how-we-work wording in one place.
For each new enquiry, rewrite only the client-specific understanding and the recommended path, then attach or link the quote. Once that library exists, assembling a first draft from your own problem statements, approach and proof is one place a simple tool, or AI, can help, with a person always checking before it goes out. The person checking is the one who notices the enquiry mentioned a constraint nobody has addressed yet. Try one change on the next proposal and keep it if it holds.
What happens after you send the proposal?
After you send the proposal, follow up with something useful rather than another "just checking in". An adjusted path, a question about a constraint they raised, or a note on when the team could start is easier to answer than a nudge with nothing in it. The Design Business Council's page on estimates with options puts the aim of an estimate as continuing the conversation: one figure invites a yes or no, while options keep the discussion open. The same idea applies once a proposal is out.
Once they want to move, the quote (or the pricing section you pointed at the quoting guide) becomes the scope you check every new request against. Our guide on how to stop scope creep in a design studio covers what to do when a request lands outside that document. If you agreed review windows up front, they earn their keep later, when you're the one waiting, and our guide on chasing client feedback shows how to keep those reviews moving. Finished proposal work still needs to show up in your week, and our guide on seeing which jobs need you this week shows how to keep every active job in one weekly list.
Questions studios ask about design studio proposals
How do you write a design studio proposal without starting from scratch?
Separate reusable case pieces (problem you solve, approach, proof, recommended path) from what is specific to this client, rewrite only the client-specific parts, and attach or link the quote.
What is the difference between a proposal and a quote?
A proposal makes the case (problem, approach, why this studio, proof and next step); a quote sets out price and terms for a defined scope. business.gov.au's Capability Improvement Grant guidance asks for both together when evaluating consultants. For day-to-day studio work, use a quote alone when the job is clear, and add a proposal when the client needs the case before they buy.
What should a creative proposal include?
Include the client's problem in their language, the recommended approach, why this studio fits, proof of a similar problem, the next step if they say yes, and a clear place for the quote.
When is a quote enough, and when do you need a proposal?
A quote is enough when the scope is clear and the client mainly needs a price and terms. You need a proposal when the enquiry is larger or more strategic and they need the approach and the proof before they decide.
Should price live inside the proposal or in a separate quote?
Either can work, as long as price and scope are as clear as the quoting guide requires. Some studios keep one document; others attach a separate quote. Pick the shape your clients can act on.
Bring the proposal that took longest to write
If a proposal came to mind while you were reading, start with that one. Bring it to Caddy's free workflow review and we'll help you see which parts you rewrite every time before you change anything.