Your champion loves your proposal. Their CFO has questions about ROI. Their procurement manager wants to see contract terms. Their technical lead wants to understand your methodology. One generic proposal can’t satisfy all four, and the one it fails to satisfy is often the one with veto power.
The Multi-Stakeholder Reality
The Challenger Sale documents a consistent pattern in B2B deals: the average enterprise purchase decision involves 5.4 stakeholders, each with distinct priorities and concerns. Even in mid-market deals ($25K–$150K), it’s common for 2–4 people to review a proposal before it’s approved.
Most freelancers and consultants write proposals for their champion, the person they talked to, the person who seems excited about the project. That’s the wrong target. The champion is already sold. The people who need convincing are the ones who didn’t participate in discovery and have only the proposal to go on.
The Multi-Persona Proposal framework designs each section for a specific reader, in the language they use, answering the question they’re actually asking.
The Four Buyer Personas and What They Need
Persona 1, The Executive (CEO, CMO, VP) What they’re asking: Is this worth the investment? What they read: Executive summary only. What they need: Business problem (one sentence), expected outcome (quantified), investment (contextualized against the outcome), timeline (specific). Word limit: 200–250 words. No methodology. No deliverable lists. No process.
Persona 2, The Director (Project owner, department head, champion) What they’re asking: Will this actually work? What they read: Situation analysis, methodology, team qualifications, case studies. What they need: Evidence that you understand their specific context, a credible phased approach, proof from comparable engagements. Word limit: 600–900 words across these sections. They read thoroughly, earn it.
Persona 3, Procurement (Operations, Legal, Finance) What they’re asking: Is this contractually clean? What they read: Investment section, terms summary, risk section. What they need: Defined scope, payment schedule, IP ownership, termination clause, liability cap. Word limit: Keep this section scannable. Use bullet points and headers, procurement is looking for specific items, not reading narrative.
Persona 4, The Technical Lead (CTO, IT director, engineering manager) What they’re asking: Can they actually do this, and will it integrate with what we have? What they read: Methodology details, team qualifications, security and compliance section. What they need: Specificity about tools and platforms, named team members with relevant technical experience, any security or data handling protocols.
Every section in your proposal has a primary reader. Write the section header and opening line as if that specific person opened directly to this page and has 60 seconds to decide whether to keep reading.
Structuring the Document for Navigation
A multi-persona proposal only works if readers can navigate to their section without reading everything first. Required structural elements:
Table of contents with page numbers. Required for any proposal over 6 pages. Each section name should tell the reader what they’ll find, not just label the content type. “Investment and Expected Return” is better than “Pricing.” “Risk Mitigation and Assumptions” is better than “Terms.”
Section headers as entry points. Each section should work as a standalone read. The opening line of each section should orient the new reader, don’t assume they read the section before it.
Cover email routing. “For executive overview, see pages 1–2. For technical methodology, see section 4. For contract terms, see section 10.” This one paragraph in your email tells the champion exactly how to route the document internally, which they’ll appreciate, because they’ve been wondering how to do it.
The Executive Summary Is Not a Summary
Most consultants treat the executive summary as a compressed version of the full proposal. That’s wrong. The executive summary is a standalone business case, it assumes the reader will read nothing else. It should include:
- The specific business problem and its cost (not a vague description)
- The proposed approach in two sentences
- The expected outcome with a specific metric and timeline
- The investment, contextualized as a ratio (“$38,000 to address an estimated $310,000 in annual impact”)
- The next step
If the executive reads only this page and forwards it to procurement, the deal should still be able to close. Design the executive summary to survive without the rest of the document.
The Risk Section Wins Procurement
Procurement reviewers reject proposals not because they’re too expensive, but because they expose the company to undefined risk. A single half-page “risk and assumptions” section that addresses scope, timeline, IP, and termination will move your proposal faster through internal review than any additional case study.
Keep it matter-of-fact: “This engagement is scoped to [specific deliverables]. Changes to scope will be handled through a written change order. All work product created in this engagement is owned by [client] upon receipt of final payment.”
Applying This to Smaller Deals
You don’t need four distinct sections for a $15K project. But even at that scale, if you know two people will review the proposal, write the executive summary for the one who didn’t attend your call. That one page, 200 words, business problem, outcome, investment, doubles as an internal selling tool your champion can use when you’re not in the room.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
