The bottom line
You can estimate a day 365 LTV from just 30 days of cohorted revenue by fitting a power trend line in a spreadsheet and extending it. This lets you set early payback targets for day 7 buying decisions.
Key takeaways
- Revenue per user for days 1 to 30 is enough raw material. 2:23
- This cohorted revenue is usually available in your MMP, best split by channel, and it can also be split by geo.
- LTV is tied to a time frame such as day 60, 180 or 365. The same approach works for each, with no databases or programming.
- A power trend line fitted to that curve describes its shape. 6:32
- In Google Sheets, chart cumulative ARPU by day, add a trend line, choose power series and show the equation.
- The organic traffic fit is about 0.323 × x^0.395.
- Plugging the equation into days up to 365 projects the long-term LTV. 7:36
- Organic ARPU of $1.22 at day 30 grows to about $3.32 at day 365.
- The fitted curve gives $1.25 at day 30, a small jump from the real $1.22.
- Dividing early LTVs by the day 365 LTV shows how much cost to recover by each day. 9:52
- To break even by day 365, recover about 21% by day 7, 36% by day 30, 57% by day 90 and 75% by day 180.
- This matters because much acquisition is judged on a day 7 basis.
- The method fits a single revenue stream only. 10:42
- Mixing in-app purchases with ad revenue needs a different approach.
- If day-by-day ad revenue is available, the same method works for it too.
The goal here is to take a limited amount of data, perhaps day 30 data or even day seven, and extrapolate it to get your day 365 LTVs without requiring elaborate databases, without requiring any programming, and with just the help of a spreadsheet.
Shamauf Rao, RocketShip HQ
Chapter summaries
0:00 Why LTV needs a time frame
A lifetime of data never exists, so LTV has to be a forecast to a fixed horizon.
- LTV can only be forecast to a fixed horizon, never measured over a lifetime. 1:12
- Waiting for a user's full lifetime of data is impossible.
- The model here targets day 365.
- What LTV means depends on the app, so the definition comes first.
- Most of the apps this method was used on tie LTV to a set time frame.
2:18 Starting from the cohorted revenue export
The raw input is cohort revenue after each day, and the task is to turn it into a day 365 estimate.
- Keep the input simple with one revenue stream. 2:32
- The example uses in-app purchase revenue only.
- The export lists revenue after day 1, day 2, day 3 and so on up to day 30.
- The MMP shows every day from 1 to 30 readily.
- The problem to solve: convert this export into day 365 LTV estimates.
- Turn the export into revenue per user for each day, then chart it. 3:56
- The work is done in Google Sheets, and Excel works just as well.
- Only AppLovin and organic are compared, to keep it simple.
- The sheet gets columns for day 1 to day 30, with day 7 and day 30 as checkpoints.
- A line chart of the days shows the shape of the curve, which is the basis for extending past day 30.
5:58 Fit the curve and extend it
A fitted trend line turns 30 days of real data into a curve you can read at any later day.
- The curve can be read at any target day, not only day 365. 6:00
- Day 60, 180 or 365 all come from the same curve.
- Day 30 is the last real point, and the curve's shape decides where it goes next.
- The trend line is added to the organic-by-day chart. Line thickness is cosmetic and doesn't matter.
- Under label, pick "use equation" and the sheet prints the power curve's formula on the chart.
- The equation is typed into a table of days to extend it. 7:04
- The first day is extended down to day 365.
- Each cell takes the coefficient times the day number raised to the fitted exponent.
- The result is a smoother, continuous extrapolated curve running from day 30 to day 365.
- This run covers organic traffic only.
8:27 Turn LTV into payback targets
A table of LTV by day shows how much of the final value a day 7 buyer must already have earned.
- Day 7 ARPU is the number most buying decisions use. 8:36
- Organic day 7 ARPU is $0.71.
- Most acquisition activity is judged on a day 7 calculus, so this is the figure to compare against.
- LTV is listed for days 7, 30, 60, 90, 180 and 365. 8:58
- Day 60 is $1.63, day 90 is $1.91, day 180 is $2.51.
- Day 365 reads $3.32 in the sheet.
- Day 60 is about 49% of day 365 by these figures.
- Each early LTV divided by day 365 LTV gives the payback target. 9:52
- The assumption is a goal of recovering 100% of costs by day 365.
- Any other goal, such as a different recovery window, can be set the same way.
In the growth library
Shamanth Rao, Founder of RocketShip HQ, a paid user acquisition agency for apps. Shows how to estimate a day 365 lifetime value from only 7 to 30 days of cohorted revenue, using a spreadsheet and a power-curve trendline. The worked example turns an organic day 30 ARPU of 1.22 into a day 365 estimate of about 3.32, which gives concrete payback targets for paid acquisition.
More from
App Masters · The whole library, and ask it anything