|
|
|
|
|
by brilliantcode
3486 days ago
|
|
I was you only a few years ago. I spent a year building a really complex SaaS in my bedroom. Then I tried to sell it the next year and a half with dismal results. 1) Validate first by talking with potential customers before building. 2) If the MVP takes longer than 3 month to build, you are barking up the wrong tree. a) problem/product fit is too high for a lone developer.
b) your lack of experience & skill may be a bottleneck.
3) If people are going around saying it can be done in a couple of weeks, ignore them, unless they have done a similar project before in which I'd listen very carefully why it shouldn't take long.4) If people are telling you've been at it for too long, it's time to reevaluate your self, skills & business. 5) Don't go at it alone. Partner up with a coder. Share the pain. |
|
It doesn't necessarily mean the product isn't fit or you lack skills. It may just mean that you need to split the product into smaller releases/sprints.
Say your idea can ultimately lead to a really big software. You should sit down and spend some time planning which features are required and which ones can be released at a later time. Doing this will help take some of the pressure off if the product is not "perfect" or doesn't do everything you had planned for it.