惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

U
Unit 42
罗磊的独立博客
T
Tailwind CSS Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Jina AI
Jina AI
V
V2EX
美团技术团队
阮一峰的网络日志
阮一峰的网络日志
酷 壳 – CoolShell
酷 壳 – CoolShell
月光博客
月光博客
量子位
MyScale Blog
MyScale Blog
G
Google Developers Blog
M
MIT News - Artificial intelligence
L
LangChain Blog
Microsoft Azure Blog
Microsoft Azure Blog
Recent Announcements
Recent Announcements
MongoDB | Blog
MongoDB | Blog
N
Netflix TechBlog - Medium
有赞技术团队
有赞技术团队
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
D
DataBreaches.Net
云风的 BLOG
云风的 BLOG
B
Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
LTV (Customer Lifetime Value) Calculation. 5 Common Metho...
toshihiro sh · 2026-05-09 · via DEV Community

"My executive team wants LTV in our monthly report. But there are like four different formulas online — how do I pick the right one?"

This is one of the most common questions we hear from EC operators. LTV (Customer Lifetime Value) is widely used as a metric, but at least five common calculation methods exist. Pick the wrong one, and your business decisions rest on a shaky foundation.

TL;DR

  • There are five common LTV calculation methods: Simple, Gross Margin, Cohort, LTV/CAC, and DCF. Choose by business stage and product
  • LTV alone cannot drive investment decisions. View it together with CAC, with LTV/CAC = 3:1 as a baseline
  • The three prerequisite metrics are AOV, RPS, and purchase frequency. Without stable measurement of these, LTV figures lack foundation

Why "five methods" matters

LTV looks deceptively simple. The textbook formula is:

LTV = AOV × Purchase Frequency × Customer Lifespan

Enter fullscreen mode Exit fullscreen mode

But ask any operator running a real Shopify store, and you'll get a different number depending on what they include — gross margin, cohort retention, CAC, future cash flow discount. These produce different LTVs by 2-3x for the same business. The question is not "which formula is correct" but "which formula fits this stage of the business."

The five methods at a glance

5 LTV Calculation Methods Comparison

1. Simple LTV — early-stage EC

LTV = AOV × Purchase Frequency × Customer Lifespan

Enter fullscreen mode Exit fullscreen mode

The simplest formula, also presented in Shopify's official documentation. AOV ¥5,000 × 3 orders/year × 2 years = LTV ¥30,000. Sufficient when gross margin and customer ID linkage aren't yet structured. Note: revenue-based, so margin differences are not reflected.

2. Gross Margin LTV — scale-up EC

LTV = (AOV × Gross Margin) × Orders × Years

Enter fullscreen mode Exit fullscreen mode

Once you start serious ad investment, profit-based LTV is essential. Otherwise you hit the "LTV looks fine but no profit" trap. With 30% gross margin: ¥9,000 gross-margin LTV. Translation: keep CAC under ¥9,000.

3. Cohort LTV — repeat-rate driven

LTV = Cohort cumulative revenue ÷ Cohort customers

Enter fullscreen mode Exit fullscreen mode

Highest accuracy because it's based on observed values. Customer ID linkage is mandatory. Bain & Company has long noted that retention improvements have outsized impact on profit, and cohort-level visibility directly drives continuous improvement.

4. LTV/CAC ratio — investment decision

LTV/CAC = LTV ÷ CAC (baseline: 3:1)

Enter fullscreen mode Exit fullscreen mode

Strictly speaking, this is not a formula for calculating LTV — it's an investment-decision lens using the LTV/CAC ratio. The four formulas for LTV calculation proper are 1, 2, 3, and 5 here.

The "LTV/CAC = 3:1" baseline widely used in SaaS also applies to EC. Below 1 = unprofitable acquisition, above 3 = room to scale spending. The appropriate ratio varies by industry and product, so use your own channel-level actuals.

5. DCF LTV — high-AOV / subscription EC

LTV = Σ(Annual CF / (1 + r)^n)

Enter fullscreen mode Exit fullscreen mode

Discounts future cash flows to present value. Used for subscription EC and high-AOV products in 3-5-year investment decisions. Discount rate (typically 5-10%) heavily influences output, so document your assumptions explicitly.

The three-tier framework — AOV → RPS → LTV

All five methods share a common assumption: that AOV and purchase frequency are already being measured stably. Without that foundation, LTV figures lack reliability.

AOV → RPS → LTV three-tier framework

The three prerequisite metrics:

Metric Unit Role Relationship to LTV
AOV per order Order efficiency Starting point of LTV formula
RPS per session Revenue per visit Acquisition efficiency that creates LTV
CAC per customer Acquisition cost Denominator of LTV/CAC ratio

In practice: build a state where AOV and RPS are measured monthly with stability, then compute LTV quarterly. There's no need to view LTV daily — but AOV and RPS should be visible every day.

LTV/CAC investment decision zones

LTV/CAC ratio State Recommended action
Below 1 New acquisition is loss-making Pause ads, or improve product first
1-2 Recoverable but thin margin Decompose by channel, cut high-CAC channels
2-3 Healthy range Maintain + improve AOV/CVR to lift the ratio
Above 3 Room to scale spending Increase ad budget, open new channels

Critical caveat: this baseline must be viewed at channel and cohort level. Even if total LTV/CAC = 3, if Paid sits at 0.8 and Organic at 5.0, the right call is to pause Paid acquisition. Averages mislead.

Four common measurement pitfalls

Pitfall What happens Treatment
One-time customers Single-purchase customers drag down the average Split "first purchase only" vs "repeat"
Fixed measurement period Fixing lifespan to 3 years undervalues new customers Use observed lifespan months by cohort
Pre/post discount mixing Heavy coupon usage inflates AOV Match AOV practice — use post-discount
Channel allocation Mixing ad-acquired with Organic customers Split cohorts by initial-touch channel

Operating LTV alongside its prerequisite metrics

The summary:

  • LTV has five common calculation methods. Choose by business stage and product
  • LTV alone does not enable investment decisions. Use LTV/CAC = 3:1 as the baseline
  • The three prerequisite metrics are AOV / RPS / Purchase Frequency
  • Realistic operation: LTV quarterly, AOV and RPS visible daily
  • Decompose LTV/CAC by channel and cohort — averages mislead

I'm building RevenueScope, a tool that automatically expands the prerequisite metrics — AOV, RPS, CVR — by channel and device on the dashboard. It doesn't compute LTV directly, but it's designed to surface "the data foundation underneath LTV" — the kind of view that's missing when teams jump straight to LTV reporting.

Discussion

What LTV formula does your team currently use, and what tripped you up the first time? Curious to hear from other operators — especially the "looked good in the spreadsheet but didn't survive contact with reality" stories.