# Chargebee vs BuildBase: what 0.80% of your invoices buys

> Chargebee's Flow plan charges a percentage of what you invoice. Here is the arithmetic behind its own $66K breakeven marker, what the percentage actually buys, and where BuildBase fits instead.

- Source: https://www.buildbase.app/compare/chargebee-vs-buildbase
- Section: Comparisons
- Author: Dharmendra Jagodana
- Published: 2026-11-08

## In short

Chargebee's Flow plan is priced two ways against monthly invoicing volume: $0 plus 0.80%, or $99 plus 0.65%. Both cost $528 a month at $66,000 invoiced, which is where its breakeven marker sits. BuildBase charges a flat plan price, takes no share of your revenue, and makes billing one of 20 modules on your own Stripe.

Chargebee's pricing page shows two prices for the same plan: $0 plus 0.80% of
monthly invoicing volume, or $99 plus 0.65%. Between them sits a marker reading
$66K breakeven.

That marker is exact, and you can check it in one line. 0.80% of $66,000 is
$528. So is $99 plus 0.65% of $66,000, because $429 plus $99 is $528.

What nobody writing about Chargebee seems to say out loud is what that makes
the $99.

## The one-paragraph answer

Chargebee is a subscription billing platform priced on a share of what you
invoice, and the share buys depth: 40+ payment gateways, a dunning schedule you
configure, and a separately sold revenue recognition product that feeds
NetSuite and Xero. BuildBase is an SDK where billing is one of 20 modules,
beside authentication, workspaces and role permissions, running on your own
Stripe account for a flat plan price. Pick Chargebee when billing
across many countries and gateways is your hardest problem. Pick BuildBase when
billing is the fourth system you have not built yet and Stripe is already your
processor. The percentage is not the deciding factor. What it buys is.

## The $99 is a prepaid discount

Read the two configurations as one offer and the structure falls out. The
second one does not add a platform fee. It sells you a 0.15 percentage point
discount for $99 a month, and 0.15% of $66,000 is $99. That is the whole
reason the breakeven sits there.

So the choice at signup is a forecast of your own invoicing volume. Under
$66,000 a month the $99 costs more than the discount gives back; over it, the
discount keeps compounding while the $99 stays flat and your invoicing does
not. At $500,000 a month, which is where Chargebee's own slider stops, the
discounted configuration comes to $99 plus $3,250, or $3,349. The undiscounted
one would be $4,000. The $99 is now returning $651 a month.

Nothing is wrong with that. It is a volume discount wearing a platform fee's
clothes, and pricing it as a fee rather than a tier is clearer than most rate
cards manage. But it does mean the honest question at signup is not
"which plan am I on", it is "what will I be invoicing in a year", and that is a
question founders get wrong in both directions.

## What the percentage costs once you are growing

At $66,000 a month invoiced, which is $792,000 a year, Chargebee Flow costs
$528 a month either way. Push that to the slider's $500,000 ceiling and the
cheaper configuration is $3,349 a month, or $40,188 a year. Past $500,000 the
page simply stops, Enterprise takes over, and Enterprise carries no public
price, so neither will this post.

Scale, our top self-serve plan, is $99 a month. Billed yearly it is $990, and neither
number moves when your revenue does. At $66,000 of monthly invoicing,
Chargebee's $528 is more than five Scale plans; at $500,000, the gap is $40,188
against $990 for the year.

That comparison is also unfair in a specific way, and the unfairness is the
point of the next two sections: those two products are not doing the same
amount of work. A percentage of revenue is a defensible way to price something
whose value genuinely tracks your revenue. Whether yours does is the thing to
work out before you sign either contract. We wrote the general version of this
arithmetic in [the hidden revenue tax of billing
platforms](/blog/billing-platform-revenue-tax), including how to find your own
crossover against any vendor's published rate.

## About that free tier you have read about

Several roundups still describe a free Chargebee Starter tier below a
cumulative billing threshold. Chargebee's Billing pricing shows no such tier
today, only Flow and Enterprise, and a third-party pricing tracker,
usagepricing.com, dates the consolidation to August 2026.

We could not confirm that change, or its date, on any Chargebee page we could
load, so treat it as reported rather than official.

What is verifiable
today is the simpler half. There is no free billing tier on the page, so the
percentage applies from the first invoice, and any roundup telling you
otherwise is pricing a plan that is no longer on sale.

## Where BuildBase charges differently

BuildBase charges a flat plan price and takes no share of your revenue. Free at
$0, then Launch at $19, Grow at $49 and Scale at $99 a month, with a seven-day
trial on the paid plans and no card to start one. Yearly is ten months for
twelve. Those were current on 31 October 2026 and the live ones are always at
[/pricing](/pricing).

We do meter three things and bill overage on them: workflow runs at $0.25,
$0.15 and $0.10 per 1,000 on Launch, Grow and Scale, web analytics events at $2
per 100,000, and storage at $0.10 per GB-month. Every other quota is a hard
allowance that stops rather than bills. Stripe's own fees are Stripe's, charged
to [your own Stripe account](/blog/bring-your-own-stripe), and nothing sits in
between taking a cut.

What the billing module does is narrower than Chargebee's product and wider
than a Stripe wrapper. Subscription plans with versioning, free trials that
convert automatically, usage-based and seat-based pricing in flat, graduated or
volume tiers. Add-ons come as recurring, one-time, lifetime or consumable. Then
promotion codes and Stripe Tax at checkout, a credit ledger, overage reported
to Stripe Billing Meters, and multi-currency with per-plan pricing variants
across 21 currencies.

