January 24, 2026
Writing to the Decision-Maker, Not to the Committee
A proposal addressed generically to the evaluation committee tends to read as though it was written for no one in particular, because in an important sense, it was.
Why committees are not actually the audience
Even when a formal decision runs through a committee, one or two people usually carry the most influence over the outcome, often the budget owner or the person who will manage the relationship day to day. Writing with that specific person's priorities in mind, while still covering what the broader committee needs to see, produces a sharper document than writing to an undifferentiated group.
What changes when you write to one person
The framing of value shifts to match what that specific role cares about, a budget owner generally weighs cost predictability and risk more heavily than a technical evaluator might, who may weigh methodology and team depth more heavily. Naming the primary reader, even just for internal drafting purposes, sharpens which points get emphasized and which get shortened.
Finding out who that person actually is
Public information, who is quoted in recent company communications, who holds the specific title likely to own this decision, often points to the right person even without a direct conversation. Research done well before drafting begins is what makes writing to a specific person possible instead of guessing.
A caution about over-narrowing the audience
Writing to a specific decision-maker does not mean ignoring the rest of the committee's actual requirements, a technical evaluator on the committee still needs to see methodology and team depth addressed clearly, even if the primary emphasis is calibrated to the budget owner's priorities. The goal is sharper emphasis within a document that still covers everyone's real questions, not a document that satisfies one reader at the expense of the others.
A short way to check the balance before sending
Before finalizing a proposal, have someone other than the primary drafter read it specifically as if they were the technical evaluator on the committee, not the budget owner, and confirm their questions are still clearly answered. This second read, from a deliberately different vantage point, catches the case where emphasis on the primary decision-maker has gone so far that other legitimate readers are left with real, unanswered questions.
A short note on the risk of over-indexing on a single past win
A proposal style that won once with a particular decision-maker can tempt a team to apply the exact same framing to every future prospect with a similar title, even when the individual's actual priorities differ. Researching the specific person, every time, remains more reliable than assuming a title predicts a priority.
A short note on the relationship between proposal quality and win rate over time
A single well-crafted proposal rarely explains a meaningful shift in a firm's overall win rate, since any one outcome is influenced by many factors outside the document itself. The more reliable signal comes from tracking a consistent standard, the swap test, the scope-and-assumptions discipline, applied across dozens of proposals over a year, and watching whether the aggregate win rate moves, rather than judging the standard by any single deal.
This longer view also protects a firm from overreacting to a single loss on an otherwise well-built proposal, since some prospects were never winnable on price or fit regardless of how the document was written, and a good process should be judged on its aggregate results, not on any one outcome it could not have controlled.
A final word on what separates a good proposal process from a good proposal
Any individual proposal can be improved with enough time and attention from a skilled writer. What is harder, and more valuable, is a process that reliably produces a good proposal under normal time pressure, for the tenth prospect of the month as well as the first. The tests and checklists described throughout this piece exist for that reason, to make the tenth proposal as sound as the first one, not to make any single document perfect.
Key takeaways
- A proposal written to an undifferentiated committee usually persuades no one strongly.
- One or two people typically carry the most real influence, even in a committee process.
- Match the emphasis of the proposal to what that specific role is known to weigh most heavily.
- Research before drafting is what makes writing to a specific decision-maker possible.
Questions, answered
What is the short answer on Writing to the Decision-Maker, Not to the Committee?
Proposals often try to speak to everyone in the room at once and end up persuading no one specifically. A sharper approach names the actual decision-maker.
What are the key takeaways?
A proposal written to an undifferentiated committee usually persuades no one strongly. One or two people typically carry the most real influence, even in a committee process. Match the emphasis of the proposal to what that specific role is known to weigh most heavily. Research before drafting is what makes writing to a specific decision-maker possible.
How does VIPMarketing approach proposal automation?
VIPMarketing drafts each proposal from what the account is doing and your own library of past proposals, decks and case studies. Your approver signs off before it goes out as Word, PDF or PowerPoint.