Build the Fact Base and Diagnose the Real Problem

Build the Fact Base and Diagnose the Real Problem

Sales Strategy Playbook: Comprehensive B2B sales strategy framework covering ICP and segmentation, value proposition and pricing, route-to-market and coverage design, pipeline and forecasting discipline, RevOps, sales tech, compensation, and implementation roadmap to drive predictable revenue growth.

Sales strategy arguments usually sound like opinions—“lead quality is down,” “pricing is the issue,” “we need better reps.” The fastest way to end those arguments is to build a fact base that answers three questions: what changed, where, and why. The goal is not perfect analytics. The goal is a shared view of reality that is strong enough to drive decisions and specific enough to guide action.

2.1 Performance Decomposition: Growth, Churn, Win-rate, Deal Size, Velocity

Performance decomposition is the discipline of turning “we’re up/down” into a causal story. It matters because most sales fixes are expensive. Adding headcount, changing comp, or launching a new demand program can cost millions and takes quarters to show impact. A clean decomposition lets you pick the smallest set of levers that will move the largest outcomes.

Start with identities that make variance explainable. For new-logo bookings, three drivers dominate: how many qualified opportunities you create, how often you win, and how much you win when you do. For recurring revenue businesses, net growth is a second equation—what you add and what you leak after the sale.

New-logo identity: Bookings = (qualified opportunities created) × (win rate) × (average contract value).

Net revenue identity: Ending ARR = Starting ARR + New ARR + Expansion ARR − Churn ARR − Contraction ARR.

These identities give you a first diagnostic cut. If bookings are down, you can immediately ask: did we create fewer qualified opportunities, did win rates fall, or did average deal size compress? If net retention is down, is it true churn, contraction, or simply a lack of expansion? Each path leads to different fixes.

Then add time. Many teams miss that “velocity” problems often present as revenue problems. When deals take longer, pipeline piles up and leaders mistake the pile for progress. Your decomposition must include cycle time and stage progression, especially in enterprise motions.

Velocity check: Compare median days in stage and the percent of opportunities that advance each month. If stage time expands and advancement drops, you have a deal health problem even if pipeline volume looks fine.

Pipeline quality is the other half of the story. A pipeline can be large and still fragile if it is old or stalls in place. Two quick tests usually surface the problem: pipeline age by stage (how much has been “stuck” longer than the median), and stage advancement (what percent moved forward in the last 30 days). When age rises and advancement falls, the issue is qualification and deal control, not effort.

Template: Pipeline quality score (by segment).

  • Freshness: % of pipeline created in the last 60–90 days (adjust for cycle length).
  • Advancement: % of opportunities that move at least one stage in the last 30 days.
  • Stage integrity: % of opportunities meeting entry criteria for their stage (sample audit).

Run decomposition in three passes, each designed to eliminate a common false conclusion.

Pass 1: Separate acquisition from retention. Plot new revenue and net retention together. If churn increases materially, it can erase even strong new bookings. In that situation, the “growth” strategy is often a customer value and renewal strategy first, not an outbound strategy.

Pass 2: Separate mix from execution. Break results by segment, offer, and region, then compute a mix-adjusted view. A company can look worse simply because it shifted toward larger accounts with longer cycles. Conversely, a company can look better because it shifted toward easier-to-win deals. Mix is not an excuse; it is a fact that prevents the wrong fix.

Pass 3: Separate capacity from productivity. Split performance by seller cohort (fully ramped vs. ramping) and by manager. If results fell because a large cohort is new, the fix is ramp, coaching, and hiring quality. If fully ramped sellers also declined, you likely have an ICP, value proposition, competitive, or process problem.

To avoid debates about definitions, lock a small “metric dictionary” before you analyze. This is where many diagnostics fail: leadership argues about data rather than performance.

  • Win rate: Closed-won ÷ (closed-won + closed-lost), calculated within a consistent cohort (by opportunity creation date or by close date) and segmented.
  • Pipeline coverage: Pipeline for the period ÷ bookings target, measured at a consistent moment (for example, the first business day of the quarter).
  • Sales cycle: Median days from opportunity creation to close, plus median days in each stage.
  • Churn: Gross churn and net retention, separated by customer cohort and segment.

