Product, Pricing, and Value Proposition| Umbrex

Great businesses don’t win on claims; they win because the product solves a real job better than alternatives, the price captures a fair share of that value, and the story makes the purchase obvious to the buyer. In diligence, those three threads—product, price, and value proposition—must be tested as a system. Your task is to prove whether demand is repeatable without heroics, whether realized price reflects true willingness to pay, and whether the messaging and proof points convert skeptical buyers to acceptable economics. This chapter gives you fast, falsifiable methods to assess product‑market fit (PMF), price power, and the clarity of the offer—by segment, not in aggregate—and to translate findings directly into valuation, terms, and post‑close priorities.

8.1 Product-Market Fit Assessment Guide

Product‑market fit isn’t a slogan. It’s observed, durable behavior: target customers repeatedly buy, use, and renew the product at prices that yield attractive unit economics—without bespoke work or excessive discounts. In diligence, you don’t have months to run experiments, so you assemble a tight evidence case from retention curves, usage and activation data, win/loss and procurement interviews, realized price corridors, and external signals. You then judge PMF segment by segment and show how that judgment changes price, structure, or post‑close plans.

What “good” PMF looks like (in plain economics)

Retention is durable: Cohorts stabilize at healthy gross revenue retention (GRR) and net revenue retention (NRR) by segment; logo retention corroborates the dollars. See 6.3 for formulas and QA.
Usage is habitual: A meaningful share of customers reach the “aha moment” quickly and repeat the core action at a frequency consistent with the job‑to‑be‑done.
Price is realized, not imagined: Discount depth and rebate leakage are controlled; renewal increases land without elevated churn or downgrade.
Growth is efficient: CAC and payback are inside base‑rate ranges for the category and segment; win rates vs. named rivals are stable or improving at comparable price.
Minimal heroics: Low custom work per deal, short time‑to‑value, reliable implementations; support burden is not masking product gaps.
Concentration is manageable: Expansion isn’t overly reliant on a handful of accounts or a single channel.

An evidence ladder: from strongest to weakest signal

Cohort GRR/NRR by segment and channel (with a price‑vs‑quantity bridge).
Transactional price realization (waterfall from list to net, renewal uplift outcomes).
Usage/engagement telemetry tied to the value moment (activation, frequency, breadth).
Win/loss vs. named competitors (including price gaps that flipped outcomes).
Sales motion efficiency (conversion at each funnel stage, cycle time, payback).
External traction (sell‑through panels, marketplace ranks, integration density, review velocity).
Attitudinal signals (NPS or “would be very disappointed” scores)—useful only when tied back to renewal and price acceptance.

Weight your case heavily toward 1–4. Treat 6–7 as corroboration, not proof.

Step‑by‑step PMF assessment (built for a 2–4‑week sprint)

Step 1 — Fix the scope: segments, jobs, and “what would have to be true.”
Anchor on the segmentation rules from 6.1. Write one sentence per top segment: “In [Segment], customers with job [X] adopt within [Y] weeks, reach [aha action] ≥ [Z]/period, renew at GRR ≥ [A]% with net uplift ≥ [B] bps, and tolerate price increases of [C] bps without churn hazard rising.” These become your PMF thresholds.

Step 2 — Build the cohort spine.
Compute GRR/NRR and logo retention by cohort, segment, and channel (6.3). Plot survival and hazard. Produce a 4–8‑quarter renewal waterfall showing ARR at risk by segment and the drivers (product gap, price, competition, procurement). This is the backbone of PMF.

Step 3 — Reconstruct realized price.
For top segments, build a price waterfall (list → standard discounts → promos → rebates/chargebacks → returns → channel margins → vendor‑realized). Tag renewal uplift outcomes and any churn/downgrade associated with increases. PMF with price power shows controlled discount depth and acceptance of moderate uplifts.

Step 4 — Map activation and usage.
Define the “aha moment” (the first action reliably linked to long‑term retention) and measure: time‑to‑aha, activation rate, and frequency of the core action (e.g., weekly active users completing task X, jobs scheduled per device, API calls per active account). Segment these by role, customer size, and channel. Look for a clear usage step‑up in retained cohorts.

Step 5 — Run focused Voice‑of‑Customer.
Interview current, churned, and lost‑deal cohorts (6.2). Reconstruct the last evaluation/renewal, pricing pushback, and switching steps. Disconfirm with procurement and channel partners. Extract the three claims that most often win or lose deals in each segment.

Step 6 — Analyze win/loss and funnel conversion.
If accessible, cut CRM by segment and rival: stage‑to‑stage conversion, win rate at comparable price, POC/pilot conversion, cycle time. Where CRM is unavailable, triangulate with seller interviews and partner checks; keep confidence labels visible.

Step 7 — Pull external traction signals.
Use sell‑through/scan panels (where applicable), marketplace ranks, integration directory counts, app‑store reviews, and search/traffic trends. Treat these as directional—helpful for momentum, not for PMF proof.

Step 8 — Quantify unit economics where PMF is claimed.
Compute CAC and payback by segment and channel. Cross‑check with contribution margins and renewal outcomes; efficient growth should appear where PMF is strongest.

Step 9 — Synthesize a segment‑level verdict.
For each segment, conclude PMF: Yes / Emerging / No, with 2–3 bullets of evidence, confidence level, and implications for valuation and terms.

Step 10 — Translate to the model and term sheet within 24 hours.
Raise/lower GRR/NRR, realized price, conversion, and payback by segment; widen ranges where confidence is medium/low. Where PMF is “Emerging,” push growth into upside or structure earnouts around NRR or price realization. Where PMF is “No,” either exclude from base or require explicit post‑close plays and gates.

A copy‑ready PMF Scorecard (fill once per segment)

