SaaS pricing strategy is one of those topics where everyone has an opinion and almost nobody has actual experience. I have priced four different SaaS products from scratch, all bootstrapped, all without a VC board telling me to chase growth at all costs. And the single biggest lesson across all four is this: I undercharged at the start every single time. You probably are too.
The thing about pricing when you are bootstrapped is that it matters more than it does for funded companies. A VC backed startup can afford to underprice for years while they chase market share. You cannot. Your pricing has to sustain the business from day one because there is no safety net. That changes the entire calculation.
Why bootstrapped founders always price too low
There is a psychological trap that catches nearly every bootstrapped founder. You have built something yourself. You know every shortcut, every rough edge, every bit of technical debt hiding behind the interface. So when it comes time to put a price on it, you mentally discount all of those things. You think "well, it is not perfect yet, so I cannot charge proper money for it."
Your customers do not know about the technical debt. They do not care that you refactored the database layer at two in the morning. They care about whether the thing solves their problem. And if it does, they will pay proper money for it.
The other trap is comparison anxiety. You look at your competitors, see their pricing pages and think you need to come in underneath them to win business. This is almost always wrong. Coming in cheaper signals that your product is worse. It does not signal that you are better value. I learned this the hard way with CampSuite when I initially priced it thirty percent below the nearest competitor and spent the first year answering questions about why we were so cheap.
The three pricing models that actually work for bootstrapped SaaS
There are really only three pricing models worth considering when you are bootstrapping. Everything else is a variation or a complication you do not need yet.
Per user pricing
This is the simplest model and the one I would recommend for most B2B SaaS products when you are starting out. It scales naturally with the size of the customer. It is easy to understand. It is easy to forecast. And it gives your customers a clear mental model for what they are paying.
The downside is that per user pricing creates a perverse incentive for customers to share logins. You will need to decide early on whether you care about that. In my experience, most businesses do not bother gaming it because the hassle is not worth the saving. But if your product stores sensitive data or has compliance requirements, you will want proper user management anyway.
Usage based pricing
This works well if the value your product delivers scales with usage. Email platforms, API services, data processing tools. The customer pays more as they use more, which feels fair to them and scales your revenue naturally.
The problem with usage based pricing when you are bootstrapped is that your revenue becomes unpredictable. You cannot forecast next month with any confidence because you do not know how much your customers will use the product. That makes it harder to plan, harder to hire and harder to sleep at night. Unless your product genuinely delivers more value at higher usage, I would avoid this model early on.
Flat tier pricing
Three tiers. Maybe four at most. Each tier unlocks more features or higher limits. This is the model I use most often because it gives customers a clear choice and lets you capture different segments of the market without building entirely separate products.
The trick with tier pricing is making sure each tier has a genuine reason to exist. The bottom tier should be useful enough that people actually buy it. The middle tier should be where most customers land. The top tier should be where your most valuable customers end up, and it should be priced to reflect the value they are getting, not the cost to you of providing it.
How to actually set the number
Here is where most pricing advice falls apart. Everyone tells you to "price based on value" which sounds lovely but is completely useless if you do not know how to calculate the value. So here is how I actually do it.
Start with the problem your product solves. How much time does it save? How much money does it save? How much risk does it remove? If you can put a rough number on any of those, you have a starting point. Your price should be a fraction of the value you deliver. Not a large fraction either. If your product saves a business ten thousand pounds a year, charging two hundred quid a month is a no brainer for them and very good business for you.
Talk to ten potential customers and ask them what they would expect to pay. Not what they want to pay, what they expect. The answers will cluster around a range and that range tells you more about market expectations than any amount of competitor analysis. I cover this kind of customer research in more depth in The 28 Day Startup because it is one of the most valuable things you can do before launching anything.
Then double whatever number you arrived at. I am serious. Whatever price feels right to you as a founder, double it. You will lose fewer customers than you think and the ones you keep will be better customers. Price sensitive buyers are almost always the most demanding and the most likely to churn.
The pricing page mistakes I see everywhere
Your pricing page is one of the most important pages on your entire website and most SaaS companies get it badly wrong. Here are the mistakes I see most often.
Too many tiers
If you have five or six pricing tiers, you are making your customer's decision harder, not easier. Nobody wants to spend twenty minutes comparing feature matrices. Three tiers. Pick names that actually mean something. Move on.
Hiding the price
If a potential customer has to book a demo just to find out what you charge, you have already lost most of them. The "contact us for pricing" approach works for enterprise software but it is poison for bootstrapped SaaS. Show the price. If people leave because of the price, that is useful information. If they leave because they cannot find the price, that is just waste.
Feature bloat in the comparison table
Nobody reads a forty row feature comparison table. Highlight the three or four things that differentiate each tier. The features that make someone think "right, I need the middle one, not the bottom one." Everything else is noise that makes the decision harder.
No annual discount
Offering a discount for annual billing is the single easiest way to improve your cash flow when you are bootstrapped. Customers pay upfront for the year. You get twelve months of revenue in one go. Your churn rate drops because people who have paid for a year are much less likely to cancel. A fifteen to twenty percent discount on annual billing is a good starting point. It feels generous to the customer but the improved cash flow and reduced churn more than compensate.
When and how to raise prices
If you have not raised your prices in the last twelve months, you are almost certainly leaving money on the table. Your product is better than it was a year ago. Your costs have gone up. Your value to the customer has increased. Your price should reflect that.
The fear of raising prices is always worse than the reality. When I raised prices on one of my products by forty percent, I lost exactly two customers. Two. And both of them were customers I was happy to lose because they were the ones who submitted the most support tickets and complained the most. The remaining customers barely noticed.
Here is how to do it without causing a riot. Give existing customers plenty of notice. Sixty to ninety days minimum. Grandfather them on their current price for a period if you want to be generous. Make sure the price increase coincides with visible improvements to the product so there is a clear reason behind it. And communicate it directly. A personal email from the founder explaining why prices are going up and what customers are getting for the increase goes a long way.
New customers should see the new price immediately. Do not apologise for it. Do not explain it. Just change it. New customers have no anchor to the old price so it is a non event for them.
Free trials and freemium: the bootstrapped perspective
Free trials are almost always a good idea. Freemium plans are almost always a bad idea when you are bootstrapped.
A free trial gives people a chance to see the value before they commit. Fourteen days is usually enough. Thirty days is too long because people procrastinate and forget. During the trial, make sure the customer can experience the full value of the product. Do not cripple the trial with restrictions that prevent them from having the moment where they think "right, I need this."
Freemium, where you give away a limited version forever, sounds like a great growth strategy but it is a cash flow disaster for bootstrapped businesses. Free users cost money to support. Free users submit feature requests. Free users use infrastructure. And the conversion rate from free to paid is typically between two and five percent. You need enormous volume for that to work, and if you had enormous volume you probably would not need to bootstrap.
My advice is simple. Free trial, yes. Freemium, no. Not until you have enough revenue that the cost of supporting free users is genuinely negligible. That might never happen, and that is fine.
The pricing conversation you need to have with yourself
Before you set or change your pricing, sit down and answer three questions honestly.
First: what does this business need to earn to be sustainable? Not what you would like it to earn. What does it actually need? Hosting costs, your time, support, marketing, the occasional contractor. Work out the real number and then work backwards from how many customers at what price gets you there. If the maths does not work, your pricing is wrong. This is one of those SaaS metrics that actually matters when you are bootstrapped.
Second: who are you actually selling to? If you are selling to small businesses, there is a ceiling on what they will pay. If you are selling to mid market companies, that ceiling is much higher. If you are selling to enterprises, different game entirely. Your pricing model and your price point need to match your actual buyer.
Third: are you building a lifestyle business or something bigger? Both are valid. But a lifestyle business can sustain on fewer customers at higher prices while a growth business needs volume. The answer to this question should shape everything about how you price.
Stop overthinking it
Here is the final thing I want to say about SaaS pricing strategy. You are going to get it wrong. Everyone does. The first price you set will be wrong. The second one probably will be too. That is fine because pricing is not a one time decision. It is a lever you can adjust as you learn more about your market and your customers.
Pick a price that feels slightly uncomfortable. If it does not make you a bit nervous, it is probably too low. Launch with it. Watch what happens. Adjust. The worst thing you can do is spend three months agonising over whether to charge twenty nine or thirty nine quid a month while your competitors are out there selling.
Your pricing will never be perfect. But it needs to be good enough to sustain the business while you figure the rest out. And if you are bootstrapping, that is really all that matters.
