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 CFO 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 CFO 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 signed the most recent related filing, 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 CFO'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 CFO, 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.

Where this leaves a firm

None of this is complicated in principle, which is exactly why it gets skipped under deadline pressure. The question worth returning to before treating writing a proposal that is genuinely specific to one prospect as settled is what a careful reader would actually notice if the firm got it right. On the point raised above under “why committees are not actually the audience,” the answer is usually specific rather than clever: a proposal written to an undifferentiated committee usually persuades no one strongly. Firms that build this expectation into how they train new associates find it easier to sustain once experienced staff move on, because the standard lives in a documented habit rather than in one person's memory. The gap between a firm that talks about writing a proposal that is genuinely specific to one prospect and a firm that actually practices it shows up over several quarters, not in any single engagement, and it tends to show up most clearly in the small, unglamorous checks that a client never sees directly but benefits from anyway.

It also helps to name, plainly, who is responsible for keeping this working once the novelty of a new tool wears off. Someone should own the point raised under “what changes when you write to one person,” check it periodically rather than assume it stays true on its own, and be the person a colleague asks when a new situation does not fit the pattern described here. Put simply: research before drafting is what makes writing to a specific decision-maker possible. That kind of ownership, named and specific, is a small addition to a firm's process, and it is usually the difference between a good idea that is followed for a month and a standard that actually holds up over a year of real client work.

None of this needs to be elaborate to be effective. A short, dated note in a shared file, reviewed at the next quarterly check-in, is usually enough to keep the responsibility from quietly disappearing when the person who first cared about it moves on to something else.

VIPMarketing Editorial