4 ms·
Two tips: 1) I use this as a rule of thumb; only launch when it feels like it's version 3.0, not version 1.0. This keeps you on your toes and provides a much b
by andremedeiros 14y ago
Two tips:
1) I use this as a rule of thumb; only launch when it feels like it's version 3.0, not version 1.0. This keeps you on your toes and provides a much better product from the beginning. Remember first impressions are everything, and if customers come and see a smal set of features, they most likely won't come back.
2) Never ever change prices. Unless you're making the product cheaper. If I were to sign up for a service that increased its prices, I would just try and find alternatives. As a customer, it feels like I'm being cheated. Instead, label it as an early bird offer. 30% off in the first 3 months kind of thing. Comes off a lot better.
- Presnus 14y agoThanks for the tip. The early bird offer sounds really good!
- adam-_- 14y agoWhat's the point in launching polished features that nobody wants? Much better to release unpolished/limited features to a set of users and solicit feedback on what they're really after. Then you can release more polished/complete features and market more widely and solicit more feedback and rinse and repeat to profitability (admittedly I say this as someone that has not done this yet but plans/hopes on it).
- andremedeiros 14y agoI honestly wish you good luck. I've had too many occasions where, when evaluating a service that didn't quite do it for me. You can't expect customers to register and pay you money for a service when a) it doesn't do everything they need, and b) there is no certainty that it will ever do everything they need. Grhmpft... software is hard. Let's go shopping!
- AznHisoka 14y agoThere's a middle path. Release it even when it's not done, but don't go full throttle on marketing.