I built 27 features before talking to a single user
Building every night felt like progress. User calls felt risky. Why SaaS founders build too much too early, and what we are doing differently at Ospyr.
I built 27 features before speaking to a single user. It sounds stupid when I say it like that. If you are building SaaS, you probably know how it happens.
How the product keeps growing
You start with one useful idea. Then the dashboard needs filters. The filters need saved views. Saved views need permissions. Dark mode somehow becomes urgent too. Every night there is something new on the screen, and it feels like progress.
Why the calls stay at the bottom of the list
User calls feel different. One person can look at three weeks of work and say, "I do not really need this." So the calls stay at the bottom of the list while the product keeps getting bigger. Building gave me proof that I was working. It gave me no proof that the work mattered.
The boring advice is right
Y Combinator keeps repeating the same advice: write code and talk to users. Stripe says SaaS founders should speak with more customers than feels natural. A business system should help you learn what deserves to be built before it helps you produce more of it. That is how we think about building at Ospyr.