Who pays but uses little AI?
Find accounts with observed revenue and low attributable model cost without assuming that missing usage means zero.
Customer profitability
See which customers create margin and which ones consume it.
Revenue and AI cost only belong in the same row when they refer to the same customer account. Grow or Die makes that link explicit and keeps everything else in an unallocated bucket.
A trustworthy join
Payment identity meets model usage at your account ID.
- Observe who paid. Stripe, Lemon Squeezy, or Polar supplies orders, refunds, and its customer identifier.
- Identify the product account. Your backend links that payment customer to the opaque account ID already used by your product.
- Attribute model usage. Server SDK events carrying the same account ID contribute their priced AI cost.
- Calculate only what is covered. Revenue minus attributable AI cost becomes customer profit; gaps stay visible and are not spread across other customers.
Questions you can answer
Make pricing and product decisions from account evidence.
Who is expensive to serve?
Compare model cost with revenue for accounts whose identity coverage is complete enough to calculate.
Where is profit still unknown?
See unallocated revenue and AI cost separately, then fix the missing account or payment link.
What should change next?
Use the evidence to investigate pricing, usage limits, model choice, caching, retries, or a costly product feature.
No invented allocation
Unknown customer profit should look unknown.
Dividing unlinked cost evenly across customers makes a complete table and a misleading decision. Grow or Die shows coverage beside the result so you can tell a calculated margin from an incomplete one.