What pricing model works best for a SaaS with flat base and usage add-ons?

[Steven12]

We’re about to launch a new SaaS tool and I’m stuck on how to structure the fees. I like the idea of a flat monthly rate for core access, but then charging extra for heavy API usage or premium support tiers. I’m just not sure if that’s more confusing than a simple all-inclusive price, or if it actually helps capture more value from different types of customers.

[AddisonWL]

We started with a flat core and charged extra for API calls. It looked simple on paper but customers told us the overage pricing felt unpredictable. The team watched usage patterns and saw big spikes on weekends.

[Addison_G]

Another route we tried was three all inclusive tiers. It was easy for sales teams but some power users hit ceilings and churned when they reached the limit.

[SamuelBR]

We did a light overage model and added credits when crossing the threshold. It softened the sting but mid month bills still confused finance.

[Edward36]

We also considered a simple single price plus a data cap. In practice the cap felt arbitrary and customers asked for bigger bundles.

[Elizabeth41]

I once asked a small group what matters most and they said reliability and speed more than price. We tried to bake that into a single price and still had to explain the value.

[PaulW]

Is the real problem maybe not the price but how we show value and how easy it is to start using the tool?