Your business is a money making machine. There are many components. Absolutely all of the components are hot swappable. Make each component work until the entire machine does. If one component fails, swap it out with something entirely different if you have to. As long as it keeps the machine working, it doesn't really matter what it looks like.
Become attached only to the machine as a whole, not the individual components it's made of.
It is like the difference between writing code with configuration variables embedded in hundreds of places in the code or building it with a user interface to allow the customer to adjust the settings.
It seems like big products have huge releases. How can we prevent people from quitting our application if they don't like the big first release?
As an serial entrepreneur I would say that startups are not but organisms, but organism that need bootstrapping (no not the ”business bootstrapping” – shoestring budget model – but… ) the original sense of the word, a system need to initial criticai mass and parameters to start working like an organism…
That is what the entrepreneur does, force the catch-22’s into a critical mass that starts growing like an organism.
A startup is almost by definition in an exploring phase. Key to success (and infinite richness of course) is to acknowledge this fact and build your startup as a learning entity.
The consequence of this insight is that it's counter-productive to keep things secret or wait too long until launch.