What $1,000 MRR leaves after the AI app pays its bills
Fifty customers paying $20 each bring in $1,000 a month, which feels great until you ask what their actual usage leaves for the rest of the bills. In this example, $795 is left after $205 of selected operating costs, before founder time, tax and other expenses. Every figure here is an assumption, so swap in your own as you go.
Start with customers and their actual usage
Let's start simple: 50 paying customers at $20 per month gives 50 × $20 = $1,000 MRR. Say each customer uses 1,000 successful AI jobs per month, and the complete billable cost averages $0.002 per successful job, paid retries included. That makes the model-work line 50 × 1,000 × $0.002 = $100.
A quick note on that $0.002: it's a scenario assumption, not a provider tariff. Measure it from your own model, request lengths and failure rate. The practical catch is that if a long request costs ten times more than a short one, an average from five easy examples won't protect a flat-price subscription from a heavy user.
| Monthly scenario | Calculation | Amount |
|---|---|---|
| Revenue | 50 customers × $20 | $1,000 |
| Model work | 50 × 1,000 successful jobs × $0.002 | $100 |
| Payment fees | Assumed 3% of revenue + $0.30 for each of 50 charges | $45 |
| Shared fixed costs | Assumed builder, hosting and other fixed payments | $60 |
| Selected operating costs | $100 + $45 + $60 | $205 |
| Remainder before omitted costs | $1,000 − $205 | $795 |
Payment fees vary by country, payment method, card origin and the billing products you use. The 3% plus $0.30 line is an illustrative combined input, so replace it with your processor's actual quote, including any separate subscription-billing charges. And please don't show it to a customer or investor as a universal Stripe rate. Someone will ask where it came from.
The break-even calculation
With these inputs, each customer contributes $20 − $2 of model work − $0.90 in payment fees = $17.10 toward the $60 fixed cost. The break-even count is $60 ÷ $17.10 = 3.51, which rounds up to four paying customers. That's the operating break-even for these selected costs. It's a nice milestone, but it isn't proof that the business can support a salary.
Real life adds more: customer support, refunds, email, monitoring, storage, contractors and acquisition spending, wherever they apply. If you assign ten hours of founder work a planning value of $20 per hour, another $200 of labour value brings the example's remainder down from $795 to $595. Just keep that allocation separate from cash you actually pay out, so your books stay honest.
What happens when usage doubles?
At 2,000 jobs per customer, the model line becomes $200 and the selected remainder falls to $695. At 5,000 jobs, it becomes $500 and leaves $395 before omitted costs. Revenue didn't move at all. A flat monthly subscription needs either a workload limit or a pricing model that can survive the upper end of customer usage.
A few things that help:
- Define a useful included allowance in customer terms, such as completed documents or minutes.
- Map that allowance to billable model work, including paid retries.
- Choose how you handle expensive inputs and repeated failures.
- Set account and application spending controls before opening public access.
- Review cost per successful job and heavy-user behaviour after launch.
Check the expensive customer before setting a flat price
In the starting example, one customer moving from 1,000 to 10,000 successful jobs adds 9,000 × $0.002 = $18 of model cost. If the other forty-nine customers stay at the original allowance, the selected remainder falls from $795 to $777. That one customer's extra work costs more than the original $17.10 contribution from an ordinary account.
Now imagine all fifty customers reach 10,000 jobs. Model work alone costs $1,000, and the same $45 payment assumption and $60 fixed cost leave a $105 operating loss. Each added customer then contributes $20 − $20 − $0.90 = −$0.90 before fixed costs. Sadly, more customers can't fix a negative contribution; the price, workload allowance or production cost has to change.
One easy trap to avoid: the $0.002 input already includes paid retries per successful job, so don't apply another retry multiplier to that same measured rate. If you start from a price per attempt instead, calculate total paid attempt spending divided by accepted jobs, failed attempts included, then use that complete rate in the worksheet.
Replace the payment assumption with your actual route
For a separate US domestic-card example checked 3 November 2026, Stripe lists 2.9% plus $0.30 per successful payment. Fifty $20 payments would cost $44 for Payments. If the full $1,000 also uses Stripe Billing's 0.7% pay-as-you-go service, add $7, giving $51 in combined fees. With the same $100 model budget and $60 fixed costs, the remainder becomes $789.
What to keep in mind: that alternative only holds if those products and rates apply to your account. Other countries, international cards, conversion, contracts, taxes and additional services can change the charge. The worksheet deliberately keeps its original illustrative $0.90 per payment. For this combined-fee example, swap that input to $1.02 rather than treating the original three-percent input as a universal tariff.
Where a Lovable-built app fits
Lovable's credits can pay for building, hosting and app AI features, depending on the plan and grants. It's worth tracking which part of the balance funds customer activity. An included development grant isn't a permanent promise that every future customer request is free. And if the app calls an external provider with your own key, count that separate bill too.
The builder comparison can help you split launch spending from ongoing operation. A launch month may include a big block of development work that you shouldn't blindly repeat as the same monthly cost forever. The opposite mistake is just as common: treating ongoing fixes as a one-time expense that never comes back.
Use the worksheet as the cost side of the decision
The worksheet below starts with the $205 operating-cost example. Customer count and jobs per customer drive the model line. Payment fees are a separate count of monthly charges, initially 50, so update that field whenever the customer count changes. It calculates costs, and the linked break-even calculator lets you compare them with revenue.
Keep the actual cash statement next to the unit model. Credits purchased, credits consumed and recognised revenue are different quantities. A product can look comfortable in an average-per-job spreadsheet while a renewal or a large prepaid balance quietly squeezes the bank account, so it's worth checking both views.
Recalculate the operating-cost side
Defaults are illustrative assumptions, not provider quotes. The job rate already includes paid retries, so the attempt factor is fixed at one. Payment-charge count is independent of customer count: update both when needed. Revenue, founder time and taxes are outside this cost subtotal.
Calculate break-even for your own app →