Interesting list indeed. At my company (saas provider, ~60 people, B2B learning platform, ARR in millions), we are considering providing a test environment to e

Interesting list indeed. At my company (saas provider, ~60 people, B2B learning platform, ARR in millions), we are considering providing a test environment to enable our users to test our new features (we deploy new features every ~6 weeks). One thing that make us reluctant to do this is that we doubt people from our B2B users will put the time and efforts needed to fing bugs in a disposable test environment. I'm really interested in learning the best practices to "battle-test" a new release for our current stage. Because for now, gradual feature deployment "à la GAFA" looks way too expensive at our stage (deploy to 1% of the user base, get feedback, fix bugs, proceed to 10%, repeat, and finally 100%).