You need to validate your business as quickly as possible. Here's one way to do that: Consider your top 3 assumptions relating to the following risks: users (d

You need to validate your business as quickly as possible. Here's one way to do that: Consider your top 3 assumptions relating to the following risks: users (do people want this?), business (can you sell it will it be profitable for you?), technical (can you complete the project in a way that will be useful for others?). These are the things that, if they're wrong, will mean you'll fail. Then give yourself two days and find out the answers to those questions. The only way to find that out in that time is to go out and talk to people. Give them a call; email them; reach out on Twitter - just get that feedback however you can. Be open to learning and being wrong, even though you've worked on this for a long time. Some suggestions: Users - find some people you think would want this and talk to them about it. Business - find someone who's sold something similar successfully and talk through what they did with them. Technical - speak with people who have written similar projects at the database layer. Engineers don't typically like picking up the phone, but there's no alternative to asking questions and knocking down those risks as quickly as you can.