Proposals fail for one of two reasons: the price is wrong, or the proposal doesn’t make the decision easy. You can’t always fix the price. But you can always fix the document. These five elements are what separate proposals that get signed from those that get ignored.
1. A clear problem statement
The proposal should open with a brief description of the client’s situation in their words — not yours. One to three sentences that demonstrate you understood what they told you in the discovery call.
This section does two things: it confirms to the client that they’re reading a proposal written for them specifically, and it creates alignment on the goal before the solution appears.
Bad: “We are pleased to submit this proposal for your web development project.”
Better: “Your current website generates inquiries but doesn’t convert them to consultations — visitors land on the homepage and bounce before reaching the services page. The goal of this project is to redesign the navigation and services section to reduce that drop-off and increase consultation bookings.”
The second version names a specific problem. The client reads it and thinks: “Yes, that’s exactly the issue.” Now they’re primed to evaluate your solution against that problem, not in a vacuum.
2. Specific deliverables
Deliverables are the outputs you’ll produce. Not descriptions of work. Not categories. Specific, countable things.
Not specific: “Website redesign and copywriting” Specific: “Redesigned homepage, services page, and contact page — three pages total — built in Webflow, with up to two rounds of revisions, plus approximately 800 words of original copy for each page.”
Every vague deliverable is a potential dispute. Clients fill vague language with their own assumptions, and those assumptions are usually more generous than what you had in mind.
List every deliverable. If it’s not listed, it’s not in scope.
3. A timeline with milestones
The timeline answers three questions: when will we start, when will I need your input, and when will the work be done?
Include:
- Proposed start date (or a note that start date is subject to signed agreement)
- Client input milestones — points where you need feedback, content, or approval
- Delivery dates for major phases
- Final delivery date
Be explicit about dependencies. If the timeline assumes the client provides content within 5 business days of kickoff, say that. Client delays that blow up your timeline are easier to address when the proposal established the dependency in writing.
A timeline that shows the client’s responsibilities — not just yours — sets up the relationship correctly from the start.
4. Price and payment terms
Price should appear after the problem statement and deliverables — not before. A client who reads through a clear problem statement and a specific list of deliverables is mentally prepared to evaluate whether the price is fair. A client who sees a number before they understand what they’re getting has nothing to contextualize it against.
Include:
- Total price — one clear number or structured option (not a range)
- Payment structure — deposit, milestone payments, or full payment on completion
- Payment terms — when each payment is due (e.g., 50% on signing, 50% on delivery)
- What’s not included — this prevents scope creep arguments later
If you’re offering tiered pricing or options, keep it to two or three choices at most. More than three options create decision paralysis.
5. A clear next step
This is the most commonly missing element and the one that costs the most proposals.
“Let me know if you have questions” is not a next step. Neither is “looking forward to hearing from you.” These put the decision entirely on the client with no guidance on how to proceed.
A next step is specific: “To move forward, sign and date the proposal below and I’ll send you the kickoff invoice and confirm your start date.” Or: “Reply to this email with your approval and I’ll schedule a kickoff call for next week.”
Give the client one thing to do. Make it easy to do. Don’t ask them to think about it — ask them to act.
Putting it together in practice
These five elements don’t require a long proposal. A one-page document with:
- Two sentences of context (problem)
- A bulleted list (deliverables)
- A three-row table (timeline)
- One price line with payment terms
- One sentence (next step)
…is a complete, professional proposal. You can elaborate in each section for complex projects, but the skeleton above is the minimum.
Track whether clients are opening your proposals. If a proposal goes unread for several days, your follow-up strategy should be different than if the client opened it three times. Waco3’s proposal tracking shows you exactly that, so you follow up with context rather than guessing.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
