Briefing-to-Call Field Guide · For MDAs and Sales Directors
The briefing produces the raw material. The call uses it — or doesn't.
Across 184 pre-call briefings paired to 228 call transcripts, the data tells a consistent story: a small set of habits separates winning calls from losing ones. This guide is the working playbook — what MDAs do before sending the briefing, what SDs do on the call, what both do after.
+0.74The largest behavioral gap between wins and losses is whether the SD references the call's "why now" trigger.
57% vs 34%Win rate when a credible trigger is present (n=184) vs absent (n=44).
4 of 5Phrase families predict deal fade with 1.8–2.7× reliability — and one (the fifth) doesn't.
Above a quality floor, briefings only matter if the SD uses them on the call. The SD only uses them if the trigger is clear, the disclosure status is tagged, and the SD knows how to pivot live when the prospect surfaces something new.
Bad briefings can't be saved — briefings scoring 0–5 on the rubric close at 12% (n=16). Decent briefings (6–8) close at 48% (n=54); good ones at 58% (n=155). Above the floor, what matters is whether the SD references the trigger event, surfaces social proof at the right moment, and pivots when the prospect raises something the briefing didn't anticipate. The chain that's now observable in the data: get the briefing above the floor → SD uses what's there → SD adapts when novel context surfaces → win rate compounds. Each link is necessary; none is sufficient alone.
FOR MDAs
Four habits for briefing prep. M1 sets the floor. M2 closes the upstream research gap. M3 is the single most important field on the briefing. M4 protects future-you.
M1
Stamp out the 0–5 rubric briefings.
The biggest jump in win rate happens at the floor: going from "bad" to "decent" quadruples win rate (12% → 48%). Going from "decent" to "good" only adds 10 more points. The leverage is in the bottom of the distribution — every 0–5 rubric briefing that goes out is a deal at risk before the SD picks up the phone.
CHECK: Score this briefing on the 8-section rubric before shipping. If it's under 6, fix it before sending.
M2
Run the pre-call research checklist. Leadership churn is the #1 missed signal.
When prospects surfaced triggers live on the call that weren't in the briefing, the dominant pattern was C-suite or near-C-suite transition — five of eleven cases — and four of those five were lost deals. Companies pre-announce planned retirements. New CHRO hires show up on LinkedIn. New CEO transitions land in 8-K filings. The research is checkable; today it's not consistently being checked. See §research for the full checklist.
DATA: 5 of 11 missed-trigger cases were leadership churn. All researchable from public sources (LinkedIn, 10-K Item 5.02, 8-K filings, press releases).
CHECK: Did I check leadership team turnover in the last 12 months? Prospect tenure? Earnings/board calendar? Recent corporate events? Industry context?
M3
Put the trigger event at the top of the cheat sheet — and tag its disclosure status.
The SD's biggest behavioral gap on losing calls is failing to surface the trigger. But "we knew but didn't know how to say it" is also a real failure mode (see the coaching case below). Solve both at once: the cheat-sheet quick-take should have one bold line that names the trigger and tags how confidently the SD can use it.
Disclosure tag
What the SD does with it
Public
Lead with it directly. "I saw the [event] announcement..."
Partial (visible on LinkedIn but not formally announced)
Reference softly. "It looks like there have been some changes in the [function] team..."
Internal (from prior W50 call notes; not public)
Don't lead with it. Carry as context for live pivot if the prospect raises adjacent topics.
CHECK: Cheat sheet has one bold line: "Trigger [Public / Partial / Internal]: <one sentence>". Buried news bullets don't count.
M4
Save the call transcript to Salesforce — every call, every time.
35% of cohort Prospect-Call Events have no transcript saved to the Event's Description field. The auto-transcription is producing the files; they're just not making it to Salesforce reliably. Without transcripts in SF, none of the call-level signal — phrase recognizers, trajectory coding, utilization scoring — is recoverable for coaching or analysis. This is future-you and your colleagues' analytical capacity.
DATA: 65% transcript fill rate today. The 35% gap caps the team's ability to coach, audit, and improve over time.
CHECK: Was the call recorded? Did the transcript land in the Event's Description field? If no, push it.
FOR SDs
Four habits for execution. S1 fixes the largest behavioral gap. S2 is real-time pattern recognition. S3 stops wasted effort. S4 captures the upside the briefing couldn't predict.
S1
Surface the trigger event in the first 5 minutes — using the disclosure tag the briefing gave you.
Whether the SD references the trigger is the single biggest behavioral gap between wins and losses (Won mean 1.06 vs Lost mean 0.32, n=182). Read the cheat-sheet quick-take. If the trigger is tagged Public, lead with it. If it's tagged Partial, reference it softly. If it's tagged Internal, carry it as context but don't lead with it. The "I wasn't sure what to under-share, over-share" hesitation is a real failure mode and the disclosure tag exists to remove it.
DATA: U3 trigger surfacing has a +0.74 won-lost gap, the largest of any utilization dimension across 182 transcripts.
CHECK before each call: "What's the trigger and its disclosure tag? What's my opening sentence?"
S2
Listen for the four soft-yes-fade phrase families. Treat each as a real-time pivot signal.
Across 228 transcripts, four phrase families appear at 1.8–2.7× the rate in lost calls vs won calls. When you hear them, the deal has shifted into deferral pattern — don't validate; pivot deliberately. A fifth family ("very busy / running fast") appears at 1.3× and is too weak to act on; ignore it.
CHECK: When you hear one of the four — pause, name what's actually behind the deferral, don't accept the surface request.
Phrase family
Examples
Lost vs Won
"send me the details"
"send me the summary" / "send me what you have" / "send me a one-pager"
2.7× more in losses
"discuss internally"
"talk to my team" / "share with my CFO" / "loop in"
2.7× more in losses
"let me think"
"sleep on it" / "digest" / "give me time to"
2.4× more in losses
"circle back"
"reach back out" / "follow up later" / "in a few months"
1.8× more in losses
"very busy / running fast"
"context-shifting" / "in the weeds"
1.3× — too weak, ignore
S3
Code the trajectory of every call within 24 hours. Use it to drive disposition.
The trajectory at end-of-call is essentially a perfect outcome predictor. Use it to set follow-up cadence — and especially, to stop nurturing "neutral" exits as if they're warm. Only 4% of neutral exits recover.
CHECK: Within 24 hours, code the trajectory. Set cadence based on the table below.
Trajectory at end-of-call
Win rate
What to do
positive-closing
95%(n=103)
Done. Move to invoice.
positive-open
26% (n=76)
Recoverable but at risk. Force 5 / 10 / 14-day cadence with content drop. Don't drift.
neutral
4% (n=27)
Effectively dead. Archive unless a triggering event surfaces. Stop nurturing.
negative
5% (n=20)
Dead. Document and archive.
disqualified
0% (n=2)
Done — wrong-fit or role-change.
The most expensive misclassification is "neutral." Reps tend to nurture neutral exits as if they're warm — only 4% recover. The time spent nurturing is better spent elsewhere.
S4
Live-pivot when the prospect surfaces novel context the briefing couldn't predict.
Some triggers can only surface live — referrals the prospect names, internal politics, recent events that didn't filter into public sources at briefing time. When the prospect volunteers a leadership change, an M&A integration, a new-in-role detail, or a personal life event you didn't see in the briefing — pause, acknowledge, restructure the next five minutes around it.
Pause and acknowledge, ask one clarifying question: "Is that affecting how you're thinking about [function] right now?"
Restructure — the rest of the call is now about peers who've been through the same transition, not the original deck.
Close on the new context — the end-of-call ask should reference the trigger the prospect just surfaced, not the one you walked in with.
CHECK after the call: Did I pivot, or did I default to the original close? If I defaulted, that's what to coach next time.
⚠ The Inverted-Champion Red Flag
A named internal contact who's actually a blocker = hard pause. If the briefing flags any of the patterns below, route to senior review before the SD takes the call. None of these patterns appeared in any won deal in the cohort.
A former W50 member whose decline reason was Budget or "didn't see ROI"
An internal contact whose OK-to-mention permission was denied
The prospect themselves listed in the alumni-decline roster
A prior decline where membership was escalated to the CEO for review
Boss / peer-funder who voiced "we have enough memberships" in writing
Prospect deflecting to a junior direct report ("they know more than I do")
§ The pre-call research checklist
Five public-source patterns. The MDA + research coordinator runs these before writing the briefing standout.
Pre-call research checklist (MDAs + Research Coordinators)
Leadership team turnover, last 12 months. Count of C-suite changes (CEO, CFO, COO, CHRO, GC). For each new arrival, log the start date and whether they're an internal promotion vs an external hire. Sources: company website "Leadership" page; LinkedIn change-log; press releases; 8-K filings.
Prospect's tenure in current role. Months in current title. Under 12 months = corporate trigger. Flag it. Source: LinkedIn.
Upcoming calendar pressure, next 90 days. Next earnings date, board meeting cadence, fiscal year end, public guidance review. Source: Investor Relations site.
Industry headwinds. One sentence on what the prospect's industry is dealing with right now (tariffs, capital allocation, regulatory pressure, secular shift). Sources: industry analyst notes, recent news.
§ Pre-flight + post-call checklists
Three short checklists — one for the MDA before the briefing ships, two for the SD around the call.
MDA — Before sending the briefing
Pre-call research checklist run? Five items above completed and findings reflected in the briefing.
Cheat sheet — one bold line at the top: Trigger flagged with disclosure tag (Public / Partial / Internal) and one-sentence summary.
How Set — prospect's reply pasted verbatim (not summarized).
Past Calls — every prior call has rating + 1-line takeaway.
Why Them — at least one fact not on LinkedIn.
Champion — named contact tagged Aligned / Neutral / Inverted. If Inverted, route to senior review.
Alumni — decline patterns analyzed (not just listed).
Rubric self-check — would this score > 5 on the 8-section rubric? If no, don't ship.
SD — Before the call
What's the trigger and its disclosure tag? What's my opening sentence?
If no trigger flagged in the briefing — push back to the MDA before taking the call. Trigger-absent calls win at 34%; trigger-present at 57%.
Champion + trigger combo: who is the named champion, and how does their endorsement tie to the trigger?
Personal hook: what's the one specific detail I'll open with for rapport?
Inverted champion? If the briefing flagged any blocker dynamic, address explicitly on the call.
SD — Within 24 hours of the call
Save the transcript to the Event's Description field. (Today's miss-rate is 35%.)
Note any soft-yes-fade phrase the prospect used — capture verbatim, flag for the team.
Note any novel context the prospect surfaced live — leadership transition, M&A, new-in-role, personal event. Feed into next-round briefing.
Set disposition cadence based on trajectory: closing → invoice; positive-open → 5 / 10 / 14-day; neutral or negative → archive.
§ Coaching case
One worked example — what went wrong, and what better would look like.
Patrick O'Keefe · Universal Corporation · President 50 · Outcome: Lost
Three failure modes in one call.
The MDA's pre-call notes flagged that W50 had previously contacted Universal's relatively new CEO, Preston Wigner. The briefing's formal Standout focused on Patrick himself ("First-ever in role 5yrs"). Mid-call, Patrick volunteered the full leadership-transition picture:
Patrick (prospect)
"We have a new CHRO — it just started within the last month. We've got a search and we're getting ready to wrap up on a new CFO. So our current CFO is retiring. There is a little bit of a turnover going on right now for a company that's been extremely stable for many years."
The SD's response was the most informative line in the dataset for understanding why briefings don't translate to wins:
SD
"I knew that there was a new CEO, I saw in the notes that there was a CHRO being hired or not being hired, but I wasn't sure like, what I should under-share, over-share."
Three failure modes show up in this single exchange:
What went wrong
Pre-call research: The CFO retirement was the only piece not in pre-call notes. Companies pre-announce retirements in 8-K filings — checkable.
Disclosure confidence: The SD had pre-call signal but froze on how to use partial info. No tag on the briefing → no clarity on lead-with vs reference-softly.
Live pivot: Even after Patrick volunteered the full triple transition, the SD didn't restructure the next 5 minutes. The pivot was a sentence; the pitch frame stayed unchanged.
What better would look like
Pre-call research: M2 checklist would have surfaced the full leadership-team-transition picture, including the CFO retirement.
Disclosure tagging: Briefing flags trigger as Public for the announced CEO and Partial for the CHRO. SD opens directly: "I saw the leadership team has been turning over — I'd love to talk about how peers in similar transitions have used us."
Live pivot: When Patrick adds the CFO retirement, SD pauses, acknowledges, and restructures the close around it. End-of-call ask references the leadership transition specifically, not a generic "discuss with LT."