Home Work
SaaS developmentAI developmentAPI developmentMobile app developmentGoogle Ads managementHeadless ShopifyLaravel developmentNext.js developmentReact developmentTypeScript engineeringUI/UX designSEO & AEOEcommerce development
AI solutionsB2B platformsE-commerceHospitalityLead generationLogisticsEducationProcess automationSaaS platformsStartup MVPReal estateHealthcare
LegalHealthcareReal estateFinanceHospitality
The HagueRotterdamAmsterdamUtrechtEindhovenAlmereBredaArnhemNijmegenTilburgEnschedeGroningenLeidenDelftZoetermeerDen Bosch
Studio
AboutProcessLabBlogContact
SaaS

SaaS pricing strategies that deliver margin

MBy M. Tufan, Co-founder · Published May 2026 · 9 min read
QUICK ANSWER

The best SaaS price ties what the customer pays to the value they get. Per-seat works for team tools, usage-based for APIs and consumption, and tiers for broad audiences. Freemium pulls volume but costs margin when conversion to paid is low. Start with three tiers, price on value not on cost, and dare to raise. At NedDev, we build the billing logic so you can adjust later without a rebuild.

The biggest mistake in SaaS pricing is not pricing too low or too high. It is choosing a pricing model that does not move with the value the customer experiences. A tool that grows with the customer but has a fixed price leaves money on the table with every successful customer. A tool that charges per user while the value sits in consumption drives away your best customers instead. Pricing is not a sauce you pour over your product afterward, it is a product decision.

The four main models

There are four models that cover the vast majority of successful SaaS, each with its own logic about when it fits:

  • Per-seat: you pay per user. Works for team tools where more people also means more value, such as a shared CRM or project system.
  • Usage-based: you pay according to consumption, such as API calls, storage, or processed documents. Fair and scalable because the price follows usage, but less predictable for the customer who does not know up front what the bill will be.
  • Tiered: three or four packages with increasing features and limits. The most-used approach because it combines freedom of choice with the predictability of a fixed monthly price.
  • Freemium: a free base version that scales up to paid. Pulls volume and lowers the barrier, but is only profitable if enough users actually convert to paid.

Most platforms we build combine tiers with a usage component: a fixed package with a generous limit, and consumption above that at an extra charge. That way a heavy user fairly pays more without a light user being scared off at the door by a high entry price. You get predictability and scalability at the same time.

Price on value, not on cost

What it costs you to run the software is almost irrelevant to the price you charge. What counts is what it delivers to the customer. Does your tool save a bookkeeper ten hours a month? Then a few hundred euros a month is an easy decision for that customer, entirely separate from your server cost of a few tens of euros. The customer buys the result, not your infrastructure.

At ClaimHandler the value is concretely measurable in hours saved per case and in errors that no longer get made. The price follows that value, not the hosting bill. The common mistake is calculating a price by adding up your costs and putting a fixed margin on top. That feels safe, but it almost always leaves money on the table, because your price never rises above your cost while the value for the customer can be a multiple of that.

Research your value by talking with customers about what the product delivers to them in time, money, or peace of mind. That conversation is more valuable than a spreadsheet of your server costs. A practical technique is the Van Westendorp price model: ask customers at what price the product becomes too expensive, at what price they find it too cheap to trust, and between those you find a healthy margin. It puts your pricing conversation on data instead of on a gut feeling.

The pitfalls

A few mistakes we keep seeing, and they all cost revenue directly:

  • Too many tiers: with five or six packages the customer gets paralyzed by choice. Three is usually enough, four the maximum. Visually highlight the middle package as the recommendation.
  • Free too generous: if the free version can do everything most people need, almost nobody converts. The free tier should let people taste the value, not give away all the value.
  • Never raising: your product gets better every quarter, your price stays put for years. Dare to review periodically, at least for new customers who never knew the old price.
  • Pinning down billing logic: if your pricing model is hardcoded into your product, every small change costs an expensive overhaul.

Build in flexibility

Pricing is not a one-time decision but something you will adjust, multiple times. Your system has to be built for that. In Laravel 12 we separate the pricing rules from the product logic, so you can change tiers, limits, and usage thresholds without rewriting code. Mollie or a comparable provider handles the transactions, but the logic of which customer pays what and on which terms stays in your hands and is configurable.

A sensible approach: launch with a thought-through but simple model, measure how customers use your product, and adjust based on real data instead of assumptions. We build a complete SaaS platform with flexible billing in the range of €15,000 to €60,000. Want to spar about your pricing model before you have a line of code written? Take a look at our SaaS development service. Choosing the right model and the right flexibility before the build saves an expensive migration afterward. And remember that pricing is never finished: the best SaaS companies treat their pricing model as a living part of the product that they keep refining based on what customers actually value and use.

FREQUENTLY ASKED

SaaS · FAQ.

How many price tiers should I offer?

Three is usually optimal, four the maximum. With more packages customers get paralyzed by choice and conversion drops. A common setup is an entry package, a popular middle package that you visually highlight, and an extensive package for heavy users. Optionally combine it with a usage component for consumption above the limit.

Is freemium a good idea?

Freemium pulls in many users, but is only profitable if enough of them convert to paid. The pitfall is a free version so generous that nobody sees a reason to upgrade. The free tier should let people taste the value, not give away all the value. For B2B tools a free trial often works better than permanent freemium.

Should I price on cost or on value?

On value. What the software costs you to run is largely irrelevant to what a customer wants to pay. Determine what your tool delivers to the customer, such as hours saved or extra revenue, and price on that. Cost-based pricing almost always leaves money on the table because it ignores the real value.

NEED A HAND

Ready for your next build.

Book an intro → Direct line to the founder · M. Tufan