Usage-Based Pricing for Bootstrapped SaaS: A Solo Founder's Guide
Pure pay-as-you-go is risky for a solo founder: revenue swings and customers fear surprise bills. The pattern most public pricing pages use is a hybrid: a monthly base fee, a generous included allowance of one value metric, a clear overage rate and a spend cap. This guide shows how to choose the metric, build the table, protect both sides and bill it with Stripe, Lemon Squeezy, Paddle, Polar, Orb, Metronome or Lago.
Key takeaways
- Usage-based pricing fits when your costs and your customers' value both grow with one countable thing (emails, pages, API calls, pageviews). If value comes from people logging in, seats or flat tiers are simpler.
- Pick one value metric. Postmark charges by emails, Plausible by monthly pageviews, Supabase Pro by monthly active users and storage, and AI APIs by tokens.
- Most public pricing pages use a hybrid: base fee plus included usage plus overage. Resend Pro is $20/mo for 50,000 emails, then $0.90 per 1,000.
- Protect customers with spend caps and alerts (Supabase turns caps on by default on Pro; Vercel gives new teams a $200 default on-demand budget) and protect yourself with a minimum monthly fee.
- Billing tools differ a lot: Stripe Billing is 0.7% of billing volume and now recommends Metronome for new usage integrations, Lemon Squeezy bills usage at renewal for 5% + 50¢, and Paddle's usage billing is still an early-access beta that does not bill overage.
On this page 19
- TL;DR
- When usage-based pricing fits (and when it does not)
- How to pick one value metric
- The hybrid: base fee, included usage, overage
- Protecting customers and protecting yourself
- Protect customers: caps, alerts, visibility
- Protect yourself: minimums and margins
- Billing tools: what each one costs and does
- Worked example: a pricing table for a document-parsing API
- Launch checklist
- Mistakes to avoid
- Frequently asked questions
- Is usage-based pricing a good idea for a bootstrapped SaaS?
- How do I choose a value metric?
- What is the cheapest way to bill usage as a solo founder?
- How do I stop customers getting a surprise bill?
- Does Paddle support usage-based billing?
- Launch your pricing
- Sources
Short answer: Use usage-based pricing when your costs and your customers' value both grow with one countable thing, such as emails sent, pages processed or API calls. As a solo founder, do not launch pure pay-as-you-go. Charge a base monthly fee with a generous included allowance, a clear overage rate and a spend cap that is on by default.
Every price and limit below comes from the vendor's own page, checked on 7 Nov 2026. The pricing table in the worked example is hypothetical, and the advice in between is ours and marked as such.
TL;DR#
- Fit test: one metric drives both your cost and the customer's value. Otherwise seats or flat tiers are simpler.
- One metric only. Postmark charges by emails, Plausible by pageviews, AI APIs by tokens.
- Hybrid wins. Resend Pro is $20/mo for 50,000 emails, then $0.90 per 1,000.
- Caps are table stakes. Supabase has spend caps on by default on Pro.
- Billing tools: Stripe Billing is 0.7% of billing volume, Lemon Squeezy is 5% + 50¢, and Paddle's usage billing is a beta that does not bill overage.
Disclosure: ZeroRaised publishes this guide and is a launch site for bootstrapped products. ZeroRaised has no commercial relationship with any vendor named here and earns nothing if you sign up. Facts come from the linked sources as checked on 7 Nov 2026.
When usage-based pricing fits (and when it does not)#
If you have not set a first price yet, start with our guide on how to price a SaaS product. This post assumes you have a product and are deciding what unit to charge for.
There are three common shapes:
| Model | Customer pays for | Good fit | Weak fit |
|---|---|---|---|
| Flat tiers | A bundle of features | Tools with steady, low running cost per customer | Products where one customer can cost 100x another |
| Per seat | Each user | Collaboration tools where value grows with headcount | Solo users, APIs, background jobs |
| Usage-based | A countable unit (emails, pages, events) | APIs, infrastructure, data and AI products | Tools whose value is not tied to volume |
Usage pricing fits when three things are true: your cost scales with usage (each email or model call costs you money), customer value scales with the same unit (a shop sending 100,000 receipts gets more than one sending 1,000), and customers vary widely, so one flat price is wrong for almost everyone.
Our read: if your costs barely vary by customer and users mostly log in to do work, usage pricing adds billing complexity for no upside. Flat tiers with a usage limit between them will do.
The risks for a solo founder are on both sides: your revenue gets less predictable, and customers fear a bill they cannot forecast. Everything below is about shrinking those two risks.
How to pick one value metric#
A good value metric passes four checks: the customer already thinks in it ("emails sent" needs no explanation), it grows with value, you can count it reliably in one place, and it tracks your cost, so margins hold as usage grows.
Here is how real pricing pages do it, checked on 7 Nov 2026.
| Product | Value metric | Published pricing |
|---|---|---|
| Postmark | Emails per month | Basic $15/mo for 10,000 emails, extra emails $1.80 per 1,000. Pro $16.50/mo (extra $1.30 per 1,000). Platform $18/mo (extra $1.20 per 1,000) |
| Resend | Emails per month | Free 3,000/mo (100 per day). Pro $20/mo for 50,000, $35/mo for 100,000, overage $0.90 per 1,000. Scale from $90/mo for 100,000 |
| Plausible | Monthly pageviews (plus custom events) | Starter $9/mo, Growth $14/mo, Business $19/mo at the entry pageview tier |
| Supabase | MAUs, disk, egress | Pro from $25/mo with 100,000 MAU (then $0.00325 per MAU), 8 GB disk per project (then $0.125 per GB), 250 GB egress (then $0.09 per GB) |
| Vercel | Requests, data transfer, compute | Pro $20/mo with $20 included credit. CDN requests: 10M/month included, then from $2 per 1M. Fast Data Transfer: 1TB included, then from $0.15 per GB |
| Anthropic API | Tokens | Claude Sonnet 5.5: $2 per million input tokens, $10 per million output tokens |
| OpenAI API | Tokens | gpt-5-mini: $0.25 per million input tokens, $2.00 per million output tokens |
Postmark, Resend and Plausible each charge for one metric; Supabase and Vercel meter several, but they are platforms with large teams. Our read: copy Postmark, not Vercel. Every extra metric is another thing to explain, meter and dispute.
Avoid metrics the customer cannot predict (CPU seconds for a non-technical buyer) or that punish the behaviour you want (charging per login).
For an AI product, tokens are your cost metric but rarely the right price metric for non-developers. Charge for the outcome (documents summarised) and handle token costs with limits. Our guide on how to set usage limits for an AI product covers rate limits and token budgets in depth.
The hybrid: base fee, included usage, overage#
Pure pay-as-you-go means a customer who uses nothing pays nothing, and your revenue floor is zero. The hybrid fixes that with three parts:
- Base fee. A fixed monthly price: your predictable revenue.
- Included usage. Enough that a typical customer never pays overage. Postmark's paid plans start at 10,000 emails a month; Resend Pro includes 50,000.
- Overage rate. A per-unit price above the allowance, usually in buckets. Resend says "Overages are billed in buckets of 1,000 emails at your plan's overage rate."
Two details worth copying: overage rates fall as tiers rise (Postmark drops from $1.80 to $1.20 per 1,000; Resend Scale falls to $0.46 per 1,000 at 2,500,000 emails), which nudges heavy users to upgrade, and overage can be opt-in (Resend switches it on through "Transactional Overages" in team settings; otherwise you are offered an upgrade).
Plausible does not bill overage at all: "You will never be charged extra for an occasional traffic spike." After two consecutive months over the tier you are asked to upgrade, and dashboards lock after a week if you do not, while stats keep being collected. Our read: where spikes are outside the customer's control, this is a kind model a solo founder can run without metered billing.
Protecting customers and protecting yourself#
Protect customers: caps, alerts, visibility#
Bill shock kills trust. What the big platforms do:
- Supabase: "Spend caps are on by default on the Pro Plan." Customers can turn them off to pay as they grow (Supabase pricing).
- Vercel: "All new teams have a default on-demand usage budget of $200 (which can be customized)", and at 100% you can configure Vercel to automatically pause all projects with a hard limit (Vercel pricing).
- OpenAI: a spend alert "Sends a notification; API traffic continues", while a hard spend limit makes affected requests return a
429error (OpenAI rate limits). - Anthropic: each usage tier has a monthly spend cap, and "Once you reach your tier's spend cap, API usage pauses until 00:00 UTC on the first day of the next month, unless you request a higher limit sooner" (Anthropic rate limits).
Our read: give every paid plan a default cap the customer can raise in one click, and say on the pricing page what happens at the cap (block, degrade or queue).
Protect yourself: minimums and margins#
- Keep a minimum. A base fee, even $9, covers some support time.
- Cap free usage hard. Postmark's free plan allows 100 emails a month and says "No overages allowed in this plan."
- Check margin at the top of each tier, where a customer uses the full allowance.
- Watch upstream prices. If you resell an API, its price is your cost. OpenAI's pricing page notes that "GPT-5.6 Sol's promotional pricing is available until November 30, 2026."
Billing tools: what each one costs and does#
Prices checked 7 Nov 2026. For the processor vs merchant of record decision itself, see our guide on how to sell software online.
| Tool | Fee (published) | Usage billing support |
|---|---|---|
| Stripe Billing | 0.7% of Billing volume (pay as you go), plus card processing | Meters API included "with up to 100M events per month included"; Stripe now recommends Metronome for new integrations |
| Lemon Squeezy | 5% + 50¢ per transaction, no monthly fee | Usage records API; charged at the next renewal for the previous period |
| Paddle | 5% + 50¢ per checkout transaction | Early access (beta): included usage only, overage not billed |
| Polar | Starter 5% + 50¢; Pro $20/mo + 3.8% + 40¢; Growth $100/mo + 3.6% + 35¢; Scale $400/mo + 3.4% + 30¢ (+1.5% for non-US cards) | Events, meters, metered prices and meter credits |
| Metronome | Starter: 0.8% of billing volume plus $0.04 per 1k ingested events | Dedicated usage billing; "now part of Stripe" |
| Orb | Business: $6.00 per credit (1 credit is 0.60% of billing volume plus event ingestion and other metered dimensions); 100 free credits | Dedicated usage billing |
| Lago | Cloud pricing not published (demo or contact) | Open source under AGPL-3.0, self-hostable |
Notes from the docs:
- Stripe. Its usage-based billing docs call Metronome "the recommended starting point for all new integrations"; the Meters API "remains fully supported for existing integrations." You send meter events and Stripe aggregates them at period end. Usage alerts fire a
billing.alert.triggeredwebhook, and the pricing models page lists "fixed fee and overage, pay as you go, and credit burndown." Card fees vary by country (Stripe pricing). - Lemon Squeezy. Usage charges "are made retrospectively based on reported usage during the previous billing period", with aggregation options such as "Sum of usage during period" and "Maximum usage during period".
- Paddle. Its docs say "During early access (beta), Paddle never blocks usage or bills for overage", and suggest a third-party usage billing provider for overage.
- Polar. Meters aggregate ingested events, and metered prices apply to subscription products.
Our read: under a few thousand dollars of MRR, you do not need Orb, Metronome or Lago. Use the usage features of your payment tool. If you want a merchant of record for sales tax, Lemon Squeezy and Polar bill usage today; Paddle only fits if included usage with no overage is enough.
Worked example: a pricing table for a document-parsing API#
A hypothetical product, "ParseKit", turns PDFs into structured data at an assumed cost of $0.001 per page. The value metric is pages processed per month.
| Plan | Price | Included pages/mo | Overage | Default overage cap |
|---|---|---|---|---|
| Free | $0 | 100 | None, hard stop | n/a |
| Starter | $19/mo | 2,000 | $8 per 1,000 pages | $50/mo |
| Pro | $49/mo | 10,000 | $5 per 1,000 pages | $150/mo |
| Scale | $149/mo | 50,000 | $3 per 1,000 pages | $500/mo |
Check the maths before you publish:
- Upgrade crossovers. Starter plus overage passes the Pro price at 5,750 pages ($19 + 3.75 x $8 = $49), and Pro passes Scale at 30,000 pages ($49 + 20 x $5 = $149). Email customers when they cross these points: the upgrade saves them money.
- Margin at the top of a tier. A Pro customer using all 10,000 pages costs $10. Lemon Squeezy's 5% + 50¢ on $49 is $2.95, leaving $36.05, about 74%. A full Scale customer costs $50; the fee on $149 is $7.95, leaving $91.05, about 61%.
- Overage margin. $3 per 1,000 pages against a $1 cost is healthy even at the lowest rate.
If the Scale margin feels thin, fix it before launch, not after.
Launch checklist#
- Write down your cost per unit, with a buffer for upstream price changes.
- Define exactly what counts (failed jobs and retries should not).
- Set a base fee on every paid plan and size included usage so most customers never pay overage.
- Make overage rates fall as tiers rise.
- Turn on a default spend cap, alerts at 50%, 80% and 100%, and live usage in the dashboard.
- Meter idempotently, so a retried request is not billed twice.
- Test a full cycle in test mode, including an overage invoice and a cap hit.
- Add worked examples to the pricing page and review per-customer margins after month one.
Mistakes to avoid#
- Launching pure pay-as-you-go. No revenue floor, and inactive customers pay $0 and quietly churn.
- Charging for several metrics at once. Customers cannot predict the bill.
- Billing overage with no cap. One runaway script becomes a refund request and a lost account.
- A metric you cannot count reliably. If you and the customer get different numbers, every invoice is a dispute.
- Ignoring billing tool limits. Paddle's beta does not bill overage, and Lemon Squeezy charges usage in arrears. Pick a model your tool can bill.
Frequently asked questions#
Is usage-based pricing a good idea for a bootstrapped SaaS?#
Often, but rarely in its pure form. If your costs and your customers' value both scale with one countable unit, charging for it is fair and lets small customers start cheap. For a solo founder, a hybrid is safer: a base monthly fee with included usage, an overage rate, and a spend cap, so revenue has a floor and customers cannot get a shock bill.
How do I choose a value metric?#
Pick the one unit that your customer already thinks in, that grows when they get more value, that you can count reliably, and that tracks your own costs. Emails sent, pages processed, pageviews and API calls are good examples. Avoid metrics customers cannot predict or control, and avoid charging for more than one metric at launch.
What is the cheapest way to bill usage as a solo founder?#
If you already use Stripe, its Meters API is part of Stripe Billing pricing (0.7% of billing volume on the pay-as-you-go plan, with up to 100M meter events a month included), though Stripe now recommends Metronome for new integrations. If you want a merchant of record that handles sales tax, Lemon Squeezy supports usage-based billing at 5% + 50¢ per transaction and Polar supports meters and metered prices from 5% + 50¢ on its free plan.
How do I stop customers getting a surprise bill?#
Give every plan a spend cap that is on by default, send alerts at set usage levels, show live usage in the app, and let customers raise the cap themselves. Supabase turns spend caps on by default on its Pro plan, and Vercel gives new teams a default on-demand budget of $200 with an option to pause projects at a hard limit.
Does Paddle support usage-based billing?#
Partly. Paddle's developer docs say usage-based billing is in early access (beta), works as prepaid usage included with a plan, and that Paddle never blocks usage or bills for overage during the beta. For overage billing, Paddle suggests using a third-party usage billing provider and charging through Paddle, for example with one-time charges.
Launch your pricing#
ZeroRaised is a launch directory for products built without institutional VC. Once your pricing page is live, submit your product for free and let the first launch traffic test it. For more guides on pricing and growing without investors, join the ZeroRaised newsletter.
Sources#
- Postmark pricing, last checked 7 Nov 2026
- Resend pricing, last checked 7 Nov 2026
- Plausible subscription plans documentation, last checked 7 Nov 2026
- Plausible pricing, last checked 7 Nov 2026
- Supabase pricing, last checked 7 Nov 2026
- Vercel pricing, last checked 7 Nov 2026
- Anthropic API pricing, last checked 7 Nov 2026
- Anthropic API rate and spend limits, last checked 7 Nov 2026
- OpenAI API pricing, last checked 7 Nov 2026
- OpenAI rate limits and spend limits, last checked 7 Nov 2026
- Stripe Billing pricing, last checked 7 Nov 2026
- Stripe pricing, last checked 7 Nov 2026
- Stripe usage-based billing docs, last checked 7 Nov 2026
- Stripe recording usage docs, last checked 7 Nov 2026
- Stripe usage alerts docs, last checked 7 Nov 2026
- Stripe recurring pricing models docs, last checked 7 Nov 2026
- Lemon Squeezy pricing, last checked 7 Nov 2026
- Lemon Squeezy usage-based billing docs, last checked 7 Nov 2026
- Paddle pricing, last checked 7 Nov 2026
- Paddle usage-based billing docs, last checked 7 Nov 2026
- Polar pricing, last checked 7 Nov 2026
- Polar usage-based billing docs, last checked 7 Nov 2026
- Metronome pricing, last checked 7 Nov 2026
- Orb pricing, last checked 7 Nov 2026
- Lago pricing, last checked 7 Nov 2026
- Lago on GitHub, last checked 7 Nov 2026
Frequently asked questions
Is usage-based pricing a good idea for a bootstrapped SaaS?
Often, but rarely in its pure form. If your costs and your customers' value both scale with one countable unit, charging for it is fair and lets small customers start cheap. For a solo founder, a hybrid is safer: a base monthly fee with included usage, an overage rate, and a spend cap, so revenue has a floor and customers cannot get a shock bill.
How do I choose a value metric?
Pick the one unit that your customer already thinks in, that grows when they get more value, that you can count reliably, and that tracks your own costs. Emails sent, pages processed, pageviews and API calls are good examples. Avoid metrics customers cannot predict or control, and avoid charging for more than one metric at launch.
What is the cheapest way to bill usage as a solo founder?
If you already use Stripe, its Meters API is part of Stripe Billing pricing (0.7% of billing volume on the pay-as-you-go plan, with up to 100M meter events a month included), though Stripe now recommends Metronome for new integrations. If you want a merchant of record that handles sales tax, Lemon Squeezy supports usage-based billing at 5% + 50¢ per transaction and Polar supports meters and metered prices from 5% + 50¢ on its free plan.
How do I stop customers getting a surprise bill?
Give every plan a spend cap that is on by default, send alerts at set usage levels, show live usage in the app, and let customers raise the cap themselves. Supabase turns spend caps on by default on its Pro plan, and Vercel gives new teams a default on-demand budget of $200 with an option to pause projects at a hard limit.
Does Paddle support usage-based billing?
Partly. Paddle's developer docs say usage-based billing is in early access (beta), works as prepaid usage included with a plan, and that Paddle never blocks usage or bills for overage during the beta. For overage billing, Paddle suggests using a third-party usage billing provider and charging through Paddle, for example with one-time charges.