Tip: Write Better Proposals With a Simple Three-Part Structure

Bychris

Why Most Proposals Lose Before the Client Even Reads the Price

Most creative and consulting proposals fail not because the number is too high, but because the client reaches that number without any real reason to say yes. Structure fixes that problem before you ever touch your pricing.

A proposal is a sales document. That sounds obvious, but many freelancers and small agencies write proposals as if they are project plans — lists of deliverables, timelines, and line items dropped in front of someone who is still trying to figure out whether they trust you. When a client reads a proposal and feels confused or unheard, they default to the only concrete thing on the page: the price. And a price without context almost always feels high.

The fix is not better design, a fancier PDF template, or more detailed scope breakdowns. The fix is sequence. A simple three-part structure — situation, solution, investment — reorders the information so that every section does specific persuasive work before the next one begins.

The Core Problem: Deliverables Are Not Arguments

Before getting into the structure itself, it helps to understand what goes wrong in a typical proposal. A common format looks roughly like this: a brief intro paragraph, a scope of work list, a timeline, a price table, and payment terms. This format is logical, but logic is not persuasion.

When you lead with deliverables — “three logo concepts, two rounds of revision, final files in all formats” — you are describing what you will produce, not why it matters. The client is left to draw their own conclusions about the value. Most clients are not skilled at making that connection on their own, especially when they are evaluating multiple proposals at once.

A three-part structure does not hide deliverables. It frames them. The deliverables appear inside a narrative that has already established the problem, the stakes, and the logic of your approach. By the time a client reads what you will deliver, they understand why each piece matters.

Part One: Situation — Show Them You Were Listening

The situation section is short. Two or three paragraphs is usually enough. Its only job is to demonstrate that you understand the client’s problem with precision — not in general terms, but in the specific terms they used when they described it to you.

This means going back to your discovery call notes and pulling out the language the client actually used. If they said, “We’re losing bids to competitors who look more established,” that phrase belongs in your situation section, paraphrased closely enough that they recognize it. If they mentioned a specific event — a product launch, a rebrand after a merger, a website that’s embarrassing to share — name it.

What you are doing here is passing a test the client is giving you without realizing it. Every client who hands you money is implicitly asking: Does this person understand what I actually need, or are they going to solve the wrong problem beautifully? The situation section answers that question before they have to ask it.

A few things to avoid in this section:

  • Generic problem statements. “Many businesses struggle with brand consistency” tells the client nothing about their specific situation. It signals template, not thought.
  • Overlong history recaps. You are not writing a case study. One crisp paragraph showing you understand the core tension is more powerful than a thorough summary.
  • Your credentials. Save those for elsewhere. This section is entirely about them.

When a client reads a situation section that mirrors their actual thinking back to them clearly, the emotional effect is immediate. They feel heard. That feeling is the foundation every other section builds on.

Part Two: Solution — Translate Deliverables Into Outcomes

This is where most proposals have the most room to improve. The solution section describes what you will do — but always in terms of what changes for the client, not just what you will hand over.

Consider the difference between these two ways of describing the same work:

  • Deliverable framing: “I will design a primary logo, a secondary logo mark, and a color palette with a style guide.”
  • Outcome framing: “You’ll leave this engagement with a visual identity that positions you clearly in your market — one that gives enterprise clients confidence before the first meeting and that your team can apply consistently without coming back to a designer every time.”

Both describe the same work. Only one of them makes the client want it.

Outcome framing requires that you actually understand what the client is trying to accomplish beyond the immediate deliverable. This is why discovery matters so much. If you know that the client is preparing for a trade show in four months and needs to look credible next to well-funded competitors, you can write a solution section that speaks directly to that. The logo becomes evidence of seriousness. The style guide becomes a tool that helps their marketing coordinator execute without bottlenecks. Each deliverable gets a reason to exist.

Structure the solution section so it moves from approach to process to outcomes:

  • Approach: Your overall philosophy for this type of problem — brief, one paragraph.
  • Process: What the engagement actually looks like, phase by phase. Keep this readable, not exhaustive. Clients want to understand the journey, not approve every step of it.
  • Outcomes: What the client will have and how it will function when you’re done. This is where you name the specific changes — operational, perceptual, competitive — that your work makes possible.

One useful exercise: after you draft this section, read it and ask whether a client could understand the value without knowing anything about design, development, or your specific craft. If the value only makes sense to someone who already understands your process, rewrite it in plain language.

Part Three: Investment — Price With Context

The word “investment” is not just softer language for “price.” It signals that what follows is a return-generating decision, not an expense. Use it deliberately.

By the time a client reaches this section, they have read a clear articulation of their own problem and a compelling description of how your work solves it. They arrive at the number with context, not cold. That context does not guarantee they will accept the price, but it ensures they are evaluating it against value rather than against a blank wall.

Present pricing clearly. Avoid overly granular line-item breakdowns unless the client specifically needs them for internal approvals. When proposals itemize every hour and sub-task, clients naturally start picking apart individual lines and asking whether they need each one. A package or phase-based structure — “Phase 1: Discovery and Strategy — $X” — keeps the focus on the outcome of each phase rather than the mechanics of how you get there.

A few practical details that belong in this section:

  • What is included and what is explicitly not included. Scope boundaries prevent misaligned expectations later and signal that you have thought carefully about the engagement.
  • Payment terms. State them plainly: deposit amount, milestone payments if applicable, final payment timing.
  • Revision policy. If you include a set number of revision rounds, say so here, not buried in a terms document.

The Call to Action and the Time Limit

A proposal without a clear next step leaves the decision floating. End every proposal with a specific instruction: “To move forward, sign below and submit the deposit by [date]” or “Reply to this proposal to confirm you’d like to proceed and I’ll send the contract and invoice.” Make it easy to say yes.

Include a reasonable expiration date — typically seven to fourteen days from delivery. This is not a pressure tactic. It is honest about how you work: your availability changes, material costs may shift, and you cannot hold a project start date indefinitely. An expiration also creates light urgency that moves slow decision-makers to act. Clients who have wanted to hire you but keep putting off the reply often just need a gentle external deadline.

State the expiration date plainly: “This proposal is valid through [date]. After that point, please reach out to confirm availability before proceeding.” That framing is professional and non-aggressive while still doing its job.

A Note on Length and Format

A strong proposal is usually between one and three pages. Longer proposals are not more thorough — they are more likely to be skimmed. If you find yourself writing more than three pages, that is usually a sign that the solution section is drifting into project management detail rather than staying focused on outcomes and approach.

Use white space generously. Short paragraphs. Subheadings within each section if the content warrants them. A proposal that looks easy to read gets read. A dense wall of text gets scrolled to the price.

If you are using proposal software, the same structure applies regardless of the tool. The sequence — situation, solution, investment — is what does the persuasive work. The platform just delivers it.

Putting It Into Practice

The next time you sit down to write a proposal, open with a blank document and write the situation section first, without looking at a previous proposal template. Force yourself to describe this client’s specific problem in their own language. Then write the solution section in outcomes, not deliverables. Then present the price.

You will likely find that the first draft of the situation section is still too generic. That is normal. Revise it until you could not send it to any other client — until it reads like you were paying close attention to this conversation, this person, this problem.

That specificity is what converts. Not the price, not the template, not the PDF design. A client who feels genuinely understood is a client who is ready to say yes.

Related reading

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *