Templates
Proposal Templates
Proposal templates that follow the structure buyers expect: problem, approach, scope, pricing, timeline and next steps.
Overview
Why use a proposal template?
These proposal templates give you the structure buyers expect (the problem, your approach, the scope, the timeline, the price and the next step) with the questions each section has to answer and the mistake people usually make in it.
What they do not give you is wording to paste. A proposal is judged on whether it is about the buyer, so boilerplate paragraphs produce exactly the generic document that loses work. Fill-in-the-blank prose is worse than a blank page, because it reads as effort that was not made, and a buyer who recognises a template stops evaluating the argument and starts evaluating your interest.
The pricing table does carry across, into the quote generator, because that part is arithmetic rather than argument. Optional extras keep their flag: priced so the client can see what they cost, excluded from the total until they choose them.
Three shapes, because the documents are genuinely different. A defined project leads with the problem. A retainer lives or dies on what a month actually includes. A tender response has to follow the buyer's own structure, because a scorer working through a rubric cannot award points for something they cannot find.
Step by step
How to structure a proposal
Pick the shape
A defined project, an ongoing retainer, or a formal tender response. Each is structured differently because buyers read them differently.
Answer the prompts in your own words
Each section lists the questions it has to answer and the mistake people usually make there. The words have to be yours. That is what a proposal is judged on.
Price it in the quote generator
The pricing table carries across, with optional extras priced but kept out of the total until the client chooses them.
What you get
- Problem, approach and scope sections
- Prompts to answer rather than prose to paste
- The way each section usually goes wrong
- Pricing tables with optional extras
- Timeline and milestone blocks
- Clear next-step call to action
Background
Why a proposal cannot be templated the way an invoice can
An invoice is a form. Every one contains the same fields in the same places, and a template genuinely finishes most of the job: the only variables are the amounts and the party. A proposal is an argument, and the argument is different every time because the buyer is different every time. That is the whole reason a template can carry structure but not substance.
The structure is worth having, though, because it is remarkably consistent. Buyers want to know, in roughly this order: do you understand my problem, what will you do about it, what exactly do I get, when, how much, and what happens next. A proposal that answers those six questions in that order is doing most of what a proposal can do. One that opens with company history is answering a question nobody asked.
The order matters more than it looks. Leading with the problem, in the buyer's own words, is what earns the right to be read further. It demonstrates you listened, before you have claimed anything about yourself. Leading with credentials asks the reader to care about you before you have shown you understood them, which is the wrong way round and is the single most common structural error in proposals.
Scope is where proposals fail commercially rather than editorially. A scope section that lists only what is included leaves everything unstated as an assumption, and buyers assume generously. Naming what is out of scope, how many revisions are included, and what triggers a change order is unglamorous and prevents most of the disputes that happen three weeks into a project.
The last section is the one most often wasted. A proposal that ends with 'let us know your thoughts' has moved the decision to whenever the buyer next thinks about it. Naming exactly one action, with a date attached and a stated consequence after that date, is the difference between a document that closes and one that sits in a queue with three others.
Not to be confused with
- A quote
- A price for known work. Where the buyer already knows what they want, a quote is the right document and a proposal is overhead. Where they are still deciding what to do, a bare price answers a question they have not reached yet.
- An estimate
- An approximate figure, explicitly not fixed. Useful early and dangerous if the buyer reads it as a quote: say which it is, because the difference becomes an argument once work starts.
- A statement of work
- The contractual version of the scope section, usually attached to an agreement once the proposal has been accepted. More precise, less persuasive, and not a substitute for either.
- A pitch deck
- Presented rather than read, and structured for a room. A proposal has to survive being forwarded to someone who was not in the meeting, which is why it carries the reasoning rather than just the conclusions.
- An RFP response
- A proposal constrained by somebody else's structure and scoring. Your preferred narrative is irrelevant; answering their questions in their order is what gets points, and reformatting their pricing table is a common disqualification.
- A capability statement
- About you rather than about them: what you do, who you have done it for. Occasionally requested and never a proposal, because it makes no argument about this buyer's situation.
Reference
The sections buyers expect
Every template here uses some form of these. The order is the load-bearing part: each section earns the right to the next one, and moving credentials to the front is the error that most reliably costs the work.
The problem
Their situation in their words, showing you listened. A buyer who does not recognise themselves in the first paragraph has already decided the document is generic, and nothing later recovers that.
Required
The approach
How you will solve it, at a level a non-specialist can follow. This establishes confidence rather than proving detail: the buyer is deciding whether to trust you, not learning to do the work.
Required
Scope, including what is excluded
Precise enough to be checked. Everything unstated is assumed included, so naming the boundary is what prevents the awkward conversation later. Revisions and change-order triggers belong here.
Required
Timeline, with dependencies
Dates, and what you need from them for those dates to hold. A timeline that quietly assumes instant feedback is one you will miss and be blamed for missing.
Required
Pricing
Structured enough to show what drives it. A single undifferentiated number gives the buyer exactly one lever, which is asking for a discount on all of it.
Required
Optional extras
Priced separately and left out of the total until chosen. It lets you offer more without inflating the headline figure, and it gives a buyer something to say yes to besides the whole thing.
Optional
The next step
One action, with a date. Not a summary, not an invitation to think it over: the specific thing you want them to do and what happens if the date passes.
Required
Validity
How long the price holds. It is both commercially sensible and a mild, legitimate reason to decide: without it, a proposal has no natural moment at which it expires.
Optional
Proof, where it is relevant
Comparable work, named people who will actually be involved, verifiable results. Specific beats impressive, and naming senior staff who will not touch the project is a tactic buyers check.
Optional
Who it helps
Who needs a proposal template?
Freelancers and consultants
Most work is won or lost on a document written under time pressure between other jobs. Having the shape settled means the effort goes into the argument rather than into deciding what order things come in.
Agencies and studios
Proposals go out often enough that structure should be reusable and prose should not. A consistent skeleton also makes it possible to tell which proposals failed on the argument rather than on the format.
Anyone pitching a retainer
The hard part is defining what a month buys, and vagueness there becomes either resentment or scope creep. The retainer template leads with that section because it is where the arrangement succeeds or fails.
Anyone answering a tender
Formal processes score against stated criteria in a stated order. Following your own structure means a scorer has to hunt, and anything they cannot find scores nothing. That is a self-inflicted loss.
Small businesses bidding for larger clients
A structured, specific proposal is one of the few places a small supplier can outperform a large one, because it demonstrates attention that a templated corporate response visibly lacks.
Anyone whose proposals go quiet
Silence after sending is usually a missing next step rather than a lost deal. Naming one action with a date attached changes the response rate more reliably than any amount of rewriting.
Do it properly
Best practices
Lead with their problem, not your history
The first paragraph decides whether the rest is read. Restating their situation in their words earns that; company background asks them to care about you before you have shown you understood them.
Write the words yourself
Structure travels between proposals and prose does not. A buyer can tell the difference immediately, and a document that reads as boilerplate is answering the question of how much you wanted the work.
Say what is out of scope
Listing only inclusions leaves the boundary to the buyer's imagination, and imagination is generous. Naming exclusions, revision counts and change-order triggers prevents most mid-project disputes.
Attach dependencies to every date
A timeline is a promise conditional on things you do not control. Saying what you need and by when makes a slipped date a shared problem rather than your failure.
Price in a structure, and make some of it optional
A single number invites a single response. Breaking it out shows what drives the cost, and optional lines give the buyer something to accept short of the whole thing.
End with one instruction and a date
Not a summary and not an invitation to reflect. The specific action you want, when you need it by, and what happens after. That is what turns a proposal into a decision.
Keep it as short as the argument allows
Two to five pages suits most small-business work. Length is often mistaken for effort, and long proposals delay decisions rather than winning them: every extra page is another reason to read it later.
Avoid these
Common mistakes
Opening with your company background
Start with their problem. Nobody has ever chosen a supplier because of the year it was founded, and leading with credentials is the clearest possible signal that the document was not written for them.
Pasting boilerplate paragraphs
Write the sections yourself, using the prompts as questions. Templated prose reads as effort nobody made, and a buyer who spots it stops evaluating your argument and starts evaluating your interest.
Listing only what is included
Name the exclusions too. Everything unstated is assumed in, and that assumption always surfaces at the worst point in the project: usually after the budget is committed.
Giving one undifferentiated price
Break it into lines and mark the genuinely optional ones. A buyer who cannot see what drives the cost has exactly one negotiating move available, and it is a discount on everything.
Restructuring an RFP response to suit your narrative
Follow their document, in their order, with their pricing format. Evaluators score against a rubric, cannot award points for what they cannot find, and non-conforming price schedules are routinely disqualified.
Ending with 'let us know your thoughts'
Name one action and a date. That sentence hands the decision back with no deadline attached, which is why so many proposals go quiet and get blamed on price.
Sending a proposal when a quote was wanted
Match the document to where the buyer is. Somebody who already knows what they want and asked for a price does not want six sections first, and the delay reads as a supplier who does not listen.
FAQ
Frequently asked questions
Ready to pick a layout?
Proposal Templates is at the top of this page. Free, no signup, nothing uploaded.
Guides
Read more on this topic
Articles that go deeper than this page has room for.