A long read on the four archetypes of buyer problems and the matching prescription for each

Executive summary

In crowded markets where products look similar and buying groups have grown large and risk‑sensitive, sellers win by diagnosing the real problem and prescribing the right path—not by dumping features or chasing “one more demo.” Two secular facts explain why:

• B2B purchases now involve ~13 stakeholders, 89% cross departments, and 86% of purchases stall at some point—classic conditions where ambiguity, misdiagnosis, and internal friction kill momentum. Forrester: The State of Business Buying, 2024 [my.idc.com]

• Buyers move across about ten channels and more than half will switch suppliers when cross‑channel experiences are clumsy. If your guidance can’t travel cleanly between email threads, internal docs, Slack, and steering meetings, committees default to delay. McKinsey B2B Pulse 2024 [learn.g2.com]

This guide introduces a practical framework of four buyer‑problem archetypes—Operational, Visibility, Strategic, and Political—and the matching prescription for each. Use it to classify fast in discovery, prescribe credibly for CFO/Legal scrutiny, and help champions align their organizations.

Problem diagnosis is the new sales differentiator

The modern buying journey punishes “activity without clarity.” Buyers are ~70% through their process before engaging sales, 80% of first contacts are buyer‑initiated, and 81% already have a preferred vendor by first conversation. If you’re not the early favorite, your best chance to change outcomes is a sharp diagnosis and defensible recommendation, not a feature grid. 6sense Buyer Experience 2024 [storyproc.com]

Late‑stage hurdles are real. In software, the CFO frequently holds final decision power (79%) and Legal slows or blocks 61% of purchases. Shortlists are shrinking and 57% of buyers expect ROI ≤ 90 days, so vague problem statements and generic pitches die at the last mile. G2 2024 Buyer Behavior (Business Wire summary) [ibm.com]

Implication: Diagnosis has become the differentiator. When sellers classify the type of problem accurately, their prescribed path feels safe, relevant, and fast to value.

The four archetypes (and why reps misdiagnose)

Across internal deal reviews, most “unique” pain points collapse into four predictable patterns. Misdiagnosis is common—and costly:

• Treating a workflow problem like a technology problem triggers over‑engineering.

• Treating a strategic problem like a tactical one yields incremental fixes that fail to move KPIs.

• Treating a political problem like a functional one ignores consensus and decision rights.

• Treating a visibility problem like a process one automates the fog instead of clearing it.

The remedy is to learn the archetype tells, then match the prescription precisely.

Archetype 1: Operational problems

Definition: Inefficiencies, bottlenecks, delays, manual work, rework, scalability issues.

What you hear:
“This takes too long.” “Too many manual steps.” “Things fall through the cracks.” “We can’t keep this up as we grow.”

Hidden causes: Fragmented ownership, inconsistent workflows, unclear hand‑offs, app‑switching and rework.

Why it matters now: Knowledge workers lose 32 workdays per year to app‑switching alone—the “toggle tax” that quietly erodes capacity. Operational fixes that cut touches and context switching often deliver immediate ROI. Deloitte Productivity+ [business.l...nkedin.com]

Risk if misdiagnosed: Pitching a big “transformation” or AI program when the buyer needs simplification and automation first. That creates fear, not momentum, especially under CFO/Legal scrutiny for fast payback. G2 2024 [ibm.com]

Prescription: Simplify → standardize → automate.

• Unify the workflow: reduce steps, clarify owners, eliminate duplicate entries.

• Automate the obvious: routing, validations, SLA reminders, audit logging.

• Instrument cycle time, touches per item, rework %, and app switches.

How to quantify quickly (ranges):
Hours/week saved × fully loaded hourly rate; touches reduced × items/month; cycle‑time reduction × revenue per day (if applicable). Use the toggle‑tax figure to sanity‑check time assumptions. Deloitte [business.l...nkedin.com]

Mini‑case: An operations team spending 6–8 hours/week on manual reconciliations cut steps by 40% and added auto‑validation gates. The change reduced rework loops and recovered multiple days/quarter in cycle time—an outcome that mapped cleanly to the ≤ 90‑day ROI bar executives expect. G2 2024 [ibm.com]

Archetype 2: Visibility problems

Definition: Blind spots about performance, bottlenecks, compliance, usage, or risk exposure.

What you hear:
“We don’t know where things get stuck.” “We can’t see across teams.” “Data is everywhere.” “We find problems too late.”

Hidden causes: Disconnected systems, siloed data, low telemetry, inconsistent reporting.

The data reality: A 2024 Salesforce/MuleSoft survey of 1,050 IT leaders found 81% say data silos hinder digital transformation, 95% report integration issues impede AI, and only ~28% of apps are connected—so leaders literally cannot see the system well enough to improve it. Salesforce Connectivity Report [salesforce.com]

Poor data quality is also expensive: IBM reports over a quarter of organizations estimate losses > USD 5M/year from poor data quality, with 7% losing > USD 25M; 43% of COOs rank data quality as their top data priority. IBM IBV: The True Cost of Poor Data Quality Additionally, an Ascend2/Collibra study highlights that 37% cite data silos as a major barrier to sharing data across teams and 53% flag data reliability as a top AI challenge—undermining trust in metrics and dashboards. MarTech (Ascend2/Collibra) [ibm.com] [martech.org]

