Reading a unit economics calculator as an audit, not a plan
A Unit Economics Calculator usually gets sold as a planning tool, but its sharpest use is diagnostic. It shows where profit leaks, which assumptions are brittle, and which interventions actually move the outcome. What separates an audit from a forecast is the opening question. Not "what is our CAC?" but "where does profitability break, and why there?"
Passing the audit means three things hold at once. Each unit is structurally profitable, or can be made so with levers you could realistically pull. Scaling adds profit faster than it adds risk: cash exposure, cost volatility, support load, refunds. And the model survives stress: a shift in channel mix, a price change, a cost spike, a dip in retention. When one of those claims fails, the response is not optimization. You redesign the thing that broke: the unit definition, the pricing, the packaging, the channel mix, or the cost architecture.
Inspect the denominator before anything else
Most broken models are broken at the unit itself, because the unit is fuzzy. A unit that survives audit is measurable without interpretation, tied to revenue realization, tied to variable costs, and stable across channels and segments.
Take a B2B workflow platform that reports "active users" while its contracts are priced per workspace. Support cost scales per workspace, not per user; marketing reports CAC per signup; finance talks LTV per account. Three denominators, so the model never reconciles. The way out is to force a single unit (the paid workspace-month) with a create event defined as the first successful invoice and a termination event defined as cancellation or non-payment plus a stated grace policy, and then to insist CAC is measured per paid workspace created. That one alignment reshapes decisions downstream, because cost, revenue, and acquisition finally sit under the same unit.
What you actually keep from each sale
Revenue is usually overstated because the model reaches for list price or gross transaction value. An audit runs on net revenue: what is left after leakage. That means subtracting refunds and credits, chargebacks and dispute losses, promotional discounts and sales concessions, the taxes you collect and remit (which were never yours), and any partner revenue shares or app-store fees.
An online events platform shows the trap plainly. It reports strong GMV per attendee, but it only keeps a service fee, and some event categories refund heavily. Model GMV and you will approve acquisition spend that is mathematically impossible to recover. The unit revenue has to become the service fee collected per completed attendance, net of refunds and payout adjustments, with the refund rate segmented by event category and channel source. That is the number that tells you whether the unit is profitable in reality rather than in a pitch deck.
Sorting costs that grow with volume from ones that don't
This is where businesses quietly fail: they treat a cost as fixed right up until scale forces it to grow, and then the model collapses. The audit rule is blunt. If a cost must increase when units increase within your planning horizon, it is variable for the purposes of the audit. The costs that hide tend to be the human and metered ones: onboarding hours per customer, customer-success touches per account, support tickets per active unit, infrastructure per usage band, and third-party per-action fees for things like verification, messaging, or enrichment.
A B2B contract-management product makes the point. It sells annual contracts, and a standard onboarding runs 8–12 hours of specialist time. At small scale, founders absorb that work and onboarding looks fixed; at larger scale it becomes a hiring driver. Booked honestly as a front-loaded variable cost per unit, it changes the payback picture (margin may only begin once onboarding is complete) and it often reveals that growth is capped not by demand but by how many units the team can actually deliver.
Walking the margin down, line by line
Rather than jump to LTV, the audit walks contribution margin down one layer at a time:
- Net revenue per unit
- minus transaction leakage (fees, refunds, disputes)
- minus variable infrastructure (usage-tied compute/storage/bandwidth)
- minus vendor fees (per action)
- minus human-variable costs (support/onboarding scaled per unit)
= contribution margin per unit
The walk matters because it isolates which layer dominates. A messaging-heavy support platform is the classic case. It integrates SMS and WhatsApp notifications, customers configure alerts freely, and usage varies wildly: some customers trigger 10× the message volume with no matching revenue. Walk the margin and vendor messaging fees turn out to drive most of the variance, while a blended "gross margin" quietly averages away the negative-margin cohorts. The response follows the driver: introduce usage bands or credits, add in-product controls and defaults that curb message spam, and align pricing with message volume. When you cannot explain margin variance with a small handful of drivers, the model is missing a cost attachment.
Retention is a survival curve, not a percentage
Retention has to be read as cohort survival over time, not a single churn figure that flattens the lifecycle. A project-based SaaS shows why the average lies. Customers churn once a project wraps, but new signups keep replacing them, so monthly churn reads acceptable, even as LTV stays capped because the usage is episodic by nature. The useful cohort cut is by project type and frequency, and the real question is what share of customers start a second project within X days. If the product cannot make multi-project behavior natural, acquisition has to be constrained, because both payback and the LTV ceiling are structurally limited, and the roadmap's job becomes making repeat use easy through templates, duplication, and cross-project dashboards. That is a different conclusion from "improve churn," because here churn is structural, not tactical.
Payback is a schedule, not an amount
Two businesses can carry the same margin-based LTV and live in completely different cash realities, so the audit wants timing curves. When is CAC paid: immediately, weekly, across a sales cycle? When does margin begin: after onboarding, after delivery, after first renewal? And how does it accumulate: monthly, usage-based, seasonal?
An implementation-heavy analytics tool illustrates the gap. It sells annual contracts collected upfront but needs integrations, so cost is front-loaded and renewals hinge on adoption. Early profit looks high on the strength of that upfront cash, renewal risk climbs when adoption is slow, and an honest payback view adds a time-to-adoption leading indicator. The moves that follow (pricing implementation explicitly so cost becomes revenue, steering sales toward profiles that integrate quickly, and requiring minimum contract terms) all exist to stop upfront cash from being mistaken for durable unit economics.
Blended numbers are not evidence
An audit fails the moment it leans on blended metrics while the segments underneath behave differently. The cuts that usually matter are acquisition channel, for intent and cohort quality; plan or tier, for support and feature mix; customer size and complexity in B2B; usage intensity for usage-based products; and geography, which drags in fees, compliance, tax, and dispute rates.
A consumer subscription that grows through both search and influencer campaigns makes the failure concrete. Search brings high intent and high retention; influencers bring volume and early churn. Blended CAC and blended churn look fine, but split them and the influencer cohorts are underwater against the payback boundary. The response is cohort-specific: tighten the refund-prone influencer offers, rework onboarding to lift early retention for that group, and cap spend until the cohort clears its margin floor and payback threshold. A model that cannot produce segment-level pass/fail verdicts is not an audit tool: it is a narrative one.
Does the model survive a realistic shock?
You do not need dozens of scenarios, only the handful that actually kill businesses. A workable battery raises CAC by 20% for auction and competitive pressure, lifts the refund or dispute rate by 10% for a policy or channel shift, adds 25% to variable infrastructure cost for a workload or vendor change, increases support tickets per unit by 15% as complexity grows, and dips the retention curve early to mimic a product change that hurts time-to-value.
An expense-management SaaS shows what the battery catches. A new integration lifts adoption but also support tickets; without the shock, the team simply celebrates a successful feature. Run it, and support-driven margin erosion pushes payback past the boundary at the planned growth rate. The response is to ship self-serve diagnostics and integration health checks before scaling, put the integration behind tiers that fund its support load, and slow acquisition until the support driver returns within cap. Framed this way, growth has to earn permission by staying inside audited constraints. Re-running that battery by hand every quarter is tedious in a spreadsheet, which is why some teams park their segment assumptions in a standing unit economics model and just fire the shocks at it again.
Writing up findings so somebody can act
An audit should end in a short set of verdicts and remediations, not a metrics dump. A segment passes when it clears the margin floor and payback boundary under both the base case and mild shocks. It earns a conditional pass when the base case holds but a single shock breaks it, which points to targeted remediation. It fails when the unit is negative-margin, or when payback sits beyond the boundary even in the base case.
Each remediation names a driver and a lever. Pricing and packaging work aligns revenue to cost drivers through bands and restructured tiers. Channel work caps spend, changes targeting, or shifts creative to pre-qualify cohorts. Product work improves time-to-value and pulls down early churn and ticket volume. Operations work automates support, standardizes onboarding, and cuts implementation hours. Vendor work renegotiates fees, reduces per-action usage, and adds caching or batching. The reporting lands when it names the driver and the lever, not when it lists metrics.
Three redesigns that came out of an audit
A B2B signature-workflow tool ran a "free forever" tier that generated heavy support usage without revenue, while its healthy-margin paid tier suffered because support was overwhelmed and retention slipped. The redesign constrained the free tier by usage and support access, added self-serve onboarding and documentation, and introduced a mid-tier that monetized high-usage free users without enterprise overhead.
A consumer marketplace watched partner revenue-share creep erode net revenue per unit; acquisition looked efficient until payback failed once the shares were subtracted. The fix renegotiated shares against volume thresholds, moved growth toward direct channels for the better-margin segments, and added partner-exclusive tiers priced to protect the margin floor.
A developer platform depended on a third-party API whose per-action fees dominated margin, with a small subset of users triggering excessive vendor calls. The redesign introduced caching and batching, aligned pricing to action volume, and added monitoring alerts so customers could see and throttle their own usage. Each one starts from a verdict and ends at a driver-aligned intervention.
Where the calculator usually gets questioned
What is the difference between a unit economics "plan" and a unit economics "audit"? A plan models what you hope will happen. An audit tests whether what is happening (or what could happen under stress) is structurally profitable, and it works in pass/fail constraints rather than narrative projections.
Which metric is the most important audit output? Segmented contribution margin and payback boundary compliance. Together they decide whether scaling is safe and whether you can afford acquisition for each segment.
How do I handle businesses where costs look fixed today but won't be fixed at scale? Treat them as operationally variable in the audit. If headcount or infrastructure must rise as units rise within your planning horizon, model it per unit.
Why does the audit emphasize net revenue instead of list price or GMV? Because you cannot pay bills with gross numbers. Refunds, disputes, partner shares, and fees materially change unit profitability, and leaving them out invites false scaling decisions.
How often should a unit economics audit be run? Keep it lightweight and regular (monthly for fast-moving businesses, quarterly for slower ones) and re-run it after any major change: pricing, new channels, major feature releases, vendor cost changes, or policy changes.
What if our model fails the audit but we still need growth? Then growth has to be redesigned rather than pushed harder. You improve margin, improve retention, reduce variable costs, or constrain acquisition until the unit passes. Scaling a failing unit only multiplies the problem.
Start the audit at the denominator
Every failed audit fails in the same place: the unit was never nailed down, so every number downstream was quietly measuring something different. Before you touch CAC, LTV, or a single scenario, force one unambiguous unit (the thing that carries both revenue and variable cost) and make acquisition, finance, and support all report against it. That one act reconciles arguments that otherwise run for quarters.
From there the sequence is not negotiable: net the revenue, attach the costs that actually grow with volume, walk the margin down, and only then look at cohorts, timing, and shocks. If a segment fails, resist the urge to "optimize": a negative unit does not improve with scale, it compounds. The point of the audit is not a cleaner spreadsheet; it is the discipline to say which growth you have earned the right to fund, and which you have not.