Sales Talk Track Builder
Select a persona, an industry, and a deal stage, then assemble a starting talk track from a library of proven message components instead of writing one from scratch.
What's inside
- The 3 selection axes: persona, industry lens, deal stage
- Component library: openers (5), pain hypotheses (4 industry lenses), value bridges (3 persona types), proof points, questions, next-step asks
- The assembly sequence — which components stack in which order
- Persona component set: Economic Buyer, Champion, End User, Technical Evaluator
- Stage component set: Prospecting, Discovery, Demo/Evaluation, Negotiation, Closing
- 3 fully assembled worked talk tracks (different persona × stage combos)
- Adaptation rules — what to swap when the buyer pushes back mid-track
- Do-not-say list per persona (common mismatches that kill trust)
Pick persona + industry + stage, assemble the components, get a starting talk track.
How the builder works
A talk track is six modular components stacked in order. Pick your Persona and Deal Stage below, pull the matching components from the library, and assemble in this sequence:
Opener → Pain Hypothesis → Value Bridge → Proof Point → Question → Next-Step Ask
Axis 1 — Persona Component Set
Economic Buyer (holds the budget, cares about risk and return)
- Value Bridge: “The way this typically pays for itself is [ROI mechanism] — we can model that against your numbers specifically.”
- Do-not-say: feature lists, technical implementation detail, anything without a number attached.
Champion (internal advocate, needs to sell it upward)
- Value Bridge: “Here's the version of this you could put in front of your leadership — the headline number, plus the two objections they'll raise and how to answer them.”
- Do-not-say: anything that requires them to defend jargon they can't explain in their own words.
End User (will use it day to day, cares about friction)
- Value Bridge: “Here's specifically what changes in your week — what gets shorter, what disappears entirely.”
- Do-not-say: strategic/roadmap language; they want concrete, not visionary.
Technical Evaluator (assesses feasibility, integration, risk)
- Value Bridge: “Here's how this sits alongside what you already run, and here's the one thing we'd want to test together before you'd trust it.”
- Do-not-say: marketing superlatives; lead with architecture and constraints, not benefits.
Axis 2 — Deal Stage Component Set
Prospecting
- Opener: “The reason I reached out — [trigger event/observation specific to them], and it usually connects to [problem].”
- Question: “Is that something that's actively on your plate, or lower priority right now?”
- Next-Step Ask: “Worth 20 minutes to see if there's a fit, or should I check back in a quarter?”
Discovery
- Opener: “Before I show you anything, I want to understand where this actually hurts today.”
- Question: “Walk me through what happens right now when [problem scenario] — who's involved, how long does it take?”
- Next-Step Ask: “Based on what you've shared, I think it's worth showing you [specific capability] — can I get 30 minutes with [additional stakeholder] in the room?”
Demo/Evaluation
- Opener: “Given what you told me about [specific pain from discovery], I'm going to focus on these three things.”
- Question: “Does that match what you pictured, or is there a gap between this and what you need?”
- Next-Step Ask: “What would you need to see to feel confident recommending this internally?”
Negotiation
- Opener: “Let's talk through where this stands and what's still open.”
- Question: “Is price the actual blocker, or is there something else still unresolved?”
- Next-Step Ask: “If we solve [specific blocker], are we ready to move forward this [timeframe]?”
Closing
- Opener: “I think we've covered everything — let's talk about what happens next practically.”
- Question: “Is there anyone else who needs to weigh in before this is final?”
- Next-Step Ask: “Can we get this signed by [date] so implementation starts on schedule?”
Industry Pain Hypothesis Lenses (plug into “Pain Hypothesis” slot)
- B2B SaaS/Tech: “Most teams like yours are dealing with data living in three different systems that don't talk to each other.”
- Financial/Regulated: “Most teams like yours are balancing a compliance requirement against wanting to move faster.”
- Manufacturing/Industrial: “Most teams like yours are dealing with a process that depends on one or two people who know it by memory.”
- Professional Services: “Most teams like yours are re-creating the same work from scratch every engagement instead of reusing what's already proven.”
Worked Talk Track Example 1 — Economic Buyer × Discovery × B2B SaaS
"Before I show you anything, I want to understand where this actually hurts today. Most teams like yours are dealing with data living in three different systems that don't talk to each other. The way this typically pays for itself is the hours your team stops spending reconciling that data manually — we can model that against your numbers specifically. We did that recently for a company your size and it came out to a 4-month payback. Walk me through what happens right now when your team needs a single view of a customer — who's involved, how long does it take? Based on what you share, I think it's worth showing you the reconciliation piece specifically — can I get 30 minutes with your ops lead in the room?"
Worked Talk Track Example 2 — End User × Demo × Manufacturing
"Given what you told me about the process depending on Dave's memory, I'm going to focus on three things today. Here's specifically what changes in your week — the handoff that used to take you an email chain now happens in one screen. We saw a team cut that from 3 days to same-day. Does that match what you pictured, or is there a gap between this and what you need? What would you need to see today to feel confident this actually fits how your shift works?"
Worked Talk Track Example 3 — Champion × Negotiation × Professional Services
"Let's talk through where this stands and what's still open. Here's the version of this you could put in front of your partners — the headline number, plus the two objections they'll likely raise and how to answer them. Is price the actual blocker, or is there something else still unresolved? If we solve that, are we ready to move forward this quarter?"
Adaptation Rules — mid-track pushback
- If buyer challenges the pain hypothesis → drop straight to a discovery question, do not defend the hypothesis.
- If buyer asks about price early → answer with a range, then redirect to the value bridge before continuing the track.
- If buyer goes quiet on a proof point → ask “does that number surprise you?” rather than piling on more proof.
- Never skip the Question component — a talk track without a question becomes a monologue and loses the room.
How to use it
Identify which persona and deal stage you're walking into, pull the matching components from each section, assemble them in Opener → Pain Hypothesis → Value Bridge → Proof Point → Question → Next-Step Ask order, then adapt live using the pushback rules.