// 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.
| name | challenger-sale |
| description | 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. |
Dual-use skill:
When to activate: user asks about challenger sale, commercial teaching, insight selling, teach-tailor-take control, constructive tension, or reframing customer thinking.
<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 tensionExample: Build a Challenger teaching pitch for higher-ed AV directors
</quick_start>
<success_criteria>
<core_concepts>
| 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.
<teach_framework>
Demonstrate you understand their world. NO product mentions.
Introduce an insight that challenges their current assumption.
Data and evidence that makes the problem undeniable. Stack 2-3 proof points.
Connect to what this means for THEM personally (not the organization).
Show how to solve the problem. Still NOT your product — describe the approach/architecture.
NOW — and only now — connect your capabilities to the New Way.
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 | 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 |
<take_control>
"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?"
"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?"
"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?"
<email_templates>
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]
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>
JTBD (What job?) → Blue Ocean (Where's the space?) → BMC (How to deliver?)
↓
Challenger (What insight reframes their thinking?)
↓
NSTTD (How to communicate with tactical empathy)
↓
OUTPUT: Email / Call / Deck
JTBD: The Reframe IS the underserved outcome the prospect doesn't know they have. Use JTBD outcome scoring to identify the insight.
Blue Ocean: Commercial insights often point to ERRC factors (Create/Raise) — what the industry doesn't offer yet.
BMC: Tailoring maps directly to Customer Segments and Value Propositions blocks.
NSTTD: "Take Control" is amplified by tactical empathy, calibrated questions, and the FM DJ voice. Use accusation audits before delivering tough reframes.
<example_session>
User: Build a Challenger teaching pitch for a Higher Ed AV Director evaluating lecture capture for 50+ classrooms
You're managing AV across dozens of classrooms — maybe multiple buildings or campuses — with faculty who just want to walk in and teach. Meanwhile, students expect every lecture recorded reliably, and your team is the one on the hook when something doesn't capture. The pressure to deliver consistent hybrid delivery at scale is real, and it only grows each semester.
Most institutions think their biggest lecture capture cost is hardware. But what we consistently hear from AV teams managing 50+ rooms is that the majority of total cost is staff time — troubleshooting software encoders, rebooting crashed PCs, and re-recording failed sessions. The hardware line item is the visible cost; the invisible cost is your team's hours.
Walk them through the math using THEIR numbers (ask during discovery or estimate conservatively):
Your AV team is the one getting the call at 8 AM Monday when Professor Chen's Friday lecture didn't record. The faculty member isn't calling the software vendor — they're calling your team. And when a semester's worth of recordings is spotty, it's your department's credibility on the line with the Provost, not the vendor's.
What leading R1 universities are doing is eliminating the software layer entirely — moving to appliance-based capture that records regardless of what happens to the campus network or the classroom PC. No software agent on the podium machine means no OS updates breaking the encoder, no antivirus quarantining the capture process, no PC reboots mid-lecture.
This is exactly what Pearl-2 was built for — a dedicated hardware encoder that captures, streams, and records simultaneously with zero PC dependency. When the network drops, it keeps recording locally. When the LMS goes down, it buffers and uploads later. Faculty walk in, press one button (or it auto-starts on schedule), and the lecture is captured. Your team manages 50+ rooms from a single web dashboard instead of remoting into 50 PCs.
| Stakeholder | Reframe Angle | Key Metric | CTA |
|---|---|---|---|
| VP Academic Affairs | "Cost of failed recordings = student complaints + accreditation risk" | Staff hours lost, failure rate | Executive briefing |
| AV Director | "Your team is troubleshooting problems that shouldn't exist" | Staff hours recovered, single-pane management | Working session |
| IT Security | "No software agent = no attack surface, no OS patches to manage" | Zero endpoint footprint, HTTPS only | Reference call |
| Procurement | "Compare 5-year TCO: hardware appliance vs software + PC refresh" | TCO comparison worksheet | Formal quote |
When prospect says "We're also talking to Panopto/Echo360/Kaltura":
"Those are strong platforms for content management. The question is what sits in the classroom doing the capture. Most CMS platforms rely on a software agent running on a PC — that's the layer where failures happen. Pearl integrates with Panopto, Kaltura, YuJa, and Canvas natively. The difference is what happens when the PC freezes mid-lecture."
First question every Higher Ed buyer asks: "Does it work with our LMS?" Pearl-2 integrates with Canvas, Blackboard, Moodle, Kaltura, Panopto, YuJa, and Echo360 via LTI/REST/RTMP. Lead with this in the Warmer if you know their stack.
Subject: Lecture capture at [University]
[Name],
Most AV teams managing 50+ classrooms tell us the same thing — their
biggest lecture capture cost isn't hardware. It's staff time
troubleshooting software crashes and re-recording failed sessions.
The pattern we see at R1 institutions: they're removing the software
layer entirely and moving to appliance-based capture.
Worth 15 minutes to compare notes on what's working?
[Signature]
</example_session>
<anti_patterns>
As the final step, write to ~/.claude/skill-analytics/last-outcome-challenger-sale.json:
{"ts":"[UTC ISO8601]","skill":"challenger-sale","version":"1.0.0","variant":"default",
"status":"[success|partial|error]","runtime_ms":[estimated ms from start],
"metrics":{"insights_generated":[n],"reframes_created":[n],"stakeholders_tailored":[n]},
"error":null,"session_id":"[YYYY-MM-DD]"}
Use status "partial" if some stages failed but results were produced. Use "error" only if no output was generated.
Map task types to the best agent, skill, model, and fallback. Route any task to the right tool. Use when: which agent, route task, agent for this, best agent, capability matrix.
Orchestrate teams of parallel Claude Code sessions working on the same codebase. Handles task decomposition, agent coordination, context isolation, and merge strategies. Builds on worktree-manager for infrastructure.
REST/GraphQL API design patterns - resource naming, HTTP methods, error handling, pagination, versioning. Use when: design API, REST endpoints, GraphQL schema, error responses, pagination, rate limiting, API documentation.
Tool-based API testing with Postman and Bruno - collections, environments, test assertions, CI integration. Use when: postman, bruno, API testing, test API endpoint, API collection, HTTP request testing, endpoint validation.
Blue Ocean Strategy analysis using ERRC framework and Strategy Canvas. Use when: blue ocean, market differentiation, competitive strategy, value innovation, ERRC framework, strategy canvas, new market space, competitive analysis.
Business model design using Alexander Osterwalder's 9 building blocks. Use when: business model, canvas, value proposition, customer segments, revenue streams, startup planning, analyze business, business strategy.