Pricing model
Flat-rate pricing model
Flat-rate pricing charges every customer the same amount regardless of usage, seats, or feature consumption. It is the simplest pricing model and the most over-applied — many SaaS products that 'should' have tiered or usage-based pricing default to flat rate because it is easy to communicate.
Verified · editorial policy
How the model works
One price for everyone. $X/month, full product access. No tiers, no usage caps, no per-seat metering. Customers pay the same whether they use the product daily or weekly. Revenue scales linearly with customer count.
Best for
Products with consistent value per customer (a focused tool used by individuals). Indie SaaS at the experimentation stage (one price is operationally simpler than 3-5 tiers). Products with low usage variance — where customer A and customer B use the product similarly.
Worst for
Products with high usage variance (some customers cost 100x more to serve). Products where teams want to share access (per-seat is the model). Products where heavy users would happily pay more for more capacity (you are leaving money on the table).
Unit-economics implications
- Customer-cost variance is invisible to the price. Heavy users subsidize light users; both probably pay 'wrong' price.
- ARPU equals price — clean math, easy to project.
- LTV calculation is simple: price / churn. The cost-side is where flat-rate hides problems.
- Expansion revenue is structurally zero. No way for happy customers to spend more without buying multiple accounts.
Common implementation mistakes
- Pricing too low on flat-rate. The instinct is 'one accessible price'; in reality, flat-rate often leaves money on the table at the high end.
- Not offering an annual variant. Most flat-rate SaaS should still offer monthly + annual; the annual is the high-LTV signal.
- Sticking with flat-rate past product-market fit. Many SaaS that started flat-rate should add tiers once usage variance becomes visible.
- Charging flat-rate for teams. Almost always wrong — teams expect per-seat or per-workspace pricing.
Positioning trap to watch
Flat-rate often hides a 'we do not know who our customer is' problem. When you do not know which customer cohorts use the product differently, flat-rate is the safe-feeling default. Once cohort-specific behavior becomes visible, flat-rate starts under-monetizing the heavy users and over-charging the light ones.
Pricing teardowns of products using this model
Frequently asked
- Should an indie SaaS start with flat-rate?
- Often yes for the first 3-12 months. Simpler to communicate, simpler to operate, fewer pricing-experiment variables to manage. Migrate to tiered or usage-based once you have data on actual customer behavior variance.
Other pricing models
Diagnose the page, then pick the model
Pricing model is downstream of positioning. The free diagnostic labels which Brunson failure mode your page hits; the right pricing model follows from the positioning.