Per-unit economics (LTV, CAC, etc.)
Unit economics measures the revenue and cost of a single repeatable unit of a business, usually one customer. It strips away the headline growth numbers and asks whether each customer, on average, makes or loses money once you account for what it cost to acquire and serve them. The discomfort it creates is the point: a business can be growing revenue 200 percent a year and still be unprofitable on every customer it adds, and unit economics is the lens that refuses to let that hide.
The idea is rooted in cost accounting and the older notion of contribution margin per unit, which industrial firms used long before software existed. The startup framing crystallised around two metricsMetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference →: customer acquisition cost (CAC) and customer lifetime value (LTV). The lifetime-value side traces to direct-marketing and database-marketing work in the 1980s and 1990s, where firms began valuing a customer by projected future profit across the whole relationship, not by a single sale.
The pairing became canonical for software through David Skok's SaaS Metrics writing, which set two now-standard rules of thumb: an LTV-to-CAC ratio of roughly 3:1 or better, and a CAC payback period under twelve months. Bill Gurley and other investors reinforced the discipline by warning against vanity growth funded by buying customers who never repay their acquisition cost.
The thinking sharpened again after 2021. As cheap capital tightened, investors returned to unit economics as a screen, and the field grew stricter about what counts: fully loaded CAC including sales salaries, LTV computed on gross margin rather than revenue, and cohortCohortGrowthA group of users sharing a common characteristicView reference →-based retention rather than a single blended churn number. The metric did not change; the tolerance for fudging it did.
A subscriptionSubscriptionSales & RevenueA recurring subscriptionView reference → app charges 20 GBP per month at a 80 percent gross margin, so each customer contributes 16 GBP of margin monthly. Average customer life is 25 months, giving an LTV of 400 GBP. Paid acquisition costs 180 GBP per customer all-in. The ratio is 2.2:1, below the 3:1 bar, and payback takes about eleven months.
That single calculation reframes the roadmapRoadmapProduct SpecificationA strategic plan of features and milestonesView reference →. The team can lift the ratio three ways: raise price, cut churn so customers live longer, or lower acquisition cost. They model a retention featureFeatureProduct SpecificationA product capability or featureView reference → that extends average life from 25 to 32 months. LTV rises to 512 GBP, the ratio crosses 2.8:1, and payback is unchanged. Now the retention work has a financial case, not just a product hunch, and the team can rank it against pure acquisition spend on equal footing.
In the Unified Product Graph, Unit EconomicsBusiness ModelPer-unit economic metrics (CAC, LTV, etc.) is a leaf in the Business, GTM and Growth region, attached to the model by unit_economicsBusiness Modelmeasured byUnit Economicshierarchy. The placement is deliberate: it hangs as a sibling of business_model_measured_by_unit_economicsRevenue StreamBusiness ModelA source of revenueView reference → and revenue_streamCost StructureBusiness ModelA cost category or structureView reference → under the same business modelBusiness ModelBusiness ModelThe business model canvas or definitionView reference →, so the graph holds both the inflow and the cost of inflow in one structure. That lets a query test viability directly, reading the stream that earns and the economics that judge it together, which is the exact pairing that keeps a fast-growing model honest about whether the growth is worth funding.cost_structure
Type-specific fields on BaseNode
lifetime_valuenumberCustomer lifetime value
customer_acquisition_costnumberCustomer acquisition cost
payback_period_monthsnumberMonths to recover CAC from revenue
gross_marginnumberGross margin (0–100)
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
1 edge type connected to this entity.
business_model_measured_by_unit_economics