The hidden revenue tax of billing platforms
Some billing platforms charge a percentage of revenue instead of a flat fee. Here is the crossover math showing when that costs more than a flat plan, and how to run it with your own numbers.
In short
Some billing platforms price by taking a cut of the revenue you process, not a flat fee. That cut scales with your business, not your platform usage, so it behaves like a tax on growth. The crossover point, where percentage pricing starts costing more than a flat plan, usually lands under $1M ARR.
A 0.5% fee on your revenue sounds like nothing. It is nothing, at $200,000 a year - $1,000. Run the same rate once revenue clears $10M and it is $50,000, more than most teams spend on their entire billing stack combined. That is the part a rate card does not put in the hero section: a percentage of revenue is not a price, it is your own growth rate turned into a bill.
Several billing and subscription-infrastructure vendors, Stripe Billing, Chargebee, Paddle, Orb and Metronome among them, have been reported elsewhere as pricing at least part of what they sell as a cut of the revenue or billing volume that flows through the platform, instead of a flat subscription fee.
This is a real pricing model, not a straw man. Checked against each vendor's own pricing page on 24 September 2026:
| Vendor | What they charge |
|---|---|
| Stripe Billing | 0.7% of billing volume, pay-as-you-go |
| Metronome | 0.8% of billing volume on the Startup plan |
| Chargebee | 0.80% with no platform fee, or $99/mo plus 0.65% |
| Orb | Prices on billings, but publishes no rate - custom pricing |
| Paddle | 5% + 50c per checkout transaction, as merchant of record |
Three of the five publish a rate, and all three land between 0.65% and 0.8%. Orb says outright that it prices on "the total value of all invoices" you issue through it, then puts every tier behind a sales conversation, so the rate exists but the number is not public. Paddle is the odd one out and should be read separately: 5% is high because it is a merchant of record bundling payment processing, tax registration and chargeback liability into one line, which is a genuinely different purchase from a billing platform sitting on top of your own Stripe account.
Rates move without an announcement, so check your vendor's page on the day you run this. The Stripe Billing alternatives post and the Lago alternatives post compare these vendors in more depth, and best usage-based billing tools covers which of them enforce a usage limit rather than only billing for it after the fact. What follows is the shape of the math, with the percentage left as a variable you plug in yourself.
The question
At what revenue level does a straight percentage-of-revenue billing fee start costing more than a flat platform fee, and how fast does the gap grow after that?
The assumptions
- A rate range of 0.25% to 1% of revenue. Wide enough to bracket every published rate in the table above - Stripe Billing's 0.7%, Metronome's 0.8% and Chargebee's 0.65-0.80% all sit inside it - so you can find your own vendor's actual rate and read off the row that applies. It deliberately excludes merchant-of-record pricing like Paddle's 5%, which is buying something else.
- Annual recurring revenue standing in for billing volume. The two are not always identical (refunds and one-time charges move billing volume without moving ARR), but they are close enough for the shape of this argument.
- BuildBase's own numbers from
PLANSinpackages/shared/src/constants/platform-stats.ts, re-read 9 September 2026. Launch is $490 a year, Grow $990, Scale $1,990 - the published annual prices, not monthly times twelve. BuildBase has no free plan, but Launch starts on a 7-day trial that does not require a card. - BuildBase's fee stays flat regardless of revenue processed. The one quota that bills incrementally is storage, at $0.10 per GB beyond the plan allowance - unrelated to how much revenue moves through your connected Stripe account.
The arithmetic
First, the crossover: the ARR at which a percentage fee equals each flat BuildBase plan's annual price. Below this line, percentage pricing is cheaper. Above it, flat pricing is, and stays that way.
| Assumed rate | Crossover vs Launch ($490/yr) | Crossover vs Grow ($990/yr) | Crossover vs Scale ($1,990/yr) |
|---|---|---|---|
| 0.25% | $196,000 | $396,000 | $796,000 |
| 0.50% | $98,000 | $198,000 | $398,000 |
| 0.75% | $65,300 | $132,000 | $265,300 |
| 1.00% | $49,000 | $99,000 | $199,000 |
Second, what the percentage fee actually costs at real revenue levels, against a flat $1,990-a-year Scale plan that does not move:
| ARR | 0.25% | 0.50% | 0.75% | 1.00% | BuildBase Scale (flat) |
|---|---|---|---|---|---|
| $1M | $2,500 | $5,000 | $7,500 | $10,000 | $1,990 |
| $5M | $12,500 | $25,000 | $37,500 | $50,000 | $1,990 |
| $10M | $25,000 | $50,000 | $75,000 | $100,000 | $1,990 |
| $25M | $62,500 | $125,000 | $187,500 | $250,000 | $1,990 |
Even the low end of the range, 0.25%, already costs more than BuildBase's top flat plan at $1M ARR. By $10M, the mid-scenario rate of 0.5% is $50,000 a year against BuildBase's flat $1,990 - a difference of $48,010, and that gap did not come from anything getting more expensive to run. It came from revenue going up.
The total, and what moves it
Read the crossover table honestly and the pattern holds across every plan and every rate in the range. A percentage-of-revenue fee overtakes a flat annual plan somewhere between roughly $49,000 and $796,000 in ARR, depending on the rate and the plan you are comparing against. That is a revenue level a lot of funded or bootstrapped SaaS companies reach well before their platform choices stop being easy to change, which is exactly when this math is worth running.
The one input that actually moves this conclusion is the rate itself, and every published rate we could find today sits between 0.65% and 0.8% - which is to say between the 0.50% and 0.75% rows, near the middle of the band. If your vendor publishes 0.4%, use the 0.50% row as an upper bound and interpolate down. If they publish 1.2%, extrapolate past the 1.00% row - the crossover point only gets closer, not further. The direction of the argument does not change; only how soon you hit it does.
Key takeaway
A percentage-of-revenue billing fee is not a fixed cost. It is a cost that grows every time your revenue does, with no ceiling, while a flat platform fee stays the same number on the invoice whether you process $200,000 or $20 million through it.
Where this math stops applying
Revenue is low or unpredictable. Below the crossover point, a percentage fee is genuinely cheaper, and it carries no fixed cost to pay before you have made any money at all. That is a real advantage for a pre-revenue or early company, not a rounding error.
The percentage is bundled with work that is actually hard. Merchant-of- record vendors take on tax and VAT compliance, chargeback liability and fraud handling as part of that cut - infrastructure a flat-fee platform sitting on top of your own Stripe account does not take on for you. That is a fairness point worth stating plainly rather than waving away: the fee is buying something real in that case, not just a rate card.
Your growth has already plateaued. The whole argument is about a fee that compounds with growth. A mature company with flat or slow-growing revenue does not feel the compounding the way a company doubling every year does - the crossover math still applies, it just stops mattering as much once the denominator stops moving.
Where BuildBase sits in this
BuildBase's billing module does not process payments itself. It runs subscription lifecycle, plan versioning and usage-based metering on top of your own connected Stripe account - you still need a Stripe account, and you still pay Stripe's own processing fees on top, separately.
What BuildBase itself charges is whichever flat plan you are on: Launch, Grow or Scale, with no percentage layered over your revenue at any point, ever. The only thing that changes your bill is which plan tier your MAU, workspace count or storage needs land in, not how much money moves through your Stripe account that month.
PlugNode runs its own credit-based billing on this same module in production, alongside BuildBase auth and team workspaces - one of the products this platform is dogfooded on before it ships to anyone else. The module is also what charging per API call in Next.js is built on, if you want to see the metering-to-Stripe path this post's numbers assume.
None of that makes a percentage-of-revenue vendor wrong to choose. It makes the choice worth running through the crossover math above with your actual numbers, rather than deciding on the headline rate alone. Building the metering and subscription logic yourself instead of buying either shape of vendor sidesteps the percentage too, but it carries its own real cost, not a free one.