Section 1
Key takeaways
• Buyers spend only 17% of their buying time with sales reps; the deal is decided in the other 83%, internally, where your champion is your only voice . • A complex B2B purchase is decided by a buying group of six to ten people, most of whom you will never meet, all of whom your champion has to convince for you . • 95% of buying groups reopen a decision when new information surfaces, so a champion email that pre-answers the objection protects the deal from being reopened . • Buyers who get genuinely helpful supplier information are 2.8x more likely to find the purchase easy and 3x more likely to buy a bigger deal with less regret, that is the measurable ROI of doing your champion's homework . • The fitness test for the email: if your champion forwarded it without changing a word, would it still sell? If not, rewrite it.
Section 2
Why the meeting you run matters less than you think
Here is the uncomfortable arithmetic. The average IT buying cycle runs 16.3 months, and only about 17% of it is spent with suppliers . Multiply that out and your champion is alone with your deal, defending it, re-explaining it, keeping it alive, for well over a year. You get a handful of calls. They get the other fourteen months. And they are not defending it to a friendly audience. The typical buying group for a complex B2B solution is six to ten decision-makers . That is six to ten people with different incentives: a CFO who cares about cash, a head of ops who cares about disruption, a security lead who cares about risk, a skeptic who cares about being right. Your champion has to carry your case to each of them, usually secondhand, usually from memory, usually in a forwarded thread or a two-line Slack message. So the friction is real. 77% of buyers describe their most recent purchase as "very complex or difficult" . That difficulty is not happening on your calls. It is happening in the rooms you are not in. Your champion is the one absorbing it. Most sellers respond to this by sending their champion more, a longer deck, a recorded demo, a 12-tab pricing model. That makes it worse. As the buyer-enablement research puts it bluntly, more information has not made buying easier; it has made it harder. Your champion cannot forward a 40-slide deck into a budget review and expect anyone to read it. What they can forward is one clean email that makes the case in the time it takes to read it. This is the same discipline that runs through how you qualify the deal in the first place and how you handle objections before they're spoken. The champion email is where those two jobs meet on a single page.
Section 3
What is buyer enablement, and why does the champion email sit at the center of it?
Buyer enablement is the practice of giving the buyer the specific information and tools they need to complete a purchase, not the information you need to make a sale. Brent Adamson, who originated the concept at Gartner and co-wrote The Challenger Customer, framed the whole shift in one line: "Concentrate on making products easy to buy, not easy to sell.", Brent Adamson, co-author of The Challenger Customer Read that again with your champion in mind. "Easy to buy" does not mean easy for the person on your call. It means easy for the eight other people deciding behind closed doors. The champion email is the most concrete buyer-enablement asset there is: it is the literal document your buyer uses to do the buying. And the buying is mostly internal coordination. In the buyer-journey breakdown, building internal consensus consumes 22% of the buyer's time, more than they spend meeting any single supplier . That 22% is exactly the work the forwardable email is doing on your champion's behalf. You are not writing a sales email. You are writing a consensus-building tool and handing your champion the credit for it.
Section 4
Concrete example: a fractional CFO selling into a 40-person agency
Make it real before abstracting it. Say you run a fractional-CFO service. Your champion is the agency's head of operations. She loves you. But she does not control the budget, the two founders do, and one of them thinks "we can just hire a bookkeeper for a third of the price." You will never be in the room when that founder pushes back. Your champion will. So the email you send her after your second call should not say "Hi Sarah, great chatting, here's the proposal attached, let me know." That email dies on the first forward, because a busy founder opening it sees a vendor pitch and archives it in seconds. Instead you write the email she can forward to the skeptical founder with one line on top, "Sharing the summary from the CFO conversation, my read below." The body has to do four jobs she cannot do as well as you can: state the business outcome, carry one number she can repeat from memory, kill the "just hire a bookkeeper" objection before it's raised, and ask for something so small the founder can say yes in one reply. That is the entire game. Everything below is how you build that email so it survives the forward.
Section 5
The BGA framework: Doing the Champion's Homework, the Forwardable Five
Five load-bearing parts, in order. Each one earns its place. Cut any one and the email stops being forwardable. 1. The Outcome Headline. The subject line and first sentence state the business result, not your product. A busy exec decides whether to read or archive a forwarded email in seconds, so the point has to land first. • Bad subject: "Proposal, Fractional CFO Services." Good subject: "Plan to free up ~$18K/month in trapped cash before Q4." • First sentence states the outcome in the buyer's language: "Short version: this gets us monthly board-ready numbers and a cash runway we can actually plan against, without adding a full-time finance hire." • Rule of thumb: if the founder could read only the subject and first sentence and still know what they're being asked to fund, you passed. 2. The ROI Line. One sentence, one defensible number, repeatable from memory without opening a spreadsheet. Your champion will not have the model in front of her when the question comes up in a hallway. She needs a single figure she can say out loud. • "Comparable agencies recover 2–3 months of runway visibility in the first quarter; the engagement pays for itself if it prevents one bad hiring decision." • Anchor it to why helpfulness wins, not just price: buyers who get genuinely useful information are 3x more likely to approve a bigger deal with less regret . The ROI line is you being useful, in one sentence, on her behalf. • Rule of thumb: one number, one claim, no range wider than 2x. A precise-sounding number your champion can't defend is worse than a round one she can. 3. The Pre-Loaded Objection Kill. Name the single question the skeptic will raise, cost, risk, or lift (the effort to implement), and answer it inside the body. You do this because 95% of buying groups reopen a decision the moment new information surfaces . If the "just hire a bookkeeper" objection shows up after your email, the decision reopens and you're not there to defend it. So you put the answer in first. • "Why not just hire a bookkeeper? A bookkeeper records what happened; this is forward-looking cash and board reporting. Different job. We'd actually recommend keeping your bookkeeper and layering this on top." • Pick the one objection that kills deals like this, not all five you can think of. One pre-empted objection reads as honesty; five reads as defensiveness. • This is the same move as arming your champion with the answer to the price question, except you're doing it in writing, before the question is asked. 4. The Low-Friction Ask. Request the smallest possible next step. Never "let's find time for a 60-minute demo." The bigger the ask, the more your champion has to spend her own credibility to get it scheduled. • Good asks: "a 4–6 minute call to confirm scope," or a plain yes/no, "Does freeing up that cash visibility before Q4 sound worth a short conversation?", or simply "feel free to forward this to [skeptic] for a gut check." • A yes/no question your champion can answer for the skeptic ("she said yes") moves faster than any calendar invite. • Rule of thumb: if the next step needs a meeting longer than 15 minutes, you've asked for too much for a forwarded email. Shrink it. 5. The Forwardable Format. Strip everything that breaks on a forward. No "Hi Sarah, great chatting." No thread cruft. No "see attached", a skeptic will not download a PDF to evaluate a deal they didn't ask about. Write it in your champion's voice, so she can hit forward with one line on top and it reads as her thinking, not a vendor's pitch she's relaying. • Length: short enough to read on a phone without scrolling twice. Roughly 120–180 words in the body. • Voice check: read it as if your champion wrote it. If a phrase only a salesperson would use survives ("circle back," "value prop," "solution"), cut it. • Put the key numbers and the ask in the body text, not in a deck. The deck is for the call you already had. The email is for the room you'll never enter. Run those five in order and you've built a tool, not a touchpoint. This is the LeadOS habit of making the buyer's internal job easier, applied to the single most-forwarded document in the deal. If you want the full version with templates and the objection-kill bank, the LeadOS playbook and the Template Pack both build it out.
Section 6
How do you know which objection to pre-load?
Ask your champion directly, on the call, before you write anything: "When you take this internally, who pushes back, and what do they say?" Whatever name and sentence she gives you is your number-three. You are not guessing the skeptic's objection, you are quoting it back to her, pre-answered, so she walks in armed. If she can't name the objection, that is your signal the deal isn't qualified yet, not your signal to write a cleverer email. A champion who doesn't know where the resistance lives can't carry your case through 22% of a buying journey spent on internal consensus . Fix the qualification first. A quick gut-check on the call is a fast way to see whether you actually have a champion or just a fan.
Section 7
You're running the Forwardable Five right when…
You're running it right when your champion can forward your email to a CFO she reports to, add one sentence on top, and not feel like she's relaying a sales pitch, because the outcome is stated first, the one number is hers to repeat, the obvious objection is already answered, and the ask is small enough to approve from a phone. You're running it right when the skeptic replies to her, not to you, and the reply is a yes/no rather than a request for "more information." And you're running it right when you can no longer tell, reading the email back, whether your champion wrote it or you did. If any of those fail, if the subject line names your product, if the number needs a spreadsheet, if the ask is a 60-minute demo, if it reads like a vendor, you wrote your homework, not theirs. Rewrite it until it forwards.