challenger-sale（挑战者销售）

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.

<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)

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

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?)
                                    ↓
              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.

Email Writing Principles (First Principles Lens)

1. JTBD: Lead with the prospect's job, not your product
2. Challenger: Deliver a commercial insight that reframes their assumption
3. NSTTD: Use tactical empathy to lower defenses
4. EE lens: Be precise, concise, technically grounded — no fluff
5. Max 100 words for cold outreach </integration_points>

<example_session>

Example: Higher Ed Lecture Capture — Commercial Teaching Pitch

User: Build a Challenger teaching pitch for a Higher Ed AV Director evaluating lecture capture for 50+ classrooms

Step 1: The Warmer

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.

Step 2: The Reframe

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.

Step 3: Rational Drowning

Walk them through the math using THEIR numbers (ask during discovery or estimate conservatively):

• "How often do your software encoders crash or fail to record?" (typical range we hear: 5-15% of sessions)
• "How long does it take your team to troubleshoot each incident?" (typical: 30-60 min)
• At 50 rooms × 4 sessions/day × 180 teaching days: ~36,000 sessions/year
• Even at a conservative 5% failure rate = ~1,800 incidents requiring some response
• Not all are hands-on, but ask: "How many of those does your team physically respond to?"
• Multiply their answer × their avg troubleshooting time × their loaded labor rate
• Key: Let THEM fill in the numbers. The math is more powerful when it's their data, not yours. Never cite research you can't produce.

Step 4: Emotional Impact

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.

Step 5: A New Way

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.

Step 6: Your Solution

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 Tailoring

Competitive Reframe

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."

LMS Integration Note

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.

Cold Email (Challenger Style)

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>

Anti-Patterns

• Leading with product features — Challengers teach about the PROBLEM, not the solution
• Generic insights — "Digital transformation is important" is NOT a commercial insight
• Retreating on price — Challengers redirect to value, never discount without removing scope
• Same pitch for every stakeholder — Tailoring is not optional
• Being aggressive — Constructive tension is NOT confrontation. It's respectful disagreement backed by evidence
• Skipping the Warmer — You earn the right to challenge by first proving you understand their world </anti_patterns>

Emit Outcome Sidecar

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.