← ClaudeAtlas

unit-economics-checklisted

Checks CAC, LTV and payback for a subscription or app business, finds which input makes the numbers unreliable, and sets a safe CAC ceiling. Use when the user asks "is my CAC okay", "calculate LTV", "payback period", "can we afford to scale", "unit economics check", "ROAS target", or "what CAC can we pay". Works from the user's own data and never from industry averages.
ua5er/user-acquisition-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill ua5er/user-acquisition-skills
# Unit economics check (CAC, LTV, payback) Answers one question: can this business pay for the traffic it is buying, and how much per customer. ## When to use - Before raising paid budget. - When ROAS looks fine but cash is tight, or the reverse. - When a founder quotes an LTV number nobody can explain. - When a new offer, price or plan changes the maths. ## Inputs 1. Spend by channel and period, and the number of paying customers by the same cut (not installs, not trials). 2. Revenue per customer cohort over time: month 0, 1, 2, 3 and so on, net of refunds and store fees. 3. Gross margin items: store or payment fees, refunds, chargebacks, variable costs per user (for example AI generation cost per active user). 4. Subscription mix: plans, trial rules, renewal rates by plan if available. 5. Cash constraints: how long the business can wait for payback. ## Method ### Step 1. Define the customer A customer is a paying user. Write the definition down. Make sure spend and customers use the same definition and the same period, with lag allowed for trials. ### Step 2. CAC CAC = paid acquisition spend / new paying customers from that spend. Report three versions and say which is used for decisions: - Platform CAC (platform-reported payments). - Backend CAC (payments in your own data, attributed). - Blended CAC (all spend / all new payers, including organic). If platform and backend CAC differ a lot, route the user to attribution-sanity-check before trusting either. ### S