The dev team will likely say something along the lines of "it isn't a big deal we can handle it easily and when it becomes overwhelming we'll build it then". When it becomes overwhelming it's too late.
If you build this interface now it will force your product and dev teams to think about how every new feature will be toggled on / off. This is also a good thing. Yes this adds overhead. Yes there will be forces that say this is a complete waste of time but if you are planning on succeeding then this is a must have, not a nice to have.
A couple of essential things happen when you have this tool:
- It frees up valuable dev resources and allows them to focus on writing new code, not performing repeatable tasks that aren't adding value to your code base.
- It allows the deployment team to function outside of formal production pushes / sprint planning / whatever methodology you are using.
- It allows the sales team to spin up an instance for those high profile prospects that just can't get their heads around how it would actually function for them. Imagine showing up for the pitch with a functioning branded instance configured mostly the way it would need to be? This beats the hell out of a set of mockups.
- This also means that in terms of collecting and recognizing revenue it can be done as quickly as a non-dev can spin up an instance and hand over any other details a client would need to be up and live. Depending on how your standard contracts are structured this could be just an implementation fees OR it could be the license fee itself.
