Practice with intent
Draw a scenario.
Sharpen the conversation.
Match a GitHub product to a relevant customer persona. Use the brief to run a focused discovery role-play.
Scenario machine
Select a card to reroll only that dimension.
Sources and about this mapping
The starter mappings are role-play guidance based on documented GitHub product capabilities and the responsibilities of common customer roles. Each persona has one primary team and hierarchy level to keep scenarios easy to navigate, even when the role works across functions. These mappings are not pricing, licensing, or roadmap claims. Edit mode lets your team tailor every scenario locally.
Scenario editor
Open the hosted app in multiple tabs to sync edits and the active scenario live within the same browser. Separate browsers or laptops still require JSON export/import.
Existing-customer cold call
Practice the opener.
Start a conversation.
Use a calm, relevant opening. Recognize the account relationship, surface one possible gap, ask for their perspective, then stop talking.
Cold-call opening
Practice script
This is a hypothesis, not a diagnosis. The final question should surface a specific blind spot and make the customer think, not steer them toward a rehearsed answer.
Scenario call track
Your three-part opening
Select one option to use. Both are shown for practice.
Choose one angle for this attempt, not all three.
Pause. Let the customer speak next.
Practice focus
Opening readiness
The goal is not to pitch or force a meeting. Earn enough relevance to start a useful customer conversation.
- Recognize what the customer already uses
- Use one specific, plausible gap
- Stay neutral and easy to disagree with
- End with a specific “How do you know?” question
- Deliver slowly enough to sound conversational
If they engage
Light SPIN follow-ups
Do not turn the opener into a full discovery call. Ask one relevant follow-up, listen, and agree a customer-led next step only when useful.
Cold-call approach and sources
This builder synthesizes public guidance from Josh Braun and Benjamin Dennehy for practice. The default questions follow Braun’s “poke the bear” principle: surface a specific risk the customer may not have considered, avoid a leading answer, and let them examine how they know the current approach is working. Dennehy’s emphasis on brevity, confidence, and practice informs the delivery coaching. The wording in this app is original and configurable.