Finally, use the decomposition to create a short “variance story” that fits on one page: three drivers that explain most of the change, supported by a small number of exhibits. If you cannot explain variance simply, you are not yet ready to choose interventions. A good test is whether a frontline manager could repeat your story accurately after hearing it once.

Checklist: One-day performance decomposition.

  • Pull 6–8 quarters of bookings/ARR, churn, expansion, pipeline created, and pipeline closed.
  • Segment the data by new vs. existing customer, primary segment, and core offer.
  • Compute win rate, average/median deal size, and median cycle time by segment.
  • Split results by seller cohort (ramped vs. ramping) and identify manager outliers.
  • Write a one-page variance story with the 2–3 dominant drivers for acquisition and retention.

2.2 Customer And Deal Economics: Where Profit Is Created (Or Destroyed)

A strategy built on revenue alone is a trap. In B2B, the largest profit leaks often sit in places the sales dashboard doesn’t show: deep discounting late in the quarter, heavy implementation labor hidden inside “free services,” bespoke features promised to win a deal, or churn that wipes out acquisition investment. Your diagnostic must therefore answer a blunt question: which customers and deal types earn the right to invest?

Start by making margins comparable across segments. Gross margin is necessary but often insufficient, especially when services and support costs vary widely. Build an “economic stack” that takes you one level deeper than the financial statements.

Economic stack: Revenue → gross margin → contribution margin (after variable delivery costs) → payback (after acquisition costs). You do not need perfect allocation; you need a consistent approach that reveals relative attractiveness.

Then build economics by segment and by deal archetype. A deal archetype is a repeatable pattern—like “enterprise platform with paid implementation,” “mid-market land with free onboarding,” or “renewal with expansion add-on.” Ten archetypes often cover most revenue. When you understand their economics, you can design policy and coverage around them rather than negotiating each deal from scratch.

Two calculations are the workhorses.

CAC by segment: Fully loaded selling and marketing costs attributable to the segment ÷ new customers (or new ARR) in that segment. At minimum, include sales compensation, solutions engineering time, key marketing programs, and partner incentives if applicable.

Payback months: CAC ÷ monthly gross profit (after variable delivery costs). Payback turns “growth” into a capital decision—if payback is too long, you are funding growth with fragility.

Once you have segment economics, hunt profit leakage by looking for nonlinearities—places where economics suddenly worsen. Those points are where governance and packaging changes have outsized impact.

  • Discount cliffs: The discount level where margin collapses or where win rate stops improving. Those cliffs define discount guardrails and approval thresholds.
  • Delivery variance: The gap between estimated implementation effort at close and actual effort delivered. Persistent variance is a commercial scoping problem, not just a delivery problem.
  • Renewal drag: The level of customer success “save” effort required to renew accounts in a segment. High save effort is a signal of weak adoption, poor customer fit, or overpromised value.

Renewal economics deserves explicit attention. A renewal can look like “easy” revenue, but if it requires heavy discounting and constant escalation, the fully loaded economics can be poor. For each segment, estimate the cost to renew (customer success time, escalation time, concessions) and compare it to gross profit retained. This often reveals small cohorts that consume disproportionate capacity.

Template: Deal economics snapshot. Create one page per archetype; keep it simple enough that sales leaders will actually use it.

  • Segment/ICP: who this deal is for, with key fit attributes and common triggers.
  • Terms: list price, discount, contract length, services included, renewal terms.
  • Economics: year-1 revenue, variable delivery costs, gross profit, CAC estimate, payback months.
  • Risk flags: customization, nonstandard SLA, weak champion, unclear adoption plan.
  • Policy implications: required give-gets, required services packaging, or required approvals.