Plans can be paid by a workspace or by a person, with one payer covering
several workspaces. Entitlements are checked by feature rather than by plan
name, which is the same shape Chargebee uses and not a differentiator either
way.

| Feature | BuildBase | Chargebee |
| --- | --- | --- |
| Published price | Free $0, then $19, $49 and $99 a month, flat; our own Enterprise tier is priced by conversation | Flow shown as $0 + 0.80% or $99 + 0.65% of monthly invoicing; Enterprise by demo |
| How the bill grows | It does not grow with revenue; overage only on workflow runs, analytics events and storage | Scales with what you invoice, from the first invoice |
| Payment gateways | Stripe only, on your own Stripe account | 40+ gateways, 50+ payment methods, 100+ currencies, 150+ countries |
| Dunning and failed payments | Not built: a Slack alert on failed payments, and whatever Stripe retries underneath | Up to 4 retry attempts, intervals you set up to 45 days, and a chosen final action |
| Revenue recognition and accounting | Not built: an MRR and churn screen, no recognition, no ERP sync | RevRec sold separately, with NetSuite, Sage Intacct, Xero, QuickBooks Online and DATEV |
| Usage events included | Per-plan limits on any metric you define, reported to Stripe Billing Meters | 100M usage events a month on Flow |
| Auth, workspaces and roles | 16 sign-in methods (Enterprise SSO through your own WorkOS account, on the Enterprise plan), multi-tenant workspaces and role permissions in the same instance | Out of scope: Chargebee is a billing and revenue product |

## Where Chargebee wins

> **Where Chargebee wins:** Three things, and the first one is not close.
>
> **Getting paid outside Stripe.** Chargebee's gateways page lists 40+ gateways,
> 50+ payment methods, 100+ currencies and 150+ countries, naming Adyen,
> Braintree, GoCardless, Razorpay, Worldpay, Mollie and more. BuildBase is Stripe
> and only Stripe. If you need SEPA direct debit through GoCardless, cards
> through Razorpay in India, or the ability to switch processor without
> re-platforming, we are the wrong answer and no module count changes that.
>
> **Dunning you can configure.** Chargebee's docs set out a retry schedule of up
> to four attempts with intervals you choose up to 45 days, a final action you
> pick when the retries run out, and a follow-up email sequence with merge fields
> for the attempt count and the card update link. BuildBase ships none of that.
> Our own constants list exactly one thing: a Slack alert on failed payments.
> Stripe does its own retries underneath us, which is not the same as a recovery
> sequence you control, and we should not pretend otherwise.
>
> **The finance stack.** Chargebee sells RevRec as a separate product and
> integrates with NetSuite, Sage Intacct, Xero, QuickBooks Online and DATEV.
> BuildBase has a revenue screen showing monthly recurring revenue, churn, trial
> conversion and cash per currency. That is a dashboard, not revenue recognition,
> and the difference matters to exactly one person: the controller who needs
> deferred revenue schedules feeding an ERP. We do not serve them.
>
> A fourth, if you are closer to the enterprise end: Chargebee Billing Enterprise
> adds multi-entity management and account hierarchy. We have workspaces, which
> are not legal entities.

## So which problem do you have

Ask which system breaks first, not which rate card is lower.

If you sell in fifteen countries through four gateways, and a failed card in
Brazil is a recoverable revenue event rather than a support ticket, you want a
billing platform and Chargebee is a serious one. The percentage is buying a
gateway network and a recovery engine, and both are real. Go and price it
properly against [Stripe Billing](/compare/stripe-billing-vs-buildbase) and the
rest of the field in [Stripe Billing
alternatives](/compare/stripe-billing-alternatives).

If the honest description is "we charge a few hundred companies for seats and a
plan tier on Stripe, and we also need login, and workspaces, and a way to say
who can see what", then a percentage of invoicing is buying you a gateway
network you will not connect and a dunning sequence you will not configure.
[Metered and seat-based billing are different
businesses](/blog/metered-vs-seat-based-billing), and the multi-vendor version
of the second one is costed in [the real monthly cost of Clerk plus Stripe plus
Lago plus Knock](/blog/auth-billing-stack-cost).

We know the second shape because it is ours. PlugNode runs usage-based credit
metering on this billing module, and BuildBase meters its own workflow runs
through it, which is why the overage rates above exist at all. The thing that
made that work was never gateway coverage. It was that the meter already knew
which workspace a run belonged to and whether the caller's role was allowed to
start it. Bolt a billing platform on from outside and those two questions are
yours to answer in glue code, for every product you ship. That is the trade, and
the concessions above are not a courtesy.

A note on sourcing. Chargebee's Flow configurations ($0 plus 0.80% and $99 plus
0.65%), the $66K breakeven marker, the $500K slider maximum, the 100M usage
events and the Flow and Enterprise tiering were read on chargebee.com on 8
November 2026. The dunning behaviour is chargebee.com/docs the same day, the
gateway, payment method, currency and country counts its gateways page, and the
accounting integrations its integrations page. Chargebee's Enterprise tier and
its CPQ, RevRec and Growth products carry no public price, so this post quotes
none. Every calculation
above is ours, worked from Chargebee's published figures and shown so you can
check it. Our plan prices and overage rates come from the shared constants this
site builds from, verified 31 October 2026, and the live ones are always at
[/pricing](/pricing).
