RevOps Use Case Series (Part 3): Getting to Trustworthy Growth Economics
After reporting and runway, RevOps teams inevitably get pulled into questions about growth efficiency:
“Are we spending efficiently to acquire customers — and are those customers actually worth it?”Customer Acquisition Cost (CAC) and Lifetime Value (LTV) are foundational growth metrics, central to board decks, investor updates, and strategic planning — yet for many RevOps teams, they’re harder to calculate and trust than they should be.This post explains why CAC, churn, ARPU, and LTV are hard to operationalize, where the data actually lives, and how Data Discourse AI (DDAI) makes these metrics trustworthy and actionable.
The Problem: CAC and LTV Depend on Metrics That Don’t Live in One Place
On paper, CAC is simple: total sales and marketing spend divided by the number of new customers acquired in a given period, typically monthly.In reality, the inputs live in different systems. Sales and marketing costs are recorded in QuickBooks. New customers are tracked in HubSpot or Stripe, depending on how the business defines “customer.” Aligning those numbers to the same timeframe and definition usually requires manual work.LTV introduces even more complexity, because it depends on churn and ARPU — two metrics that are rarely cleanly defined in a single system.
Churn: One Concept, Multiple Sources of Truth
Churn sounds straightforward: how many customers leave in a given period. But where that data lives depends on how the business operates.Stripe captures subscription cancellations and downgradesHubSpot may track lifecycle stage changes or closed-lost customersQuickBooks reflects the financial impact, but not always the timing or intentAs a result, RevOps teams often export data from multiple systems just to answer a basic question like:“What was our monthly churn rate?”That churn rate is critical, because it drives average customer lifespan (ACL). If monthly churn is 4%, the average customer lifespan is calculated as 1 ÷ 0.04, or 25 months. Small inaccuracies in churn compound directly into LTV errors.
ARPU: Simple Math, Messy Inputs
Average Revenue Per User (ARPU) is calculated by dividing total revenue by the number of active customers for a given period.Again, the math is simple. The data is not.Revenue lives in Stripe and QuickBooks. Customer counts may live in Stripe, HubSpot, or both — depending on how trials, free users, and expansions are handled. Reconciling revenue and customer counts to the same population and timeframe almost always requires a spreadsheet.As pricing changes, expansion revenue grows, or customer mix shifts, ARPU changes — but spreadsheet models often lag behind reality.
LTV and the Ratio That Actually Matters
Once churn and ARPU are calculated, LTV is derived by multiplying average customer lifespan (ACL) by ARPU.On its own, LTV is useful. But the real signal comes from the LTV to CAC ratio — LTV divided by CAC.As a general benchmark:A ratio above 4 indicates strong unit economicsA ratio around 3 is healthy but worth monitoringA ratio below 1 means the business is losing money on every customerThis ratio determines whether growth is sustainable or simply expensive. Yet many teams only calculate it quarterly — using outdated assumptions — because updating the underlying inputs is so painful.
Why Spreadsheets Become the Default (and the Problem)
Because CAC, churn, ARPU, and LTV span HubSpot, Stripe, and QuickBooks, RevOps teams usually fall back on spreadsheets to reconcile everything.Those spreadsheets quickly become fragile. Definitions drift. Assumptions get hard-coded. Metrics stop updating as the business changes. Leadership loses confidence — not because the concepts are wrong, but because the numbers feel stale.
How DDAI Makes Unit Economics Trustworthy
Data Discourse AI unifies HubSpot, Stripe, and QuickBooks into a single Common Data Model and applies a semantic layer designed specifically for SaaS and RevOps metrics.Instead of rebuilding spreadsheets, RevOps teams can ask questions like:“What was CAC last month?”“What is our current monthly churn and resulting average customer lifespan?”“What is ARPU this quarter, and how has it changed?”“What is our current LTV to CAC ratio — and how is it trending?”Because these answers are grounded in live, cross-system data, the metrics stay current as costs, churn, and revenue change.
From Spreadsheets to Real Unit Economics
With DDAI, CAC, churn, ARPU, and LTV stop being abstract metrics buried in spreadsheets. They become living indicators of growth efficiency that RevOps can monitor, explain, and act on with confidence. Instead of debating the math, leadership can focus on the decision that actually matters: how to grow profitably.
