Freelancers often make proposals more complicated than clients need them to be. A ten-section document with a cover page and testimonials can actually slow down the decision process. For most projects, simple is better.
The instinct to make proposals comprehensive comes from a reasonable place: you want to show you’ve thought everything through, demonstrate your expertise, and justify the price. The problem is that more content creates more things to question, more reasons to ask for a call before deciding, and more friction between the client and a yes.
Simple proposals move faster. Here’s how to make one that works.
The four things every proposal needs
No matter how short your proposal is, it must answer these four questions:
1. What’s the situation? One to three sentences establishing that you understand what the client needs. Not a lengthy analysis—just enough to show you were listening.
2. What will you deliver? A specific list of deliverables with a timeline. “Homepage redesign, about page, and services page — delivered as a Figma prototype in two weeks” is better than “a complete website redesign process.”
3. What does it cost? State the price clearly. A single number or a small range. Avoid pricing structures so complex they require explanation.
4. What’s next? Tell them exactly what to do. “Review and sign below” or “reply to this email to confirm” or “schedule a kickoff call at this link.”
That’s the whole proposal for most projects. Four elements, one to two pages, done.
What to cut from a typical proposal
If you’re currently writing long proposals, here’s what you can almost always remove:
Your full biography. A sentence about your relevant experience is enough. Clients can look you up if they want to know more. A full paragraph about your background mid-proposal breaks the momentum.
Your process description. Clients care about outcomes, not methodology. “Here’s my seven-step design process” adds length without adding value. If the client asks how you work, tell them. Don’t front-load it.
Case studies. Save these for your portfolio or a separate document. A two-paragraph case study in the middle of a proposal interrupts the reader’s path to the decision.
Terms and conditions. If you need detailed terms, put them in the contract, not the proposal. A short reference to your standard payment terms is fine—a full legal section is not.
Testimonials. You’ve already been hired to write this proposal, which means you’ve already cleared the trust threshold. Adding testimonials to a proposal you were asked to write is redundant.
Every line in your proposal should be moving the client toward a decision. If a section is answering a question they didn’t ask, cut it. If it’s building trust you already have, cut it. Proposals aren’t portfolios.
A simple proposal structure that works
Here’s a one-page proposal format that handles most freelance projects:
[Client Name] — [Project Name] Proposed by [Your Name] | [Date]
The situation [1–3 sentences about what the client needs and why it matters.]
What I’ll deliver
- [Deliverable 1] — [brief description]
- [Deliverable 2] — [brief description]
- [Deliverable 3] — [brief description]
Timeline [Start date] → [Delivery date]
Investment $[Amount] — [Payment terms: e.g., 50% upfront, 50% on delivery]
To move forward [Clear next step: sign below / reply to confirm / schedule kickoff call]
That’s it. For projects under $5,000, this format handles almost everything.
When to add more
Some situations call for a longer proposal:
- The client explicitly asked for a detailed proposal
- The project is complex enough that scope ambiguity could cause disputes
- The price is high enough that the client needs more context to feel confident
- Multiple decision-makers will review the proposal
In those cases, add sections as needed—but keep the same discipline. Every addition should serve the client’s decision-making process, not your desire to appear thorough.
The simple proposal and follow-up
Simple proposals tend to generate responses faster than complex ones. When you send a short, clear proposal, the client’s next action is obvious. That said, you still need to follow up.
Wait two to three business days after sending, then check in with a short message. If you can see when the client opened your proposal—which tools like Waco3 make possible—you can time that follow-up for right after they’ve read it, when it’s freshest in their mind.
The combination of a simple proposal and a well-timed follow-up closes more work than a complex proposal followed by a vague “let me know if you have questions.”
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
