If there’s one truism about software projects it’s that they’re never on time. Or on budget. So that may be frustrating and make you lose momentum.
Normally, a startup goes through the following steps until it launches:
Step 1.
You come up with an idea. You tell your friends about it, they love it so you start writing specs. Lots of specs.
Step 2.
You’re happy with the specs so you start looking for a software development house or grow an in-house team in order to get it rollin’.
Step 3.
You develop, test and refine the product. Then you develop, test and refine your product again. And again. And again. You’re happy and enthuziastic the first month. Heck, even the second. Actually if I think about it, you’re all caught up in the process even the third month. But then…
… you start having doubts: is it gonna be up and running soon (or ever?), are people gonna like the product, will they use it, will I still make millions, will my competition get ahead of me?. To make it short, you lose momentum. You’re not as confident and enthuziastic as you were when you started working.
Well, let me tell you one thing: if you spent 3 months working on the project, it’s probably worth something. It’s probably gonna have some fans, make some money (or a lot of them, who knows !?
), open a new market or even get founded or bought. So hang in there. Sooner or later, you’ll see it up and running.
On the other hand, if 3 months passed by and you don’t have at least a rough beta, you should dump the team, rethink the strategy and rewrite the specs, ’cause at one point something went really wrong. Of course, I’m not talking about rocket science here… a’aight? If you build rockets, then you better think of a strategy to keep the momentum baybe, ’cause it’s kinda gonna fly by.