What Nobody Tells You About Building SaaS Products
What Nobody Tells You About Building SaaS Products
SaaS — software as a service — is the business model that ate the software industry. Instead of selling someone a box with a CD in it, you charge them monthly and host everything yourself. It's recurring revenue. It's scalable. It's the reason every pitch deck since 2010 has a hockey stick chart in it.
I've been building SaaS products for a long time. Some worked. Some didn't. The ones that worked taught me things that the blog posts and Twitter threads about SaaS never mention.
It's a service business disguised as a product business
The "S" at the end of SaaS stands for "service" but most founders skip right past it. They think they're building a product — write the code, ship the feature, move on. In reality, the moment someone starts paying you monthly, you're in the service business.
That means uptime matters more than features. It means a customer who emails you at 9pm on a Sunday expects a reply before Monday morning. It means the boring parts — billing, account management, password resets, data exports — are just as important as the clever parts.
I learned this the hard way with my invoicing tool. We'd ship a beautiful new feature on Tuesday and spend Wednesday dealing with support tickets from users whose PDF exports broke. Nobody cared about the new feature. They cared that their invoices looked wrong when they sent them to clients.
The best SaaS founders I've met aren't the best engineers or the best designers. They're the ones who internalised that they're running a service and act accordingly.
Churn is the only metric that matters
When you're starting out, you obsess over acquisition. How do I get more signups? More traffic? More trials converting to paid? That feels like the game because the numbers are small and every new customer is exciting.
Then you hit a few hundred paying users and you realise something uncomfortable: you're losing almost as many as you're gaining. The bucket has holes.
Churn — the percentage of customers who cancel each month — is the metric that determines whether your SaaS business is viable or just a treadmill. A 5% monthly churn rate sounds harmless until you do the maths and realise you're replacing half your customer base every year. That's not growth. That's running to stand still.
Reducing churn by even one percentage point will do more for your business than doubling your marketing budget. It's less exciting than launching a new feature or running a campaign, which is exactly why most founders don't focus on it until they're already in trouble.
Pricing is a mess and it never stops being a mess
I've changed pricing on my SaaS products more times than I can count, and I've never once felt confident that I got it right. Too cheap and you attract users who don't value the product. Too expensive and you lose everyone who's comparing you to competitors. Freemium sounds great until 95% of your users are on the free tier and your server bill arrives.
The one thing I've learned about pricing: charge more than you think you should. Almost every indie SaaS founder underprices out of insecurity. You think "who would pay $30/month for this?" and the answer is almost always "more people than you expect, and they'll take it more seriously than the people paying $5."
If someone uses your software every day in their business, they're not going to cancel over $10/month. They cancel because the product stops solving their problem, not because of the price.
The feature trap
There's a phase every SaaS product goes through where customers start requesting features and you start building them. Customer A needs an API. Customer B needs a Slack integration. Customer C needs custom roles and permissions. You build all of it because you're terrified of losing them.
Six months later your codebase is a mess, your product is confusing, and none of those customers are happier because they each only use their one specific feature and find the rest cluttered.
The hardest skill in SaaS isn't building features. It's saying no to features. Every feature you add is a feature you maintain forever. It's a feature that makes the product more complex for every other user. It's surface area for bugs, support tickets, and documentation.
The products I admire most are the ones that got better by removing things, not adding them. That's incredibly hard to do when a paying customer is asking you for something specific, but it's almost always the right call.
It's a long game
The SaaS success stories you read about — "We hit $1M ARR in 18 months!" — are survivorship bias in its purest form. For every one of those, there are a thousand products that took three years to reach ramen profitability, and another thousand that never got there at all.
If you're building SaaS as an indie developer, the most important quality isn't technical skill or marketing savvy. It's patience. The ability to keep showing up and improving something when the MRR graph is flat and nobody's writing blog posts about you.
Most of my SaaS products took at least a year before they felt like real businesses. The temptation to quit at month six is enormous. The people who make it through that dip aren't smarter — they're just stubborn enough to keep going.
Is it worth it?
Yeah. For all the headaches, SaaS is still the best business model I've found for a solo developer. Recurring revenue means you can plan. Hosting the software yourself means you control the experience. The feedback loop between you and your users is direct and fast.
But go in knowing it's a service business, not a product launch. The launch is day one. The service is everything after.