Your First 10 Users > Your First 10 Features: Hard Truths About SaaS MVPs

Published 2025-09-10

Bootstrapping a SaaS MVP isn’t just a coding sprint—it’s a mental grind.

As a Senior Software Engineer at Microsoft (after Clear Software’s acquisition) and through side projects like Spare Cloud and SitePixel, I’ve stumbled plenty. Each project left me with hard-learned lessons about what not to do.

Here are six mental hurdles I hit—and how I overcame them.


1. Ship first. Polish later.

At Clear Software, I wasted days building AS400 integration… only for it to get scrapped when we doubled down on SAP customers. In my side projects, I burned hours polishing UIs for features that never shipped.

The problem: perfectionism kills progress.

The fix: I now use a Kanban board for side projects where I ruthlessly focus on the smallest possible amount of functionality needed to solve the problem. At Clear Software, we nailed one SAP integration first before expanding.


2. Chasing Non-Business Tasks

I once spent days hunting down and setting up analytics tools for a project with zero users because I wanted the best setup. At Clear Software, I tinkered with logging systems instead of helping my team better optimize our products and delivery for customers.

The problem: users don’t care about your tech stack or tools.

The fix: focus on tasks that directly provide value.

If not, it goes in the ā€œLaterā€ pile.


3. Thinking a Product Is a Business

My Spare Cloud backup service had a slick UI and backend. I thought I was golden. But with no users and no revenue, it was just… code.

Even at Microsoft, acquisitions like Clear Software only mattered because there was a business model attached.

The fix: plan business with product.

At Clear Software, we moved quickly to get our product in front of more people. That accelerated our learning and made our product more useful. Sometimes it was evolving how we used our own product, not just manipulating the codebase.


4. Validate or fail fast.

I used to keep ideas secret, worried about people stealing them. A few project's flopped because I never validated with real people.

The problem: ideas in your head don’t count.

The fix: share early, validate often.


5. Your first 10 users matter more than your first 10 features.

I thought good products sold themselves. Wrong. Most of my side projects fizzled because I had no outreach or distribution plan. At Clear Software, sales and marketing turned our tech into an actual business.

The fix: treat distribution like coding.

Your first 10 users matter more than your first 10 features.


6. Overvaluing My Engineering Effort.

SitePixel, my feedback widget, had two paying customers. Someone once offered me $5,000 to buy it. I refused, thinking the engineering effort I’d poured in made it worth more. I eventually lost both customers, shut it down, and pocketed less than $5k.

The problem: I confused my effort with actual value.

The fix:


Keep Building

Bootstrapping is a head game. To survive it:

Between Clear Software, Microsoft, Spare Cloud, and SitePixel, I learned these lessons the hard way. You don’t have to.

šŸ‘‰ What’s your biggest MVP hurdle? Drop a comment or ping me on X.


šŸš€ Join My Next Startup Launch

I’m currently building StackSite — a platform designed for businesses where social media isn’t the core product, but staying present online still matters.

If that sounds like you, join the launch list here to get early access and behind-the-scenes updates.