challenger-sale
The Challenger Sale methodology — Teach-Tailor-Take Control framework for B2B sales. Use when: challenger sale, commercial teaching, constructive tension, reframe, teach tailor take control, insight selling, commercial insight, challenger rep.
What this skill does
<objective>
Challenger selling: win deals by teaching prospects something new about their business, tailoring the message to their stakeholders, and taking control of the conversation. Based on Dixon & Adamson's research of 6,000+ sales reps.
**Dual-use skill:**
- **BDR/Sales Mode:** Build commercial insights for outreach, tailor messages to stakeholders, handle objections with constructive tension
- **Strategy Mode:** Develop teaching pitches for entire verticals, build reframe narratives, design commercial teaching choreography
When to activate: user asks about challenger sale, commercial teaching, insight selling, teach-tailor-take control, constructive tension, or reframing customer thinking.
</objective>
<quick_start>
# Quick Start
**Three modes:**
- `Teach`: Build a commercial insight for [prospect/vertical]
- `Tailor`: Adapt insight for [stakeholder role] at [company]
- `Take Control`: Handle [objection] with constructive tension
**Example:** `Build a Challenger teaching pitch for higher-ed AV directors`
</quick_start>
<success_criteria>
# Success Criteria
- [ ] Commercial insight passes the "So What?" test — prospect learns something new about their OWN business
- [ ] Message is tailored to specific stakeholder type (economic buyer vs champion vs user vs blocker)
- [ ] Objection handling uses reframe (not retreat or discount)
- [ ] Teaching pitch follows the 6-step choreography (Warmer > Reframe > Rational Drowning > Emotional Impact > New Way > Your Solution)
- [ ] Insight leads to YOUR unique capabilities (not generic advice anyone could give)
</success_criteria>
<core_concepts>
# Core Concepts
## The 5 Rep Profiles (CEB Research — 6,000+ Reps)
| Profile | % of Star Performers | Approach |
|---------|---------------------|----------|
| **Challenger** | 39% | Teaches, tailors, takes control |
| Hard Worker | 17% | Always going above and beyond |
| Relationship Builder | 7% | Builds strong personal advocacy |
| Lone Wolf | 25% | Follows own instincts, breaks rules |
| Reactive Problem Solver | 12% | Reliably resolves service issues |
**Key insight:** In complex B2B sales, Relationship Builders are the WORST performers (only 7% of stars). Challengers dominate because customers value insights over relationships.
## The 3 Challenger Skills
1. **Teach** for differentiation — lead with insights, not products
2. **Tailor** for resonance — adapt the message to the stakeholder
3. **Take Control** of the sale — assert on value, not price
</core_concepts>
<teach_framework>
# Commercial Teaching Pitch — 6-Step Choreography
## Step 1: The Warmer
Demonstrate you understand their world. NO product mentions.
- "Universities running 50+ lecture halls face a specific challenge with hybrid delivery..."
- "Courts managing remote testimony are discovering that consumer video tools create compliance gaps..."
## Step 2: The Reframe
Introduce an insight that challenges their current assumption.
- Pattern: "Most [personas] believe [common assumption]. But [data/evidence] shows [surprising reality]."
- "Most teams think their biggest cost is hardware. But what we hear from AV teams managing large deployments is that the majority of total cost is actually staff time — troubleshooting, re-recording, and fielding complaints."
## Step 3: Rational Drowning
Data and evidence that makes the problem undeniable. Stack 2-3 proof points.
- Industry stats, peer benchmarks, cost calculations
- "That's $X per year in staff time" / "Y% of events experience quality issues"
## Step 4: Emotional Impact
Connect to what this means for THEM personally (not the organization).
- "Your team is the one getting the call at 8 PM when the stream drops during the board meeting."
- "When lecture capture fails mid-semester, it's your department that takes the heat."
## Step 5: A New Way
Show how to solve the problem. Still NOT your product — describe the approach/architecture.
- "The solution is hardware-based encoding that eliminates the software layer entirely..."
- "What leading institutions are doing is separating capture from distribution..."
## Step 6: Your Solution
NOW — and only now — connect your capabilities to the New Way.
- "This is exactly what Pearl was designed for — appliance-based encoding with..."
## Template
```
WARMER: "[Persona] dealing with [situation] face [specific challenge]..."
REFRAME: "Most believe [assumption]. But [evidence] shows [surprise]."
DROWNING: "[Stat 1]. [Stat 2]. That's [quantified impact]."
EMOTIONAL: "Your team is the one that [personal consequence]."
NEW WAY: "What leading [peers] are doing is [approach]..."
SOLUTION: "This is exactly what [product] was built for — [capability]."
```
</teach_framework>
<tailor_framework>
# Stakeholder Tailoring Matrix
| Stakeholder | Cares About | Language | Insight Angle | CTA Style |
|-------------|------------|----------|---------------|-----------|
| **Economic Buyer** (CFO/VP) | ROI, risk reduction, strategic alignment | Business outcomes, $ | "Cost of inaction is $X/year" | Executive briefing |
| **Champion** (Director/Mgr) | Solving their pain, career impact | Operational metrics | "Here's what your peers are doing" | Working session |
| **End User** (Technician) | Will it work? Integration? Workflow? | Technical specs | "Here's what you're missing in your stack" | Technical demo |
| **Blocker** (IT/Procurement) | Risk, compliance, vendor lock-in | Standards, SLAs, security | "Here's how to de-risk this" | Reference call |
## Tailoring Rules
1. Same insight, different framing for each stakeholder
2. **Economic buyer:** Lead with business impact, end with ROI
3. **Champion:** Lead with peer comparison, end with their career win
4. **User:** Lead with technical proof, end with workflow improvement
5. **Blocker:** Lead with risk mitigation, end with standards compliance
</tailor_framework>
<take_control>
# Constructive Tension Techniques
## The Assertive Redirect (when asked for discount)
> "I understand budget is a concern. Before we talk pricing, let me make sure we agree on the value. You mentioned [pain point] costs your team [X]. If we solve that, we're talking about [Y] in savings. Does that math work for you?"
## The Pocket Veto Counter (when deal stalls at consensus)
> "It sounds like there might be different priorities across your team. In our experience, the most effective approach is to align on the problem first. Would it help if I put together a brief for [economic buyer] that quantifies the impact?"
## The Respectful Challenge (when prospect is wrong)
> "I hear that. And I've seen other teams take that approach. What I've also seen is [counter-evidence]. Would you be open to looking at it from a different angle?"
## Price Anchoring Sequence
1. Quantify the problem FIRST (rational drowning)
2. Establish the cost of doing nothing
3. THEN present price as a fraction of the problem cost
4. Never defend price — redirect to value gap
</take_control>
<email_templates>
# Email Templates — Challenger Style
## Cold Email (under 100 words)
```
Subject: [Specific challenge] at [Company]
[Name],
Most [role/vertical] teams assume [common assumption].
But [surprising data point] — meaning [quantified impact for their org].
[One sentence about the new approach leading organizations are taking].
Worth a 15-minute conversation to see if this applies to [Company]?
[Signature]
```
## Follow-up — The Reframe Nudge
```
Subject: Re: [Original subject]
[Name],
Wanted to share one more data point — [peer organization] was in a similar
position and found that [specific outcome after changing approach].
Would it make sense to compare notes?
```
</email_templates>
<integration_points>
# Integration Points
## Strategy Skill Cluster — First Principles Pipeline
```
JTBD (What job?) → Blue Ocean (Where's the space?) → BMC (How to deliver?)
↓
Challenger (What insight reframes their thinking?)
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.