I run a small, independent software company. First timer. > I estimate 2 weeks It is going to take longer than 2 weeks. And it is going be harder than you think. Building a product is only the beginning. You will have to write copy, find customers, implement billing and charge folks, offer support, do maintenance, build features, again find customers, talk to them, again build features, tweak copy, handle legal/accou…
Ask HN: Should I Build This?
11–19 of 19 posts
Re: Ask HN: Should I Build This?
#12Join YC Startup School, it will answer many questions and teach you a framework for thinking about your potential product. Or you can watch the videos on YouTube
This looks like a great suggestion! Have you used it yourself or just heard about it?
Re: Ask HN: Should I Build This?
#13If it takes just 2 weeks to build it, you should do it. No second thoughts.
Thank you. Possibly less as its a very simple product technically speaking. In terms of value added for the services using it - I think its quite beneficial but this is what I'm struggling to quantify or be objective about. This is very low maintenance and I am planning on doing this so it's as small technical debt as possible
Re: Ask HN: Should I Build This?
#14If it takes just 2 weeks to build it, you should do it. No second thoughts.
Thank you. Possibly less as its a very simple product technically speaking. In terms of value added for the services using it - I think its quite beneficial but this is what I'm struggling to quantify or be objective about. This is very low maintenance and I am planning on doing this so it's as small technical debt as possible
Re: Ask HN: Should I Build This?
#15Earlier quoted context omitted.
Thank you. Possibly less as its a very simple product technically speaking. In terms of value added for the services using it - I think its quite beneficial but this is what I'm struggling to quantify or be objective about. This is very low maintenance and I am planning on doing this so it's as small technical debt as possible
If it's technically very simple, why would your customers buy your product rather than build it themselves?
Re: Ask HN: Should I Build This?
#16Re: Ask HN: Should I Build This?
#17In terms of finding if it is a needed solution, you will need to find your target customer in depth. Your target customer profile should be so narrow that it makes you uncomfortable.
Re: Ask HN: Should I Build This?
#18Earlier quoted context omitted.
If it's technically very simple, why would your customers buy your product rather than build it themselves?
Because 99.9% of the population are not programmers?!
How would you provide a service like that without any programmers?
Re: Ask HN: Should I Build This?
#19If it takes just 2 weeks to build it, you should do it. No second thoughts.
Thank you. Possibly less as its a very simple product technically speaking. In terms of value added for the services using it - I think its quite beneficial but this is what I'm struggling to quantify or be objective about. This is very low maintenance and I am planning on doing this so it's as small technical debt as possible
Even if you tell your idea 99% of people won't do anything with it. If they do yours could still be implemented better and beat them or you could still beat them to market, or there could be a big enough market everyone can fit.
E.g there are like 10 uptime monitoring apps on indiehackers doing >3k mrr. Very simple function, tons of profitable competitors.
My advice is just say what it is you want to build and get actual feedback on the whole concept, you might even uncover better features by getting insight. Don't be afraid of people stealing your ideas. Ideas are a dime a dozen, successful startups are 1 attempt out of 99.