Use sensitivity checks to avoid false precision. If an input is uncertain, model a low/medium/high scenario and see whether the conclusion changes. Economics is what turns sales strategy into enforceable trade-offs: what you pursue, what you standardize, and where you walk away.

2.3 Voice Of Customer + Voice Of Field: The Minimum Viable Truth Set

Dashboards tell you what happened; buyers and sellers tell you why. The challenge is to capture “why” without turning the diagnostic into a months-long research effort. The answer is a minimum viable truth set: a small, structured set of conversations that reliably surfaces decision mechanics—triggers, success criteria, stakeholders, proof, and friction.

Minimum viable truth set: 25–35 structured interviews completed in 1–2 weeks, balanced across wins, losses/no decision, renewals, and internal field perspectives. The balance matters because wins alone make you overconfident and losses alone make you reactive.

Keep interviews chronological. People remember sequences—what triggered action, what created doubt, what proof resolved risk—better than abstract ratings. Chronology also reveals where you are weak: early (no point of view), middle (can’t build consensus), or late (procurement and legal).

Customer interview guide (core questions):

  • Trigger: What happened that made this a priority now? What would have happened if you did nothing?
  • Success criteria: What outcomes were non-negotiable, and how were they measured?
  • Decision team: Who influenced the decision and who could veto it?
  • Alternatives: Which vendors or approaches were seriously considered, including “build” and “status quo”?
  • Proof and risk: What evidence mattered most, and what almost killed the deal?
  • Commercials: How did price, terms, and procurement affect timing and choice?
  • Value realization: After signature, what drove adoption and what caused friction?

For win/loss interviews, logistics matter more than people expect. Offer confidentiality, keep the call to 25–30 minutes, and make it clear you are not trying to reopen a negotiation. If you can, have someone other than the account team run the conversation; prospects are more candid when they don’t feel they are hurting a relationship. For losses, prioritize “no decision” outcomes—those often reveal the real blockers (risk, internal alignment, competing priorities) that your sales process must address.

For field interviews, insist on concrete deal examples. Ask each rep or manager to walk you through one win, one loss, and one stuck deal, and to identify the single change that would most improve outcomes. Sellers often have accurate pattern recognition on where deals stall and what collateral is missing; they are less reliable on root cause, which is why you pair their insights with data and customer voice.

Capture results in a simple table and code themes. You are not writing a research paper; you are creating a decision input. Count how often themes appear by segment and by outcome. A theme that appears in 70% of losses in one segment is a strategy problem; a theme that appears once is an anecdote. When themes conflict—customers say “price” while sellers say “product”—look for the underlying mechanism: “price” often means “insufficient proof of value,” and “product” often means “we didn’t frame the right use case.”

Signal-quality tips: Avoid “What do you think of us?” and ask “What would you warn a peer about?” Always ask “What almost killed the deal?” and “What proof finally made you comfortable?” Those questions expose real risk drivers and often reveal the missing assets your team needs.

2.4 Competitive Commercial Benchmarking (What To Copy Vs. Avoid)

Competitive benchmarking is most useful when you focus on how competitors sell, not what they claim. In many markets, product gaps are narrower than teams like to admit, which means competitors win through positioning, proof, packaging, and deal control. Benchmarking should therefore answer: what are the commercial behaviors that change buyer decisions, and what should we do differently?

Limit your benchmark to the elements that directly affect conversion, cycle time, price realization, and retention.

  • Positioning and message: what problem they lead with and what “frame” they use for urgency.
  • Proof system: the evidence they bring early (ROI tools, references, certifications, benchmarks).
  • Offer design: what is standard vs. custom, and how they package services and onboarding.
  • Commercial posture: how they anchor price, where they concede, and what concessions are traded for.
  • Motion and coverage: whether they sell top-down, bottom-up, through partners, or through pilots.

Collect evidence from sources that are observable and fast: customer interviews (especially lost deals), partner conversations, public packaging and case studies, job postings that reveal role specialization, and internal call recordings where competitors are discussed. When you lack direct customer input, “mystery shopping” your own category can be revealing: request demos, download trials, and observe how competitors qualify, follow up, and frame value. Keep the exercise ethical and within your company’s competitive guidelines.

