A revenue screenshot has a wonderful talent: cropping out expenses.
Imagine a hypothetical app collecting $12,000 in a month. Its founder would like $100,000 a year in cash profit before personal tax. The screenshot looks encouraging. The arithmetic is less easily impressed.
Follow one dollar
Start with what the number actually measures. Customer spending, money received by a payment processor, and cash arriving in the business account are different starting points. If your source already deducts a fee, do not deduct it again.
Now write down refunds, payment or platform costs, hosting, paid data, AI usage, email, contractors, support tools and customer acquisition. Include annual bills as monthly amounts. A subscription paid in January still costs something in February.
Here is an illustrative budget, not a forecast:
| Monthly item | Amount |
|---|---|
| Revenue after refunds and payment costs | $11,000 |
| Infrastructure and data | $900 |
| Contractors and software | $600 |
| Customer acquisition | $1,200 |
| Cash profit before personal tax | $8,300 |
Twelve identical months produce $99,600. That is already slightly below the target, before an unexpected refund wave or an expensive migration. The founder’s own labour is not charged in this cash-profit definition; the hours still matter to the person doing them.
Run the ugly month
Change one assumption at a time. What happens if acquisition costs double? What happens if the data provider raises its minimum charge? If the business needs every assumption to behave perfectly, its apparent margin is fragile.
Keep a second column for evidence: invoice, actual cohort, provider quote, or guess. A neat spreadsheet does not promote a guess into a fact.
Before studying another app’s revenue, build this worksheet for your own proposed product. It will tell you which missing number is worth investigating next. Revenue earns your attention. The expense column decides whether it earns your time.