Chapter 04 — Revenue & Unit Economics
Chapter 04 — Revenue & Unit Economics
"Revenue is vanity, profit is sanity, unit economics is reality."
Knowing total revenue tells you almost nothing about whether a business works. This chapter explains how revenue should be recorded, and then builds the toolkit that answers the real question: does each unit of business — each customer, each service, each transaction — create more value than it costs?
4.1 Revenue Recognition — When Is Revenue "Earned"?
Principle: Revenue is recognized when the service is delivered, not when cash is collected. (This mirrors the accrual logic of Chapter 02.)
Worked Example
A customer pays $1,200 on January 1 for a 12-month subscription.
Cash received Jan 1: $1,200
Revenue recognized in January: $100
Deferred revenue (a liability!): $1,100
Each subsequent month: +$100 revenue, −$100 deferred revenue
That $1,100 of deferred revenue is a liability — you owe the customer 11 more months of service. If the company shut down in February, that money would (legally and morally) need refunding.
Key takeaway: A pile of annual-plan cash is not profit; it's an obligation being worked off month by month.
4.2 Granularity — Attach Revenue to the Right Object
Revenue recorded only at the company level answers no operational questions. Best practice is to attach each revenue event to the most granular unit that earned it — ideally a service, not just a project or the company as a whole.
Why it matters — worked example:
Project "Streaming Platform" revenue: $80,000/month ← looks healthy
Broken down by service:
Video CDN service revenue $60,000 COGS $18,000 margin 70% ✅
Live transcoding revenue $15,000 COGS $13,500 margin 10% ⚠️
Archival storage revenue $5,000 COGS $7,200 margin −44% ❌
The project-level view hides a service that loses money on every sale. Only service-level revenue attribution exposes it.
4.3 Gross Margin (Recap from Chapter 01)
Gross Profit = Revenue − COGS
Gross Margin % = Gross Profit ÷ Revenue
Gross margin is the ceiling on everything else: marketing, R&D, and profit must all fit inside it.
4.4 Unit Economics
Definition: Revenue and cost expressed per unit — per customer, per order, per API call, per GB streamed. Unit economics answers: "If we add one more unit of business, do we gain or lose money?"
Worked Example — Per-Customer Economics
A SaaS service has:
Monthly revenue per customer (ARPU) $40.00
Variable cost to serve one customer:
Cloud compute & storage $6.20
Payment processing (2.9%+30¢) $1.46
Support cost (allocated) $3.00
------
COGS per customer $10.66
Contribution per customer = $40.00 − $10.66 = $29.34
Contribution margin = 73.4%
Every new customer adds $29.34/month toward covering fixed costs (payroll, rent, R&D) and, eventually, profit.
Break-Even from Unit Economics
Fixed monthly costs = $45,000
Break-even customers = $45,000 ÷ $29.34 ≈ 1,534 customers
4.5 CAC — Customer Acquisition Cost
Definition: The total sales & marketing cost required to win one new customer.
CAC = Total S&M spend in period ÷ New customers acquired in period
Worked Example
In Q2 you spend:
Paid ads $36,000
Content & SEO agency $9,000
Sales salaries (2 ppl) $30,000
-------
Total S&M $75,000
New customers in Q2: 500
CAC = $75,000 ÷ 500 = $150 per customer
Pitfall: Counting only ad spend ("$36,000 ÷ 500 = $72") flatters CAC by half. Include people costs.
4.6 LTV — Customer Lifetime Value
Definition: The total contribution profit a customer generates before churning.
Average lifetime (months) = 1 ÷ monthly churn rate
LTV = Contribution per customer per month × Average lifetime
Worked Example
Monthly churn = 2.5%
Average lifetime = 1 ÷ 0.025 = 40 months
Contribution per customer = $29.34/month (from §4.4)
LTV = $29.34 × 40 = $1,173.60
4.7 LTV : CAC — The Verdict Metric
LTV : CAC = $1,173.60 ÷ $150 = 7.8 : 1
Interpretation guide:
| Ratio | Reading |
|---|---|
| < 1 | Every customer destroys value. Stop. |
| 1–3 | Marginal; growth burns cash with little payoff |
| ~3 | The classic healthy benchmark |
| > 5 | Excellent — possibly under-investing in growth |
Payback Period — The Cash Companion
LTV:CAC can look great while cash runs out. Check how fast acquisition spend returns:
CAC payback = CAC ÷ Contribution per month
= $150 ÷ $29.34 ≈ 5.1 months
Under 12 months is generally considered healthy for SaaS; under 6 is excellent.
4.8 The Full Funnel in One Table
Metric Value Source
─────────────────────────────────────────────────────────────
ARPU $40.00 billing data
COGS per customer $10.66 cost items / usage
Contribution per customer $29.34 derived
Monthly churn 2.5% subscription events
LTV $1,173.60 derived
CAC $150.00 marketing + sales costs
LTV : CAC 7.8:1 derived
CAC payback 5.1 months derived
Notice that every derived number depends on accurate cost capture — which is why Chapters 01–03 come first. Garbage cost data in, fictional unit economics out.
4.9 In Practice — TupicFinance
TupicFinance records each revenue event against a specific service, not merely a project — a deliberate modeling decision that makes the per-service margin analysis of §4.2 possible out of the box. Marketing campaigns are tracked with their full cost (including the Pay Now / Pay Later flows of Chapter 02) and feed the CAC dashboard, while customer and usage figures arrive through the Usage Metrics pipeline rather than manual campaign fields — keeping spend data and outcome data in separate, auditable streams. The result is that the entire table in §4.8 can be assembled from live data per service, per project, across the Tupic ecosystem.