The Problem Articulation Series
Most revenue leaders can describe what's wrong. Very few can define the problem with enough precision that every downstream decision becomes obvious.
That gap — between describing and defining — is the difference between strategy that generates activity and strategy that generates results.
Richard Rumelt called diagnosis the first act of good strategy. McKinsey built entire methodologies around structured problem decomposition. The Challenger Sale showed that reframing a buyer's understanding of their own problem is the highest-leverage selling act. MIT Sloan called problem articulation "the most underrated skill in management."
But each tradition keeps the skill in its own silo. Strategists treat it as internal analysis. Consultants treat it as decomposition for the team room. Sales methodologies treat it as a discovery technique for individual reps. Positioning experts treat it as a setup for the product pitch.
Nobody has connected them into a single discipline where the quality of your problem articulation — how precisely you name what's broken, why, and what's at stake — is itself the competitive advantage. Where the diagnosis earns the right to prescribe.
This is a three-part series on that discipline.
| Article | Title | Focus |
|---|---|---|
| 1 | Problem Articulation as a Skill | The framework: 8 vectors that separate vague complaints from actionable diagnosis |
| 2 | The Archetype Multiplier | Applied: the same problem articulated for CRO and VP Sales — same root cause, completely different language |
| 3 | The Z Axis | Depth + force: how archetype dimensions and the forces acting on a buyer turn a relevant problem into an inevitable conversation |
Article 1: Problem Articulation as a Skill
Blair Enns wrote: "Prescription without diagnosis is malpractice." That's the right frame. Most revenue organizations prescribe constantly — new playbooks, new methodologies, new tools, new hires — without ever precisely diagnosing the problem those prescriptions are meant to solve. The result is activity without coherence. Initiatives that sound right but don't connect to root cause.
A well-defined problem does three things:
- Names the constraint. Not the aspiration, not the symptom — the actual bottleneck limiting performance.
- Identifies the friction inside the system. Where behavior, incentives, perception, or capability are misaligned — and why.
- Makes the stakes explicit. What happens if this isn't resolved. To whom. How fast.
Without all three, teams chase symptoms. They ship initiatives that sound right but don't connect to root cause. They solve adjacent problems while the real one compounds.
When the problem is clear, it becomes a filter:
- Insights must explain why that problem exists.
- Choices must aim to resolve it.
- Actions must demonstrably reduce it.
- Outcomes should feel like the logical consequence.
If an initiative can't be traced back to the defined problem, it doesn't belong in the strategy.
The Eight Vectors of Problem Articulation
Every problem statement can be evaluated along eight vectors. Think of them as dials. Weak statements have most dials turned down. Strong ones have them up. The skill is knowing which dials are low and turning them up.
The vectors follow a sequence in three phases:
Phase 1 — Establish. Who cares and what's happening?
Phase 2 — Diagnose. Why, where in the system, and how deep?
Phase 3 — Stakes. How urgent, and who pays?
Vector 1: Relevance
From generic to "that's MY problem."
Relevance comes first because it determines whether the rest get heard. You can articulate a problem perfectly — specific, causal, quantified — and get nothing back. Not because it's wrong, but because it's framed for a different audience.
The same issue — "reps aren't engaging the buyer group effectively" — is a completely different problem depending on who you're talking to:
| Audience | The same problem, made relevant |
|---|---|
| CRO | "43% of your commit deals slip because there's no independent buyer signal validating deal readiness — your forecast is a confidence poll, not a data model." |
| VP Sales | "Your middle 60% of reps run single-threaded deals on junior contacts because the playbook tells them what to do but not how to read the buyer." |
| Sales Manager | "You spend 70% of your deal review time on deals that were already going to close or already dead — you have no signal for which deals in the middle need your intervention this week." |
| Seller | "You lost the Acme deal because someone in finance you never met redirected the budget — and you had no way to know they existed." |
| CFO | "Forecast variance has exceeded 15% for three consecutive quarters because the input is rep self-assessment, not buyer behavior data." |
Same problem. Five framings. Each lands because it's stated in the language of that person's priorities, metrics, and daily reality.
The test: If you swapped the audience — gave the CFO version to the seller — would it still land? If yes, it's not relevant enough.
How to dial it up: Know the archetype. Their top priorities. Their KPIs. Their highest-severity pain point. Their communication style. Frame in their metrics, their language, their consequences.
Relevance is the multiplier. The other seven vectors make the problem good. Relevance makes it land.
Vector 2: Specificity
From vague to precise. Name the segment, the metric, the timeframe.
| Level | Example |
|---|---|
| Vague | "Our pipeline isn't strong enough." |
| Moderate | "Our enterprise pipeline is underperforming this quarter." |
| Specific | "Enterprise pipeline above $100K has declined 22% quarter-over-quarter while SMB has grown 15%, creating a mix shift that drops average deal size and puts $2.4M at risk." |
The test: Can someone who wasn't in the room understand exactly what's wrong, in what segment, by how much, and since when?
Vector 3: Quantification
From qualitative to measured.
| Level | Example |
|---|---|
| Qualitative | "Reps aren't productive enough." |
| Directional | "Most reps are below quota." |
| Quantified | "34% of reps hit quota last quarter, down from 52% two quarters ago. The gap between top and bottom quartile win rates has widened from 1.8x to 2.6x in 12 months." |
The test: Could two people read this and arrive at the same understanding of severity? Numbers eliminate ambiguity. Adjectives create it.
Vector 4: Causality
From symptom to root cause. Ask "why" at least twice.
| Level | Example |
|---|---|
| Symptom | "Win rates are declining." |
| Proximate cause | "Win rates are declining because deals stall in late stages." |
| Root cause | "58% of deals that reach proposal are single-threaded on a mid-level champion who lacks the authority to push a buying decision — and our process has no step requiring multi-threading before a proposal goes out." |
The test: If you removed the cause from the statement, would it still feel complete? If yes, you've described a symptom.
Vector 5: Locus
From "it's happening to us" to "we're creating this."
| Level | Example |
|---|---|
| External | "The market is more competitive." |
| Shared | "Competitive pressure increased and our approach hasn't adapted." |
| Internal | "We're losing competitive deals because our reps engage the buyer group the same way regardless of whether there's an incumbent — and we have no playbook for displacement deals, which now represent 40% of pipeline." |
The test: Does the statement point to something you can change?
Vector 6: Systemic Depth
From isolated incident to structural pattern.
| Level | Example |
|---|---|
| Incident | "We lost the Acme deal because the champion left." |
| Pattern | "We've lost three enterprise deals this quarter when our primary contact changed roles." |
| Systemic | "78% of our enterprise deals are single-threaded. Our CRM, deal review, and methodology don't require or measure multi-threading — so we systematically build fragile deals and discover the fragility only when a person leaves." |
The test: If you fixed this one instance, would the problem come back?
Vector 7: Tension
From comfortable to urgent. What breaks if this continues?
| Level | Example |
|---|---|
| Low | "We should probably look at our sales process." |
| Moderate | "If deal cycles keep extending, we'll miss the annual target." |
| High | "Deal cycles have expanded 38% in four quarters. At this trajectory, we close 23 fewer enterprise deals this year — a $4.1M gap that can't be filled by adding pipeline because the bottleneck is conversion, not volume. Every quarter we wait, the gap compounds." |
The test: Does it create a felt need to act now? Tension comes from trajectory (getting worse), compounding (delay increases cost), and irreversibility (window closing).
Vector 8: Stakeholder Consequence
From abstract to personal.
| Level | Example |
|---|---|
| Abstract | "Forecast inaccuracy creates planning challenges." |
| Departmental | "Forecast misses force finance to revise hiring plans." |
| Personal | "When the CRO's commit drops 20% in week 10, the CFO re-cuts the plan, the CEO re-sets with the board, and the CRO walks into the next meeting having missed two quarters in a row — a pattern that raises the question of whether the revenue function has the right leadership." |
The test: Can the person hearing this see themselves in the consequence?
The Sequence
| Phase | Vector | Question | Job |
|---|---|---|---|
| Establish | 1. Relevance | Is this their problem? | Target |
| 2. Specificity | What exactly? | Name | |
| 3. Quantification | How bad? | Size | |
| Diagnose | 4. Causality | Why? | Explain |
| 5. Locus | Can we fix it? | Locate | |
| 6. Systemic Depth | Pattern or one-off? | Depth-test | |
| Stakes | 7. Tension | How urgent? | Time-bound |
| 8. Consequence | Who pays? | Personalize |
The phases mirror how a listener processes a problem. First: "Is this about me? What is it? How big?" Then: "Why? Can we fix it? Will it recur?" Finally: "How urgent? What happens to me?"
Skip a phase and you lose the room. Establish without Diagnose: "Interesting, but what do we do?" Diagnose without Stakes: "Makes sense, but we have other priorities." Stakes without Establish: "You're being dramatic — show me the data."
Five Registers
The same problem can be articulated in different registers depending on context. Below, one problem — reps lose deals because they can't read the buyer group — stated five ways.
Register 1: The One-Liner
For: elevator pitches, cold outreach, slides.
"Your reps run the same playbook on every buyer regardless of role — so a CFO who needs an ROI model gets the same pitch as a VP Engineering who needs an architecture review. That's why your top 20% close at 2x the rate of everyone else: they adapt. The system gives the other 80% no way to."
Register 2: The Diagnostic
For: discovery calls, strategy reviews, root-cause analysis.
"The win rate gap is 2.6x between top and bottom quartile. The differentiator isn't activity — it's buyer-reading ability. Top reps identify whether they're engaging a consensus builder or a technical decision maker and adapt. Middle reps default to one approach. The CRM, playbook, and enablement provide no archetype intelligence at the point of action. This isn't a people problem. It's a capability-distribution problem."
Register 3: The Economic
For: CFOs, board presentations, business cases.
"With 120 reps at $800K quotas, moving the middle 60% from 16% to 22% win rate — still below the top 34% — represents $6.9M in incremental closed revenue with zero additional pipeline, headcount, or marketing spend. The cost of not solving this isn't just unrealized revenue — it's the compounding effect of compensating for low conversion by adding volume, which increases CAC and compresses margins every quarter."
Register 4: The Narrative
For: offsites, strategy presentations, building conviction.
"A rep who joined six months ago. Smart, coachable, works hard. She's in a $200K deal. Three great meetings with the VP of Operations. She sends the proposal. Silence. Three weeks. Deal goes dark. She marks it 'no decision.'
What she didn't know: the CFO — who she never met — was redirecting that budget to infrastructure. The IT Director — who she never spoke to — had a ten-year relationship with the incumbent. Three people in the deal who would determine the outcome. She only ever spoke to one.
She didn't fail. The system failed her. It told her to multi-thread but never told her who else was in the room."
Register 5: The Competitive
For: reframing inaction as strategic risk.
"Every company selling to enterprise faces the same buyer-group complexity. The question is whether your team navigates it with intelligence or intuition. Right now, your top reps use intuition and your middle reps barely navigate it at all. Meanwhile, competitors are instrumenting the buyer side: mapping stakeholders, classifying archetypes, scoring deal health on buyer signals. The window where this is a differentiator — rather than table stakes — is now."
Qualification Scorecard
Before presenting a problem statement, run it through this scorecard. Each question maps to a vector.
| # | Vector | Question | Weak (1) | Moderate (3) | Strong (5) |
|---|---|---|---|---|---|
| 1 | Relevance | Would this person recognize it as their problem? | Generic audience or wrong role | Touches their world but uses your language | Stated in their KPIs, priorities, consequences — would feel wrong delivered to a different role |
| 2 | Specificity | Could two people understand the exact same problem? | "We need to improve" | Named segment OR metric, not both | Segment, metric, timeframe |
| 3 | Quantification | Are there numbers? | None | Directional: "most," "many" | Precise: percentages, dollars, comparisons |
| 4 | Causality | Does it explain why? | Desire or symptom only | Proximate cause | Root mechanism — system design, incentive, or structural gap |
| 5 | Locus | Does it point to something we can change? | External: "market is tough" | Shared: "market changed and we haven't adapted" | Internal: specific system, process, or capability gap |
| 6 | Systemic Depth | If we fix this instance, does it come back? | Isolated incident | Recurring pattern | Mechanism that generates the pattern |
| 7 | Tension | Felt need to act now? | No urgency | Implies risk | Trajectory, compounding, or closing window |
| 8 | Consequence | Can the audience see who pays? | Abstract: "creates challenges" | Departmental | Personal: named role, specific toll |
32-40: Ready. Clear enough to filter every decision that follows. 24-31: Close. Identify which vectors are below 3. 16-23: Not ready. Will generate debate about what the problem is. Below 16: Topic, not a problem. Start over.
Grammar Patterns
Six patterns for constructing problem statements. Once you internalize them, you generate new statements fluently.
1. The Quantified Gap
"[Metric] is at [current] against [target], a gap of [X%], because [root cause]."
2. The Misaligned System
"We measure/incentivize [X], but the outcome we need requires [Y]. The result is [consequence]."
3. The Invisible Cause
"[Symptom] is not caused by [common assumption]. It's caused by [hidden root cause] — which is why [standard remedy] hasn't worked."
4. The Compounding Trajectory
"[Problem] has moved from [past] to [present] over [timeframe]. At this trajectory, [future consequence]. The standard response — [what we've been doing] — accelerates the problem because [why]."
5. The Capability Asymmetry
"[Top performers] achieve [result] because they [capability]. [Everyone else] cannot, because [system/tooling/process] provides no mechanism to [scale it]. The gap costs [quantified impact]."
6. The Structural Blindspot
"Our [system] captures [what it tracks]. It doesn't capture [what it misses]. This means [decision] is based on [incomplete input], producing [failure mode]."
Article 2: The Archetype Multiplier
Miller Heiman gave us four buyer roles — Economic Buyer, User Buyer, Technical Buyer, Coach. Useful but purely structural: two Economic Buyers can behave completely differently and the framework can't distinguish them. The Challenger Sale gave us seven stakeholder archetypes — Go-Getters, Teachers, Skeptics, Guides, Friends, Climbers, and the monolithic "Blocker." Better, but classified by mobilization capacity, not by how to engage them. MEDDIC gave us a qualification checklist — find the Champion, identify the Economic Buyer — but treated each as a box to check, not a behavioral model. Gartner showed us that buying groups now average 13-19 stakeholders with 74% exhibiting "unhealthy conflict" during the decision process.
Every framework classifies buyers. None tell you how to talk to them — how to calibrate the problem, the causality, the stakes, and the language to the specific person across the table.
The archetype is Vector 1 — Relevance — made systematic. It tells you what this person is measured on, what keeps them up at night, how they process information, and how they make decisions. The same underlying problem requires completely different articulation depending on who hears it. Not different spin. Different structure. Different causality, different locus, different consequence.
CRO — Chief Revenue Officer
The Archetype
| Dimension | CRO Profile |
|---|---|
| Communication style | Data-driven — leads with metrics, expects evidence, distrusts narrative without numbers |
| Decision pattern | Consensus — builds alignment across sales, marketing, CS, finance before committing |
| Budget authority | Shared — owns revenue budget but needs CFO alignment for major investments |
| Influence scope | Cross-functional — touches marketing, product, CS, finance; everything flows through revenue |
What They're Measured On
| Priority | Weight | What it means |
|---|---|---|
| Pipeline Generation | 5 | Sufficient coverage to hit targets |
| Win Rate Improvement | 5 | Converting pipeline through better execution and buyer engagement |
| Sales Velocity | 4 | Shortening cycles to accelerate recognition |
| Quota Attainment | 4 | Majority of reps hitting quota consistently |
| Forecast Accuracy | 3 | Precise forecasts that build trust with CFO and board |
What Hurts Most
| Pain Point | Severity |
|---|---|
| Pipeline Quality | 5 — unqualified pipeline inflating coverage without substance |
| Forecast Misses | 5 — deals slipping from commit, eroding board credibility |
| Rep Ramp Time | 4 — new hires taking too long, creating revenue gaps |
| Cross-Functional Alignment | 3 — marketing and product not aligned with GTM |
Articulation Rule
The CRO is data-driven. Every problem must be quantified. They manage by metrics — if you can't put a number on it, it doesn't exist. But numbers alone don't move them. The number must connect to one of their five priorities, explain why it's happening, and make clear what's at stake personally — their credibility with the board, their ability to call the number, their confidence in the team.
The CRO doesn't want to hear "things could be better." They want: "Here's the metric. Here's the gap. Here's the mechanism. Here's what it costs. Here's what we do."
Problem 1: Pipeline Substance
Derived from: Pipeline Generation (weight 5) + Pipeline Quality (severity 5).
Instead of, "We need more pipeline,"
Say, "62% of our pipeline has no identified decision maker engaged — our 3.2x coverage ratio is masking a qualified-pipeline gap that puts the majority of forecasted revenue at risk this quarter."
| Vector | Applied |
|---|---|
| Relevance | CRO's #1 priority and #1 pain point. Uses their language: coverage ratio, forecasted revenue, at risk. Framed as a CRO visibility problem. |
| Specificity | Pipeline without a decision maker. Not "pipeline is bad" — which pipeline, and why. |
| Quantification | 62% without a decision maker. 3.2x coverage. The CRO's own metrics turned against the comfortable narrative. |
| Causality | System rewards pipeline creation (seller actions) but doesn't measure qualification (buyer actions). Reps are incentivized to fill, not qualify. |
| Locus | Internal. CRM stage definitions, pipeline review criteria, and rep incentives are all within the CRO's control. |
| Systemic Depth | Nothing in the process requires buyer-side validation before a deal counts as coverage. Fix one quarter and the mechanism produces the same result next quarter. |
| Tension | The CRO presents this pipeline to the board. When 40%+ of commit deals slip because no budget holder was engaged, credibility erodes. Two consecutive misses and the conversation shifts from pipeline to leadership. |
| Consequence | The CRO stands in front of the board with a number built on pipeline that's never been tested against buyer reality. The CFO loses trust. The board loses patience. |
Coherence chain: Pipeline coverage and pipeline substance are two different things, but the system treats them as one. Insight: The CRO is making forecast and resource decisions on a metric that doesn't reflect commercial reality. Choice: Measure pipeline by buyer group completeness, not dollar volume. Action: Buyer group mapping on every deal. Pipeline reviews filtered by buyer group health. Outcome: The CRO tells the board "3x coverage, 72% with a qualified buyer group and decision maker engaged." Pipeline becomes diagnostic.
Problem 2: Forecast Integrity
Derived from: Forecast Misses (severity 5) + Forecast Accuracy (weight 3).
Instead of, "We need better forecast accuracy,"
Say, "43% of deals marked commit in week 6 slip by quarter close because our forecast is built on rep self-assessment, not buyer engagement signals — we have no independent mechanism to verify deal readiness."
| Vector | Applied |
|---|---|
| Relevance | Forecast accuracy is weight 3, but forecast misses are severity 5. The articulation targets the pain, not the priority. You don't sell "improving forecast accuracy" (sounds like RevOps). You sell "never walking into a board meeting with a number that's about to move." |
| Specificity | Commit deals in week 6 that slip by close. Not "the forecast is off" — where in the quarter, which category. |
| Quantification | 43% commit-to-slip rate. |
| Causality | Reps grade their own homework. Downgrading feels like failure. The incentive structure rewards optimism. Buyer signals — decision maker engagement, blocker presence, procurement involvement — sit in emails and transcripts nobody synthesizes. |
| Locus | Internal. The methodology, the category definitions, the review cadence. The system gives the CRO no independent signal and asks the most optimistic people to self-report. |
| Systemic Depth | Forecast looks solid in week 4, degrades by week 10. Every quarter. The org frames it as "reps need to be more honest" rather than "the system has no verification layer." |
| Tension | The CFO builds hiring plans, cash flow, and board commitments on the CRO's number. Each miss makes the next one harder to explain. |
| Consequence | The CRO is the only executive whose primary planning metric is built on subjective self-reporting by the people most incentivized to be optimistic. Two consecutive misses and the board question isn't about the forecast. |
Coherence chain: The forecast is a confidence poll, not a data model. Insight: It aggregates seller belief, not buyer behavior. Choice: Build a parallel signal layer that reads buyer behavior and scores deal health independently. Action: Deal authority scoring. Buyer signal tracking that flags divergence from rep-reported stage. Outcome: At-risk deals surface in week 4, not week 10. The CRO's number becomes defensible.
Problem 3: Win Rate Variance
Derived from: Win Rate Improvement (weight 5) + Rep Ramp Time (severity 4).
Instead of, "We need to improve rep productivity,"
Say, "Top 20% close at double the win rate of the middle 60% — not because they work harder, but because they instinctively read buyer archetypes and adapt, a capability our playbooks and tooling have no mechanism to transfer."
| Vector | Applied |
|---|---|
| Relevance | Win rate is co-#1 (weight 5). But "improve rep productivity" sounds like enablement. "Your top performers have a capability your system can't distribute" is a system design problem — which matters because the CRO owns the system. |
| Specificity | Top 20% vs. middle 60%. Win rate gap, not activity gap. Names the capability: reading buyer archetypes. |
| Quantification | 2x win rate gap. |
| Causality | The playbook says what — "multi-thread," "find the economic buyer" — but not how. It doesn't tell a rep that the VP Ops is a Process Owner archetype who cares about workflow disruption, not ROI. Top reps figure this out over years. The system gives everyone else nothing. |
| Locus | Internal. Playbook, CRM, enablement — all within the CRO's system. Leadership frames it as a people problem. It's a capability distribution problem. |
| Systemic Depth | Every new hire starts from zero on buyer-reading. Every quarter the middle 60% underperforms. The org responds by adding pipeline or forecast calls. The actual gap is never addressed. |
| Tension | Revenue plan depends on the middle 60%. Hiring to compensate is losing math: more headcount, same win rate, higher CAC. 7+ month ramp compounds it. Every quarter unaddressed, the response is more volume — compounding Problem 1. |
| Consequence | The CRO owns the win rate. If the middle can't convert, their options are: hire more (expensive, slow), generate more pipeline (masks it), or fix the system that creates the variance. The first two are what they've been doing. |
Coherence chain: Top reps don't work harder — they read buyers better. Insight: A CFO needs a different conversation than a VP Product. Top reps adjust instinctively. The middle has a CRM and a one-size-fits-all playbook. Choice: Systematize the pattern recognition. Action: Archetype classification on every contact. Engagement guidance matched to archetype. Outcome: Variance shrinks. Win rate lifts across the team. Ramp compresses.
Problem 4: Invisible Blockers
Derived from: Win Rate Improvement (weight 5) + Pipeline Quality (severity 5).
Instead of, "We need better deal visibility,"
Say, "67% of lost deals were single-threaded at time of loss, and in 40%+ of those an internal blocker — defending an incumbent, protecting budget, or resisting change — was present and the rep never identified them."
| Vector | Applied |
|---|---|
| Relevance | Connects to win rate through the mechanism of why deals die. Reframes deal review: "You're reviewing the visible buyer group — the people who kill deals are the ones you can't see." |
| Specificity | Single-threaded at loss. Blocker present but unidentified. Three types: incumbent defenders, budget protectors, change resisters. |
| Quantification | 67% single-threaded. 40%+ with unidentified blocker. |
| Causality | CRM captures who the rep engaged. It can't capture who should be engaged but isn't. The Budget Guardian in finance, the Status-Quo Defender in operations — they don't show up because the rep doesn't know they exist. The system only records seller-side activity. |
| Locus | Internal. Deal review process, CRM data model, pipeline qualification — none require buyer group completeness beyond known contacts. |
| Systemic Depth | The org loses deals to the same blocker archetypes repeatedly. Loss reports say "no decision" — a label, not a diagnosis. |
| Tension | Every deal killed by an unseen blocker was counted. It showed coverage. It may have been in the forecast. Coaching is directionless — "qualify harder" changes nothing when the rep can't see who's missing. |
| Consequence | The CRO tells reps to multi-thread but gives them no way to know who's missing. Tells them to neutralize blockers but gives them no way to detect them. Coaching a behavior the system makes impossible. |
Coherence chain: Reps see who they're talking to. They can't see who they're not. Insight: Blockers are precisely the people who don't volunteer for meetings. Choice: Map the full buyer group — who's missing, not just who's present. Action: Blocker archetype detection from signals, role analysis, and transcript evidence. Outcome: Loss reasons become specific. The org learns from every deal.
Problem 5: Sales Velocity
Derived from: Sales Velocity (weight 4) + Quota Attainment (weight 4).
Instead of, "We need to shorten deal cycles,"
Say, "Cycle time has expanded from 68 to 94 days over four quarters, with the expansion concentrated between solution validation and negotiation — where the buyer's internal process takes over — because our CRM tracks seller stages but gives zero visibility into the buyer's procurement path or stakeholder alignment."
| Vector | Applied |
|---|---|
| Relevance | Velocity is weight 4, but directly compounds quota attainment (also 4): longer cycles = fewer deals per rep per year. For a data-driven CRO, this is a math problem. Framed as "we've optimized everything we can see and the remaining drag is in a process we can't see." |
| Specificity | Expansion between Stage 3 and Stage 5. Not "deals are slow" — exactly where the delay concentrates. |
| Quantification | 68 to 94 days. Four quarters. 38% expansion. |
| Causality | The CRO has optimized the sales process. The remaining drag is in the buyer's process: consensus builders need five-stakeholder alignment, economic buyers need a board-ready case, legal needs security review. None of it is in the CRM. The rep's update is "waiting for the customer." |
| Locus | Feels external but is internal. The system was built around the seller's process. The buyer's process is invisible by design, not by accident. |
| Systemic Depth | Different deal archetypes have fundamentally different buyer processes. Enterprise Land-Expand has a pilot path. Complex Multi-Thread has a committee path. The CRO is optimizing one generic process against five buying processes. |
| Tension | Every day a deal extends costs three ways: recognition delay, higher cost of sale, fewer deals per rep per year. "Create urgency" doesn't work because urgency is a buyer condition, not a seller behavior. |
| Consequence | The CRO has done everything the playbook says. Stages, methodology, exit criteria. Cycle times still expanding. The levers they've been pulling are the wrong levers. The remaining performance gain is on the buyer side, and they have no instrument to reach it. |
Coherence chain: The remaining velocity drag isn't in the seller's process — it's in the buyer's. Insight: The buyer's process varies by deal archetype. Choice: Classify every deal by archetype. Map the expected buyer process. Action: Deal archetype classification. Buyer process mapping. Alerts when actual diverges from expected. Outcome: Interventions become specific instead of generic.
The CRO's One Problem
Five expressions of one underlying problem:
The CRO's entire operating system — pipeline metrics, forecast methodology, rep enablement, deal review, velocity tracking — is built on seller-side data. It measures what the rep did. It doesn't measure what the buyer is doing.
| Vector | The underlying problem |
|---|---|
| Relevance | The CRO owns the system that's blind. The VP Sales sees rep performance. The seller sees individual deals. The CRO sees the system — and it has a hole. |
| Specificity | Buyer group composition, stakeholder archetypes, blocker presence, decision-maker engagement, procurement status. |
| Quantification | 62% unqualified pipeline, 43% commit-to-slip, 2x win rate variance, 67% single-threaded losses, 38% cycle expansion. |
| Causality | Every tool measures seller activity. CRM stages track what the rep did. Forecast reflects what the rep believes. The buyer's side is absent by design. |
| Locus | Internal. CRM, methodology, incentives, review cadence — all within the CRO's control. |
| Systemic Depth | Not fixable by training or coaching. The architecture excludes buyer-side data. Same blind spot, every deal, every quarter. |
| Tension | Every quarter the CRO responds to symptoms — more pipeline, more scrutiny, more coaching — without seeing root cause. Each response reinforces the seller-side system. The gap compounds. |
| Consequence | The CRO keeps solving symptoms. The board keeps asking why. The real constraint goes unaddressed because it was never named. |
Adrata makes the buyer visible.
VP of Sales
The Archetype
| Dimension | VP Sales Profile |
|---|---|
| Communication style | Data-driven — but closer to deal-level detail than the CRO; wants diagnostic precision, not just dashboards |
| Decision pattern | Consensus — builds alignment with peers and CRO, but has more operational autonomy |
| Budget authority | Departmental — owns sales budget but needs CRO sign-off for significant investments |
| Influence scope | Departmental — owns the team, the managers, the reps, the process |
What They're Measured On
| Priority | Weight |
|---|---|
| Quota Achievement | 5 — team hits the number |
| Pipeline Health | 5 — qualified coverage with velocity |
| Rep Productivity | 4 — revenue per rep |
| Sales Process Compliance | 3 — methodology adherence, CRM hygiene |
| Team Retention | 3 — keeping top performers |
What Hurts Most
| Pain Point | Severity |
|---|---|
| Inconsistent Rep Performance | 5 — 2.6x gap between top and bottom quartile |
| CRM Data Quality | 4 — rep-entered data is unreliable; every pipeline review starts with "is this data even right?" |
| Forecast Reliability | 4 — deals slip from commit; last-minute scrambles |
Articulation Rule
The VP Sales is closer to the deals than the CRO. They don't want system-level abstractions — they want to know which reps, which deals, which behaviors are causing the gap. But they're not in the deals themselves. They work through managers, and the signal they get is filtered through CRM data and deal reviews.
Their frustration is specific: they know they have a distribution problem, they can see the variance in every report, and they've tried every coaching lever — ride-alongs, call reviews, pipeline scrubs, forecast calls. None of it moves the middle because they're all coaching on seller-side behavior.
The VP Sales doesn't need "things could be better." They need: "Here's why your coaching isn't working. It's not a coaching problem — it's a signal problem. You're coaching on what the rep did. You need to coach on what the buyer is doing."
Problem 1: The Coaching Ceiling
Derived from: Rep Productivity (weight 4) + Inconsistent Rep Performance (severity 5).
Instead of, "Reps need more coaching,"
Say, "Your managers spend 8+ hours per week in deal reviews coaching reps on activity and compliance — the performance gap hasn't closed in four quarters because coaching on seller behavior doesn't work when the problem is buyer navigation, and your system gives managers zero buyer-side signal to coach on."
| Vector | Applied |
|---|---|
| Relevance | Coaching is the VP Sales's primary lever. This doesn't say coaching is wrong — it says coaching has hit a ceiling because the inputs are wrong. Direct hit on how they spend their operating time. |
| Specificity | Deal reviews. No buyer-side signal. Coaching on seller behavior when the problem is buyer navigation. |
| Quantification | 8+ hours per week per manager. Four quarters flat. Investment is real. Return isn't. |
| Causality | Deal reviews follow a pattern: stage, last action, next step. Every question is about the rep. None about the buyer: Who else is involved? What's their archetype? Is there a blocker? Managers can't coach buyer dynamics because the system doesn't surface them. |
| Locus | Internal. Deal review template, CRM fields, coaching framework — all within the VP Sales's control. |
| Systemic Depth | Every new manager follows the same pattern. Every deal review covers the same ground. Rep variance stays flat. The org responds by hiring "better coaches." The constraint isn't coaching skill — it's coaching input. |
| Tension | The VP Sales has trained the managers, added cadences, deployed methodology. Variance hasn't moved. When the CRO asks "why isn't coaching working?" the VP Sales doesn't have an answer that holds. |
| Consequence | Personally accountable for rep productivity. If the middle 60% doesn't improve, the VP Sales faces two options: accept the variance or keep investing in coaching that hits the same ceiling. |
Coherence chain: Coaching on seller activity has diminishing returns because the performance gap isn't about what reps do — it's about how they read the buyer. Choice: Give managers buyer-side intelligence in deal reviews. Action: Contact archetype classification. Gap analysis showing who should be engaged but isn't. Coaching prompts tied to buyer dynamics. Outcome: Deal reviews become diagnostic. The coaching ceiling breaks.
Problem 2: Pipeline That Passes Inspection But Fails Conversion
Derived from: Pipeline Health (weight 5) + CRM Data Quality (severity 4).
Instead of, "We need better pipeline quality,"
Say, "Your pipeline passes every inspection — coverage looks right, stages are filled, next steps logged — but stage-3-to-close conversion has dropped 18% in three quarters because CRM data reflects what the rep entered, not what the buyer is doing."
| Vector | Applied |
|---|---|
| Relevance | Pipeline health is co-#1. But the VP Sales experiences it operationally — they're in the reviews, asking about specific deals. Framed as "your reviews are passing deals that shouldn't pass." |
| Specificity | Stage 3 to close conversion. Surface looks right. Failure is beneath. |
| Quantification | 18% conversion decline over three quarters. |
| Causality | Reviews check stage, amount, next step, close date. All seller-entered. A rep can have a $200K deal in Stage 3 with one contact — a mid-level champion who likes the product — and it passes review. No decision maker, no budget holder, no blocker surfaced. |
| Locus | Internal. Review criteria, stage definitions, required fields — all within the VP Sales's control. |
| Systemic Depth | Every review follows the same checklist. Every quarter, deals that passed review stall or die. Tightening stage definitions or adding fields — more seller-side process — doesn't help because it's still inspecting the wrong data. |
| Tension | The VP Sales reports pipeline health to the CRO. When stage-3 deals die, it's a cascade: forecast miss, coverage recalculation, scramble. The VP Sales is the last person to touch these deals before the forecast. |
| Consequence | The VP Sales runs a disciplined pipeline process. Invested in stage definitions, review cadences, hygiene standards. Deals still die after passing every checkpoint. The consequence isn't just lost deals — it's erosion of confidence in their own operating system. |
Coherence chain: Pipeline review inspects what the CRM contains. It can't inspect what the CRM is missing. Choice: Add buyer-side qualification. A deal doesn't count as Stage 3 until the buyer group is mapped and a decision maker identified. Action: Buyer group health score on every deal. Automatic flags when deals advance without buyer engagement. Outcome: Pipeline reviews catch hollow deals before the forecast.
Problem 3: The Middle 60%
Derived from: Quota Achievement (weight 5) + Inconsistent Rep Performance (severity 5).
Instead of, "We need better quota attainment,"
Say, "Top 20% at 34% win rate. Bottom 20% at 13%. Middle 60% flat at 16-18% for four consecutive quarters despite new methodology, coaching investments, and enablement programs — because the differentiator isn't effort or process, it's buyer-reading ability, and there's no mechanism to transfer it."
| Vector | Applied |
|---|---|
| Relevance | Quota achievement is #1 and inconsistent performance is their #1 pain. Framed differently than for the CRO: this validates the VP Sales's effort ("you've done the right things") while explaining why it hasn't worked ("the lever doesn't reach the root cause"). |
| Specificity | 34% vs. 16-18% vs. 13%. Four quarters. Middle 60% is the population. Stagnation despite intervention is the pattern. |
| Quantification | The numbers tell the story. |
| Causality | The differentiator is the ability to classify a buyer by archetype and adapt in real time. The CFO who needs ROI, the VP Ops who needs workflow validation, the IT Director protecting the incumbent. Top reps read this instinctively. The system gives the middle nothing. |
| Locus | Internal. Enablement, methodology, coaching, tooling — all within the VP Sales's system. The gap isn't caused by talent. It's caused by a system that captures what top reps do but not what they know. |
| Systemic Depth | Every new hire enters the same system, gets the same enablement, follows the same playbook — and reaches the same ceiling. The few who break through develop pattern recognition independently over 18+ months. The system reliably produces a stuck middle. |
| Tension | Revenue plan assumes the middle improves. Every year the VP Sales commits to closing the variance. Every year it persists. Compensating with headcount or pipeline increases CAC and compresses margins. |
| Consequence | When the CRO asks "why hasn't coaching moved the middle?" — "we need more time" stops working after four quarters. The VP Sales's credibility depends on moving a number their current system cannot move. |
Coherence chain: The gap is buyer-reading capability. It develops over years in top performers and never develops in most. Choice: Deliver it as contextual intelligence, not abstract training. Action: Archetype classification on every contact. Engagement guidance at the point of action. Outcome: The middle 60% gets the intelligence that top reps develop intuitively. Variance shrinks.
Problem 4: Process Compliance Without Process Intelligence
Derived from: Sales Process Compliance (weight 3) + CRM Data Quality (severity 4).
Instead of, "Reps need to follow the process better,"
Say, "82% methodology compliance — stages updated, next steps logged, MEDDIC populated — but compliance hasn't improved conversion because the process measures seller activity, not buyer progress, and a rep can be perfectly compliant on a deal with no path to a decision."
| Vector | Applied |
|---|---|
| Relevance | Compliance is weight 3, but the VP Sales's real pain is that compliance hasn't translated to results (severity 5). This connects them: "the process works as designed — the design is the problem." |
| Specificity | 82% compliance. MEDDIC populated. Stages updated. What's missing: buyer group mapping, decision-maker validation, blocker identification. |
| Quantification | 82% compliance. Conversion unchanged. Gap between compliance and results is the indictment. |
| Causality | Every stage is a seller action: discovery done, demo completed, proposal sent. None require buyer-side validation. A rep can advance through every stage without confirming the buyer's organization is ready to decide. |
| Locus | Internal. Methodology, stage definitions, required fields — all the VP Sales's. |
| Systemic Depth | MEDDIC, SPICED, value selling — each improves discipline, none improve conversion. Same pattern because every methodology assumes seller actions are the leading indicator. They're not. |
| Tension | The VP Sales is about to invest in the next methodology refresh. It will improve compliance. It won't improve conversion. |
| Consequence | The VP Sales has staked credibility on process. If it doesn't translate to results, they look like someone who optimized the wrong thing. |
Coherence chain: Process compliance and deal progress are not the same thing. Choice: Add buyer-side gates. Stage 2 requires a mapped buyer group. Stage 3 requires a decision maker. Stage 4 requires blocker assessment. Action: Buyer group mapping in stage advancement. Automatic health checks at each gate. Outcome: Compliance becomes predictive, not just descriptive.
Problem 5: Retention Risk from System Frustration
Derived from: Team Retention (weight 3) + Inconsistent Rep Performance (severity 5).
Instead of, "We need to retain our top reps,"
Say, "Your best reps succeed despite the system — they build their own buyer intelligence, maintain their own relationship maps, develop their own archetype intuition over years. Your middle reps fail because of the system. The day top reps find better tooling elsewhere, they leave — and their pattern recognition leaves with them."
| Vector | Applied |
|---|---|
| Relevance | Retention is weight 3, but losing a top rep is visceral: 7+ month revenue gap and institutional buyer knowledge disappears. Framed as "your top performers succeed in spite of your system." |
| Specificity | Top reps build shadow intelligence: buyer models, relationship maps, archetype intuition. None captured in the CRM. None transferable. |
| Quantification | 7+ month ramp for replacement. |
| Causality | Top reps compensate for system gaps. They build mental models of who's in the deal, what each person cares about, who might block them. When they leave, the org loses intelligence it didn't know existed because it was never in the system. |
| Locus | Internal. System designed to track seller activity, not buyer intelligence. |
| Systemic Depth | Every top performer builds private intelligence. Every departure erases it. Every new hire starts from zero. The org never accumulates institutional buyer intelligence. Permanent ramp-time tax. |
| Tension | Tools providing buyer intelligence are emerging. The VP Sales's top performers will see the gap between what their system provides and what's available. The system becomes a retention liability. |
| Consequence | A top rep leaves. Revenue drops for two quarters. Deals in progress lose buyer context. The VP Sales realizes: the only buyer intelligence in the org was in one person's head. |
Coherence chain: Buyer intelligence is stored in heads, not systems. Choice: Build it into the platform. Action: Every contact classified. Every deal mapped. Every insight persisted across rep transitions. Outcome: Ramp compresses. Departures are painful but not catastrophic. The system itself becomes a retention draw.
The VP Sales's One Problem
The VP Sales's operating system — coaching, pipeline reviews, methodology, enablement, retention — is designed around seller activity. It measures what reps do. It doesn't measure what buyers are doing.
| Vector | The underlying problem |
|---|---|
| Relevance | The VP Sales is the operator. The CRO sees the system from above. The VP Sales runs it — deal reviews, pipeline scrubs, coaching, forecast calls. They feel the ceiling in every interaction. |
| Specificity | Deal reviews without buyer group data. Coaching without archetype context. Pipeline reviews without buyer validation. Process compliance without buyer-side gates. |
| Quantification | Flat middle-60% win rates. 18% conversion decline. 82% compliance with no result improvement. 7+ month ramp for every hire. |
| Causality | Every tool was designed to improve seller behavior. The assumption was that better seller behavior produces better outcomes. It does, up to a point. The remaining gain is on the buyer side, and the toolkit can't reach it. |
| Locus | Internal. Methodology, coaching framework, pipeline process, CRM configuration. Design choices, not market forces. |
| Systemic Depth | Every refresh follows the same pattern: improve seller-side discipline, hope it translates. It improves compliance. Not conversion. |
| Tension | Seller-side levers are exhausted. Returns are diminishing. The CRO is asking why variance hasn't closed. The next investment in seller-side improvement will yield less than the last. |
| Consequence | If four quarters of coaching, two methodology rollouts, and rigorous enforcement haven't moved the middle 60%, the VP Sales faces a credibility question: are they solving the right problem? |
The CRO's problem is a system design problem. The VP Sales's problem is an operating problem.
The CRO needs to see the buyer. The VP Sales needs to coach the buyer side.
Adrata makes the buyer coachable.
Sales Manager and Individual Seller sections follow — same blind spot, different lens. The Manager sees it as a deal review problem. The Seller sees it as "I lost and I don't know why."
Article 3: The Z Axis — Understanding Demand
A Problem at Rest Stays at Rest
Precision is the first dimension — 8 vectors that turn complaints into diagnoses.
Relevance is the second — the same problem reframed for the CRO and VP Sales, because the archetype determines which version lands.
Together they produce problem statements that are accurate and targeted. A CRO hears it and nods. "That's a real problem."
And then they go back to their week.
Because a problem at rest stays at rest. Unless acted on by a force.
This is the gap in the conversation. Bob Moesta wrote about "struggling moments" — the origin of demand. Rob Snyder built PULL around the conditions that cause buyers to rip products out of your hands. The Challenger Sale showed how reframing a buyer's understanding of their own situation creates urgency. Jobs To Be Done mapped the four forces of progress — push, pull, anxiety, habit.
Each got something essential right. But nobody has connected the pieces: what demand actually is, how force creates it, how depth sharpens it, and how a seller interacts with it without manufacturing false urgency. Everyone uses the physics metaphor — "it's like inertia," "deals need force" — but nobody has actually built the physics.
This article builds it.
What Is Demand?
Demand is not desire. Demand is not interest. Demand is not pain.
People in equilibrium will complain about their pain — and then do exactly nothing about it. Pain is a state. Demand is a vector: it has magnitude and direction. It's the measure of how hard someone is pushing against their status quo.
Demand exists when a person is actively trying to change their situation — when they have a project on their priority list, something made it unavoidable, they've looked at options, and those options aren't working.
That's the definition. Four conditions, all observable:
1. Project. There's something on their to-do list. Not a wish, not an awareness — a funded, staffed, or deadlined initiative. The CRO doesn't just "know" pipeline quality is an issue. Pipeline quality is a line item in their Q3 plan. Someone owns it. There's a meeting cadence around it.
No project → "That's a great point. We should think about that." (Translation: nobody owns this, nothing will happen.)
2. Force. Something made the project unavoidable. The board asked a pointed question — twice. A competitor won a deal they should have owned. Two top reps left in the same month. A new CRO arrived with a mandate to fix pipeline in 90 days. These are forces — external events that act on the person and make inaction untenable. Without force, projects sit in the backlog indefinitely.
No force → "It's on our roadmap for next year." (Translation: nothing is compelling action now.)
3. Failed remedies. They've tried to solve this. More coaching. More pipeline. New methodology. A CRM migration. And it didn't work. The standard playbook has hit its ceiling. This is critical: when the obvious solutions have failed, the buyer becomes open to solutions that are fundamentally different. If they haven't tried and failed yet, they'll reach for the obvious thing first — and you'll be competing against "let's try more of what we're already doing."
No failed remedies → "We've got some initiatives underway. I think we're handling it." (Translation: they still believe the current approach will work.)
4. Limitations of alternatives. The options they've considered — competitors, manual processes, hiring, doing nothing — have severe limitations. They've looked at the landscape and nothing solves the actual problem. This is where your diagnosis becomes decisive: if you've articulated the problem precisely enough that the buyer can see why their alternatives don't work, you've earned the position before the product demo starts.
No limitations → "We're evaluating a few vendors." (Translation: they're in a bake-off and you're one of five interchangeable options.)
When all four conditions are true, demand is present. The person isn't just nodding — they're leaning forward. The conversation shifts from "should we do something?" to "how fast can we move?"
When one is missing, you know exactly which one — and the italicized responses above are the diagnostic tells. Each maps to a missing condition. Knowing which condition is absent changes what the conversation needs next.
Why This Matters: The Two Failure Modes
Force without diagnosis. Something hit them — a board question, a lost deal, a missed quarter. They're in motion. They've got budget. They're taking meetings. But they have no clear picture of what they're solving. They say "we need to fix our pipeline" the way a patient says "I don't feel well." This produces RFPs, bake-offs, and committee decisions where five vendors compete on features because nobody anchored the evaluation on a precise problem. Gartner's data bears this out: 40-60% of qualified pipeline ends in "no decision." Not because buyers don't care — because they can't build consensus around a problem nobody defined clearly enough.
Diagnosis without force. You deliver a perfectly precise, archetype-relevant problem statement. The CRO agrees with every word. "You're exactly right. This is a real problem." And then nothing happens. Not because they disagree — because no force is acting on them. The board hasn't asked. The numbers haven't broken visibly enough. They haven't tried and failed yet. The problem is real but it's at rest.
Diagnosis + demand. The CRO just missed their second forecast. The board asked pointed questions. They tried adding pipeline and it didn't fix conversion. They tried more coaching and the variance didn't move. And then they hear: "62% of your pipeline has no decision maker engaged. Your system measures seller activity but not buyer engagement — which is why more pipeline and more coaching haven't worked. They're solving the wrong side of the equation."
That's a different conversation. The force made them ready. The diagnosis gave them clarity. The failed remedies made them open to a fundamentally different approach. Together: "How fast can we move?"
The Z Axis: Force × Depth
The X axis is precision — how well-articulated is the problem? (8 vectors)
The Y axis is relevance — is it framed for the right person? (archetype role)
The Z axis is force × depth — what demand conditions are present, and how precisely is the articulation calibrated to this person's specific situation?
Force comes first because it's the prerequisite. Without force — without an active project, a compelling event, exhausted alternatives, and limited options — depth is academic. An impressive insight that produces no action. "You clearly understand our business. Let's talk next quarter."
With force present, depth determines whether you win the conversation or someone else does.
What Is Depth?
Depth is archetype layering. In Article 2, we used one dimension: the executive archetype. CRO. VP Sales. That's the role layer — it tells you what someone always cares about. But "CRO" is still a segment. Within that segment, one CRO is at a scaling startup burning through a Series C, and another is at a Fortune 500 in an efficiency cycle. Same title. Completely different situation. The articulation that moves one won't move the other.
Eight archetype dimensions determine depth:
| # | Dimension | What it answers |
|---|---|---|
| 1 | Executive Archetype | What role, priorities, KPIs? |
| 2 | Persona Archetype | How do they behave as a buyer? |
| 3 | Communication Style | How do they process information? |
| 4 | Decision Pattern | How do they commit? |
| 5 | Company Archetype | What's the organization doing? |
| 6 | Deal Archetype | What's the buying pattern? |
| 7 | Buyer Group Role | What structural role are they playing? |
| 8 | Blocker Archetype | What resistance pattern is present? |
Not every conversation needs all eight. Most need three:
- Executive Archetype — always. The role sets the baseline.
- Company Archetype — usually. It determines context, urgency, and what "good" looks like for this org.
- One situational dimension — deal archetype, blocker archetype, or buyer group role — whichever is most active in this conversation.
The skill is knowing which dimensions matter for the meeting you're walking into.
Force × Depth: The CRO at Three Levels
Take Pipeline Substance — CRO Problem 1 from Article 2.
Level 1: Executive Archetype only.
"62% of your pipeline has no identified decision maker engaged — your 3.2x coverage ratio is masking a qualified-pipeline gap that puts the majority of forecasted revenue at risk."
Lands with any CRO. Same statement for every CRO at every company. No depth.
Level 2: Add Company Archetype. (Scaling Startup)
"You're hiring reps faster than you can qualify pipeline. Every new rep adds $800K in reported pipeline in their first quarter — but stage definitions don't require buyer validation, so new reps fill coverage with single-contact deals at the exact moment the board is watching unit economics. You don't have a volume problem. You have a substance problem that's accelerating because the thing you're scaling — headcount — is the thing producing unvalidated pipeline."
The tension changes: growth compounds the issue. The causality changes: hiring is the accelerant. The consequence changes: the board is watching unit economics. An Enterprise Optimizer CRO would hear a completely different version.
Level 3: Add Deal Archetype + Blocker Archetype. (Complex Multi-Thread + Budget Guardian)
"Your largest deals — the $200K+ multi-threads with 5+ stakeholders and 90-day cycles — are the most exposed. They sit in pipeline longest, inflate coverage most, and are most likely to have an unidentified Budget Guardian in finance redirecting spend. Three of your last five enterprise losses followed the same pattern: rep engaged the operational champion, built consensus at the user level, never identified the CFO's office was running a parallel budget review. Those deals passed every pipeline review because the review checks who the rep engaged — not who they should have."
The person hearing this doesn't nod politely. They think of the deal they lost last quarter.
The 2×2: Force × Depth in Practice
| Low Depth (role only) | High Depth (3+ dimensions) | |
|---|---|---|
| No Force | Cold outreach. Gets ignored. | Impressive insight. "Let's talk next quarter." |
| Force Present | You get the meeting. So do five competitors. Nobody can tell you apart. | The conversation that closes. They see the diagnosis, they recognize their situation, they're already compelled to act. |
The bottom-right quadrant is where deals happen fast and competitors don't get invited. Force opens the door. Depth makes you the only one who belongs in the room.
Reading Demand: The Four Checks
Before any conversation, check for demand. Each condition is observable — verifiable from public information, discovery questions, or champion intelligence.
| Condition | How to check | What you're listening for |
|---|---|---|
| Project | Is this on their actual priority list? Is someone assigned? Is there budget? | "We have a pipeline quality initiative this quarter." "My VP of RevOps owns this." Evidence of structure, not just awareness. |
| Force | What happened that made this unavoidable? | "The board asked about our win rates." "We missed forecast two quarters running." "Our new CRO wants this fixed in 90 days." Specific events, not general sentiment. |
| Failed remedies | What have they tried? What was the result? | "We rolled out MEDDIC last year." "We added two SDRs." "We ran a pipeline quality sprint in Q2." Evidence of attempts that didn't close the gap. |
| Limitations | What options are they considering, and where do those fall short? | "We've looked at a few tools but they all just add more dashboards." "We tried to build this internally but it didn't scale." Evidence that existing options don't solve the actual problem. |
If a condition is missing, you have two choices: surface information that activates it — "Your stage-3 conversion has dropped 18% in three quarters; have you seen that in your data?" — or recognize that demand isn't present and invest your depth elsewhere.
How Demand Changes the Conversation
The same problem, same depth, different demand profile:
All four conditions present — project exists, force is acting, remedies have failed, alternatives are limited:
Lead with the solution path, not the problem. They already know it's broken. They need to see what changes, how fast, and what they tell the board.
Force + project, but no failed remedies — they're working on it but haven't hit the ceiling yet:
Show them why the obvious approach won't work. They're about to invest in more pipeline or another methodology. Surface the ceiling before they hit it: "More pipeline won't fix this because the problem isn't volume — it's that 62% has never been buyer-validated."
Force + failed remedies, but no clear project — the pain is acute but nobody owns it:
Help them build the project. Define the scope, the owner, the timeline, the success metric. You're not selling a product — you're helping them organize the initiative that will eventually buy one.
Project + force + failed remedies, but alternatives seem adequate — they're evaluating competitors who look similar:
This is where depth wins. Generic articulation puts you in a bake-off. Depth-3 articulation — company archetype, deal pattern, blocker type — makes you the only one who understands their specific situation. The competitors are pitching pipeline tools. You're diagnosing why Budget Guardians in finance keep killing their Complex Multi-Thread deals.
Demand doesn't just tell you whether to have the conversation. It tells you which version of the conversation to have.
The Seller's Role in the Force Equation
There is a legitimate debate about whether sellers can create demand or only find it. Rob Snyder argues you can only find it — demand is supply-agnostic and exists before the seller arrives. The Challenger Sale argues sellers create urgency by reframing the buyer's understanding of their own situation. Both are partially right.
The more precise framing: sellers don't create force. They surface it.
A CRO whose stage-3 conversion has dropped 18% over three quarters has force acting on them — but they may not see it yet because nobody's shown them the number in this frame. A VP Sales whose middle 60% hasn't moved in four quarters has force — but they've been told it's a coaching problem, not a system problem. The force exists. It's latent. The seller's job is to make it visible.
This is not manufacturing urgency. It's not the artificial tension of "this offer expires Friday." It's the legitimate act of helping someone see a force that's already acting on them — and understand why their current response to it isn't working.
The seller interacts with the demand equation in three ways:
- Surface force. Show the buyer a pattern they haven't seen — the 18% conversion decline, the 67% single-threaded loss rate, the 38% cycle expansion. Make the force visible with their own data.
- Name the failed remedy. Show them why the thing they've been trying doesn't address root cause. "More coaching hasn't moved the middle 60% because it's coaching on seller-side behavior, and the gap is on the buyer side."
- Expose the limitation of alternatives. Use depth to show why generic solutions miss their specific situation. "Most pipeline tools add dashboards. They don't tell you that the Budget Guardian in finance is redirecting the budget on your largest deal."
None of these create demand from nothing. All of them accelerate demand that already exists by removing the friction between latent force and conscious action.
The Three-Article Arc
Precision. Relevance. Force and depth. Each builds on the last.
The 8 vectors make any problem statement precise enough to act on. The archetype multiplier ensures it's framed for the person who needs to hear it. Force and depth determine whether that person is compelled to act — and whether your articulation matches their specific situation closely enough that nobody else belongs in the room.
The right problem, to the right person, at the right depth, at the right time.
| Axis | What it is | What it answers | Without it |
|---|---|---|---|
| X — Precision | 8 vectors | Is the problem well-articulated? | Vague complaints that generate debate, not action |
| Y — Relevance | Archetype role | Is it framed for this person? | Accurate diagnosis delivered to the wrong audience |
| Z — Force × Depth | 4 demand conditions × archetype dimensions | Is this person compelled to act, and does the articulation match their specific situation? | Good insight that produces no urgency, or urgency with no differentiation |
The archetype system is already built — 20 executive archetypes, 25 buyer group role archetypes, 5 persona archetypes, 5 deal archetypes, 5 company archetypes, 4 blocker archetypes. The Z axis turns that system into the thing that makes every conversation feel like it was prepared by someone who's been inside the building.