Module 05 of 7
Words That Travel Without You
Contextual congruence: build a deal your champion can re-pitch, in the room you can't enter.
From Chapter 5 · Contextual Congruence
Build a pitch that survives the room you can't enter.
Most deals aren't decided in the meeting you're in. They're decided in a Slack thread, a hallway, or a five-minute readout to the CFO — by people you'll never meet, using words your champion had to remember on the fly. If your message can't survive that trip, the deal dies as “no decision.”
The Champion Carry Test: could a busy, half-distracted champion re-deliver your pitch to the Observant Middle, finance, and procurement — accurately, in three sentences, without you in the room? If not, you don't have a message. You have a meeting.
Your champion loving you is nice. Your champion being able to quote you, accurately, on a Tuesday, with the CFO in the room — that's what closes.
The rooms you won't be in
Each unseen stakeholder is running one question in their head. Your message either answers it in one line — or gets filed.
| Stakeholder | The one question they're actually asking |
|---|---|
| The Observant Middle | “Is this going to make my week harder or easier? Whose side does it put me on?” |
| The CFO / Finance | “What does this replace, what does it cost fully loaded, and how do I explain it in one line?” |
| Procurement | “Where's the risk, where's the wiggle room, and what's the comparable I can benchmark against?” |
| Security / IT / Legal | “What breaks? What's the blast radius if this goes sideways? Who owns it then?” |
Who's carrying it, into which room
Be specific. A named person, a real room, a real week. “The exec team” isn't a room. “Tuesday's staff meeting, after the roadmap review” is.
Write the three carry lines
The most your champion will actually remember: why now, what it costs, what it's worth. One sentence each. Plain-spoken. No adjectives that need a slide to earn them.
Run the Champion Carry Test
Read your three lines out loud, once. Now try to recite them from memory a minute later. If you can't, your champion won't. Then answer honestly:
Build the one artifact they'll actually forward
Not the 40-slide deck. One page — or one email — your champion can paste into a thread without editing. Includes the three carry lines, the skeptic's objection answered upfront, and one costly signal from Module 3.
Also from Chapter 5 · Context is the other half
The right words in the wrong room, channel, or moment still read as noise.
Congruence isn't only about what you say. It's about where it lands. A perfectly-crafted message sent through the wrong channel, at the wrong hour, into a room that's already made up its mind — is a message the buyer's bouncer files under didn't get it.
Two contextual moves keep the carry-lines from getting bounced: match the channel's weight to the message's weight, and pack the context into pricing before pricing gets audited without you.
Channel weight vs. message weight
The channel is already talking before your words get a turn. When the weight doesn't match, people decide you don't get it before they read a word.
| The heavy message | What the wrong channel signals |
|---|---|
| A price increase mid-cycle | Sent over Slack — “this wasn't important enough to look you in the eye.” |
| A timeline slip on a committed date | Buried in a status email — “I was hoping you wouldn't notice.” |
| Bad news about a person or account owner change | Announced in a group thread — “I'd rather not have the one-on-one conversation.” |
| A pricing negotiation ask | Dropped into a calendar invite title — “I want the concession without the conversation.” |
Pick the right channel
Audit the last heavy thing you sent on this deal. Before the words, what did the channel say for you?
The pricing context block
Your pricing will be audited in a room without you — against a cheaper competitor, an AI benchmark, a board member's cousin's quote. If the explanation arrives after the audit, it reads as spin. If it arrives before, it reads as context. Pack it in.
Scoreboard Stop
Log one leak, one cost, one fix.
Flip back to the Signal Scoreboard and log Module 5: the leak, its cost in days / discount points / probability, and the fix you're running by Tuesday. Not someday. Tuesday.