Risk if misdiagnosed: Automating a broken, invisible process; trying to “optimize” what nobody can see, which multiplies rework and erodes credibility.

Prescription: Centralize signals first; improve the system second.

• Integrate data sources and define shared telemetry (status, wait time, owner, exception).

• Stand up unified, real‑time dashboards with drill‑through to the case level.

• Publish cross‑functional reporting and early‑warning indicators (SLA risk, backlog growth, aging).

• Only after clarity: target the biggest friction with automation or redesign.

How to quantify quickly:
Reduce “time to detect” problems (MTTD) and “time to resolve” (MTTR); price lost time using team rates and quantify avoided rework. For economic framing, cite the IBM figures above to anchor the cost of poor visibility/quality. IBM [ibm.com]

Mini‑case: A company that centralized telemetry uncovered that 35% of delays occurred in one approval queue. By instrumenting SLA risk and queue aging, they fixed the choke point without a full replatform—accelerating cycle time and improving executive trust in the numbers (a must for CFO/Legal sign‑off). Salesforce Connectivity Report [salesforce.com]

Archetype 3: Strategic problems

Definition: Misalignment between current operations and future priorities—scale, market shifts, product strategy, or customer model.

What you hear:
“We can’t hit our goals with the current model.” “We’re not set up for where we’re heading.” “Competitors are moving faster.”

Hidden causes: Outdated operating model, technical debt, under‑invested capabilities, channel mismatch, structural talent gaps.

Why it appears late in deals: Buying groups often approach vendors after aligning on outcomes, not means. By the time they engage, they’ve researched deeply: the buying cycle averages 11.3 months, with most requirements set before first contact. If you treat this as a “fix a step” problem, you under‑prescribe. 6sense 2024 [wwps.microsoft.com]

Compounding factor: Omnichannel expectations. Buyers use ~10 channels and expect a seamless path end‑to‑end; strategic shifts typically require workflow redesign + platform modernization + capability uplift to support that experience. McKinsey B2B Pulse 2024 [learn.g2.com]

Risk if misdiagnosed: Offering tactical automation where the constraint is structural. That yields incremental wins and executive disappointment.

Prescription: Phased transformation aligned to strategic objectives.

• Phase 0/1 (foundation): clarify future‑state KPIs; address high‑impact bottlenecks; retire “accidental complexity.”

• Phase 2 (platform): modernize core systems or data plane to support scale, governance, and omnichannel continuity.

• Phase 3 (capability expansion): add net‑new capabilities (e.g., self‑serve, AI co‑pilots) once telemetry and workflow are stable.

• Governance: publish decision criteria, risk thresholds, and change‑management plans for CFO/Legal.

How to quantify quickly:
Tie phases to time‑to‑value milestones inside the average cycle (e.g., 90‑day releases). Use a “blended ROI” that includes capacity lift, revenue pull‑in, and risk reduction—aligned with the market’s ≤ 90‑day ROI appetite. G2 2024 [ibm.com]

Mini‑case: A company trying to add AI‑assisted customer workflows without shared data standards confronted the integration reality: only ~28% of apps were connected and 95% of leaders cited integration issues blocking AI. The correct prescription sequenced data integration, then capability rollout—meeting both strategic ambition and feasibility. Salesforce Connectivity Report [salesforce.com]

Archetype 4: Political problems

Definition: Internal friction, misaligned incentives, hidden stakeholders, unclear decision rights, or competing priorities.

What you hear:
“Different teams want different things.” “It’s been stuck for months.” “Legal/IT/Finance is blocking.” “No one agrees on what ‘good’ looks like.”

Why this dominates late stages: Large committees and cross‑department purchases make politics inevitable: ~13 stakeholders, 89% of purchases cross functions, and 86% stall. The constraint isn’t functionality; it’s consensus and risk ownership. Forrester 2024 [my.idc.com]

Reinforcing dynamic: Committees want a defensible decision. High‑quality, insight‑based content is more trusted than marketing and often prompts decision‑makers to reconsider vendors—evidence that reasoned guidance can shift internal coalitions. Edelman–LinkedIn 2024 Thought Leadership [martech.org]

Risk if misdiagnosed: Leading with features or ROI when the true blocker is alignment and process legitimacy.

Prescription: Lower political risk and guide consensus.

• Multi‑thread with economic buyer, operator, security, finance, and legal; clarify decision rights and risk thresholds.

• Facilitate shared success criteria and a one‑page “Definition of Done.”

• Provide carry‑forward artifacts: CFO‑ready ROI summary, risk‑control map, and executive‑friendly dashboard mockups.

• Offer one credible alternative and its trade‑offs to preserve autonomy and signal neutrality.

How to quantify quickly:
Price the cost of delay (e.g., daily value deferred × days of internal slippage), not just the solution’s upside. Show how the plan reduces approval steps/time and increases decision defensibility for CFO/Legal—the two groups who often decide the outcome. G2 2024 [ibm.com]

Mini‑case: A deal stalled for months until the seller reframed the ask from “new capabilities” to “a pilot that standardizes decision criteria, creates audit logs, and removes two approval steps.” The committee moved because the political risk fell, even before features were debated—classic late‑stage reality in ~13‑person, cross‑functional decisions. Forrester 2024 [my.idc.com]