“Build first launch later” or “Launch first build later”?

[kinggeorge]

@ericro Launch, get feedback, iterate quickly, and adapt to market needs.

 

[personalizedbook]

@ericro If this is a B2B product, I would personally secure an MVP deal with a prospective client first before beginning development. The client could even act as a mentor or contact source during and after development.

 

[ambersoul]

@ericro If this is software someone is going to pay for - do not write 1 line of code until you have 5 customers who have paid.

You can promise to deliver the product within agreed upon time period (ideally 30 days, never more than 90) or they get their money back.

This has 2 benefits:

1 - Proof there is demand

2 - Cash as incentive to finish your app

Writing an app is always the easy part. I don't care how complicated the app is.

You can always improve the product later.

The hardest part of any software project is getting customers.

And if you are a developer the last thing you ever want to do is have to market and sell your product.

But unless you (or a co-founder) can do this - your software will not get any customers.

You also don't need an ad budget to do this.

Start with the people you know. And go from there.

 

[cdtaylor]

@ericro If other players exist then build first. If no ones solving that problem then you need to launch asap. This was the advice from lemlist CEO (which is now around 150m valuation if I am not wrong)

 

[613jono]

@ericro Do fucking something don't get paralized