Talk Track Builder

Build practical, role-specific talk tracks that help sellers run clearer, more outcome-focused conversations.

Confirm Inputs First

• If a current revenue-enablement-context exists, use it first for ICP, persona language, stage labels, and proof standards.
• Confirm audience role and seniority (AE, SDR, SE, manager).
• Confirm persona and buying stage.
• Confirm use case or commercial motion.
• Confirm core value message and proof points.
• Confirm top objections or risk themes expected in the conversation.
• Confirm desired call outcome and next-step ask.
• If inputs are incomplete, ask for only the minimum missing items or proceed with labeled assumptions.

Read The Right Reference

• Read references/talk-track-framework.md before drafting tracks; use it for structure, branch logic, and stage-specific variants.

Default Workflow

1. Anchor the talk track to one call objective and one concrete next-step commitment.
2. Pull existing message assets when available: value proposition, objection library, battlecard guidance, and current release notes.
3. Select the right track variant: discovery, demo, commercial, renewal/expansion, or manager inspection coaching.
4. Define the conversation arc: opener, context framing, diagnosis, value bridge, proof, close.
5. Write persona-specific prompts and assertions for the selected stage objective.
6. Draft concise transitions between sections to avoid scripted jumps.
7. Add proof inserts that sellers can deliver naturally in under 20 seconds.
8. Add branch paths for high-likelihood turns: skeptical buyer, multi-stakeholder pushback, pricing pressure, and competitor challenge.
9. Add landmines to avoid overclaiming or premature pitching.
10. Add manager inspection cues that test whether the track improves decision quality.
11. Route adjacent work: For message strategy or differentiation, use value-prop-and-positioning. For objection playbooks across many scenarios, use objection-library-builder. For competitor-specific counters, use battlecard-builder. For coaching on a real call, use call-review-coach.

Output Contract

• Talk tracks versioned by role, persona, and stage.
• Discovery question set grouped by objective.
• Transition lines and checkpoint language.
• Proof snippets and when to deploy them.
• Branch-path response lines for common derailments.
• Manager inspection checklist for track adherence and effectiveness.
• Assumptions list when source inputs were incomplete.

What To Avoid

• Writing polished scripts that sound unnatural in live calls.
• Mixing discovery and demo goals into one unfocused conversation.
• Ignoring role/stage differences and shipping a one-size-fits-all track.
• Treating objection handling as rebuttal lines without diagnostic questions.

Quality Bar

• Track sounds like natural speech rather than marketing copy.
• Questions create diagnostic insight, not generic rapport.
• Proof statements are specific and credible.
• Role and stage differences are explicit, not cosmetic.
• The next-step ask is concrete and testable.