Retention: Cumulative GRR ≥ ___% by month ___; NRR range –%; logo retention trend ___.
Price realization: Average discount depth ___%; renewal uplift acceptance ___ bps; price‑related churn hazard Δ ___.
Usage & activation: Time‑to‑aha ___ days; activation rate ___%; frequency of core action ___/period; breadth (# features or modules used) ___.
Sales efficiency: Win rate vs. top rival ___% at price parity; sales cycle ___ days; POC→close %; CAC $; payback ___ months.
Implementation & support: Median time‑to‑value ___ days; services % of revenue ___%; tickets per account per month ___; on‑time delivery/SLA ___.
External traction: Integration count ___; partner tier/listings ___; marketplace rank/review velocity ___.
Concentration: Top‑10 accounts % of ARR ___%; channel dependency note ___.
Confidence: High / Medium / Low (and why).
Implications: Model changes (lines & deltas), term‑sheet levers, post‑close actions and owners.

Store each completed scorecard in the data book with footnotes and source links.

Base‑rate guardrails (edit by category; use as ranges, not absolutes)

These are directional ranges to frame debate—tighten with your evidence by segment.

B2B SaaS (Mid‑Market): GRR 88–94%; NRR 105–120%; payback 9–18 months; win rate vs. top rival 25–45% at comparable price; renewal uplift 150–300 bps without hazard spike.
Enterprise software: GRR 90–96%; NRR 110–125% (expansion‑led); payback 12–24 months; longer cycles offset by higher stickiness.
Usage‑based models: Focus on active‑rate and intensity bands; NRR can exceed 120% in true PMF but is volatile—separate promo‑driven spikes from durable usage.
Marketplaces (two‑sided): Buyer repeat rates and seller churn are the signal; GMV growth with stable take rate is stronger than GMV growth with take‑rate compression.
Hardware + service: The annuity tells the truth—device shipment spikes don’t equal PMF; target consumables/services retention and attachment.

Anti‑patterns that masquerade as PMF

NRR looks strong but logo churn rises. Concentrated expansion is hiding decay—split cohorts by segment and remove top accounts to see the base.
Price “power” that lives only at list. Realized prices tell a different story once rebates, chargebacks, and channel margins are included.
Heavy bespoke work to land every deal. Services dependency signals poor product fit and fragile margins.
Promo‑dependent repeats. Re‑purchase collapses when incentives stop—treat as unsustainable.
Young cohorts underperform older ones. Growth is seeding future churn—move those dollars to upside only.

Outside‑in proxies when data access is thin

If telemetry or ledgers are unavailable, combine two or more of the following and carry lower confidence:

Renewal letters or pricing addenda + procurement interviews.
Distributor sell‑through + partner delist/list events.
Integration directory counts + expert/implementer interviews on time‑to‑value.
Review velocity (not just averages) + win/loss calls within the last 6–12 months.
Search/traffic trends + marketplace rank history tied to releases.

A 72‑hour PMF sprint plan (from blank page to decision)

Day 0: Freeze segments and PMF thresholds; publish the scorecard shell.
Day 1: Land cohort GRR/NRR for 2–3 top segments; build the first renewal waterfall; start price waterfall reconstruction.
Day 2: Run 8–12 VoC calls across current/churned/lost; tag activation/usage metrics; pull external traction signals.
Day 3: Fill segment scorecards; issue PMF verdicts with confidence; update the model (GRR/NRR, price, conversion, payback); propose term‑sheet levers and post‑close actions.

Hooks into valuation, terms, and the post‑close plan

Valuation: PMF raises confidence in revenue durability and price realization; encodes narrower ranges on GRR/NRR, realized price, and conversion.
Terms: Where PMF is “Emerging,” use earnouts tied to NRR or price realization, covenants on promo intensity or take‑rates, and conditions on key channel listings or licenses.
Post‑close: Concentrate resources on segments with proven PMF: product hardening where activation lags, migration tooling where switching costs block upsell, partner certifications where shelf access unlocks growth.

Acceptance criteria for a decision‑grade PMF assessment

Segment‑level scorecards completed with sources and confidence labels; no averages that hide truths.
Cohort retention, price waterfall, and usage/activation cuts produced for top segments and verified (see 4.4 for QA).
Win/loss and procurement perspectives captured; disconfirming evidence addressed.
Model updated within 24 hours; explicit note of which lines moved and why.
Residual uncertainty translated into price ranges, earnouts, covenants, or conditions.
All claims footnoted; raw artifacts stored in the data book; clean‑team rules followed for sensitive data.

When you run this play, “product‑market fit” stops being a vibe and becomes a verdict you can defend. You’ll know where the product truly resonates, what price the market will bear, and how to spend the next dollar—on the deal and after it closes.

8.2 Pricing Architecture Analysis – Step-by-Step Guide

Pricing architecture analysis answers three practical questions: what customers actually pay (not list), why it varies, and where you can lift realized price without breaking demand or channels. The work is part forensic accounting, part product design. You will reconstruct the price waterfall to the vendor‑realized and pocket price, map packaging and value metrics, expose discount and rebate habits, and translate findings into model inputs and a post‑close pricing roadmap. Keep it segmented—by customer, product tier, channel, and geography—or averages will lie.

Ground rules before you start

Fix scope: define segments, time window (e.g., LTM), and the metric you will report (vendor‑realized revenue per unit/seat/order; pocket price where available).
Lock compliance: operate under clean‑team rules for invoice‑level data; avoid any pre‑close price coordination topics with competitors; observe MAP/RPM and marketplace terms.
Tie to decisions: set explicit “would‑have‑to‑be‑true” thresholds (e.g., “+150–300 bps realized price in Mid‑Market without GRR falling below 92%”). If analysis won’t change price, terms, or the post‑close plan, simplify.

Step 1 — Assemble the pricing evidence pack

Collect artifacts that show list, discounts, rebates, fees, and channel economics. Prioritize originals over summaries.

Price books and CPQ exports (quotes, approvals, discount ladders, exceptions).
Executed contracts, order forms, SOWs, addenda, renewal letters, MFN/price‑parity clauses.
Invoices/credit memos; rebate and co‑op agreements; chargeback files; returns.
Channel agreements (reseller, distributor, marketplace) with take‑rates, MDF, and tiering.
Promotion calendars and funding sources.
Packaging/feature matrices; SKU catalogs; bill of materials (hardware); service rate cards.
For SaaS/usage: rate cards, meters (value metrics), tier thresholds, overage rules, minimum commits.
For healthcare/regulated: reimbursement schedules, codes, fee schedules, price caps.
For consumer/retail: scanner/POS panels, KVI lists, promo depth/length history.

Step 2 — Map packaging and value metrics

Packaging drives willingness to pay and discounting behavior. Document the structure that customers actually buy.

Tiers/modules/add‑ons; what’s gated at each tier.
Value metric(s): per user, per device, per location, per GB/API call/order; concurrency rules; minimums; overage pricing.
Bundles and options; attach rates and cannibalization.
Term structure: monthly/annual/multi‑year; prepay vs. pay‑as‑you‑go; price‑protection and indexation.
Price fences: segment, usage, channel, geography; who qualifies and how it’s enforced.
Services: implementation, training, managed service—rate cards and typical scope.

Quick test: Could a junior rep classify a deal’s tier and meter in 30 seconds? If not, packaging is likely creating leakage.

Step 3 — Reconstruct the price waterfall to pocket price

Your aim is the money that lands with the vendor per unit—and what remains after incentives.

Definitions

Vendor‑realized (net revenue per unit): List − on‑invoice discounts − promos − rebates/chargebacks − returns/credits − channel margin/take rate ± shipping/handling (as contracted). Exclude taxes and duties.
Pocket price: Vendor‑realized − off‑invoice incentives (co‑op, MDF, spiffs) − payment terms/cash discounts − warranty/guarantee reserves − free goods/extended trials.
Pocket margin: Pocket price − COGS − service cost‑to‑serve.

Do this, segmented by product × customer × channel × geo

Compute median and interquartile realized price corridors (e.g., $14–$19 per seat/month in Segment B).
Quantify leakage by source: average discount depth, promo mix, rebate accrual %, chargebacks %, returns %, channel margin %.
Produce one simple exhibit per segment: List → Vendor‑realized → Pocket price → Pocket margin.

Step 4 — Build discount ladders and approval maps

From CPQ and contracts, recover how discounts actually happen.

Standard ladders (volume bands, term length).
Discretionary discounts (frequency, depth, and who approves).
Deal‑desk/DOA thresholds: how often were they exceeded; approval latency; variance by region or rep.
Price floors and guardrails in practice vs. policy; rogue discount patterns (rep or region outliers).

Output: a one‑pager per segment showing typical discount path and the 80th/95th percentile depths.

Separate promotion from price. Promotions can build trials but also train customers.

Identify promo types: temporary price reductions, buy‑downs, bundles, free months, coupons, financing.
Funding: vendor vs. channel; accrual %; true‑up mechanics.
Measure lift and decay: volume during promo, post‑promo retention/repurchase, and net margin after all incentives.
Flag promo dependency segments where baseline demand collapses without incentives.

Step 6 — Resolve channel gross‑to‑net

Route‑to‑market often decides realized price more than list.

Direct vs. reseller vs. distributor vs. marketplace vs. OEM/white‑label.
Take‑rates/margins by route and tier; MDF/co‑op; paid placement and lead fees.
Channel conflict and price parity/MAP obligations; delist risk.
Build a channel bridge: list → channel economics → vendor‑realized.

Step 7 — Tie pricing to retention and win rates

Price power is only real if dollars stay.

Overlay price increases with cohort GRR/NRR (see 6.3); compute churn/downgrade hazard post‑increase.
Cut win/loss by price gap vs. named rivals; note thresholds that flip outcomes.
Use the 6.4 elasticity method to separate true price sensitivity from promo/mix noise.

Step 8 — Benchmark competitor price architecture (outside‑in)

You need parity and differentiation points, not a catalog.

Packaging and value metrics: where rivals gate features; bundle plays; unlimited claims with fine print.
Public price pages, quotes, distributor lists, marketplace ASINs/SKUs (respect TOS; no scraping behind log‑ins).
Typical realized corridors from procurement/channel interviews.
Anticipate responses: bundling, KVI holds, take‑rate changes, migration tools.

Step 9 — Quantify pricing headroom and hazards by segment

Synthesize findings into actionable ranges and risks.

Headroom: difference between willingness‑to‑pay (VoC pricing tasks, competitor corridors, value proof) and current realized price.
Hazards: MFNs, price‑parity, channel MAP, promo dependency, usage spikes masked by promos, price caps (regulated), and indexation gaps.
Uplift corridors: e.g., “Segment A +150–300 bps; Segment B 0–100 bps (KVI, price image sensitive).”
Time‑to‑realize: map to renewal cycles, channel notice periods, and CPQ/policy changes.

Step 10 — Push into the model (24‑hour rule)

Update the driver‑based model with:

Realized price per segment/channel (base and range).
Gross‑to‑net (channel margins, rebates, promo drag).
Pocket price and pocket margin (if service costs matter).
Price‑led churn/downgrade hazard where observed.
Scenario toggles: price uplift, promo reduction, take‑rate change, indexation adoption.

Step 11 — Quick wins vs. structural moves

Quick wins (next 90 days)

Enforce price floors and DOA; remove orphan discounts; standardize term/volume ladders.
Introduce CPI/indexation on new/renewed multi‑year contracts.
Localize price points and rounding; fix obvious currency mis‑parities.
Clarify meters and tier thresholds in CPQ; stop giving away high‑value add‑ons.
KVI list in consumer/retail: hold or limit increases on price image items; monetize the tail.

Structural moves (6–18 months)

Redesign packaging (Good‑Better‑Best, modular add‑ons); align value metric to customer outcomes.
Migrate from unlimited to usage‑based or hybrid; add minimum commits.
Re‑platform channel terms; renegotiate take‑rate tiers and MDF.
Introduce outcome‑based pricing where proof exists; phase pilots.
Rationalize services pricing; productize implementation.

Step 12 — Industry patterns to handle explicitly

SaaS/usage: Meter selection is the strategy—pick a value metric customers won’t game; define overage rules, minimums, and true‑up cadence.
Marketplaces/platforms: Revenue = GMV × take rate − incentives − returns/fraud; take‑rate compression is the default unless countered by unique value.
Hardware + service: Price equipment cycles separately; most value sits in annuity (consumables/services).
Healthcare: Constrained to reimbursable codes; model payer mix; price increases follow coverage and policy, not desire.
CPG/retail: Distinguish sell‑in vs. sell‑through; promo depth/length drives realized price; KVIs anchor elasticity.
Industrial distribution: Rebates, ship‑from‑stock vs. direct, freight terms, and payment terms dominate pocket price.

Step 13 — Risks, controls, and compliance

Document MFNs, price‑parity, MAP/RPM, and channel clauses; model their constraints.
Keep invoice‑level analyses within a clean‑team; share only aggregated, anonymized outputs.
For primary research, disclose purpose (unless counsel approves blind) and avoid eliciting MNPI or future pricing intentions from competitors/customers.

Step 14 — Acceptance criteria (what “done” means)

Verified price waterfall to vendor‑realized and pocket price by segment and channel, with corridors and leakage quantified.
Discount ladders and approval maps reconstructed; outliers identified with owner and fix.
Promo/REB/MDF ROI assessed; channel gross‑to‑net bridge produced.
Uplift corridors and hazards defined, with renewal/channel timing to realize.
Model updated (base/range) and linked to retention and elasticity evidence.
Term‑sheet levers proposed where uncertainty remains (earnouts tied to price realization, covenants on promo/take‑rate intensity, conditions on key channel renewals).
All exhibits footnoted; raw artifacts stored in the data book; verifier sign‑off logged.

Step 15 — Common failure modes (and how to avoid them)

Using list price anywhere near a conclusion → rebuild realized/pocket price; show the waterfall.
Averaging across channels/regions → compute per route and geo; roll up with value weights.
Treating promo as price → separate and measure decay; don’t call promo‑led volume “price power.”
Ignoring MFNs/price‑parity → you can’t raise one segment if clauses drag others.
Underestimating implementation effort → tie uplifts to renewal cadence and CPQ/policy changes.
No QA → require a model‑to‑deck tie‑out; replicate numbers from source registers before circulation.

Copy‑ready templates

Pricing Architecture Canvas (one per segment)

Offer & meter: tier(s), modules, value metric, thresholds, minimums.
Realized price corridor: median and IQR; pocket price if available.
Waterfall shares: discounts, promos, rebates/chargebacks, returns, channel margin, off‑invoice incentives.
Discount ladder & DOA: bands, typical exceptions, 80th/95th percentile.
Channel economics: take‑rate tiers, MDF/co‑op, paid placement.
Terms: indexation, MFN/price‑parity, price caps, warranty/SLAs, payment terms.
Headroom & hazards: uplift corridor, promo dependency, elasticity notes, regulatory constraints.
Confidence & sources: H/M/L, key artifacts (invoices, CPQ extract, contracts).

Quote Sampling Plan (run in parallel)

Pull 50–100 recent quotes/invoices stratified by segment × channel × geo.
For each: tier/meter, list components, discounts, rebates, promo, take‑rate, add‑ons, term, approval path, realized price, outcome (won/lost/renewed).
Tag anomalies for deal‑desk follow‑up.

72‑hour sprint plan

Day 0: Lock segments and “would‑have‑to‑be‑true” thresholds; publish artifact requests; confirm clean‑team.
Day 1: Land first waterfalls for two segments; reconstruct ladders and DOA from CPQ; start channel bridge.
Day 2: Overlay retention and win/loss; measure promo drag; draft uplift corridors; flag MFN/price‑parity constraints.
Day 3: Update model (price, gross‑to‑net, hazard); publish canvases and a quick‑win/structural roadmap; align term‑sheet levers.

Run this play and your pricing story will move from list‑price myths to hard numbers: what you keep after incentives, where headroom exists, how fast you can take it, and which guardrails and terms keep value intact.

8.3 Unit Economics Template

Unit economics is the speedometer of a deal. It tells you, per customer or per transaction, how much value you keep after the real costs of winning, serving, and retaining that revenue. In diligence, you don’t need a glossy model; you need a clean, segmented build you can defend: a precise definition of the “unit,” the revenue you actually realize, the cost stack required to deliver it, and the cash and P&L payback once you’ve spent to acquire the customer. Do this by segment and route‑to‑market, wire it into your bottom‑up sizing and retention work, and translate the result into constraints for valuation, terms, and post‑close priorities.

Start with two principles. First, define the unit to match how demand forms and how pricing works (seat, device, order, GMV dollar, procedure, API call, visit). Second, model vendor‑realized and pocket price, not list; your waterfall from 8.2 is the revenue truth. Everything else—contribution margin, CAC, LTV, and payback—hangs from those anchors.

Step 1 — Fix the unit and the segmentation

Write the unit in one sentence and freeze it: “Per paying seat per month in Mid‑Market manufacturing, sold direct in North America,” or “Per order in marketplace grocery, seller‑funded promos included, platform take rate net.” Apply the same segmentation you locked in Chapter 6 (customer/job, size band, channel, region, product family). If economics differ, it’s a different unit or a different segment.

Step 2 — Build the revenue engine (per unit and per customer)

Reconstruct the vendor‑realized price per unit using the price waterfall from 8.2 (list → discounts → promos → rebates/chargebacks → returns/credits → channel margin/take rate). Where relevant, also compute pocket price (vendor‑realized minus off‑invoice incentives, payment terms/cash discounts, MDF, and guarantees). For subscription and usage models, translate to ARPU by segment: ARPU = active rate × intensity (units per active) × realized rate. For marketplaces, revenue = GMV × take rate − incentives − returns/fraud. Present corridors (median and interquartile range), not single points.

Step 3 — Build the cost stack (the part that really moves)

Separate cost into layers and keep fixed costs out of unit economics unless they vary meaningfully with volume.

COGS / fulfillment: materials, manufacturing/hosting, logistics, third‑party data, payment processing, fraud losses, returns handling, warranties.
Service cost‑to‑serve: support tickets, onboarding/implementation labor, success/CSM time, field service, cloud usage directly tied to a customer or unit.
Channel economics: reseller or marketplace take rate, rebates, co‑op/MDF, paid placement, lead fees.
Other variable drags: bad debt/chargebacks, trial/POC spend that scales with new customers, service credits/SLAs.

Compute CM1 (gross margin) = vendor‑realized revenue − COGS.
Compute CM2 (contribution margin) = CM1 − variable service cost‑to‑serve − variable channel/incentive costs.
You can add CM3 by subtracting semi‑variable GTM costs that scale with increments (e.g., implementation teams when tied to bookings), but do not blend in corporate overhead.

Step 4 — Compute CAC the right way (and label it)

CAC is slippery; define it so the CFO and CRO would agree.

Blended CAC: fully loaded sales + marketing + partner fees + commissions + SDRs + promo spend that is acquisition‑linked, divided by new paying customers in period.
New‑logo CAC vs. expansion CAC: separate if expansion is material; otherwise you’ll overstate efficiency.
Channel CAC: for partners/marketplaces, include rev share, co‑op/MDF, paid placement, and sales coverage for partner enablement.
Time alignment: shift CAC by average sales cycle so spend lines up with revenue start; otherwise payback “improves” on paper.
Cash CAC vs. P&L CAC: cash includes spiffs, prepayments, and working‑capital effects; label which you’re using.

Step 5 — LTV from cohorts, not from folklore

Lifetime value should fall out of your cohort and retention analysis (6.3), not a back‑of‑the‑napkin “ARPU divided by churn.”

Cohort LTV (preferred):
LTV = Σ_t [(ARPU_t × gross margin %) × survival_t × discount_factor_t] − variable service cost_t.
Where survival_t comes from observed GRR/logo curves by segment; ARPU_t reflects price increases and mix; the discount factor reflects the cost of capital (use an annual rate and convert to period).
Constant‑churn approximation (sanity check only):
If monthly churn = c and no price growth, LTV ≈ ARPU × GM / c. Use only as a bound; it hides cohort shape, price changes, and expansion.
Usage‑based nuance: model active rate, intensity, and collectability separately; a spike in intensity can inflate LTV if cloud or service costs scale faster.
Marketplaces: compute LTV on the side that drives your CAC (buyer or seller), include GMV per period × take rate net of incentives × retention, and watch return/fraud leakage.

Choose a horizon that matches reality (often 36–60 months for B2B; shorter for SMB/consumer), then show both undiscounted and discounted LTV with confidence labels.

Step 6 — Payback: P&L and cash, both matter

P&L payback (months): months until cumulative CM2 covers P&L CAC.
Cash payback (months): months until cumulative cash inflows (after working capital) exceed cash CAC.
Working‑capital levers: annual prepay (SaaS often has negative working capital), DSO and refund/chargeback timing (consumer), inventory and payables (CPG/hardware), and claims payment lag (healthcare). In downturns, cash payback is the tripwire that matters.

Step 7 — The Unit Economics Canvas (copy and fill one per segment)

Unit & scope: definition, channel, region, product family.
Realized price (corridor): median and IQR; pocket price if available; sources.
COGS / fulfillment: per unit and as % of realized price; drivers.
Service cost‑to‑serve: per unit; key drivers (tickets, onboarding hours, cloud step‑ups).
Channel economics: take rate/rebates/MDF; gross‑to‑net bridge.
CM1 / CM2: values and %; notes on variability with scale.
ARPU model: active rate × intensity × realized rate; attach rates for add‑ons.
CAC: definition used (new/blended/channel); dollars and primary drivers.
LTV: method (cohort vs. approximation), horizon, discount rate; range and confidence.
Payback: P&L and cash months; renewal or purchase cadence assumptions.
Sensitivity levers: price +/− bps, churn/NRR shift, CAC ±, channel take‑rate ±, COGS step‑change.
Risks & gates: MFNs, MAP/price‑parity, promo dependency, policy caps, partner renewals.
QA & sources: verifier, links to data book, date of last refresh.

Step 8 — Sensitivity and scenario discipline

Run a short tornado to identify the 2–3 variables that swing LTV/CAC and payback: realized price, GRR/NRR and survival shape, CAC per channel, and a single cost driver (cloud or service labor). Toggle those in base/downside/upside and tie each to an early‑warning indicator (discount depth, rebate accruals, hazard after price increases, partner take‑rate notices, cloud unit‑cost changes). Resist the urge to add knobs you won’t monitor.

Step 9 — Business‑model modules (pick what fits your deal)

B2B SaaS / subscription
Unit: paying seat/account per month or ARR dollar.
Revenue: ARPU = seats × realized rate; expansion from seats/modules; indexation on renewals.
Cost: hosting, support, success, payment processing; implementation labor if not billed.
CAC: sales/SDR/marketing + partner fees; align to cycle.
Watch: GRR/NRR by segment, price‑led churn hazard, annual prepay (cash payback often immediate), multi‑year terms and MFNs.
Usage‑based software / APIs
Unit: active account/month or metered unit (API call, GB).
Revenue: active rate × intensity × realized rate; tier thresholds and overage.
Cost: cloud/compute per unit, support per heavy user, third‑party data.
Watch: intensity cliffs at tier thresholds, collectability, rate‑plan downgrades.
Marketplaces / platforms
Unit: buyer order or seller month; GMV dollar.
Revenue: GMV × take rate − incentives − returns/fraud; two‑sided CAC if you recruit supply and demand.
Cost: payment processing, support, trust & safety, chargebacks, paid placement.
Watch: take‑rate compression, return/fraud drag, liquidity thresholds, multi‑homing.
Hardware + service (annuity)
Unit: device shipment and service month.
Revenue: device price (cyclical) + annuity (consumables/services) with attach and usage.
Cost: BOM, freight, warranty; field service; spare parts.
Watch: installed‑base retention, annuity ARPU, replacement cycles; avoid projecting a shipment spike into LTV.
CPG / retail
Unit: consumer unit or store‑week.
Revenue: scanner sell‑through × price net of trade (promo, rebates, slotting).
Cost: COGS, freight, shrink, returns.
CAC: trade spend, shopper marketing, merchandising; account‑level acquisition (new distribution) vs. consumer pull.
Watch: KVI price constraints, promo dependency, retailer margin asks, delist risk.
Services / implementation
Unit: billable hour or fixed‑fee project.
Revenue: rate × utilization × realization.
Cost: labor comp, bench, travel, subcontractors.
Watch: utilization discipline, scope creep, collection lag.

Step 10 — QA and guardrails you should enforce

Numerator/denominator match: the revenue you use for margins must be the vendor‑realized for that unit and segment.
No list‑price math: always show the waterfall to realize and pocket price.
CAC alignment: shift CAC by cycle length; separate new vs. expansion; include channel incentives.
Cohort‑based LTV: prefer observed survival curves; label discount rate and horizon.
Cash vs. P&L: compute both paybacks; include working‑capital effects (DSO/DPO/inventory or deferred revenue).
Verifier sign‑off: a second person can reproduce all numbers from the data book; every exhibit footnoted.

Step 11 — Red flags (and immediate responses)

Strong NRR with rising logo churn: expansion concentration is masking decay. Cut LTV by segment and compute “with/without top 10 accounts.”
Pocket margin thinness at scale: cloud or service costs scaling with usage faster than price; add cost step‑ups to sensitivities; push for price‑to‑value or architecture work post‑close.
Promo dependency: CM2 collapses without incentives; move price uplift to upside only and model higher CAC.
Channel leakage: take‑rate hikes or paid placement erode gross‑to‑net; tighten ranges; consider covenants on take‑rate intensity.
MFNs/price‑parity traps: uplifts in one segment trigger give‑backs elsewhere; reflected in headroom and term sheet.
Invoice‑to‑model mismatches: freeze exhibits until waterfall and model re‑tie.

Step 12 — Translate to valuation, terms, and the post‑close plan

Valuation ranges: bind base/downside with CM2, LTV/CAC, and cash payback by segment; widen where evidence is thin.
Terms: when uncertainty is material, use earnouts tied to NRR or realized price, covenants on promo/take‑rate intensity, and conditions on key channel renewals or price‑indexation adoption.
Post‑close actions: price floors/DOA enforcement, KVI strategy, packaging/meter fixes, channel renegotiations, onboarding automation, cloud unit‑cost reductions, success coverage where hazard spikes.

Step 13 — 72‑hour sprint plan (from blank page to decision‑grade)

Day 0: Freeze unit definitions and segments; publish the Unit Economics Canvas shell; confirm clean‑team scope for invoice‑level data.
Day 1: Land realized price corridors and pocket price for two top segments; build CM1/CM2; assemble CAC by channel with cycle alignment.
Day 2: Compute LTV from cohort survival; add P&L and cash payback; run a first tornado on price, GRR/NRR, CAC, and a key cost driver.
Day 3: Fill canvases for all material segments; update the model with base/range; issue red‑flag notes and term‑sheet levers; assign post‑close owners for the top three unit‑economics moves.

Acceptance criteria (use this as your “done” check)

Unit and segment definitions frozen; vendor‑realized and pocket price corridors verified.
CM1/CM2 computed with a visible waterfall and cost stack; sources footnoted.
CAC definition explicit; new vs. expansion/channel CAC separated where material; cycle‑aligned.
LTV from cohorts with horizon and discount rate stated; constant‑churn version used only as a check.
P&L and cash payback calculated; working‑capital assumptions documented.
Sensitivity results identify the top 2–3 drivers; early‑warning indicators tied to each.
Model updated within 24 hours; valuation ranges and term‑sheet protections adjusted; post‑close actions listed with owners and dates.
Verifier sign‑off recorded; data book contains invoices/contracts extracts, cohort sheets, price waterfalls, CAC build, and replication notes.

Build unit economics this way and you’ll replace generalities with operating truth: what a customer is worth, what it costs to win and keep them, and how fast the cash returns—by segment, by channel, with levers you can pull. That is the level of clarity that moves a deal from “story” to “price, terms, and plan.”

8.4 Differentiation Scorecard Checklist

Differentiation is not a tagline. It is the repeatable reason customers choose you at a healthy price—and stay. In diligence, you need a way to judge that reason quickly, segment by segment, with evidence that ties to unit economics. The Differentiation Scorecard does exactly that. It translates claims into testable criteria, requires proof, assigns weights that reflect what matters in each segment, and yields a single, auditable score you can compare against named rivals and wire into valuation, terms, and the post‑close plan.

Begin with two anchors. First, differentiation is segmented: what wins in Enterprise compliance may not matter in SMB self‑serve. Second, differentiation is economic: it should show up as realized price premium or discount resilience, higher win rates at parity price, faster payback, better NRR/GRR, or structurally lower cost‑to‑serve. If you cannot see it in the P&L or the funnel, treat it as marketing until proven otherwise.

What the scorecard measures

Use four buckets that together explain whether an edge exists, pays, and lasts:

Customer Resonance (Does it matter to buyers?)
Outcome superiority on the job‑to‑be‑done, time‑to‑value, reliability, ease of use, integration depth, and proof that buyers care (win/loss reasons, VoC).
Economic Yield (Does it show up in numbers?)
Realized price premium or discount resilience at equal service, win‑rate advantage at parity price, CAC/payback edge, contribution margin advantages tied to the edge, NRR/GRR lift.
Durability (Will it hold?)
Switching costs, data and network effects, IP/regulatory gates, channel exclusivity, learning‑curve or cost‑curve position, time‑to‑copy for rivals.
Operational Readiness (Can the company exploit it?)
Coverage and enablement in the sales motion, partner mindshare, delivery capacity, release velocity, and the incentive systems that protect realized price.

Scoring scale (0–5 per criterion; calibrate once, then lock)

0 – Parity or myth: No observable advantage; claim not evidenced.
1 – Weak: Minor preference in anecdote; no economic signal.
2 – Emerging: Early signals in a sub‑segment; thin or inconsistent economics.
3 – Meaningful: Clear segment‑level buyer preference and some economic yield.
4 – Strong: Repeatable yield (price/win/NRR) with early durability proof.
5 – Category‑leading: Durable edge evidenced across multiple segments, with rivals disincentivized or unable to copy within the hold period.

Recommended default weights (adjust to segment realities; document changes)

Enterprise, regulated segments: Customer Resonance 25%, Economic Yield 30%, Durability 30%, Operational Readiness 15%.
Mid‑market B2B: 30%, 35%, 20%, 15%.
SMB/self‑serve or consumer: 35%, 30%, 15%, 20%.
Marketplaces/platforms: 25%, 30%, 30% (durability heavier for network effects), 15%.

Step‑by‑step: build and use the scorecard in a diligence sprint

Fix scope and segments.
List the two to five segments that move value (from 6.1). For each, write a one‑line WHTBT statement: “In Mid‑Market Manufacturing, the product’s workflow integration reduces cycle time by ≥25% and supports a 200–300 bps price uplift with no GRR deterioration.”
Inventory differentiation claims and rewrite them as tests.
Convert slogans into evidence‑seeking prompts: “Price premium at equal SLA,” “NRR +5–10 points tied to feature X,” “Implementation hours 30–50% lower than peer,” “Distributor margin 200 bps better due to throughput.”
Define criteria within the four buckets (keep it tight).
Customer Resonance: outcome superiority, time‑to‑value, ease/integration.
Economic Yield: realized price premium/discount resilience, win‑rate lift, CAC/payback, NRR/GRR.
Durability: switching costs, data/network effects, IP/regulatory, cost curve, channel exclusivity, time‑to‑copy.
Operational Readiness: sales coverage/enablement, partner shelf control, delivery capacity and SLAs, release velocity, pricing governance.
Set weights and lock them by segment.
Adjust the default weights to reflect buying physics. For instance, in the public sector, raise Durability (contracts, approvals) and Operational Readiness (contract vehicles).
Define the proof required for each criterion (minimum two sources).
Examples: invoices/contracts + procurement interview for price; cohort GRR/NRR + VoC for retention; CPQ/approval logs for discount governance; distributor sell‑through + partner terms for channel; usage telemetry + implementation time studies for time‑to‑value; patent/approval documents for IP/regulatory; cost stack for cost curve.
Score with anchors, not vibes.
Use the 0–5 scale with written anchors per criterion. Example for “Realized price premium at equal service”:
0–1: none; heavy discounting.
2: corridor overlap; sporadic uplifts.
3: 1–3% uplift sustained in a segment without churn hazard.
4: 3–6% uplift sustained across two segments.
5: >6% uplift plus MFN/parity managed; rivals disincentivized to match (bundle cannibalization or channel conflict).
Calibrate against a named rival.
Score the target and two top competitors on the same card using the same evidence rules. This prevents grade inflation and surfaces where the edge is relative, not absolute.
Compute the Weighted Differentiation Score (WDS).
WDS_segment = Σ (Criterion Score × Criterion Weight). Show the math and the confidence label (High/Medium/Low) tied to evidence quality.
Tie the WDS to economic outcomes.
Plot WDS against realized price corridor, win rate at parity price, GRR/NRR, and CM2 by segment. If high WDS doesn’t correlate with yield, revisit assumptions—either the edge is unexploited (Operational Readiness gap) or it isn’t real.
Stress‑test durability with response scenarios.
For each top segment, test one rival response (bundling, take‑rate change, migration tooling, price aggression). Re‑score Durability and Operational Readiness with the counter in place; adjust confidence and ranges in the model.
Push results into the model and term sheet within 24 hours.
Raise/lower realized price, win‑rate, CAC/payback, and GRR/NRR by segment in line with the scorecard. Where confidence is medium/low, reflect residual risk in valuation ranges and structure (earnouts tied to price realization or NRR; covenants on promo/take‑rate intensity; conditions on key certifications, licenses, or partner renewals).
Publish the scorecards and assign owners for gaps.
Every gap with economic materiality gets an owner and a 90‑day post‑close action: harden integration X, enforce discount guardrails, secure partner tier, ship migration tooling, lock data rights.

Copy‑ready Differentiation Scorecard (one per segment; fill and file)

Segment and scope: product family, customer/job, size band, channel, region.
Customer Resonance (weight __%):
Outcome superiority (0–5; evidence); time‑to‑value (0–5; evidence); integration/workflow fit (0–5; evidence); operational reliability/SLA (0–5; evidence).
Economic Yield (weight __%):
Realized price premium or discount resilience (0–5; evidence); win‑rate at parity price (0–5; evidence); CAC/payback vs. peers (0–5; evidence); NRR/GRR delta (0–5; evidence); CM2 edge (0–5; evidence).
Durability (weight __%):
Switching costs (0–5; evidence); data/network effects (0–5; evidence); IP/regulatory/approvals (0–5; evidence); cost‑curve/learning (0–5; evidence); channel exclusivity/shelf control (0–5; evidence); time‑to‑copy estimate (0–5; rationale).
Operational Readiness (weight __%):
Sales coverage & enablement (0–5); partner mindshare & certifications (0–5); delivery capacity/SLAs (0–5); release velocity & quality (0–5); pricing governance (0–5).
WDS and confidence: calculated score, H/M/L with rationale.
Correlation to economics: observed links to price, win, NRR, CM2.
Top 3 erosion risks & clocks: what, why, estimated time‑to‑impact.
Countermeasures & owners: post‑close plan items with dates.
Sources & QA: footnotes to invoices/CPQ/VoC/panels; verifier sign‑off.

Using the scorecard to drive pricing, roadmap, and GTM

Pricing: Where WDS is high and Economic Yield anchors are substantiated, move realized price corridors up or reduce discount ladders; add CPI/indexation at renewal; protect KVIs in price‑image‑sensitive channels; tie earnouts to realized price where confidence is medium.
Roadmap: Fund features that reinforce the edge (e.g., deeper integration that raises switching costs) and kill parity chases that don’t move economics in the scored segments.
GTM: Point coverage and partners at advantaged segments; harden enablement and objection handling around the verified edge; negotiate channel tiers/exclusives where shelf drives gross‑to‑net.

Parity‑creep monitor (make it a habit)

Watch competitor release notes and pricing page diffs, integration directory counts, partner tier changes, and discount depth trends by segment.
Track time‑to‑parity for features that previously scored 4–5; if it compresses, shift emphasis to edges with longer clocks (data rights, workflow lock‑in, cost curve).
Add a quarterly “moat audit” in the PMO: re‑score Durability on the top two edges per segment; update early‑warning indicators (delistings, take‑rate notices, migration tool launches, price‑led win/loss swings).

Quality controls that keep scores honest

Two‑source rule for each criterion; prioritize evidence close to cash (invoices, renewals, sell‑through) over opinions.
Same segmentation and period across all comparisons; numerator/denominator alignment for price and share.
Independent verifier reproduces WDS and ties it to cited sources before any exhibit goes external.
Red‑team session to challenge causality: could discounting, promo, or channel explain the “edge”?
Confidence labels visible on the card and in the deck; ranges widened where evidence is thin.

Common failure modes—and quick fixes

Feature checklists masquerading as differentiation. Fix: reframe around outcomes and economics; drop items that don’t move price, win, payback, or NRR.
Averages that hide truths. Fix: score by micro‑segment and route‑to‑market; roll up with value weights only after differences prove immaterial.
List‑price mythology. Fix: rebuild realized price and discount ladders; treat promos separately.
Over‑weighting non‑durable edges. Fix: add time‑to‑copy and rival incentives; discount scores where copy is cheap or cannibalization is low.
Unexploited advantages. Fix: if Operational Readiness scores lag, push post‑close actions (enablement, pricing governance, partner upgrades) before paying for upside.

72‑hour sprint plan (from blank page to a defendable score)

Day 0: Lock segments, weights, and WHTBT statements; publish the empty scorecard and evidence checklist.
Day 1: Land price waterfalls and win/loss/VoC for two top segments; start cohort GRR/NRR and CM2 cuts; draft first two cards with evidence links.
Day 2: Add durability proofs (integrations, data rights, IP/regulatory, channel tiers), and operational coverage/capacity; calibrate against two named rivals.
Day 3: Compute WDS, correlate it to economics, push into the model (price, win, NRR, CAC/payback), and propose term‑sheet levers and post‑close owners for gaps.

Acceptance criteria for a decision‑grade scorecard

Segment‑level cards completed for the top value pools; weights documented; scoring anchors written.
Each criterion supported by at least two sources, with verifier sign‑off; confidence labels present.
WDS correlated to economic outcomes; where correlation is weak, causes identified and actions proposed.
Model updated within 24 hours; residual risk reflected in valuation and structure.
Early‑warning indicators and parity‑creep monitors defined; owners and check‑in cadence set.

Run this checklist and the conversation shifts from claims to proof. You will know where the target is different in ways buyers pay for, how long that difference will last, and what to do—now and after close—to widen the gap.

Commercial Due Diligence Playbook >

Product, Pricing, and Value Proposition