[cbono1]

Would you have the staging environment share data with production or have its own infrastructure? or use feature gating? One customer may not care that it shares the same DB, but another might.

How would this work at scale? say if there were say 10 customers wanting approval, you'd have to have separate code release branches/versions for each customer? I imagine this could get error prone.

I suppose to your point on charging additional fees for this you can afford any sort of workflow.

[daniellarusso]

From your description, yes, you would basically have forks of your codebase for each customer and deploy that to a sandboxed staging server.

That would be used for acceptance testing.

Bonus points for having up-to-date data in the staging DB.

I assume this is a multi-tenant implementation.

The other option is to charge the customer to disable unwanted features, in addition to enhanced features.

If it is multi—tenant, having the ability to ‘feature-gate’ could be worth the effort, if you can charge for enabling AND disabling features.