The Archetype Multiplier
Part two of the Problem Articulation Series
Here is a problem that exists inside every revenue organization on earth:
Reps lose winnable deals because they engage the buying group with one message, regardless of who is sitting across the table.
That sentence is true. It is also useless.
It is useless because a CRO hearing it thinks about forecast variance and system design. A VP Sales hearing it thinks about coaching leverage and rep performance distribution. A CFO hearing it thinks about cost per acquisition and resource misallocation. A frontline manager hearing it thinks about the deal review they ran yesterday where a rep had no idea who else was in the buying group.
Same problem. Same root cause. Completely different resonance depending on who is listening.
This is what most sales methodologies get wrong. They teach reps to articulate the problem. They never teach reps to articulate the problem for this specific person. And in enterprise B2B, where Gartner research shows buying groups now average 8 to 13 stakeholders with 74% exhibiting "unhealthy conflict" during the decision process^1^, that distinction is the difference between a conversation that advances and a conversation that stalls.
Kahneman and Tversky demonstrated this decades ago with prospect theory: the same information, framed differently, produces fundamentally different decisions^2^. Not slightly different. Fundamentally different. People presented with identical outcomes will choose one path when the frame emphasizes gain and the opposite path when it emphasizes loss. The content did not change. The frame did. And the frame determined the action.
In enterprise sales, the archetype is the frame.
Why Personas Are Not Enough
The B2B sales world is drowning in buyer personas. Marketing teams build them. Enablement teams distribute them. Sales teams ignore them.
The reason is structural, not motivational. A persona tells you that a CFO cares about cost and a CRO cares about revenue. That is the equivalent of telling a surgeon that the heart pumps blood. Technically correct. Operationally empty.
Forrester shows that two-thirds of B2B buyers expect more personalization than B2C consumers, yet 81% report dissatisfaction with the winning provider in their most recent purchase^3^. The gap is not awareness. The gap is depth. Sellers do not know how to translate "this person is a CFO" into a structurally different conversation.
A persona is a label. An archetype is a behavioral model. The persona says: "CFO. Cares about ROI." The archetype says: "This CFO processes information through financial models, makes decisions by consensus with the board, and experiences the current problem as an inability to trust the revenue number their CRO delivers." The persona gives you a topic. The archetype gives you a language.
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 cannot distinguish them. The Challenger Sale gave us seven stakeholder archetypes -- Go-Getters, Teachers, Skeptics, Guides, Friends, Climbers, Blockers. 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 to adapt to.
Every framework classifies buyers. None tell you how to talk to them.
The Same Problem, Two Languages
Let me make this concrete.
The underlying problem: The revenue organization's operating system is built on seller-side data. It measures what reps do. It does not measure what buyers are doing. This creates a structural blind spot that compounds across pipeline, forecast, win rate, and velocity.
That is the diagnosis. It is precise, causal, and quantified. It scores high on all eight vectors from Part 1 of this series.
It also cannot be delivered the same way to a CRO and a VP Sales.
Not because one is smarter. Because they sit at different altitudes, are measured on different outcomes, and process information through different mental models.
The CRO is the architect. They see the revenue system from above -- pipeline coverage, forecast accuracy, board credibility. When something is wrong, they ask: "What is the structural cause and how do I redesign the system?"
The VP Sales is the operator. They are inside the machine -- running deal reviews, coaching managers, enforcing methodology. When something is wrong, they ask: "What is the specific lever and why isn't it working?"
Same problem. Different altitude. Different language required.
The CRO Conversation
How the CRO Thinks
The average CRO tenure is 25 months^4^. CRO turnover accelerated more than 50% from 2022 to 2023, with 70% of departing CROs being asked to leave^4^. Only 41% of CEOs express confidence that their CRO can drive commercial success^4^.
The CRO is the C-suite ejector seat. Every quarter is an audition. Every forecast miss is a data point in a narrative that ends with "we need a different leader." This is the psychological context of every conversation you have with a CRO. They are thinking about:
- The number. Can I call it with confidence? Will it hold?
- The system. Is the revenue engine designed correctly? Where is it structurally weak?
- The board. Do I have credibility? Am I building it or spending it?
- The team. Is this a people problem or a system problem? (Hint: they desperately want it to be a system problem, because systems they can fix.)
The CRO is data-driven. If you cannot put a number on it, it does not exist. But numbers alone do not move them. The number must connect to a core priority, explain why at a structural level, and make clear what is at stake personally.
What the Problem Sounds Like for a CRO
Do not say: "Your reps aren't engaging the buying group effectively."
Say: "43% of your commit deals slip by quarter close because your forecast is built on rep self-assessment, not buyer engagement signals. You have no independent mechanism to verify deal readiness -- your commit category is a confidence poll, not a data model. Two consecutive misses at this rate and the board conversation shifts from forecast methodology to leadership."
Why does this land with a CRO and only a CRO?
It leads with a metric that maps to their highest-severity pain -- forecast misses are existential, not merely important. It names the structural cause ("rep self-assessment" as the sole input), which the CRO recognizes as a system architecture flaw in their domain. It connects to personal consequence -- "the board conversation shifts" -- which they have lived or watched someone live. And critically, it is not about reps. A CRO who hears "your reps need to do X better" assigns it to the VP Sales. A CRO who hears "your system has a structural blind spot" owns it personally.
Here is another version for the same CRO:
"Your pipeline shows 3.2x coverage. But 62% of that pipeline has no identified decision maker engaged. You are presenting coverage to the board that has never been tested against buyer reality -- your coverage ratio and your qualified coverage ratio are two different numbers, and only one of them predicts close."
It takes a metric they report to the board (3.2x coverage) and reveals it is hollow. It does not say "your pipeline is bad." It says "you are making board-level decisions on a metric that does not reflect commercial reality." CRO problem. CRO language. CRO consequences.
The VP Sales Conversation
How the VP Sales Thinks
The VP Sales lives closer to the ground. They run pipeline reviews, forecast calls, coaching sessions. They can name their top ten deals and the rep on each one.
Where the CRO asks "is the system designed correctly?", the VP Sales asks "why isn't it working?" They have built the process, deployed the methodology, trained the managers, enforced the cadence. And the numbers are not moving. Their frustration is specific:
- The coaching ceiling. They have invested in coaching. Managers are doing ride-alongs, reviewing calls, running pipeline scrubs. The performance distribution has not changed in four quarters. Top 20% still crushing it. Middle 60% still flat. Bottom 20% still struggling. What are they missing?
- The CRM trust problem. Every pipeline review starts with the same internal question: "Is this data even right?" The numbers in the system are what reps entered. The VP Sales knows that rep-entered data is aspirational, not diagnostic.
- The methodology gap. 82% methodology compliance. Stages updated. MEDDIC populated. Next steps logged. Conversion rate unchanged. They followed the prescription. The patient did not improve.
The VP Sales wants deal-level resolution -- which reps, which deals, which behaviors are causing the gap. And they want a lever they can pull this quarter.
What the Problem Sounds Like for a VP Sales
Do not say: "Your forecast is built on rep self-assessment, not buyer engagement signals."
That is the CRO version. It is accurate. But the VP Sales hears it as a RevOps problem, or worse, as an accusation that they are not managing their team. It does not connect to their daily reality of running deal reviews and coaching sessions.
Say: "Your managers spend 8+ hours per week in deal reviews coaching reps on next steps and stage progression -- and the performance gap hasn't moved in four quarters. It's not a coaching problem. It's a signal problem. The deal review asks what the rep did last week. It never asks what the buyer is doing. Your managers are coaching on seller activity when the gap is in buyer navigation."
Why this lands with a VP Sales:
It validates their effort -- "8+ hours per week" is a number they feel in their bones. The articulation does not say coaching is wrong. It says coaching has hit a ceiling because the inputs are wrong. "You're doing the right thing with the wrong data" gets you a follow-up meeting. "You're doing it wrong" gets you thrown out.
It reframes the constraint. "Not a coaching problem -- a signal problem." The VP Sales has been told for four quarters they need better coaching. Hearing that the bottleneck is signal, not skill, gives them a new lever they have not pulled.
It is operationally specific. The VP Sales can picture the last deal review they ran: "What's the next step? When's the follow-up? Have you sent the proposal?" All seller-side questions. The articulation makes them see the gap in their own operating cadence. And critically, the deal review template, the coaching framework, the questions managers ask -- these are within their control. No CRO sign-off required.
Here is another version for the same VP Sales:
"Top 20% at 34% win rate. Middle 60% flat at 16-18% for four consecutive quarters. You've rolled out new methodology, added coaching cadences, invested in enablement. The differentiator isn't effort or process compliance -- it's the ability to read buyer archetypes and adapt in real time. Your top reps do this instinctively. Your system gives the middle 60% no mechanism to learn it."
This targets the VP Sales's number one pain point. It acknowledges every intervention they have tried while explaining why none worked -- and reframes the gap from a people problem ("hire better reps") to a capability distribution problem ("your system can't transfer what top reps know").
The Structural Difference
Let me lay these side by side so the pattern is clear.
| Dimension | CRO Version | VP Sales Version |
|---|---|---|
| Altitude | System design | Operational execution |
| Language | Metrics, architecture, structural cause | Deals, coaching, behaviors, team dynamics |
| Core frame | "Your system has a blind spot" | "Your coaching has hit a ceiling" |
| The problem is | Missing data architecture | Missing signal for managers |
| The cause is | Seller-side data model | Seller-side coaching inputs |
| The consequence is | Board credibility erodes | Credibility with CRO erodes |
| The action is | Redesign the system | Change the deal review |
| They own | The architecture | The operating cadence |
| They fear | Two consecutive misses | "Why hasn't coaching moved the middle?" |
Same problem. Same root cause. But the CRO version would confuse a VP Sales ("that's a RevOps thing") and the VP Sales version would bore a CRO ("tell my VP to handle it"). The frame must match the listener.
Beyond CRO and VP Sales: Four More Archetypes
The CRO and VP Sales represent two ends of the altitude spectrum within revenue leadership. But enterprise deals involve a much wider cast. Here is how the same underlying problem -- seller-side blind spot, no buyer intelligence -- translates for four additional archetypes a seller will encounter.
The CFO
Their world: Capital allocation, forecast reliability, unit economics, board reporting. They care about the accuracy of the revenue number that feeds their financial model.
The problem in CFO language: "Revenue forecast variance has exceeded 15% for three consecutive quarters. The input to your financial model is a number built on rep self-assessment -- no independent verification. You are building hiring plans, cash flow projections, and board commitments on data with no buyer-side validation. The variance isn't a sales execution problem. It's a data integrity problem in your planning inputs."
The language shifted to variance, financial models, planning inputs, data integrity. The CFO does not think in pipeline stages. They think in forecast reliability. Gartner's 2025 report places "metrics, analytics, and reporting" as the number one CFO priority^5^ -- this articulation hits it directly.
The Frontline Sales Manager
Their world: Ten deals in this week's review. Three reps who need help. Forecast call on Friday.
The problem in Manager language: "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 actually need your intervention this week. The three deals that needed you -- where a blocker was emerging or a decision maker hadn't been engaged -- got the same fifteen minutes as everything else."
Visceral. They can picture Tuesday's review and the deal they spent twenty minutes on that closed anyway, while the one that died Friday never got discussed. The frame is time allocation in a deal review. Solvable by Thursday.
The Individual Seller
Their world: The deal they are working right now. The prospect who went dark.
The problem in Seller language: "You lost the Acme deal because someone in finance you never met redirected the budget. The CRM told you to multi-thread. The playbook told you to find the economic buyer. Neither one told you that the VP of Finance at a Series C company always runs a parallel budget review in Q4, or that the IT Director who never joined a call had a ten-year relationship with your competitor."
No metrics. No system architecture. A story about a deal they lost and the specific intelligence that would have changed the outcome.
The Head of Revenue Operations
Their world: Data architecture, system integrations, reporting accuracy, process design.
The problem in RevOps language: "Your CRM captures 100% of seller activity and 0% of buyer behavior. Every report, dashboard, and forecast model is built on one side of the equation. Stage progression measures what the rep did. None of it measures whether the buyer's organization is actually progressing toward a decision. You have a comprehensive seller-activity database masquerading as a deal-health system."
Same problem. The RevOps leader hears data models, field architecture, integration points. Completely different entry point.
The Translation Matrix
Here is the practical tool. For any problem you need to articulate, run it through this matrix before the conversation.
| Question | What It Determines | Example: Buyer Blind Spot |
|---|---|---|
| What is this person measured on? | Which metric to lead with | CRO: forecast accuracy. VP Sales: quota attainment. CFO: plan variance. |
| What have they tried that hasn't worked? | Which failed remedy to name | CRO: added pipeline. VP Sales: added coaching. CFO: added scrutiny to the number. |
| What keeps them up at night? | Which consequence to make personal | CRO: board credibility. VP Sales: flat middle 60%. CFO: unreliable planning inputs. |
| What is within their control? | Which action to suggest | CRO: system architecture. VP Sales: deal review template. CFO: approval of investment. |
| How do they process information? | Which register to use | CRO: system metrics. VP Sales: deal-level detail. CFO: financial models. Manager: this week's calendar. |
| What is their time horizon? | How to frame urgency | CRO: 18-month system change. VP Sales: this quarter's number. CFO: next board meeting. Manager: Friday's forecast call. |
The Challenger Sale research across 6,000+ reps found that the Challenger profile -- teach, tailor, take control -- represented 39% of top performers versus 23% of core performers^6^. The "tailor" component is precisely this. But the research identified the behavior without operationalizing the mechanism. How do you tailor? By understanding the archetype at a depth that changes the structure of the conversation, not just the vocabulary.
The Multiplier Effect
Here is why this matters at an organizational level, not just in individual conversations.
Research from Corporate Visions and similar organizations shows that 40-60% of qualified B2B pipeline ends in "no decision"^7^. Not lost to a competitor. Lost to inaction. A massive study of 2.5 million recorded sales conversations found that 56% of these "no decision" outcomes stem from buyer indecision -- not status quo preference, but the inability to build internal consensus^7^.
Now think about what consensus requires when 8 to 13 people are in the buying group^1^. Each person needs to hear the problem in a way that connects to their world. When a seller articulates the problem one way -- even if that way is precise and well-quantified -- it lands with one person and confuses or bores the rest. The deal becomes single-threaded not because the rep failed to get meetings, but because the message was single-threaded. One frame. One language. One altitude.
Multi-threading is not just about getting meetings with multiple people. It is about having a structurally different conversation with each one that leads them all to the same conclusion through different paths.
Companies implementing multi-threaded, stakeholder-specific engagement see win rates increase by as much as 6x over single-threaded approaches^8^. Not because more contacts means more coverage. Because each contact hears the problem in their language, builds their own conviction, and becomes an internal advocate who can articulate it to their peers in terms those peers understand.
The archetype is the multiplier. One diagnosis, multiplied across every relevant stakeholder, each version structurally adapted to land.
How to Build This Skill
This is not theory. Here are five things a seller can do starting Monday.
1. Stop Preparing One Pitch
Before any meeting, answer three questions:
- What is this person's title and what are they measured on?
- What have they probably tried to solve this problem?
- What happens to them personally if it is not solved?
If you cannot answer all three, you are not ready for the meeting. You will default to your standard pitch, which is optimized for one archetype and irrelevant to the rest.
2. Lead with Their Metric, Not Yours
If you are talking to a CRO, lead with forecast accuracy or pipeline coverage. If you are talking to a VP Sales, lead with win rate variance or coaching ROI. If you are talking to a CFO, lead with plan variance or cost per acquisition.
Never lead with your product's value proposition. Lead with the metric that keeps this person accountable. Then show them why that metric is broken in a way they have not seen before.
3. Name the Failed Remedy
Every stakeholder has tried something. The CRO added pipeline. The VP Sales added coaching. The CFO added forecast scrutiny. Name it. Validate it. Then explain why it did not work.
"You added 40% more pipeline last quarter. Coverage went from 2.8x to 3.2x. Conversion dropped from 22% to 18%. The additional pipeline was unqualified -- no decision maker engaged in 62% of new deals. More volume amplified the quality problem."
This is the Challenger Sale's "teach" move, made specific. You are teaching them something about their own situation that reframes why the thing they tried did not work.
4. Map the Buying Group by Archetype Before the Deal, Not After
Most sellers discover the buying group reactively -- someone forwards an email, the champion mentions "legal needs to review this." By then it is too late to prepare an archetype-specific conversation.
Before the first meeting, map the expected group: economic buyer, technical evaluator, potential blockers, end users. For each, identify their archetype and what they need to hear. With only 17% of the total buying journey spent meeting with potential vendors^9^ -- and that time split among all vendors being considered -- every interaction must land.
5. Test Your Articulation Against the Wrong Audience
Write your problem statement for a CRO. Then read it as if you are a VP Sales. Does it still land? If yes, it is not specific enough to either. A well-tailored articulation should feel slightly wrong delivered to a different archetype. The CRO version should make the VP Sales think "that is too abstract for my world." The VP Sales version should make the CRO think "that is too tactical for mine."
If swapping the audience changes nothing, you have written a persona-level statement (label-deep) instead of an archetype-level statement (behavior-deep).
The One Problem, Six Ways
One underlying problem. Six archetypes. Six structurally different conversations.
Root cause: The revenue organization measures seller activity but not buyer behavior.
CRO: "Your entire revenue operating system -- pipeline, forecast, deal review, velocity tracking -- runs on seller-side data. It is architecturally incapable of answering the question the board actually asks: 'Are buyers progressing toward a decision?' You are flying a $50M revenue plan on instruments that read seller altitude, not buyer altitude."
VP Sales: "Your managers coach reps on what to do next. They cannot coach reps on who is missing from the deal, what the blocker's concern is, or whether the buyer group is aligned -- because none of that information is in the system. Coaching has hit a ceiling and the ceiling is signal, not skill."
CFO: "The revenue number in your financial model is the output of a system that has no buyer-side inputs. Rep self-assessment is the sole verification mechanism. You are building a board-ready financial plan on data with no independent validation. This is the equivalent of publishing financial statements audited only by the people who generated the numbers."
Frontline Manager: "You reviewed twelve deals on Tuesday. You asked about next steps on all twelve. On three of them, a blocker you have never heard of is about to kill the deal. You have no way to know which three."
Individual Seller: "You are going to lose a deal this quarter to someone you never met. They will not attend a meeting. They will not respond to an email. They will redirect the budget or defend the incumbent from inside the organization, and you will mark the deal 'no decision' because that is the only label the CRM offers for 'I got outmaneuvered by a person I did not know existed.'"
RevOps Leader: "You built a CRM that tracks every seller action with precision. It cannot answer the most basic buyer question: 'How many people in this account are involved in the decision, and how many of them has the rep actually engaged?' Your system is a comprehensive record of seller behavior and a complete void on buyer behavior."
Six versions. Each one would land with its target and miss with the others. That is the archetype multiplier at work.
What This Means for Revenue Leaders
The traditional sales playbook treats problem articulation as a fixed asset. You craft the message, train the team, and deploy it uniformly. That approach worked when buying groups were small and decisions were made by individuals.
It does not work in a world where the average enterprise deal involves 8 to 13 stakeholders across multiple departments, where 77% of buyers describe their last purchase as "very complex or difficult"^10^, where 86% of purchases stall at some point in the process^3^, and where only 25-30% of reps are hitting quota^11^.
The shift required is not incremental. It is structural.
From one message to many. The same problem must be articulated differently for every archetype in the buying group. Not different spin. Different structure, different causality, different consequence.
From persona to archetype. Personas give you a label. Archetypes give you a behavioral model -- how someone processes information, what they fear, what they have tried. The depth of the model determines the depth of the conversation.
From training to system. You cannot train every rep to read buyer archetypes instinctively. That is what top performers develop over years. You can build a system that classifies contacts by archetype and delivers the right framing at the point of action. The capability moves from heads to platform.
From seller-side to buyer-side. The entire revenue operating model was built to measure what sellers do. The next unlock is measuring what buyers are doing. Not to surveil them. To understand them well enough to have the conversation they actually need to hear.
The archetype is the multiplier. The problem is the constant. The combination is what turns a relevant diagnosis into an inevitable conversation -- with every person who needs to say yes.
This is Part 2 of the Problem Articulation Series. Part 1, "Problem Articulation as a Skill," establishes the eight vectors that separate vague complaints from actionable diagnosis. Part 3, "The Z Axis," introduces force and depth -- how the conditions of demand and the layers of archetype intelligence turn a well-framed problem into a conversation the buyer cannot walk away from.
Endnotes
^1^ Gartner, "B2B Buyer Teams and Unhealthy Conflict," 2025. 74% of B2B buyer teams demonstrate unhealthy conflict; buying groups average 8-13+ stakeholders.
^2^ Kahneman, D. and Tversky, A., "The Framing of Decisions and the Psychology of Choice," Science, 1981.
^3^ Forrester Research, "The State of Business Buying," 2024. 81% buyer dissatisfaction with winning provider; 86% of purchases stall; two-thirds of B2B buyers expect more personalization than B2C.
^4^ Harvard Business Review, "The High Costs of Chief Revenue Officer Turnover," October 2024. Average CRO tenure 25 months; turnover up 50%+ from 2022-2023; 70% of departing CROs asked to leave; only 41% CEO confidence.
^5^ Gartner, "2025 CFO Priorities Report." Metrics, analytics, and reporting ranked number one CFO priority.
^6^ Dixon, M. and Adamson, B., The Challenger Sale, 2011. 6,000+ reps studied; Challenger profile: 39% of top performers vs. 23% of core.
^7^ Dixon, M. and McKenna, T., The JOLT Effect, 2022. 2.5M sales conversations; 40-60% of pipeline ends in "no decision"; 56% from buyer indecision.
^8^ Salesforce State of Sales Report, 2024. Multi-threaded engagement: up to 6x win rate improvement over single-threaded.
^9^ Gartner, "The B2B Buying Journey." Buyers spend 17% of total purchasing time with vendors.
^10^ Gartner, 2024-2025. 77% of B2B buyers describe their latest purchase as "very complex or difficult."
^11^ Bridge Group 2024 SaaS AE Metrics Report. Only 51% of AEs hitting quota (down from 66% in 2022); quotas rose 37% YoY.