Social
Capture buying signals and run Director-to-VP conversations where the stakeholder is verifiably active.
- Personalization4
- Scale3
- Trust2
- Speed3
- Cost4
- Enterprise fit4
AN INTERACTIVE OPERATING SYSTEM FOR ENTERPRISE ACQUISITION
Catch the TunaThe Enterprise Acquisition Operating System
you don't catch tuna by casting wider
Nine instruments run one enterprise deal end to end, from an ocean of 41,000 companies to a signed contract. Three deals exist, one industry each, and the eight modules that do the work run identically in all three.
Enterprise deals are not won by better messages. They are won by state, evidence, and coverage: sensors that keep the picture current, policies that turn it into action, and loops that correct both.
The dive plan, 9 steps from open water to the verified close.
- Module 01: Waters, Market Definition & ICP
- Module 02: Sonar, Buying-Signal Intelligence
- Module 03: Species, Account Prioritization & Capacity
- Module 04: Nets, Channel Selection & Orchestration
- Module 05: Stakeholders, Buying Committee & Multi-Threading
- Module 06: Discovery, Discovery & Problem Quantification
- Module 07: Consensus, Consensus & the Internal Sale
- Module 08: Closing, Procurement & the Verified Close
- Synthesis: The Bridge, Deal Integrity & the Operating Loop
*Meridian, Helm, Baltica, and everyone you meet here are fictional. The mechanics are not.
MODULE 01 · OPEN WATER
Waters · Market Definition & ICP
know your waters before you cast
You are at the surface of the system. Everything below operates on the universe this module defines, so nothing downstream works until this does.
An ICP is a falsifiable hypothesis, not a demographic wishlist. The claim has a fixed shape: companies where a structural condition holds hit a specific problem at a measurable cost, are triggered to act by known events, and buy through a predictable committee. Industry, size, and geography are proxies for that condition. They are not the condition.
The test of a defined market is enumeration: a named list you could read aloud, not a filter description and not a spreadsheet TAM. The map below starts at 2,515,000 companies across 9 industries and 9 regions, on every continent. Each cut deletes the accounts that fail one layer of your hypothesis. What survives should be small enough to operate and large enough to carry a number.
9 industries, 9 regions, 6 size bands, 6 revenue models. The control deck below is the funnel itself: nine tiers, each one narrower than the tier above it, each carrying the count that survived its cut. Set the seven cuts and watch the column thin beside them. The instrument opens on the slice the rest of this page works, so start by changing the industry to yours.
INSTRUMENT 01 · MARKET MAP
SERVICEABLE UNIVERSE
120accounts
0.005% of the 2,515,000 companies on the map.
ICP HYPOTHESIS
Multi-site terminal and port operations in Continental Europe, 1,000 to 10,000 employees, earning through transaction and service fees, and metered usage. The claim: they lose more every year to SLA penalties they discover only after the money is already owed than fixing it would cost, and a VP already owns the number it shows up in. Serviceable under residency we can meet, a security review we pass today, no incumbent lock, and delivery coverage we already have: 120 accounts you could name.
This is wrong if the penalty exposure turns out to be insured rather than absorbed. Then you are in the wrong waters.
Operable universev1 · refit quarterly
REGION FRICTION+25 days
GDPR, plus in-country hosting expectations in Germany and France that go past the letter of the law. Transfer questions arrive in the first call.
Works councils and the data protection officer sit inside the cycle, not after it. Plan for both or lose two months.
Meridian Freight Group sits inside this slice. That is the account modules 02 to 08 work end to end.
Total watersevery company on the map2,515,000
Industrylogistics and supply chain400,000
Segmentmulti-site terminal and port operations24,000
RegionContinental Europe4,107
Company size1,000 to 10,000 employees1,142
Business modeltransactional and services, and usage-based869
Serviceableaccounts you can legally and practically serve315
Reachable at VPa VP who owns the number120
120 accounts you could name, reachable at VP level. Every constraint you set here is a deal you will not lose six months in.
Nine tiers, each one narrower than the tier above it. The mouth is every company on the map, the seven cuts are your hypothesis one layer at a time, and the catch is what survives all of them. It opens on the slice the rest of this page works. Change the industry to yours.
Total watersEvery company on the mapthe whole ocean2,515,000
1IndustryLogistics and supply chainkeeps 16%400,000
The ocean you fish. Everything below is a cut inside it.
SLA penalties they discover only after the money is already owed.
2SegmentMulti-site terminal and port operationskeeps 6.0%24,000
Where the problem structurally lives, not where the logo looks good. Leave every box clear to keep the whole industry.
Few operators, heavy assets, penalty clauses with teeth. The seeded slice.
3RegionContinental Europekeeps 17%4,107
Geography is not a filter. It is a different sales motion. Leave every box clear to keep all of them.
Works councils and the data protection officer sit inside the cycle, not after it. Plan for both or lose two months.
4Company size1,000 to 10,000 employeeskeeps 28%1,142
A proxy for the problem reaching economic scale. Never the ICP itself.
Employees1,000 to 10,000
minmax
The floor of the range decides the motion. At 1,000 to 2,500 employees: multi-site problems become real. So does the internal sale.
5Business model2 modelskeeps 76%869
How they earn decides who owns your budget line. Leave every box clear to keep all of them.
2 revenue models. Check that your pricing shape survives all of them before you commit.
6Serviceability4 of 4 appliedkeeps 36%315
Accounts you can legally and practically serve. The cost is per region.
7Buyer altitudeVPkeeps 38%120
Not how many exist. How many you can actually get into at that level. Access and authority move in opposite directions, so pick the rung knowing both.
120 reachable at VP level, 74 of them able to commit. The other 46 are an internal sale you do not get to run.
- Buys you
- Commit the budget, set the timeline, and overrule the incumbent preference below them.
- Never buys you
- Be reached by volume. Every route here costs trust you have to have earned first.
Hard to reach, able to decide. The best trade on the ladder, which is why it is crowded.
The catchAccounts you could name0.005% of the ocean120
◦ Defaults, not laws. Recalibrate against your last 20 closed deals.
The mechanism
The bands are your hypothesis, one layer at a time. Read the chain the instrument opens on: 2,515,000 companies on the map, 400,000 once you pick an industry, 24,000 in the segment where the problem is structural, 4,107 in the regions you can sell into, 1,142 where it reaches economic scale, 869 whose revenue model matches your pricing, 315 you can legally and practically serve, and 120 you can actually reach at the level that owns the number. Change any control and every one of those figures is recomputed from the same arithmetic. None of them is looked up in a table.
The failure-mode reading
Notice what the counter never shows: a percentage of a $40B TAM. Push the filters one way and you get 43,836 accounts, a whole industry with no segment, no region, and no size discipline. That is a filter description, not a market. Push them the other way, keep only the 10,000-plus band, and the universe collapses to 9 accounts: not focus, a rounding error with a strategy deck attached. One lost deal would rewrite the whole model. Both failures are reachable in every industry on the map, which is the point.
Your waters, not mine
The instrument seeds on logistics and supply chain in Continental Europe because that is where Meridian Freight Group sits, and modules 02 to 08 work that one deal end to end: 4,200 employees, 43 terminals, Terminal data silos → manual SLA reporting → SLA-penalty exposure, worth $2.3M/yr. That is an example, not the subject. Set the industry to software, the region to Brazil, the altitude to director, and the map, the count, and the hypothesis all rewrite around you. The arithmetic does not care which ocean you fish.
Framework · ABM (Account-Based Marketing)
- What it does
- Treats a named list of accounts as the market: you enumerate the accounts, work them as individual markets, and stop buying reach against a segment.
- When to use it
- From the moment your deal size makes any single account worth weeks of work, which is the whole enterprise motion.
- What it prevents
- Volume targeting spreads a finite team across accounts that were never winnable, so nothing gets the depth an enterprise deal needs.
- Where it sits here
- Waters builds the named universe that everything downstream spends against. ABM as an operating discipline, not a display-ads budget.
Field note · The demographic wishlist
Wrong. ICP = "companies with 1,000+ employees in tech". A wishlist that mirrors who you would like to sell to.
Correction. Start from the structural causes of the problem. Firmographics are proxies for that condition, and they get demoted to layer two.
Field note · The ICP written once
Wrong. Define the ICP at founding, then never touch it again.
Correction. Re-derive it every quarter from your last 20 closed deals and delete any attribute that fails to separate wins from losses. Losses are the model’s best training data. Fewer than 20 deals? Widen the window and mark the hypothesis low confidence.
Field note · The $40B TAM
Wrong. Sizing the market as a spreadsheet TAM and calling that a strategy.
Correction. The market map is a named-account list you could read aloud. If you cannot enumerate it, you have not defined it.
Instruments of the trade
- Apollo.ioDraw the first raw account list from firmographic filters: size, geography, industry, headcount of the owning function.
- ClayEnrich that list in one table and run the ICP hypothesis against it column by column, so the fit gate is a rule and not an opinion.
- CrunchbaseCheck ownership, funding stage, and recent capital. These are the facts that decide whether an account can actually buy at your price.
- LinkedIn Sales NavigatorConfirm the owning function exists and is staffed before an account enters the universe.
Tools are listed where they do a job, not as a stack to adopt. Every one of these is replaceable; the mechanism is not.
The list that survives the last cut is your waters. Next: which of those accounts are moving right now.02 · Sonar
MODULE 02 · OPEN WATER
Sonar · Buying-Signal Intelligence
listen before you move
You are listening to the 120 accounts Waters kept (↑ 01). Inside defined waters a signal means something. Outside them it is just news.
Know which accounts are entering a buying window while the signal is still warm.
Signals are events that raise the odds an account is entering a buying window. They are not equal and they do not keep. Each class carries a base strength, how reliably it predicted real opportunities in your own history, and a half-life. A demo request sits near the top of the scale and is worthless in a month. A former champion surfacing inside a target account stays warm for a quarter. Current value is base × 0.5^(days ÷ half-life), and account intent is the sum of what is still alive, so one weak signal never fakes a hot account. The console holds Meridian's last 8 months: 7 signals, 78 of 100. The 72-hour rule is not discipline theatre. It is what the decay math says.
Switch the 6 categories on and off and watch the composite recompute. Every card carries its base weight against what is left of it today. Baltica Terminals sits alongside as the cold control.
INSTRUMENT 02 · SIGNAL CONSOLE
Composite heat
Meridian Freight GroupIN-MARKET
Comparator
Baltica TerminalsCOLD · fit without intent
Signal log · last 8 months
base strengthvalue todayv = S0 × 0.5^(age ÷ half-life)
Routing rule
Quote their own language back, to the function that owns the number.
Executive initiative statement · base strength 7.0 of 10 · half-life 90 days · below 0.5 it leaves the sum
Routing rule
Air cover first: the committee is reading before it is talking.
Category research surge · base strength 8.0 of 10 · half-life 90 days · below 0.5 it leaves the sum
Routing rule
Direct, personal, same day: a known champion in a new building.
Champion migration, re-engaged · base strength 9.0 of 10 · half-life 90 days · below 0.5 it leaves the sum
This is the thread that becomes your champion candidate. → 05 · Stakeholders
Routing rule
Same-channel follow-up within 72 hours, addressed to the attendees.
Committee engagement · base strength 4.0 of 10 · half-life 30 days · below 0.5 it leaves the sum
Routing rule
Capability build-out: route to the technical evaluator, not the buyer.
Hiring pattern · base strength 5.0 of 10 · half-life 60 days · below 0.5 it leaves the sum
Routing rule
Executive peer outreach inside the first 90 days of the mandate.
New executive in owning function · base strength 7.0 of 10 · half-life 90 days · below 0.5 it leaves the sum
Routing rule
Watchlist only: verify the renewal window before any outreach.
Tech-stack change · base strength 6.0 of 10 · half-life 120 days · below 0.5 it leaves the sum
Meridian reads 78: 7 live signals, the heaviest a champion migration that fired 45 days ago. Baltica, same industry, reads 22.
Signal categories
◦ Defaults, not laws. Recalibrate against your last 20 closed deals.
Reading the feed
Top to bottom, 8 months of Meridian. The oldest event on the log started the clock quietly 240 days ago: Competitor ops-suite contract expiry detected. Then the executive arrival at 120 days, Tomas Berg hired as CTO (ex-Maersk digital), is a heavy class on a 90-day half-life. Engage while the mandate is new or the window shuts. The freshest event at 14 days, Q2 earnings call: "penalty exposure from reporting gaps", is the most quotable of the lot, because it names your problem in the buyer's own words.
The failure-mode reading
Switch off people moves and Meridian falls from 78 to 51, under the in-market line. Now run it the other way, which is how most teams actually fail: a webinar, a pricing-page visit, a newsletter open, a like. Weak signals do not stack into real urgency. They corroborate. Weight first, then sum, and a pile of soft touches stays a pile.
The comparator
Baltica Terminals reads 22 and sits beside Meridian as the control. Same fit, no motion: no hires, no initiative, no engagement. Fit without intent is a watchlist, not a target. Sonar keeps listening and nobody spends a touch.
Field note: the flat trigger list
Wrong: treating every trigger as equal and permanently fresh, so a funding round from March and a demo request from this morning sit in the same queue.
Correction: strength times decay. Score each class on what it predicted in your own closed deals, give it a half-life, and let the aggregation make one weak signal visibly insufficient.
Field note: signal hoarding
Wrong: collecting signals into a spreadsheet nobody actions, then reaching out on 60-day-old news as though it happened yesterday.
Correction: decay makes staleness visible, and a 72-hour rule on the fast-decaying classes forces routing on the day. A stale signal actioned reads as automation, not attention.
Field note: celebrating the RFP
Wrong: treating an inbound RFP as a signal that you are winning.
Correction: an RFP you did not shape is usually a procurement formality around a vendor already chosen. Assume column fodder until the evidence says otherwise, which is exactly what the Deal Integrity check is for (the Bridge).
Instruments of the trade
- LinkedIn Sales NavigatorAlert on job changes, new executives, and headcount moves inside universe accounts. These are the fastest-decaying signals in the system.
- Google AlertsFree, adequate coverage of funding, M&A, regulatory, and leadership news for a named account list.
- BuiltWithDetect stack changes: an incumbent tag disappearing is a buying window opening.
- 6senseAccount-level intent when you need research behavior you cannot see anywhere else. Treat it as a weak signal, never a trigger on its own.
- Common RoomResolve community and social activity back to named accounts so a mention becomes a routable event.
Tools are listed where they do a job, not as a stack to adopt. Every one of these is replaceable; the mechanism is not.
Sonar tells you who is moving. Species decides who is worth the fuel, because a loud signal on a badly fitting account is still a bad account.03 · Species →
MODULE 03 · OPEN WATER
Species · Account Prioritization & Capacity
not every fish is worth the fuel
Sonar left you 120 scored accounts, and one of them reads 78 out of 100 (↑ 02 · Sonar). This module decides who gets pursuit capacity, and who does not, however loud they are.
A rep can genuinely orchestrate 15 to 25 Tier-1 accounts: bespoke research, several channels, several threads at once. That capacity is the scarcest asset in the whole system, and the account score exists to spend it deliberately. Four components do the work.Fit asks whether the problem is structurally present and worth enough to pay for. Intent is the Sonar output. Timing is renewal windows, fiscal calendars, dated mandates. Access is a warm surface into the committee. Fit gates first: below 40, an account is parked however loud its signals are, because fit errors cost months and access errors cost weeks. Past the gate the composite weighs Fit 0.35, Intent 0.30, Timing 0.20, Access 0.15.
Drag the four weight sliders and watch the ranking re-order. Pick any account for its score card. The board holds 11 accounts, and one of them is a trap.
INSTRUMENT 03 · CONTACT CLASSIFIER
PURSUIT RANKING · TOP 5
COMPOSITE SCORE- 1Meridian Freight Group80TIER 1driven by F 91 · I 78
- 2Nordvang Shipping66TIER 2driven by F 87 · I 62
- 3Verranova Express53TIER 2driven by I 74 · F 42
- 4Transbaltic Lines52TIER 2driven by F 63 · I 55
- 5Dockside Freight Co47TIER 3driven by I 71 · F 44
CAPACITY1 Tier-1 account against a budget of 15 to 25 slots.
THE BOARD
Pick an account for its score card.
Tuna: high fit and high intentMackerel: mid-market, mid-motionSardine: hot, small economicsGhost: fit without intentMarlin: trophy logo, wrong fit
TUNA · high fit and high intent
Meridian Freight Group
80 / 100
TIER 1Full orchestration. Hard cap of 15 to 25 per rep.
Fit91is the problem structurally present, and big enough to pay for
Intent78the live Sonar output for this account
Timing72renewal windows, fiscal calendars, dated mandates
Access66a warm surface into the committee
Fit 34, under the gate at 40. This account cannot be ranked at any weighting.
0.35×91 + 0.30×78 + 0.20×72 + 0.15×66 = 79.6
Recommended actionAttack now. Multi-thread immediately.
The fit and the window arrived together. That is the whole definition of a tuna.
CATCH THE TUNA · SPECIES · ACCOUNT SCORE CARD
Meridian scores 80, the only Tier 1 on this board. 8 accounts clear the gate; one earns full orchestration.
0.35
0.30
0.20
0.15
WEIGHTS SUM TO 1.00 · AUTO NORMALIZED
◦ Defaults, not laws. Recalibrate against your last 20 closed deals.
Show the pipeline math. Where the Tier-1 cap actually comes from.
The cap is not a preference. It falls out of three numbers you already have. Put yours in and see what capacity you are really allowed.
2
Quota divided by average deal size, rounded up to whole deals.
30%
Your last twenty closed deals, not the number in the board deck.
35%
Of the accounts you work properly, how many produce a real cycle.
2 ÷ 0.30 ÷ 0.35 ≈ 19
19 accounts
INSIDE THE CAPThat lands inside the range a single rep can actually orchestrate.
Tier-1 treatment is bespoke research, several channels, several threads. That is why the working cap is 15 to 25 accounts per rep, and why account number 26 costs you one you already picked.
Reading the plot
Meridian sits top right at fit 91, intent 78: the tuna, rank 1, the only Tier 1 on the board. Nordvang fits nearly as well at 87 but moves at only 62, so it stays a Tier 2 nurture until a signal promotes it. The sardines along the right edge are hot and small: real intent, $18k economics that cannot fund an enterprise pursuit.
The failure-mode reading
Press Chase the marlin. Grupo Andino Mining, a $6B logo at fit 31, vaults to number 1 and the list gets worse in the same motion. All of its intent is conference badge intent: no budget owner, wrong vertical. The gate exists because a famous $0 deal eats quarters of one of your 19 Tier-1 slots, which is more than the logo is worth.
The capacity ladder
The ladder is the point of the score. Tier 1 gets treatment that is undeliverable at scale, which is exactly what makes it Tier-1 treatment. Tier 2 gets programmatic nurture. Tier 3 stays on Sonar. Open the pipeline math and derive the cap from your own win rate instead of trusting ours.
Framework: Account Tiering & Capacity Caps
What it does. Scores every named account on fit, intent, timing, and access, ranks them, and then cuts the list at the number of accounts your team can genuinely work. Tier 1 gets full treatment and everyone else gets less, by design.
When to use it. Every planning cycle, once the account universe exists and before anyone plans a single touch.
The problem it solves. A pursuit list longer than your capacity is a wish list. Without a cap, every account gets thin coverage and the winnable ones lose to the loud ones.
Where it sits here. This is the tiering half of ABM made arithmetic: Module 03 derives the Tier-1 cap from your own win rate and deal target, and every account carries a reason code for the tier it landed in.
Field notes: Score theater
Wrong. Tuning the weights until the list matches your gut, then citing the score as if it were evidence.
Correction. Reason codes put the drivers on the surface. Once a quarter, check whether the score deciles actually predicted win rate, and retune against what happened rather than against your preferences.
Field notes: Logo lust
Wrong. Pursuing famous accounts with fit under 40 because the brand would look good on the website.
Correction. The fit gate is not negotiable. A famous $0 deal costs more than its logo is worth, and it costs it in the currency you have least of.
Field notes: The list that never shrinks
Wrong. A “prioritized” list of 300 accounts that all get the same sequence, where nothing is ever demoted.
Correction. The capacity cap is the mechanism, and intent decays by construction. No live signal and no timing window means out of Tier 1 automatically. Trust the decay.
INSTRUMENTS OF THE TRADE
- ClayComputes the four components in one table where every input stays visible and tunable.
- SalesforceHold tier as a field on the account so capacity caps are enforced by the system, not by memory.
- Apollo.ioFill the access dimension: who is reachable, at what altitude, and through which of your people.
- PocusFold product-usage evidence into the score for accounts that already have users inside them.
Tools are listed where they do a job, not as a stack to adopt. Every one of these is replaceable; the mechanism is not.
Portello Couriers wanted it most and still did not rank. Meridian is the tuna. Now pick thenets that can actually reach it.
MODULE 04 · OPEN WATER
Nets · Channel Selection & Orchestration
match the net to the water
Species ranked Meridian first, so this is the tuna (↑ 03). Now you plan channels against a hypothesis of its committee: seven silhouettes you have not met yet.
A channel is a routing decision, not an identity. Sixteen of them are on the table and each one has physics: how far it scales, how much it can be shaped to one person, how much trust it borrows on arrival, how fast it tells you the truth, what it costs, and whether a committee will answer it at all. Selection is a function of stakeholder times stage. Send the touch where that person already spends attention. Your preference is not an input. Cover every Tier-1 stakeholder on at least two channels, because a single-channel pursuit inherits single-channel failure.
Two faces, one instrument. Sort the registry, put any two channels on the radar, then move the fleet sliders and watch committee coverage answer.
INSTRUMENT 04 · NET CONFIGURATOR
Sort by
Category
Sorted by Enterprise fit. How well the channel reaches and moves a real buying committee (EB, veto-holders) on six-figure deals (5 = committee-grade).
| Compare | Channel | Category | Personalization | Scale | Trust | Speed | Cost | Enterprise fit |
|---|---|---|---|---|---|---|---|---|
| Customer | Customer | 5 | 2 | 5 | 4 | 5 | 5 | |
| Customer | Customer | 5 | 1 | 5 | 5 | 5 | 5 | |
| Partner | Partner | 5 | 1 | 5 | 4 | 4 | 5 | |
| Partner | Partner | 3 | 3 | 4 | 1 | 3 | 5 | |
| Events | Events | 5 | 1 | 3 | 2 | 2 | 5 | |
| Social | Social | 4 | 3 | 2 | 3 | 4 | 4 | |
| Community | Community | 4 | 2 | 4 | 3 | 3 | 4 | |
| Outbound | Outbound | 5 | 2 | 3 | 5 | 4 | 3 | |
| Outbound | Outbound | 4 | 5 | 1 | 3 | 5 | 3 | |
| Community | Community | 4 | 2 | 3 | 4 | 4 | 3 | |
| Content | Content | 1 | 5 | 2 | 1 | 3 | 3 | |
| Social | Social | 3 | 3 | 2 | 4 | 4 | 2 | |
| Community | Community | 3 | 2 | 2 | 4 | 3 | 2 | |
| Community | Community | 2 | 3 | 2 | 3 | 4 | 2 | |
| Partner | Partner | 1 | 4 | 2 | 2 | 3 | 2 | |
| Social | Social | 2 | 3 | 1 | 2 | 3 | 1 |
Head to head
Show
Partner
Warm Introductions
Borrow a third party's standing to reach one named stakeholder who would never answer a cold touch.
- Personalization5
- Scale1
- Trust5
- Speed4
- Cost4
- Enterprise fit5
LinkedIn leads on Scale by 2, Warm Introductions on Trust by 3. What arrives pre-trusted rarely scales. That is the whole trade.
Capture buying signals and run Director-to-VP conversations where the stakeholder is verifiably active.
Best for
- Pre-outreach research on committee members and org structure
- Signal capture: job changes, new-executive hires, engagement from target accounts
- Ambient credibility with mid-funnel stakeholders who research vendors quietly
- Signal-triggered DMs to Directors and VPs who post or comment regularly
Advantages
- Richest public dataset on who holds which role at a target account
- Job-change and new-executive signals surface here first
- Content compounds: one asset warms many Tier-1 stakeholders at once
- Accepted venue for a first professional touch, unlike most social channels
Limitations
- Many economic buyers and veto-holders (CFO, GC, CISO) are functionally inactive
- Sequenced automation is saturated; buyers pattern-match templated touches as spam
- Reply rates say nothing about deal health; the channel invites vanity metrics
- Algorithm and platform-policy changes can reprice the channel overnight
Example plays
- A Sales Navigator alert fires on a new VP of Operations at a Tier-1 account: inside 72 hours, send a DM naming the specific problem the predecessor left open. No congratulations, no deck.
- Publish a teardown of the workflow your category fixes, then let the Tier-1 stakeholders who engaged with it enter the outbound queue already warmed.
- A mapped committee member comments on the incumbent's post: log it as a weak signal on the account record and route it to the owner. Do not reply in public.
How you run it
- Verify activity first: check each mapped stakeholder's posting and commenting history; route inactive personas to another channel.
- Set alerts on Tier-1 accounts for job changes, new executives, and funding; treat each as a Sonar event with a 72-hour SLA.
- Send DMs only with a live signal, a point of view, and a proportional ask; never send a connection-note pitch.
- Publish problem-focused content aimed at the Tier-1 list so direct touches land on warmed ground.
- Log engagement from committee-role people as a weak signal. Note it, do not pounce.
What you measure
- Qualified conversations with mapped committee members per month
- % of Tier-1 stakeholders verified active on the channel (decides whether to use it at all)
- Reply rate to signal-triggered DMs (10% to 20% when the signal is real; low single digits without one)
- Signal-to-touch latency on job-change alerts (target under 72 hours)
ToolsLinkedIn Sales NavigatorClayCommon RoomAuthoredUp
Cold Email
OutboundDeliver researched, signal-triggered first touches to Director and VP stakeholders at a scale no other one-to-one channel reaches.
Best for
- Signal-triggered first touches across Tier-2 accounts
- Reaching personas who are inactive on every social channel
- Testing problem narratives quickly across a segment
- Re-engaging aged threads with a new, dated signal
Advantages
- Only channel that scales research-backed one-to-one touches into the thousands
- Cheap per touch; the economics survive low response rates
- Fully measurable: deliverability, replies, and meetings are all attributable
- Persona-agnostic: everyone on the committee has an inbox
Limitations
- Zero borrowed trust; the message must earn everything alone
- Deliverability is a permanent operating tax: domains, warmup, list hygiene
- Enterprise inboxes filter aggressively and buyers pattern-match sequences on sight
- Rarely reaches C-level; the altitude-match rule pushes executive outreach to executive senders
Example plays
- A Tier-2 account posts three roles for the team that owns the process you fix: one email cites the hiring, names the scaling problem, and asks for twenty minutes with the owner.
- Aged thread, ninety days silent: reopen it with a dated new signal such as funding, a re-org, or regulation, never with a note about circling back.
- Split one segment across two problem narratives at 150 sends each, then keep the narrative that produced meetings with mapped stakeholders, not the one with the higher open rate.
How you run it
- Gate every send on a live signal; no signal, no send.
- Build each touch as signal + point of view + proportional ask; delete anything that reads as a template.
- Run separate sending domains with warmup, and hold hard deliverability floors before adding volume.
- Cap pressure at 3 touches per stakeholder per 14 days across the whole sequence.
- Review meetings-per-effort monthly against other channels and reallocate.
What you measure
- Reply rate (1% to 5% typical for cold lists; 5% to 12% for tight, signal-triggered sends)
- Meetings with mapped stakeholders per 1,000 sends
- Bounce rate under 2% and spam-complaint rate under 0.1% (deliverability floor)
- % of sends tracing to a live signal (target 100%; anything else is spray)
ToolsClaySmartleadApollo.ioMailReach
Move an established relationship onto the fastest, highest-attention direct line, strictly after consent.
Best for
- Deal coordination with an engaged champion: scheduling, confirmations, MAP nudges
- Markets where WhatsApp is the default business messenger (Brazil, wider LatAm, Southern Europe, India, Middle East)
- Fast-decay moments: confirming attendance or unblocking a stalled approval same-day
Advantages
- Highest read and response rates of any channel once the number is exchanged
- Near-synchronous: feedback in minutes, not weeks
- The exchange itself is a trust event: a stakeholder sharing a personal number signals real relationship progress
Limitations
- Not a cold channel: unsolicited outreach reads as intrusive and can end the relationship
- Compliance exposure: regulated industries often prohibit deal communication on personal messengers (record-keeping rules)
- No scale: strictly one-to-one and relationship-gated
- Regionally uneven: near-zero enterprise norm in the US and DACH
Example plays
- The champion offers a direct number after a strong first meeting: use it to confirm the next session and unblock scheduling, and keep the business case on email where the committee can forward it.
- An approval stalls two days before the steering-committee date: send one short message asking what is needed from you today, instead of a five-paragraph email.
- In Brazil or the Gulf, ask for the number at the end of the first in-person meeting. The exchange itself is a progress marker worth logging on the committee map.
How you run it
- Wait for the invitation: exchange numbers in person or after a strong meeting, never as a first touch.
- Confirm compliance posture: ask the champion whether their organization restricts messenger use before deal content moves there.
- Reserve the channel for coordination and time-critical nudges; keep substantive artifacts on email where the committee can forward them.
- Match the stakeholder's register: short and informal, no pasted pitch blocks.
- Mirror every material agreement back to email so the deal record stays complete.
What you measure
- Response latency vs. email on the same thread (typically minutes vs. days)
- % of active Tier-1 deals with a consented WhatsApp line to the champion
- Gone-quiet rate after moving a thread to the channel (rising means you moved too early)
ToolsWhatsApp Business PlatformTwilio360dialogWati
Maintain ambient founder and brand credibility for the minority of ICPs whose stakeholders actually browse it.
Best for
- Founder-brand visibility in industries with strong visual culture (retail, hospitality, CPG, agencies)
- Humanizing the company for stakeholders doing informal late-stage diligence
- Event coverage that keeps the account warm between touchpoints
Advantages
- Low competition for B2B attention: few vendors show up credibly
- Informal diligence surface: stakeholders check it even when they would never engage
- Behind-the-scenes content builds a familiarity no whitepaper produces
Limitations
- Weakest enterprise channel on this list: committees do not make vendor decisions here
- No native path from attention to a business conversation
- Visual production demands are high relative to any pipeline effect
- Attribution to enterprise pipeline is effectively unmeasurable
Example plays
- Before investing, sample fifty followers against ICP roles; if the audience is peers and job candidates rather than buyers, cut the channel and move the budget to owned dinners.
- Post the roundtable you hosted, showing the room, the topic, and the people, so a stakeholder running informal diligence finds a company that convenes their peers.
How you run it
- Audit whether ICP stakeholders are present at all before investing; for most enterprise ICPs the answer is no. Stop here.
- If present, run it as air cover only: culture, events, customer moments; never outbound DMs.
- Repurpose assets from other channels; do not create Instagram-first content for an enterprise motion.
- Review quarterly against Tier-1 penetration and cut without sentiment if it shows nothing.
What you measure
- Follower overlap with ICP roles (audit a sample manually; it usually reveals the channel's real audience)
- Mentions of content by stakeholders during live deals (qualitative log)
- Cost per post vs. other ambient channels (content and webinars usually win)
ToolsMeta Business SuiteLaterCanva
X (Twitter)
SocialEarn technical and founder mindshare in the niches where the committee's evaluators actually read their feed.
Best for
- Developer-tool, infrastructure, security, and AI categories where technical evaluators live in the feed
- Real-time signal capture: complaints about incumbents, stack discussions, executive commentary
- Founder-to-founder or founder-to-executive visibility in tight scenes
Advantages
- Fastest public feedback loop of any content surface
- Technical credibility compounds through reposts by respected practitioners
- Incumbent complaints and stack chatter are searchable, current buying signals
- Low production cost per touch
Limitations
- Persona coverage is narrow: most economic buyers and veto-holders are absent
- Reach is volatile under algorithm and platform-policy shifts
- Public replies to prospects can read as performative; DMs mostly go unread without prior engagement
Example plays
- Save a search on the incumbent's name plus outage, migration, and pricing; when someone at a universe account posts one, route it to the account owner as a Sonar event.
- Answer three practitioner threads a week with specific technical detail for a month before publishing anything of your own; the reposts are the credibility, not the follower count.
- A technical evaluator at a Tier-1 account replies to your thread: move to email within two touches. The feed carries signal, not deals.
How you run it
- Confirm the niche: search where your technical evaluators discuss the problem; if they are not here, leave.
- Monitor incumbent names and problem keywords; route complaints from universe accounts as Sonar events.
- Build presence through substantive replies to practitioners before publishing threads of your own.
- Move interested parties to email or a call quickly; the feed is for signal and credibility, not deal-making.
What you measure
- Engagement from named target-account employees (identity-resolved), not raw impressions
- Inbound DMs and mentions from ICP roles per month
- Incumbent-complaint signals from universe accounts captured and routed within SLA
ToolsTypefullyCommon RoomBrand24
Influence the anonymous research phase where evaluators pressure-test vendors without ever talking to them.
Best for
- Categories where evaluators search "X vs Y" and trust anonymous peers over analysts (dev tools, IT, security)
- Detecting unfiltered incumbent dissatisfaction and the buyer's own requirements language
- Long-tail search presence: high-ranking threads shape shortlists for years
Advantages
- Most honest voice-of-buyer data available anywhere: no vendor present, no posturing
- Threads rank in search and keep influencing shortlists long after posting
- Skepticism is the norm, so a genuine recommendation carries real weight
Limitations
- Openly commercial participation is detected and punished; the channel cannot be run as outbound
- Anonymous: you rarely know whether a commenter sits inside a target account
- Slow, indirect path to any specific deal; this shapes markets, not pipelines
- One bad interaction is archived and searchable forever
Example plays
- Pull the last twenty "X vs Y" threads in your category and lift the buyer's own requirement language verbatim into your discovery hypotheses and objection map.
- Answer a technical question in your problem space with disclosed affiliation and no link; the standing you build over months is what makes a later recommendation land.
- Audit the top-ranking comparison threads quarterly. They shape shortlists for years, so a correction posted late is still worth writing.
How you run it
- Monitor category, incumbent, and problem keywords; treat dissatisfaction threads as market intelligence, not outreach targets.
- Participate as identifiable practitioners answering technical questions, with disclosure, on a months-long horizon.
- Feed thread language verbatim into discovery hypotheses and objection maps. It is how evaluators actually talk.
- Never run pseudo-organic accounts; the detection cost exceeds any conceivable gain.
What you measure
- Share of voice in category-comparison threads (audited manually, quarterly)
- Sentiment trend in incumbent-vs-you discussions
- Inbound deals citing Reddit research in discovery (ask the question; log the answer)
ToolsGummySearchF5BotBrand24
Slack Communities
CommunityBe present and useful in the invite-only spaces where practitioners ask for vendor recommendations in real time.
Best for
- Categories with strong practitioner Slacks (data, DevOps, RevOps, security, design systems)
- Catching "anyone using something for X?" moments: live shortlist formation
- Soft access to individual committee members through shared-space familiarity
Advantages
- Recommendation requests are the highest-intent moment on any social surface
- Semi-private context lowers guard; conversations start peer-to-peer
- Membership overlap with target accounts is often verifiable through profiles
Limitations
- Communities ban solicitation; value must be deposited long before anything is withdrawn
- Coverage is one persona deep: the practitioner, almost never the economic buyer
- Message half-life is hours; presence must be continuous to matter
- Unsearchable and unattributable from outside; impact surfaces only in self-reported attribution
Example plays
- Someone at a universe account asks "anyone using something for X?" in a RevOps Slack: answer the question honestly the same day, then follow up in DM with a proportional ask.
- Audit member profiles against the Tier-1 list each quarter and record every match as Access on the account score.
- Spend the first six weeks in a new community answering questions with no product mention. That is the deposit that makes a withdrawal possible.
How you run it
- List the 3 to 5 communities your technical evaluators and users actually inhabit; join with named, real accounts.
- Answer questions in your problem space for weeks before your product is ever mentioned.
- Route recommendation-request moments involving universe accounts as fast-decay signals. Act the same day.
- When mentioned by others, follow up in DM with a light, proportional ask; never pitch in-channel.
What you measure
- Recommendation-request threads engaged per month, and whether others named you unprompted
- Members from named target accounts identified and added to committee maps
- Inbound citing the community as source (self-reported attribution question)
ToolsCommon RoomSlack ConnectThreado
Discord
CommunityHold ground in developer-native spaces where bottom-up adoption of technical products begins.
Best for
- Developer-first products whose end users gather in Discord servers
- PLG-to-enterprise motions: nurturing the users who become internal evidence for the top-down sale
- Fast technical Q&A that turns individual users into internal advocates
Advantages
- Direct line to end users, the committee's adoption vote, at near-zero media cost
- Real-time product feedback doubles as discovery input
- An owned server compounds into a support and advocacy asset
Limitations
- Almost no decision-makers or veto-holders present; strictly bottom-up
- Chat is invisible to search from outside; knowledge evaporates without deliberate capture
- Community management is a real, ongoing labor cost
- Pseudonymous identity makes mapping members to accounts unreliable
Example plays
- Three engineers from one Tier-1 account join your server in a month: treat the cluster as a product-usage signal and route it to the account owner.
- Bridge your best support answers to public, searchable docs so the effort compounds instead of scrolling away.
- Staff the technical channels with real engineers on a rota; developers identify a marketing account in one reply.
How you run it
- Choose a direction: run your own server (product-led) or participate in category servers (community-led); resource one properly rather than both thinly.
- Staff real technical presence; developers detect marketing accounts instantly.
- Bridge valuable answers to a public, searchable surface so the effort compounds.
- When server users cluster inside one company, treat it as a product-usage signal and route it to the account owner.
What you measure
- Active members mapped to named target accounts (best effort; expect low match rates)
- Time-to-answer on technical questions in your server
- Server users who later surface as champions in deals (log per deal)
ToolsCommon RoomAnswer OverflowStatbot
Professional Communities
CommunityBuild peer-level trust with senior stakeholders inside vetted networks that cold outreach cannot enter.
Best for
- EB-altitude relationship building (CFO, CRO, CISO networks) years ahead of any deal
- Category intelligence: how buyers at your ICP actually evaluate and purchase
- Warm-intro pathways through shared membership
Advantages
- Vetted membership pre-filters for seniority: the altitude cold channels cannot reach
- Peer context transfers trust: you are a member first, vendor second
- Relationships survive job changes and produce signals for years
Limitations
- Slow: quarters to years before trust converts into product conversations
- Membership and time costs are significant, and per person rather than per company
- Selling inside the community burns the asset permanently
- Coverage is limited to whoever your team can personally sustain
Example plays
- Your CRO joins a peer network at the same altitude and runs one benchmark session a quarter with no product mention. The relationships arrive years before the deals.
- Cross-reference the member directory against the account universe and record every match as Access on the account score.
- A fellow member's company fires a funding signal: ask for context peer-to-peer before any formal outreach reaches the account.
How you run it
- Match membership to altitude: your executives join EB-level networks; your practitioners join practitioner ones.
- Contribute before extracting: sessions, benchmarks, honest vendor-agnostic answers.
- Map fellow members against the account universe and record them as Access in the account score.
- When a member's account fires a signal, request context peer-to-peer before any formal outreach.
What you measure
- Committee-altitude relationships active per executive (met within the last quarter)
- Warm intros generated into Tier-1 accounts per quarter
- Deals where a community relationship appears on the committee map (log it)
ToolsPavilionChiefCommsorISACA
Events
EventsCompress weeks of multi-threading into days of in-person contact with stakeholders who ignore every digital channel.
Best for
- Meeting multiple committee members from one Tier-1 account in a single week (conferences)
- EB and veto-holder relationships built pre-deal (owned dinners and roundtables)
- Mid-deal acceleration: a scheduled in-person meeting resets a stalled thread
- Reading committee dynamics invisible on remote calls: who defers to whom
Advantages
- Highest-bandwidth channel: an hour in person outranks a quarter of email
- Reaches executives who are unreachable on every digital channel
- Owned micro-events control the room: the guest list is your Tier-1 committee hypothesis
- Signal-rich: attendance, questions, and dinner conversation are all discovery input
Limitations
- Most expensive channel per touch; sponsorships routinely fail cost-per-conversation math
- Calendar-bound: you wait for the event, and follow-up decay is brutal
- Zero scalability: every additional attendee costs linearly
- Booth presence without pre-booked meetings produces badge scans, not pipeline
Example plays
- Decide conference attendance from the attendee list: fewer than eight Tier-1 stakeholders on site and the money goes to a dinner instead.
- Host a twelve-seat roundtable built from one Tier-1 committee map: one discussion topic, no pitch, and seating planned so the economic buyer sits beside a customer.
- Pre-book meetings three to four weeks out and clear every follow-up inside 72 hours; after that the context is gone and the badge scan is all you own.
How you run it
- Decide attendance from the attendee list, not the agenda: how many Tier-1 stakeholders will physically be there?
- Pre-book meetings three to four weeks out; the event is the excuse, the calendar is the point.
- For owned dinners, build the guest list from Tier-1 committee maps and seat deliberately; no pitch, one discussion topic.
- Execute follow-up within 72 hours while context is alive; route every substantive conversation into the committee map.
- Score each event on cost per qualified conversation and cut the ones a dinner outperforms.
What you measure
- Pre-booked meetings with mapped stakeholders per event (the metric that decides attendance)
- Cost per qualified conversation vs. other channels (often $500 to $2,000 at conferences; owned dinners frequently beat it)
- Tier-1 accounts with a new committee thread opened within 30 days of the event
ToolsLumaSplashGoldcastCvent
Partnerships
PartnerBorrow an adjacent vendor's trust, access, and paper process to enter accounts you cannot open alone.
Best for
- Co-selling with vendors already installed inside Tier-1 accounts
- Cloud-marketplace transactions that shortcut procurement via pre-committed spend
- Entering regulated or relationship-gated verticals behind an incumbent integrator
- System-integrator channels where the SI owns the transformation program
Advantages
- Warm access at altitude: the partner's champion becomes your introduction
- Marketplace procurement can cut the paper process from months to weeks: budget already committed to AWS, Azure, or GCP
- Overlap data turns "who do we know there" into a queryable system
- Partner presence is itself account intelligence: stack, spend, initiative context
Limitations
- Slowest channel to stand up: quarters of enablement before the first sourced deal
- You inherit the partner's incentives; their account priorities are not yours
- Attribution disputes and margin-sharing create internal friction
- A partner-sourced deal can leave you one relationship layer removed from the committee
Example plays
- Run account mapping against the Tier-1 list, then build the co-sell motion with the two partners holding real coverage, not the two with the biggest logos.
- List on the marketplace your buyer already draws committed spend from, and use it as a procurement path when legal timelines threaten the critical event.
- On a partner-sourced deal, open your own thread to the economic buyer in the first two weeks: the partner opens the door, you still map the room.
How you run it
- Map overlap first: run account mapping against the Tier-1 list and rank partners by real coverage, not logo appeal.
- Start with two or three partners and build a repeatable co-sell motion before widening.
- List on the cloud marketplaces your ICP already buys through; treat it as a procurement path, not a demand channel.
- On co-sold deals, insist on direct committee threads. The partner opens the door; you still map the room.
- Review sourced and influenced pipeline quarterly; prune partners with coverage but no motion.
What you measure
- Partner-sourced and partner-influenced pipeline % (mature enterprise programs run 20% to 40% influenced)
- Overlap coverage: % of Tier-1 accounts where a live partner holds a relationship
- Marketplace transaction share and cycle-time delta vs. direct paper
- Time from partner signing to first sourced opportunity (expect 2 to 4 quarters)
ToolsCrossbeamTackle.ioWorkSpanPartnerStack
Affiliates
PartnerPay independent referrers a commission for demand you could not have named in advance.
Best for
- Self-serve or mid-market tiers of the product that seed future enterprise expansion
- Niche influencers and newsletters whose audiences overlap practitioner personas
- Long-tail geographies or verticals your team does not cover
Advantages
- Pure pay-for-performance; near-zero waste on the direct spend
- Reaches audience pockets invisible to your targeting
- Runs largely unattended once the program and tracking exist
Limitations
- Structurally misaligned with enterprise: affiliates convert clicks, not committees
- No control over message or context; brand risk in regulated categories
- Enterprise buyers do not purchase through affiliate links; at best the channel warms an end user
- Fraud and attribution gaming require ongoing policing
Example plays
- Recruit five niche newsletters whose readers are practitioners in your category, and pay on activated accounts rather than clicks.
- Flag affiliate-sourced signups whose email domain matches a universe account and route them to the owner as product-usage signals.
- Audit affiliate creatives quarterly: someone promising outcomes you do not deliver becomes a credibility problem in the security review.
How you run it
- Scope honestly: run affiliates for the self-serve tier and treat any enterprise effect as a bonus, not a plan.
- Recruit a small set of credible niche referrers over volume marketplaces.
- Instrument the bridge: flag affiliate-sourced users whose email domains match universe accounts and route them as product-usage signals.
- Audit quarterly for fraud and for brand safety in how affiliates present the product.
What you measure
- Revenue per affiliate-sourced account vs. house average (usually far below enterprise ACV)
- % of affiliate-sourced users who later appear inside universe accounts (the only enterprise-relevant number)
- Program ROI net of commissions and management time
ToolsPartnerStackimpact.comFirstPromoterRewardful
Referrals
CustomerConvert existing trust into the warmest possible first touch: the intro that skips cold outreach entirely.
Best for
- First touch on any high-Access Tier-1 account, always the first choice when a path exists
- Reaching economic buyers and veto-holders who ignore all outbound
- Re-entering an account after a champion moves there (champion-migration signal)
Advantages
- Highest trust transfer of any channel: the introducer's credibility becomes your starting position
- Referred deals convert at multiples of cold-sourced deals and typically close faster
- Feedback is immediate: the introducer usually knows within days whether there is interest
- Near-zero marginal cost
Limitations
- The ceiling is your network's actual reach; the channel cannot be scheduled or scaled on demand
- Passive waiting produces almost nothing; referrals must be engineered account by account
- Asking spends social capital; over-asking damages the relationships the channel runs on
- Quality varies with the introducer's real standing: a weak intro can anchor you low
Example plays
- For every Tier-1 account, list the former colleagues, investors, customers, and partners who can reach the committee, and rank the paths by the introducer's real standing.
- A champion-migration alert fires. A past champion just started at a universe account: request the intro inside 72 hours, while the goodwill and the new mandate are both live.
- Send the introducer a three-sentence forwardable blurb naming the person, the reason now, and the ask. Then report the outcome back either way.
How you run it
- Map paths account by account: for every Tier-1 account, list former colleagues, investors, customers, and partners who can reach the committee.
- Make the ask specific and effortless: name the person, state why now (the signal), and provide a forwardable three-sentence blurb.
- Route champion-migration signals within 72 hours. A past champion at a new account is the warmest path in the system.
- Close the loop with introducers regardless of outcome; the report-back is what earns the next intro.
- Track intro paths as the Access component of the account score, not as a side list.
What you measure
- Intro-to-meeting conversion (typically 50% to 70%, vs. low single digits for cold outreach)
- Win rate on referred vs. cold-sourced opportunities (expect a 2× to 4× gap; measure your own)
- % of Tier-1 accounts with at least one credible intro path mapped
- Intros requested and completed per quarter: the activity you can actually control
ToolsCommsorThe SwarmLinkedIn Sales NavigatorCrossbeam
Existing Customers
CustomerTurn deployed accounts into the acquisition engine: expansion revenue, reference proof, and advocate-sourced pipeline.
Best for
- Land-and-expand: growing a departmental deployment into an enterprise agreement
- Reference calls and proof assets that unblock late-stage committees
- Advocate-driven pipeline: champions who buy again at their next company
- Usage-signal-driven expansion as new teams adopt inside the account
Advantages
- Trust is already established and contractually evidenced; no other channel starts there
- Expansion cycles skip most of the paper process: the MSA exists, security already passed
- Win rates and acquisition cost on expansion are structurally better than any net-new channel
- Every renewal and QBR is a legitimate, expected touchpoint, with no outreach fatigue
Limitations
- Bounded by current customer count; a small base means a small channel
- Requires actually delivered value; advocacy cannot be extracted from a mediocre deployment
- Reference capacity is finite and burns out when over-drawn
- Expansion can mask stalling new-logo acquisition when the two are reported together
Example plays
- Usage jumps in a second business unit: the owner opens an expansion thread on the existing MSA instead of running a new-logo motion.
- Run the QBR as discovery: quantify delivered value in the customer's own numbers, then reuse that page as both the expansion business case and the reference story.
- Your champion resigns: the account gets a succession plan the same week, and the new employer enters the pursuit list.
How you run it
- Instrument usage signals per account: new-team adoption, seat growth, and API expansion route to the owner as Sonar events.
- Run QBRs as discovery: quantify delivered value in the customer's numbers. It becomes the expansion business case and the reference story.
- Build the reference bench deliberately: match by industry and role, track usage, and reward participation.
- Alert on every champion departure: the account gets a succession plan, and the champion's destination enters the pursuit list.
- Report expansion and new-logo pipeline separately so this channel's strength never hides a top-of-funnel problem.
What you measure
- Net revenue retention (durable enterprise motions run 110% to 130%)
- Expansion pipeline as % of total (healthy, but watch the new-logo mix)
- Reference and advocacy actions completed per quarter vs. bench capacity
- Champion job-change alerts actioned within 72 hours (each one is a new-logo signal)
ToolsGainsightVitallyPocusUserEvidence
Warm Introductions
PartnerBorrow a third party's standing to reach one named stakeholder who would never answer a cold touch.
Best for
- Opening a specific seat on the committee map, usually the economic buyer or a veto-holder, where no customer relationship exists
- Accounts where an investor, board member, advisor, or former colleague sits one hop from the person you need
- Re-entering an account that went quiet, through a broker the committee already trusts
- Altitudes where sender credibility, not message quality, decides whether there is a reply at all
Advantages
- The broker's credibility arrives with the request: the meeting is granted to them and extended to you
- Aimed at one named person, so it fills exactly the gap the committee map exposes
- The broker's read on politics, budget, and incumbent standing is often worth more than the meeting
- Fast and honest feedback: a broker who declines is telling you something about the account
Limitations
- Bounded by who your team, investors, and advisors actually know; it cannot be scheduled or scaled on demand
- Every ask spends the broker's capital rather than yours: a bad-fit request costs a relationship you will need again
- The broker controls framing and timing; a vague forward anchors you as a favor instead of a fit
- It opens one door only; the rest of the committee still has to be mapped and threaded the hard way
Example plays
- The committee map shows no thread to the CFO: find the board member you share with the account, send a forwardable paragraph, and ask for a double opt-in introduction.
- An investor's portfolio company runs the incumbent you replace: ask for the operator intro before their renewal window, not after it closes.
- A former colleague now reports to your target economic buyer: ask for context and a warm forward, and offer something worth taking credit for internally.
How you run it
- Work backward from the committee map: name the seat you cannot reach, then find the shortest path to that person, not to the account.
- Brief the broker in one forwardable paragraph: who, why now, what you are asking for, and what happens if they pass.
- Ask for a double opt-in forward rather than a blind connection; the broker keeps control and the recipient keeps the choice.
- Cap the asks at roughly one per broker per quarter unless they offer more; the channel dies from over-drawing.
- Report the outcome back inside a week, favorable or not. The report-back is what buys the next intro.
What you measure
- % of Tier-1 accounts with at least one credible broker path mapped to a named committee member
- Intros requested vs. completed per quarter: the gap measures how well you brief brokers
- Meeting-held rate on completed intros (expect well above half; below that, the ask was mis-targeted)
- Broker reuse rate: how many brokers agree to a second ask, the honest measure of how you spend their capital
ToolsThe SwarmAffinityLinkedIn Sales NavigatorCrossbeam
Content / Inbound
ContentCapture demand at the account level: publish what the committee reads while researching, and route the universe accounts that surface.
Best for
- Reaching the committee members who research anonymously and answer no outbound at all
- Shaping evaluation criteria and requirements before anyone writes an RFP
- Air cover on the Tier-1 list so direct touches land on warmed ground
- Categories where buyers self-educate for months before contacting any vendor
Advantages
- One asset works on the whole committee at once and keeps working after publication
- The only channel a buyer can use without identifying themselves, which is how most enterprise research happens
- Committee members forward good material internally; the asset multi-threads on your behalf
- Marginal cost of the next reader is effectively zero once the asset exists
Limitations
- Slowest feedback on this list: months between publishing and any account-level signal
- No control over who arrives; hand-raises from outside the account universe consume capacity without producing pipeline
- Attribution is partial: the assets that shape a decision are rarely the ones a form captures
- Quality is the entire channel; commodity content produces traffic and no conversations
Example plays
- Publish the evaluation checklist the buyer would otherwise build themselves, so the criteria you win on are the ones they write down.
- Run a 45-minute practitioner webinar on the problem, then route every registrant from a universe account to the owner as a signal inside 72 hours.
- Three people from one Tier-1 account read the pricing-model teardown in a week: that is a buying window opening, and the account owner should know the same day.
How you run it
- Write for the committee you mapped, not for a keyword: the CFO, the CISO, and the user lead each ask a different question about the same problem.
- Instrument account-level identification so a visit from a universe account becomes a Sonar signal instead of an anonymous session.
- Gate almost nothing. The form is a routing mechanism, not a toll booth, and gating suppresses the anonymous research you are trying to influence.
- Run inbound through the same fit gate as outbound; a hand-raise from outside the universe is still not a Tier-1 account.
- Reuse every asset as an outbound artifact and a champion-enablement document; one page should serve all three jobs.
What you measure
- Universe reach: % of Tier-1 accounts with at least one identified visit or download per quarter (the number that decides the investment)
- Hand-raise to qualified-conversation rate, reported separately for universe and non-universe accounts
- Assets cited by stakeholders during live discovery (ask the question; log the answer)
- Time from first identified account visit to first conversation with a mapped stakeholder
ToolsAhrefsHubSpot6senseGoldcast
◦ Scores are calibration defaults, not laws: starting positions to tune against your own trailing deals.
Committee coverage
seven hypothesised seats · module 05 names them
5 of 7
2 DARK- Champion candidate180reached
- Economic buyer60unreached
- Exec sponsor (potential)85reached
- Technical evaluator165reached
- Security veto90reached
- Procurement gate25unreached
- User buyer / blocker100reached
Presets
◦ A seat counts as reached at 75 coverage points out of a possible 300. Scores are calibration defaults, not laws: starting positions to tune against your own trailing deals.
LinkedIn leads on Scale by 2, Warm Introductions on Trust by 3. What arrives pre-trusted rarely scales. That is the whole trade.
Channel physics
Every row is physics, not preference. Events reach VP and above with real trust transfer at a brutal cost per touch. Cold email scales into the thousands and tops out at director altitude. Content compounds for months before it signals anything at all. No shape is best. What the six axes answer is best for whom, at which stage.
The coverage failure reading
Drag outbound to 100 and coverage falls to 4 of 7. The pre-seeded mix does better at 5 of 7 and still misses the same two seats: 60 points for the economic buyer, 25 for procurement, against a threshold of 75. Sender rank has to match recipient rank above VP. An SDR sequence does not reach an SVP, and no ad has ever reached procurement.
The touch test
- live signalSomething happened that justifies contact today, not in general.
- point of viewSomething they could not have read on your website.
- proportional askTwenty minutes on a problem, sized to the trust you actually have.
A touch missing all three is spam, however well-written. So it does not send. There is no template. That is the point.
Framework in play
Multi-Channel Orchestration
- What it does
- Plans a channel per person instead of a campaign per account: each stakeholder is reached where they already pay attention, and every touch carries a signal, a point of view, and an ask.
- When to reach for it
- After the list is tiered and the committee roles are known, before the first touch goes out.
- What it prevents
- One channel for everyone means the CFO gets the same cold email as the platform engineer. Orchestration collapses into volume, and the account learns to ignore you.
- Where it sits here
- Module 04 is the execution half of ABM: air cover on the named list, a routed channel per role, and a floor of two channels for every Tier-1 stakeholder.
Field note · the monoculture
Wrong: one channel as team identity. "We are a cold email shop." Or the original playbook's LinkedIn-only premise.
Correction: route per stakeholder and cover every Tier-1 person on at least two channels. A single-channel system inherits that channel's algorithm changes, its inbox saturation and its missing personas, all at the same time and usually in the same quarter.
Field note · response rate retires here
Wrong: judging a channel on response rate. It is the metric that survives because it is easy to collect, not because it predicts anything.
Correction: measure qualified conversations with mapped committee members per unit of effort. A channel running 2 percent response at VP level beats one running 20 percent from people who cannot buy, cannot veto, and cannot sign.
Field note · killing the slow fleets
Wrong: cutting content, events and partnerships because last-touch attribution cannot see them.
Correction: ambient fleets are air cover. Judge them on Tier-1 penetration over quarters, not on the last click before a form. They exist so the direct touches land on warmed ground, and the allocator shows what happens to coverage the moment you zero them.
Instruments of the trade
- LinkedIn Sales NavigatorVerify a stakeholder is actually active on the channel before you route a touch there.
- SmartleadRun sending domains, warmup, and pressure caps so the email channel survives its own volume.
- WhatsApp Business PlatformKeep consented messenger threads inside a compliant, logged channel instead of a personal phone.
- Common RoomTrack which communities your buyers inhabit and which of your people are present there.
- LumaRun owned dinners and roundtables: invitations, guest list, and attendance in one place.
Your nets reach 5 of 7. Those seven are still a hypothesis: role labels on a coverage grid, not people.Module 05 gives them names→
MODULE 05 · THE HAUL
Stakeholders · Buying Committee & Multi-Threading
chart the crew that decides
You are inside Meridian now: flagged at 78 by Sonar, ranked first by Species, and running a channel mix that reaches 5 of the 7 people it could even name (↑ 04). Time to give the silhouettes names.
See who really decides, with influence, stance, and vetoes, before they see your proposal.
Enterprise purchases are decided by a committee you mostly never meet, in rooms you are not in. Modern committees run six to eleven people, and the ones who kill deals are rarely the ones who take your calls: security and legal hold hard vetoes, procurement owns the process, finance validates the budget, and someone in the building quietly defends the status quo.Map influence over this decision, not rank on the org chart. Give every person a stance, then count threads: relationships that took an action with you in the last 14 days. Three active threads before any proposal. And a champion is not a feeling. There are four behavioral tests, and warmth passes none of them.
Select anyone on the chart for their card: what moves them, what they will push back on, what they can cost you, what they need from you. Then flip the departure switch and watch what a single-threaded deal is actually worth.
INSTRUMENT 05 · COMMITTEE CHART
Cards run in order of power over this decision. Each carries the person's role, stance, thread status, and the people they report to, influence, or block.
reports toinfluencesblocksthread activeholds a vetooff your mapPosition is the person. Height is power, width is support.
DEAL STRENGTH
Thread gate met · 3 of 3
COVERAGE3 of 8 engaged · 38%
Ticks are the gates: 50% to exit Discovery, 60% to exit Consensus. Mapped committee: 8.
THREAD DEPTH3 active · gate 3
A thread is a relationship that took an action with you in the last 14 days. The gate is 3 of them before any proposal goes out.
CHAMPION BATTERYDana Voss · 2 of 4 · candidate under development
- InformationpassedShares non-public information you did not ask for: budgets, politics, a number.
- StakepassedHas a personal outcome riding on the change, not just an opinion about it.
- AccesspendingUses their access to power on your behalf, getting you the meeting they said they would.
- ActionpendingDoes internal work between meetings, without you in the room.
2 of 4 to exit Discovery. 4 of 4 to exit Consensus.
Dana Voss
Director, Ops Technology
Champion candidateInfluence: MedStance: AdvocateConviction 82/100Thread activeHolds a vetoDeparted
- What moves them
- Dana wants the connected-operations program to become real, and wants a visible win to claim.
- What they will push back on
- Dana has been burned by a vendor before, so nothing goes internal until the arithmetic can be defended without backup.
- What they can cost you
- Today Dana is the only thread into the power centre: a job change zeroes the deal.
- What they need from you
- An unbranded story retellable in Dana’s own voice: problem, cost of inaction, options considered, recommendation.
8 mapped, 3 engaged, deal strength 64. Dana is 2 of 4 on the champion tests: a candidate, not yet a champion.
Deal strength 64 → 31 · threads 3 → 2 · champion 2 of 4 → none
◦ Defaults, not laws. Recalibrate against your last 20 closed deals.
Reading the chart
8 contacts, placed by power over this decision rather than by title. Ingrid Halloran, SVP Operations, owns the $2.3M penalty line: high influence, conviction 40, and no thread. Willem Kuipers, Marta Rehn and Sofia Marchetti sit on the gate row because security, legal and procurement can each stop this deal regardless of everyone else's enthusiasm. Ed Larkin starts at 15. Ed wants the terminals to run, and wants to not repeat the 2023 rollout the unit absorbed. Mapped, not avoided. The two dashed contacts at the top are the CEO and the CFO: you know they exist, and that is all you know.
The failure-mode reading
Flip the departure switch. Dana's edges gray out and deal strength falls 64 to 31 in one move, because in the pre-seeded state that is the only active thread into the power centre. Threads go 3 to 2, under the gate of 3, and the champion term goes to zero. Nothing else changed. That arithmetic is the case for the coverage rules: three or more active threads before any proposal, two relationships inside the champion's power centre, and any single-threaded deal reported at half its weighted value.
The champion battery
Dana scores 2 of 4. Evidenced: information and stake. Unproven: access and action. Access to power has never been spent on your behalf, and no internal work has happened between meetings. That is a candidate under development: enough to exit discovery, nowhere near enough to carry a proposal. Coverage sits at 38%, under the 50% exit gate, which is the same fact stated a second way.
The frameworks doing the work here
MEDDICC / MEDDPICC
A verification spine across eight dimensions: metrics, economic buyer, decision criteria, decision process, paper process, identified pain, champion, competition. Each one is graded on evidence rather than opinion.
When: Continuously, from the first mapped stakeholder to signature; re-scored whenever new evidence arrives.
Solves: Forecasts built on rep confidence. Grading on evidence exposes the dimension that is actually missing before the quarter does.
Deal Integrity is the MEDDPICC spine running under modules 05 to 08 and reported on the Bridge. A live score, not a once-a-stage checkbox form.
Champion Development
Tests whether someone is actually a champion by behavior: do they give you information, access, and action, and do they carry personal stake. How warm the calls feel is not evidence.
When: As soon as one stakeholder starts helping you; re-run the test before every stage gate.
Solves: Mistaking a friendly coach for a champion. A coach can inform you; only a champion can carry the deal in rooms you will never enter.
Stakeholders scores the champion 0 to 4 on the behavior tests. Consensus is where a 4/4 champion earns their keep.
Multi-Threading
Turns relationship coverage into arithmetic: how many live threads the opportunity has, how much of the committee is covered, and where the single points of failure sit.
When: From the first meeting onward, and especially before forecasting anything that runs through one person.
Solves: Single-threaded deals die when one person changes job, priority, or mind. The failure is invisible until it happens.
The Module 05 committee map computes thread depth and coverage, then applies a forecast haircut when the count is thin. Not "CC more people".
Buying Committees
Models the purchase as an organizational decision: champion, economic buyer, technical buyer, user buyer, executive sponsor, procurement, legal, and security each hold different power over it.
When: Before you write a message to anyone: the roles decide who gets reached, on what channel, with which argument.
Solves: Selling to a persona. Every four-box model leaves out the people who most often kill enterprise deals: security, legal, procurement, and whoever is paid to defend the status quo.
Stakeholders maps influence, motivation, objections, risks, and information needs per role, and Nets routes a channel per person from that map.
Field note: the coach you called a champion
Wrong: promoting the friendliest contact to champion because the calls go well, they answer fast, and they say encouraging things about the product.
Correction: a coach informs you. A champion spends their own credibility on you in a room you are not in. The difference is behavioral and it is testable: information, stake, access, action. Dana passes 2 of the four today, which is why the chart reads candidate and not champion. Warmth is not evidence, and a coach mistaken for a champion is how a deal reaches proposal with nobody inside the building carrying it.
Field note: single-threading through whoever answers
Wrong: building the whole deal on the person who replies fastest, which is usually the person with the least to lose. Responsiveness runs against seniority.
Correction: thread depth is a number you report, not a feeling you have. Three active threads before any proposal, two of them inside the power centre, and a 50% haircut on the forecast when the count is thin. The switch above prices the comfortable path: 64 to 31, from one resignation.
Field note: a committee of fans
Wrong: spending your meetings on the advocates because those meetings feel better, and leaving all 3 veto holders for contract time.
Correction: if everyone you know is an advocate, you do not know the committee. Blockers get addressed through their concerns, usually via a peer running an operation that looks like theirs. An unengaged veto holder is not a neutral party. It is a scheduled ambush with a date on it, and the date is always the worst week of your quarter.
Instruments of the trade
- LinkedIn Sales NavigatorReconstruct the org chart around the initiative: who reports to whom, who is new, who owns the budget line.
- SalesforceStore the committee as structured contact roles with influence and stance, so coverage is queryable and survives a rep leaving.
- LucidchartDraw the influence map when the reporting line and the real decision path disagree. That is most of the time.
- The SwarmFind who on your team, board, or investor bench already knows a stakeholder you cannot reach.
Tools are listed where they do a job, not as a stack to adopt. Every one of these is replaceable; the mechanism is not.
8 people, 3 gates, one champion candidate at 2 of 4. Discovery is how you learn what each of them actually needs, and Consensus is where the remaining two tests get proved or disproved.06 · Discovery →
MODULE 06 · THE HAUL
Discovery · Discovery & Problem Quantification
measure the depth before you dive
The committee is mapped: 8 people, three gates, Dana at 2 of 4 (↑ 05). Questions differ by role, and rounds are scarce.
Turn a stated annoyance into a buyer-confirmed number a CFO can't dismiss.
Discovery's product is a quantified gap: the distance between where the buyer is and where they want to be, priced in their numbers and anchored to a dated event. Everything else, rapport included, is packaging. The mechanics run in order. Verify the signal hypothesis. Chain implications until a stated annoyance becomes a recognized business cost. Reframe if the problem is mis-scoped. Then quantify with their metrics, labelling every estimate as an estimate. Two fields predict a close better than all the others: Impact and Critical Event. A deal without a dated critical event has no close date, only a hope. And the value pool has to clear 3× your first-year price, because finance runs that division whether you do or not.
Round 1 is already played. Pick your question in rounds 2 and 3 and watch what each one buys, or wastes, on the eight-segment intel meter. Rewind anything. The polite dead ends are the curriculum.
INSTRUMENT 06 · DISCOVERY CONSOLE
THE CALL
Thirty minutes with Dana Voss, Director of Ops Technology at Meridian. Dana took the meeting because your first message quoted the earnings call back word for word.
You believe Meridian is bleeding money through manual SLA reporting. You cannot prove it. Neither can Dana, yet.
Three questions fit in the time. Each one costs you a round. Some buy a number you can take to a CFO. Some buy a warm, useless yes.
Nothing in this room is random. It only looks that way from the inside.
ROUND 1Dana Voss · already played
This one is on the record before you arrive, so the mechanism is visible before you spend anything.
DANA VOSS · OPS TECHNOLOGY
Dana confirms it. Tomas Berg's connected-operations program made SLA reporting a named workstream. The penalty number is not Dana's. It belongs to Ingrid Halloran, SVP Operations.
- The real problem · buyer-confirmed
- The number · your hypothesis
- The inside seller · your hypothesis
METER 4 OF 24
ROUND 2Dana Vossyour call
Your call. One of these three, and the other two are gone.
DANA VOSS · OPS TECHNOLOGY
ROUND 3attendance not settled
Attendance depends on what you ask in round 2.
COMPLETE ROUND 2 FIRST
DANA VOSS · OPS TECHNOLOGY
AFTER THE CALL
The mutual summary
Helm sends a written summary of what was said, what it costs, and what happens next. Dana corrects two numbers and forwards it to Ingrid. Nothing in it is yours; that is why it survives.
Nothing on this call was ad-libbed. What felt like a conversation was a system, running exactly as built.
You never asked what the problem costs or who owns that number, so Ingrid had no reason to take the call. Round 3 ran on second-hand answers, and second-hand answers cap out at a hypothesis.
The summary could not mention what nobody said out loud. Still at zero:
Written down, but still yours rather than theirs:
Nothing at zero. Every dimension has at least a hypothesis behind it.
Round 1 is on the record at 4 of 24. Two questions left, and what you ask next is what you will know.
Rewinding round 2 also rewinds round 3. Who is in the room depends on what you asked.
Reading the meter
Eight things a deal is graded on, each one filling from unknown to documented. Round 1 is already on the record: the signal-verification question turned a public signal into a confirmed initiative and surfaced who owns the number, which is 4 of 24 before you have spent anything. Played well, the call exits at 13 of 24, split M2 · E1 · Dc2 · Dp1 · P2 · I2 · Ch2 · Co1. E reads 1 because Ingrid has engaged but hasn’t yet confirmed worth-solving-at-this-cost; that confirmation is the Consensus exit.
The failure reading
Pick the dashboard walkthrough and Dana says "looks interesting, send some material". Warm, engaged, and worth nothing: no number, no owner, no date. The meter does not move, and a call that collects sympathy instead of a number reads as progress in the CRM for another three weeks. Skip the question about what the problem costs and Ingrid never joins round 3, so the answers you do get cap out at your own hypothesis. That is the whole penalty, and it is invisible until you need the number.
The gap, and the date
The product of this call: $2.3M a year of confirmed annual pain, in the buyer's own numbers, against a $180k first-year price. That is 12.8× against a 3× floor, and it is the only number the business case in Consensus is allowed to lead with. The critical event is dated. Fiscal year end: funds move by Nov 28 or the penalty clauses renew. The consequence of missing it was stated by the person who owns the budget. "Q3-ish" and "it would be nice" both read as absence here. The paper-process question asked in round 3 is also the reason Closing has a parallel-path toggle at all.
How the frameworks divide the work
Four methodologies touch this call and they are not competing. One shapes the questions, one shapes the record, one shapes the argument when the buyer has mis-scoped the problem, and one shapes the arithmetic. Take the mechanism from each and leave the certification.
SPIN
Structures discovery questions so the buyer, not you, states the cost: Situation, Problem, Implication, Need-payoff. Implication is the one that does the work.
When: In discovery, once the buyer has named an annoyance and you need to find out what it actually costs downstream.
Solves: A stated annoyance is not a business case. Without implication chains, you present value the buyer never agreed exists.
Discovery uses the Problem to Implication chain to turn "this is annoying" into a number the buyer says out loud. The rigid four-step script is discarded.
SPICED
Gives discovery a record structure: Situation, Pain, Impact, Critical Event, Decision. Every conversation fills the same fields.
When: As the shape of your discovery notes and CRM record, from first call through close.
Solves: Discovery that lives in a rep's head cannot be inspected. Missing Impact and Critical Event is how a deal gets a close date built on hope.
The discovery record in Module 06 is SPICED-complete, and the Critical Event field is what Closing builds the mutual action plan backward from.
Challenger
Teaches a commercial insight that reorders how the buyer sees their problem: you think the cost is X, the evidence says it is Y, and Y is more expensive.
When: When the buyer has mis-scoped the problem, or when you arrived late into requirements someone else wrote.
Solves: Answering the buyer's stated requirement makes you column fodder in an evaluation that was framed by a competitor.
Discovery uses the reframe deliberately and only with evidence behind it: a move, never a personality type.
Gap Selling
Makes the deal about a measured delta: current state in facts and metrics, future state in target metrics, and the gap between them.
When: Before any proposal. The gap is what you quantify in discovery and what the business case is built on.
Solves: Product-led pitches have nothing to be evaluated against. A buyer with no quantified gap is a conversation, not an opportunity.
The Module 06 gap calculator is Gap Selling made visible: no confirmed delta, no deal to advance.
Field note: the demo as discovery
Wrong: demo-first selling. The demo becomes the discovery, the solution gets framed before the problem is measured, and price anchors to features instead of value.
Correction: no demo before a quantified gap exists. After that the demo has a job: show gap closure, specifically, in the buyer's own numbers.
Field note: interrogation discovery
Wrong: twenty checklist questions and no insight given back. The buyer experiences unpaid consulting, for you.
Correction: teach, test, quantify. Every question you ask is paid for with a point of view, which is also the only reliable way to earn the second call.
Field note: taking the stated problem at face value
Wrong: accepting the first-stated problem, which is usually a symptom scoped by the altitude of whoever said it.
Correction: implication chains plus a reframe, validated on at least two threads. The user's version and the executive's version of the same problem often differ enough to change the deal.
Instruments of the trade
- GongCheck what the buyer actually said against what the record claims: implication answers, critical event, decision criteria.
- GrainCapture and clip the moment the buyer quantifies the problem in their own words; that clip is the business case's first evidence.
- SalesforceHold the discovery record in fixed fields: pain, impact, critical event, decision and paper process. Gaps become visible.
- Google SheetsModel the gap live on the call: current-state metrics, target metrics, and the delta the buyer confirms.
Tools are listed where they do a job, not as a stack to adopt. Every one of these is replaceable; the mechanism is not.
Played to the canon path, this call exits at 13 of 24 and clears the gate: 12 or better, with no dimension at zero. A total on its own is not enough. A 13 with a blind spot in it is a different deal.
DEAL INTEGRITY
- M at 2 of 3
- E at 1 of 3
- Dc at 2 of 3
- Dp at 1 of 3
- P at 2 of 3
- I at 2 of 3
- Ch at 2 of 3
- Co at 1 of 3
You have the pain, the number, the date, and the route Meridian takes to buy. Consensus is where the deal is actually won, mostly in rooms you are not in.07 · Consensus →
MODULE 07 · THE HAUL
Consensus · Consensus & the Internal Sale
every hand pulling, or no haul
Discovery banked a buyer-confirmed $2.3M gap and a Nov 28 critical event (↑ 06). Now the committee has to agree, mostly in rooms without you.
Arm your champion to win the rooms you'll never enter.
The hardest sale happens without you: your champion selling your deal in rooms you will never enter. Buying groups mostly fail to buy because they cannot agree, not because they prefer a competitor, so this stage is buyer enablement run as two parallel workstreams. One: a business case in three scenarios that leads with the conservative bound, carries full TCO including the buyer's internal costs, and survives review by a mapped skeptic before finance ever sees it. Two: an internal campaign your champion runs with your assets: an unbranded deck in the company's own voice, a value narrative per stakeholder in their own metric, an objection map, a pre-mortem. Your job is arming, not attending.
Six moves, seven meters. Assign each one and watch weighted consensus recompute against the70-point threshold, remembering that a veto holder below 50 fails the deal whatever the average says.
INSTRUMENT 07 · CONSENSUS BOARD
THIS QUARTER
Moves left: 0 of 6
try one
Tap a move, then a person.
- w:med100
- w:hi50
- w:hi65
- w:med70
- w:med25
- w:gate35VETO · BELOW 50
- w:gate40VETO · BELOW 50
w:hi / w:med / w:gate influence weightVETO CLEARANCE · 50CONSENSUS THRESHOLD · 70
THE BUSINESS CASE · CONSERVATIVE-LED
Co-authored with Ingrid · skeptic-tested by Willem's objections · led by the bound that survives finance
Value pool $2.3M/yr
| Scenario | Value captured / yr | 3-yr ROI | Payback |
|---|---|---|---|
| Conservative: lead with thisA case that survives at its conservative bound is unkillable. | $460k | 134% | 6 mo |
| BaseThe number you would have led with. Nobody is persuaded by it. | $920k | ||
| Upside: discount it yourselfA case that needs the upside case is already dead. | $1.5M |
Reviewed by Priya before finance sees it.
THE ENABLEMENT DECK
The unbranded deck: problem, cost of inaction, options considered, recommendation, ask. All in Meridian’s voice, presented as Dana’s. Your logo’s absence is the point.
6 moves on Dana: the meter caps at 100 and 24 points evaporate, while consensus sits at 58 and Willem and Sofia both stand.
Dragging a meter sets a manual override. Overrides are yours to test with and are never saved.
The single-threading failure, priced
The pre-seeded allocation puts all six moves on Dana. Dana's meter maxes out at 100, and the deal fails anyway: weighted consensus 58 against a threshold of 70, with Willem 35, Sofia 40, both under the 50 a veto holder must clear regardless of the average. A maxed champion in an unconvinced committee is module 05's single-threading lesson, now priced.
The balanced allocation
Press "Balanced." Consensus clears at 74: the security pre-review moves the security veto over its line, the pilot converts the user buyer's scar tissue into contained evidence, the ROI workshop puts the business case in the economic buyer's own numbers, and the enablement deck turns Dana's conviction into artifacts carried into rooms without you. The battery reaches 4 of 4: verified by behaviors this stage naturally produces, not by warmth. Vetoes clear at Willem 61, Sofia 61.
The business case, in their numbers
Assign the ROI workshop to the economic buyer and the business case opens: three scenarios, led by the conservative bound, full TCO on your own side of the ledger. A case that survives at its conservative bound is unkillable; one that needs the upside case is already dead. And Ingrid's verbal, worth solving at roughly this cost, before any proposal, is the exit criterion. Proposals confirm. They do not persuade.
How the frameworks divide the work
One shapes the internal campaign, one shapes the arithmetic finance will actually accept. Take the mechanism from each and leave the certification.
Consensus Building / Buyer Enablement
Arms the champion to run the internal sale: an unbranded document in the company's own voice, a value narrative per senior stakeholder, an objection map, and a pre-mortem.
When: After the gap is quantified and before any proposal goes out. That is the moment the decision moves into rooms you cannot attend.
Solves: Consensus is the buyer's hardest job and the one sellers help with least, so deals stall at "everyone agrees, nobody decides".
Module 07 builds the assets the champion presents as theirs; your logo's absence is the point.
ROI / Business-Case Modeling
Builds a three-scenario model led by the conservative case, with full cost of ownership, a stated payback period, and assumptions a skeptic can attack.
When: Once the buyer has confirmed the gap, and again whenever finance or procurement re-opens the number.
Solves: Vendor ROI theater. An upside-case spreadsheet dies in finance review and takes the champion's credibility with it.
The Module 07 business case extends the Module 06 gap calculator, and it is what price defense in Closing is anchored to.
Field note: attending every meeting
Wrong: Trying to personally attend every internal conversation. It is impossible, and it signals that the champion cannot carry the deal alone.
Correction: Your job is arming, not attending. Measure asset delivery and champion actions, not your own meeting count.
Field note: the vendor deck
Wrong: A seller-branded deck as the internal artifact. Consensus does not form around vendor decks.
Correction: The unbranded deck: problem, cost of inaction, options considered, recommendation, in their language, presented by their person. Your logo’s absence is the point.
Field note: ROI theater
Wrong: An upside-case spreadsheet built on your assumptions, delivered as a PDF. Finance discounts it to zero on contact.
Correction: Conservative led, their numbers, co-authored, and reviewed by a mapped skeptic whose objections get incorporated before finance ever sees it.
Instruments of the trade
- Google SheetsBuild the three-scenario ROI model in a file the champion can open, edit, and defend without you in the room.
- Google SlidesProduce the unbranded internal deck in the company's own voice: problem, cost of inaction, options, recommendation, ask.
- DockGive the committee one shared space holding the business case, proof assets, and next steps, and see what actually gets opened.
- UserEvidenceTurn customer outcomes into verifiable proof assets a skeptical veto-holder will accept.
Tools are listed where they do a job, not as a stack to adopt. Every one of these is replaceable; the mechanism is not.
Consensus 74, vetoes cleared, Dana at 4 of 4. Everything above was earned in rooms you were not in, which is exactly the point. What is left is the part everyone underestimates.
DEAL INTEGRITY14/24PROPOSAL GATE ≥16
The committee agrees. Meridian still has to buy it through security, legal and procurement, on a clock that does not move for anyone.08 · Closing →
MODULE 08 · THE HAUL
Closing · Procurement & the Verified Close
it counts when it's weighed ashore
Consensus passed at 74/100 with vetoes cleared and the economic buyer's own verbal: Ingrid, verbal: "worth solving at roughly this cost." The proposal is now a confirmation document. (↑ 07). That verbal is why this module confirms a number instead of building a case for one.
Walk procurement's gauntlet in parallel and close on the buyer's clock, verifiably.
Between a verbal yes and a signature sits the gauntlet: security review, legal redlines, procurement onboarding, and executive signature. Run one after another, four to sixteen weeks routinely outlast the quarter they were meant to close in, and none of that delay is a competitor's doing. It is arithmetic nobody did. Two policies fix it. Parallel path everything: start security, legal, and procurement the day of verbal selection, not at contract, because every step discovered late costs two to four weeks and every step run in parallel costs days. And a mutual action plan is the close itself: a shared, dated document built backward from the buyer's critical event, with an owner on every step. A buyer who will not co-own one is telling you the deadline is not real. That is diagnostic information, not an inconvenience.
The pre-seeded plan is the failure: every gate run in sequence, missing the buyer's clock by a margin nobody can see until it is too late to close it. Flip the three toggles below and watch what each one actually buys, and what the discount actually costs.
INSTRUMENT 08 · CLOSE PLANNER
- Security review: starts week 1, 7 weeks.
- Legal redlines: starts week 8, 5.5 weeks.
- Procurement onboarding: starts week 14, 3.5 weeks.
- Exec approval + signature: starts week 17, 2 weeks.
Projected closeJan 9
First year value$180k
Slip riskwide
6 WEEKS LATESequential processing closes Jan 9, 6 weeks after the buyer's critical event. Every gate is known today. Only the order is wrong.
Two consecutive MAP slips → re-verify the critical event with Ingrid.
◦ Defaults, not laws. Recalibrate against your last 20 closed deals.
The sequencing failure
The pre-seeded plan runs the four gates in sequence: security, then legal, then procurement, then signature. It closes Jan 9, 6 weeks late. Fiscal year end: funds move by Nov 28 or the penalty clauses renew Nothing about the deal changed between the verbal yes and that date. The calendar arithmetic was simply never done, which is how a confirmed yes quietly becomes next quarter's forecast.
Parallel path and the mutual action plan
Flip parallel path alone and the close pulls in to Dec 2, 4 days late, a toggle that exists only because round 3 of discovery mapped the paper process (↑ 06). Add the mutual action plan and the close moves to Nov 4, 24 days early: dated owners slip less, and once security stops being the longest pole, a surprise redline round costs zero days on the critical path instead of the two to six weeks it costs a sequential plan.
The discount, priced
The quarter-end discount pulls the date from Nov 4 to Oct 21 and costs $18,000, 10% of first year value, dropping it to $162k. That buys weeks the deal did not need and teaches procurement that waiting produces a lower price. Trade, never donate: a concession should buy a multi-year term, a prepayment, or a reference, and the price defense is the payback period the buyer's own numbers produced, not your list price.
The framework this module runs on
Enterprise Procurement Practice
Treats the paper process as a mapped project: security review, questionnaires, DPA, MSA redlines, vendor registration, budget release, and signature chains, run in parallel with a mutual action plan built backward from the critical event.
When: Map it in discovery; start every track at verbal selection, not at contract.
Solves: Sequential processing turns six weeks into sixteen, and every approval step discovered late costs another two to four.
Module 08 parallel-paths the gauntlet and negotiates by trade, never by donation. Procurement is the deal, not post-sale admin.
Field note: procurement as post-sale admin
Wrong: legal and procurement folded into one late line item, an afterthought once the "real" selling is done.
Correction: the paper process is mapped in discovery, parallel-pathed at verbal selection, and tracked in the mutual action plan. Sequential processing out of politeness is how six weeks become sixteen. Buyers respect vendors who understand how buying actually works.
Field note: going dark during legal
Wrong: weeks of silence while lawyers trade redlines, while consensus quietly decays and the status quo's defenders regroup.
Correction: keep the champion and economic buyer threads warm through procurement. The mutual action plan review call is the vehicle, not an extra touchpoint you have to invent.
Field note: celebrating at signature
Wrong: sign, celebrate, then improvise onboarding.
Correction: kickoff is booked with names and a date before the signature happens. Signature is the midpoint of the customer's story, not the finish line, and expansion revenue is priced into every acquisition cost model that actually works.
Instruments of the trade
- SalesforceTrack the mutual action plan and its dates as deal fields, so a slipped step is visible the week it slips.
- VantaAnswer security questionnaires from a maintained trust center instead of starting each one from scratch.
- IroncladRun redlines against pre-approved fallback positions so legal turns days rather than weeks.
- SAP AribaComplete vendor registration and purchase-order steps on the buyer's procurement platform. This is the step discovered late that costs a quarter.
- DocuSignRoute the signature chain in the right order once every approval is cleared.
Tools are listed where they do a job, not as a stack to adopt. Every one of these is replaceable; the mechanism is not.
Signed Nov 28: $180k, 3 business units, a path to $520k. Deal Integrity closes at 21/24, commit grade.
DEAL INTEGRITY19/24COMMIT GATE ≥20 + PAPERWORK 3
Eight instruments, one deal, and every number on this page traces back to a call, a signal, or a stage. Meridian is signed. Now look at the system that got you here.09 · The Bridge →
SYNTHESIS
The Bridge · Deal Integrity & the Operating Loop
run the ship from the bridge
One run, end to end: 41,000 → 120 waters · Meridian at 78 · ranked #1 · mix reached 5/7 · 8 mapped, 3 gates · $2.3M gap, Nov 28 · consensus 74 · signed at $180k · Deal Integrity 21/24.
A playbook is a sequence. An operating system has state, sensors, policies, and feedback loops. The spine that holds the eight modules together is Deal Integrity: eight dimensions, each scored 0 to 3, unknown, seller hypothesis, buyer confirmed, confirmed with documented evidence. It gates every advance: 12 to exit discovery, 16 to send a proposal, 20 to forecast commit, and it moves backward when evidence degrades, which is the point. A falling score turns "bad feeling about this one" into a number with named causes. Below is the full scorecard, loaded with Meridian's closing state. Then score a live deal of your own.
The operating loop, 9 steps: Waters through The Bridge, with Closing feeding back into Sonar.
- Module 01: Waters, Market Definition & ICP · outcome: 120 waters.
- Module 02: Sonar, Buying-Signal Intelligence · outcome: 78 heat.
- Module 03: Species, Account Prioritization & Capacity · outcome: tuna #1.
- Module 04: Nets, Channel Selection & Orchestration · outcome: 5/7 nets.
- Module 05: Stakeholders, Buying Committee & Multi-Threading · outcome: DS 64.
- Module 06: Discovery, Discovery & Problem Quantification · outcome: 13/24.
- Module 07: Consensus, Consensus & the Internal Sale · outcome: 74 consensus.
- Module 08: Closing, Procurement & the Verified Close · outcome: signed Nov 28 at $180k.
- Synthesis: The Bridge, Deal Integrity & the Operating Loop
Annotations show your manipulations this session; defaults are the worked Meridian run.
DEAL INTEGRITY SCORECARD
VERIFYINGMeridian's closing state is loaded and read only. Switch to your live deal, score each dimension honestly from 0 to 3, and read the gate verdicts as you go. The score can move down; that fall is the early warning.
Identified painThe root problem, past the first stated symptom, confirmed across at least two threads.
Confirmed and documented. Written down somewhere you can point to.
MetricsThe quantified gap lives in numbers the buyer confirmed, not numbers you supplied.
Confirmed and documented. Written down somewhere you can point to.
Economic buyerIdentified, engaged, and on record that solving this is worth roughly this cost.
Confirmed and documented. Written down somewhere you can point to.
Decision criteriaWritten down, and you know who authored it and shaped it where you could.
Buyer confirmed. Someone on their side said it out loud.
Decision processEvery step from yes to signature has a named owner and a date.
Buyer confirmed. Someone on their side said it out loud.
Paper processSecurity, legal, and procurement mapped, with durations and who starts them.
Confirmed and documented. Written down somewhere you can point to.
ChampionThe four test battery: 0 to 1 tests reads a 1, 2 to 3 reads a 2, 4 of 4 reads a 3.
Confirmed and documented. Written down somewhere you can point to.
CompetitionAlternatives known, including doing nothing and building it internally: the two that win most no decision losses.
Buyer confirmed. Someone on their side said it out loud.
21/24
Discovery exit 12+: PASSProposal 16+: PASSCommit 20+ and paper process at 3: PASS
Weakest dimension Decision process. Map the route. 06 · Discovery
Commit grade: 21 of 24 with paper process at 3. This forecast is evidence, not a feeling.
The score should fall when evidence degrades: champion goes quiet, critical event slips, the economic buyer delegates downward. That fall is the early warning, with named causes.
LOSS ATTRIBUTION
Every closed lost deal gets exactly one primary cause code. The quarterly distribution names the module to fix. This table is also how you leave this page.
| Loss cause | The fix lives in |
|---|---|
| No decision, stayed with the status quo | 06 · Discovery (no critical event) or 03 · Species (no real timing) |
| Went dark after the proposal | 05 · Stakeholders (single threaded, proposal before consensus) |
| Lost to a competitor on criteria | 07 · Consensus (criteria shaped by their champion) or 06 · Discovery (arrived after the reframe) |
| Killed by security or legal | 08 · Closing (late parallel path) or 05 · Stakeholders (veto holder unmapped) |
| Budget cut, or failed the finance review | 06 · Discovery (value pool below the floor) or 07 · Consensus (case was not conservative led) |
| Champion left, or was reorganized away | 05 · Stakeholders (no thread redundancy) |
| Never reached power | 04 · Nets (altitude mismatch) or 05 · Stakeholders (economic buyer rule ignored) |
THE OPERATING CADENCE
| Loop | Frequency | What happens |
|---|---|---|
| Signal triage | Daily, 15 min | New signals routed per SLA. 72 hours for fast decay signals; stale ones expire by decay. |
| Pipeline integrity review | Weekly | Every active deal read against its exit criteria and Deal Integrity gates, evidence aloud, not vibes. Failing deals move backward, publicly, without stigma. |
| Tier 1 rescore | Biweekly | Scores recomputed, promotions and demotions executed, the cap enforced. |
| Channel efficiency review | Monthly | Meetings with mapped stakeholders per unit effort, by channel. Reallocate. |
| ICP refit and loss attribution | Quarterly | ICP re derived from the trailing 20+ deals, every loss coded, signal strengths recalibrated against what actually converted. |
THE OPERATING RECAP
- WatersDefine the market as a falsifiable hypothesis and a named list. If you can't read your market aloud, you don't have one.
- SonarSignals have strength and half lives. Act on fast decay within 72 hours or don't act at all.
- SpeciesFit gates, then fit beats intent beats timing beats access. Capacity is the scarcest asset, so cap Tier 1 and defend the cap.
- NetsChannels are per stakeholder routing decisions: two per person, chosen by where they already spend attention.
- StakeholdersMap influence and stance, not titles. Three active threads before any proposal, and champions are tested, never assumed.
- DiscoveryDiscovery produces a buyer confirmed gap of at least 3x price and a dated critical event, or it produces a disqualification.
- ConsensusArm the champion to sell in rooms you'll never enter. Lead with the conservative case and let a skeptic fail to kill it.
- ClosingParallel path the paper process and build the mutual action plan backward from the buyer's date. The close is a verification, not an event.
Then attribute every loss to the module that caused it, and the system corrects itself.