“Can a product be built?” is now an irrelevant question for the majority of startups. Services like AWS, EC2, and Rackspace, let you build scalable services that would have been impossible to build a few years ago (unless you raised millions of dollars). Now any decent programer can feasibly build a product that can scale to tens of thousands of users (or more) from their garage. The game has completely changed in a few short years. The playing field has been leveled.
The most pressing question a startup now must answer is “Should this be built?”.
It’s much easier to be concerned about the “good problems” (how is this going to scale to millions of users) than the real problem – “What if no one cares?”.
I learned this lesson the hard way:
Should I build this product?
Do you have any customers?
When I was in college, I worked in the Admissions Office to help pay my way though school. I learned the ins and the outs of the Admissions department. I studied our marketing materials and would often ask potential students what they thought of our advertising efforts. I did this for about a year. I believed I knew exactly where my schools strengths and weaknesses were in promotional materials.
Fast forward a few months to when I had my own company that was working on mobile applications. I decided it would be a great idea to leverage my experience working in an Admissions office to build an iPad app that solved all of their pain points. After all, I did believe I had a good grip on the industry.
I sunk a good month and a half into the project. I mapped out an elegant custom infrastructure that would scale effortlessly. I polished it up and I got a meeting with the head of an Admissions office.
That’s when the bombshell hit. With all of my customer infrastructure, the finished product was going to cost 5 times what a college was willing to pay. I had to completely retool, move to a generic infrastructure, and simplify some of features to make it financially viable for schools.
Lesson learned: Infrastructure doesn’t make you special. If it works and is reasonably responsive, it’s going to be fine for the vast majority of people. As a nerd, this broke my heart but as an entrepreneur, it was a joyful discovery.
Is it the right time for this product?
It’s possible that you can have a fantastic idea, but the market might not be ready for it. One thought exercise I use is this: “If I had the product finished right now, could I call around and get a paying customer today?” If you believe the answer is “yes”, call them immediately and those lines of communication for when you’re ready to launch.
The worst case scenario is that no one cares about what you’ve built, and you’ve saved yourself some serious time. Figure out if your startup should be built before you worry about infrastructure.
Technical scalability has essentially been solved for most startups. These problems have been solved well, and are cheap to use. Don’t waste a lot of time on re-inventing the wheel. Focus on your app and the things that set you apart, not the commodities.