4 ms·
It would depend what the scalability of your service was - if your service set up one server, and 3 days later I need 40 more identical ones up in the next half
by A1kmm 16y ago
It would depend what the scalability of your service was - if your service set up one server, and 3 days later I need 40 more identical ones up in the next half-hour, without having to manually re-enter all the settings, would your service be able to handle that? I think that would probably need to be in the minimum viable feature set.
Even with that said, I think that I would normally prefer to vertically integrate that type of work into a startup (incremental adjustments to the deploy script during dev, technical founder uses the deploy script during early days, when the business grows, a dedicated sysadmin will be required anyway) - but that does depend on the price and exactly what is offered.
If you pitched it as:
* Our core business is to license common deployment scripts (i.e. the scripts are commercial software, and you sell a license to use them).
* For a small fee, you can use our web interface to help you generate a customised version of our script - or you can edit the script yourself.
* For a small fee, we can also keep track of all your deployments and deployment scripts, and run your deployment scripts for you on demand via a web interface.
then the value proposition might make it worthwhile if the price was right.