We spent 6 months building our mobile app in secret. Launch day brought 12 downloads.
For the first two years of our SaaS, we were desktop-only. But we kept hearing the same feedback: "I love this tool, but I wish I could use it on my phone."
So, we decided to go all-in. We hired a mobile developer and spent six months and about $35,000 building a native iOS and Android app. We worked in complete secrecy. We didn't post any teasers, we didn't build a waitlist, and we didn't tell our existing users what we were working on. We wanted it to be a massive surprise.
Launch day finally arrived. We sent out a single email blast to our 5,000 users and posted a launch thread on Twitter. I sat back and waited for the downloads to roll in.
By the end of the day, we had 12 downloads. Not 1,200. Twelve.
I was crushed. I reached out to our most active users to ask why they didn't download it. Their responses were a punch to the gut: "Oh, I didn't know you were building an app," or "I only use your tool at my desk, so I don't really need it on my phone."
I realized I had fallen into the classic "Build It And They Will Come" trap. I assumed that because people asked for a mobile app, they would actually use it. But I never validated the demand, never built an audience ahead of time, and never got a single pre-launch commitment. I spent $35,000 on a product that solves a problem our users don't actually have.
For founders who have launched a new product or feature: How do you validate demand before spending months building?
Do you require a waitlist or a deposit before you start coding? Do you launch a bare-bones version first and iterate? I need to figure out how to stop building things nobody wants.
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.