How to Write a Project Proposal That Wins (7 Sections)
To write a project proposal that wins, structure it in seven sections: the client's problem in their own words, the outcome you commit to, your approach in phases, a timeline with milestones, the team, the price with its scope, and terms. Decision makers read the first two sections carefully and skim the rest, so the proposal is won or lost on how precisely you restate their problem.
TLDR
- Seven sections in a fixed order; problem and outcome carry the decision.
- Restate the client's problem in their vocabulary, not your service categories.
- Always include the price, attached to exactly what it buys and excludes.
- Four to eight pages. Past ten, you are adding places for doubt to live.
- Track proposals in a pipeline with follow-up dates; unsent follow-ups lose more deals than pricing.
Section by section
1. The problem, in their words
Open with two or three sentences describing the client's situation using the phrases they used in discovery. This is the highest-leverage writing in the document: it proves you listened, and clients buy from people who heard them. Do not open with your company history; nobody has ever hired the history paragraph.
2. The outcome
One paragraph stating what will be true when the project succeeds, in observable terms: the store launches, the report exists, the process takes a day instead of a week. Outcomes sell; activities reassure.
3. The approach
Three to five phases, each with what happens and what the client receives. Phases show competence without drowning the reader in method.
4. Timeline
Milestones with dates or week numbers. If dates depend on client inputs, say which ones; this sentence saves relationships later.
5. The team
Who does the work, one line each. Names beat logos.
6. Price, with scope attached
The number, what it includes, what it excludes, and the payment schedule. A deposit belongs here (see our guide on payment terms that get you paid). A proposal without a price is a brochure the client cannot say yes to.
7. Terms
Validity window, revision rounds, ownership. Short and unambiguous.
Proposals that become projects
In Vivotics a won proposal converts into the client, the project and the invoice.
What ten years of pitching taught us
At Vivotic Solución we sent proposals for a decade, and two patterns separated the wins. First, speed: the proposal sent within 48 hours of the discovery call won disproportionately, because it landed while the conversation was still warm. Second, follow-up: a proposal without a scheduled follow-up date quietly expired. We lost more revenue to unsent follow-ups than to any competitor. That is why proposals in the Vivotics sales pipeline carry owners and next-action dates like any other deal stage.
After the yes
The proposal's last job is becoming the project brief. If your tools are connected, the accepted proposal converts into the client record, the project scope and the draft invoice without re-typing, so delivery starts from exactly what the client agreed to. That unbroken chain is the core argument of our complete guide to one-platform operations.
Key takeaways
- Win the proposal in the first two sections: their problem, your outcome.
- Price plus scope, always; deposits filter as well as fund.
- Send within 48 hours and schedule the follow-up before you hit send.
- A won proposal should become the project without re-typing.
Frequently asked questions
What are the sections of a project proposal?
Seven: the client problem in their words, the outcome you commit to, your approach in phases, a timeline with milestones, the team doing the work, the price with what it includes, and terms. In that order: decision makers read the first two and skim the rest.
How long should a project proposal be?
As short as credibility allows. For most service projects that is four to eight pages. Past ten pages you are not adding persuasion, you are adding places for doubt to hide.
Should you include the price in the proposal?
Yes, with scope attached to it. A proposal without a price is a brochure; the client cannot say yes to it. Present the number next to what it buys and what it excludes.
Ready to run everything in one workspace?
Projects, CRM, HR, payroll and invoicing, connected from day one.
Get started. It's FREE See pricing