Then classify learning into three buckets.

  • Table stakes: things buyers now expect because competitors made them normal (for example, a security narrative, an implementation plan, or credible references).
  • Competitor advantages: strengths you must counter with a specific response (different proof, different wedge, different stakeholder strategy).
  • Competitor fragilities: recurring weaknesses you can exploit (rigid terms, delivery risk, poor adoption outcomes, slow procurement).

Copy vs. avoid rule: Copy mechanisms, not slogans. A competitor’s tagline is rarely transferable, but their mechanism—like a standardized pilot offer, a mutual action plan discipline, or a give-get discount playbook—often is. Avoid copying models that don’t fit your economics, such as a field-heavy motion when your deal sizes can’t sustain it. Also avoid copying what is merely visible (slick decks) versus what is causal (proof, stage discipline, and stakeholder strategy).

2.5 Diagnostic Readout: Hypotheses, Root Causes, And “No-regret” Moves

The diagnostic readout is where analysis becomes decisions. It should feel like a short, crisp narrative that explains performance in a way the field recognizes as true and that leadership can act on without another month of debate. If your readout requires 40 pages to be convincing, it is not yet clear enough.

Start with hypotheses and then score them. Early in the project, write what you believe is driving performance and what evidence would prove it. After analysis, label each hypothesis as confirmed, disproved, or partially true. This discipline prevents retroactive storytelling and reduces politics.

Hypothesis format: “We underperform in segment X because Y, evidenced by Z. Fixing Y should improve metric A by B.” Even if B is a range, forcing a directional impact makes the next step concrete.

Move from symptoms to root causes. A symptom is “win rates fell.” A root cause is something that, if fixed, would improve multiple downstream metrics. Root causes in B2B sales usually live in four places: targeting (ICP), offer/value (message and proof), coverage/motion (roles and handoffs), and execution (process discipline and coaching). Your job is to name the two to four dominant causes, not to catalog everything that could be improved.

When you write root causes, use short “because” chains that connect back to evidence. Example: win rates fell because differentiation weakened; differentiation weakened because reps don’t lead with quantified outcomes and proof; proof is weak because segment-specific references and ROI tools aren’t usable in discovery. Each link suggests specific interventions you can test.

Template: Diagnostic readout (8–10 pages).

  • What changed: acquisition and retention decomposition with the 2–3 dominant drivers for each.
  • Where profit sits: economics by segment and deal archetype, plus the largest leakage points.
  • Why it changed: top themes from customer and field voice, tied to decision mechanics.
  • Competitive reality: table stakes, competitor advantages, and exploitable fragilities.
  • Root causes and implications: 2–4 root causes linked to evidence and affected metrics.
  • No-regret moves: actions you can launch immediately that help under any strategy option.

No-regret moves are the bridge between diagnosis and transformation. They create momentum and improve performance while leadership debates larger choices like segmentation, pricing posture, or route to market. The best no-regret moves tighten standards, stop obvious leakage, and ship usable field assets.

  • Stage and qualification reset: define early-stage exit criteria and remove pipeline that doesn’t meet them.
  • ICP guardrails: publish an initial ICP scorecard and require approval for low-fit deals entering forecast.
  • Discount give-get: implement a simple give-get table so concessions buy something valuable (term, scope, references, payment).
  • Top-deal control: run weekly deal reviews on the quarter’s largest opportunities using a consistent deal plan.
  • Win/loss loop: complete a small number of rapid win/loss calls monthly and update plays and proof accordingly.

Close the diagnostic with a decision log: the decisions leadership must make next, the options under consideration, and what evidence would change the call. This prevents relitigating the same questions and keeps the strategy process moving. By the end of this work, you should be able to say—without hand-waving—what is driving performance, where money is being made or lost, and which interventions will matter most.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]