2 ms·

Yeah I totally agree - in no way should your company's software be dependent on the continued existence of my service. My thinking on this is that the service I

Yeah I totally agree - in no way should your company's software be dependent on the continued existence of my service. My thinking on this is that the service I'm offering needs to be sliced up into opt-in units - $X/month for the builder, cost-plus for hosting and scaling, gateway fee for ecommerce and so on. That way, companies that want to scale out can mix and match the offering as they choose. I am somewhat concerned that someone could build most of their app and then export the code and cancel, but as I'm still building out the MVP I'll leave that for later :)

startupdiscuss 10y ago
Don't be afraid of that, you should be happy to have that as a service and encourage some people to do that if they want. I think 98% of the people will end up exporting their code and not using the service. It will be free. But it will make your service famous and the few people who do pay will be loyal. You can't do everything well. If the main thing you do is an MVP producing service, that is great. Add on to that. You might end up adding a whole different set of services such as paying for user feedback or user analysis or something else. Edit: Just to be clear - I don't mean to advise you on what the service should or should not be. I just mean that it will evolve in ways you may not anticipate. The market will pick and choose what it wants. The things you initially think are small might turn out to be more profitable than the things you initially think are big.
- beaconstudios 10y ago
  I'm not really aiming for an MVP service in the long run though - I want to enable people to scale out their idea into a full product without having to export and start coding. I also don't think I would be keen to build this as a completely free (or effectively free) service, as this is going to be a big project and I want to scale it out into a business. I don't want to lock in users either though, so I'm aiming to find a good point where the product provides enough value that users would prefer to keep using it over exporting and coding.

startupdiscuss 10y ago

Don't be afraid of that, you should be happy to have that as a service and encourage some people to do that if they want. I think 98% of the people will end up exporting their code and not using the service. It will be free. But it will make your service famous and the few people who do pay will be loyal. You can't do everything well. If the main thing you do is an MVP producing service, that is great. Add on to that. You might end up adding a whole different set of services such as paying for user feedback or user analysis or something else. Edit: Just to be clear - I don't mean to advise you on what the service should or should not be. I just mean that it will evolve in ways you may not anticipate. The market will pick and choose what it wants. The things you initially think are small might turn out to be more profitable than the things you initially think are big.

beaconstudios 10y ago
I'm not really aiming for an MVP service in the long run though - I want to enable people to scale out their idea into a full product without having to export and start coding. I also don't think I would be keen to build this as a completely free (or effectively free) service, as this is going to be a big project and I want to scale it out into a business. I don't want to lock in users either though, so I'm aiming to find a good point where the product provides enough value that users would prefer to keep using it over exporting and coding.