Skip to main content
Andrew Brown
Gainsight Employee ⭐️
Gainsight Employee ⭐️
September 3, 2026
Product Update

Introducing a New Release Cadence and Beta Feature Center in Gainsight CS

  • September 3, 2026
  • 42 replies
  • 990 views

TL;DR

Starting September 19, 2026, Gainsight CS will release new features and enhancements on a six-week cadence.

That means one consistent schedule for product updates throughout the year, whether a release includes focused improvements, larger capabilities, or a mix of both. The six-week rhythm also builds on a cadence many customers already know from our On-Demand releases.

As part of the change, we’re also introducing the Beta Feature Center, which will give admins one place to discover eligible Open Beta features as they’re introduced going forward.

 

A Simpler Way to Keep Up With What’s New

Until now, Gainsight CS updates have come through different release motions, including standard and On-Demand releases. We’re bringing those together into one six-week cadence, which gives you a clearer schedule to follow and removes the extra step of submitting a support ticket to access eligible features.

Rather than reserving certain types of updates for different release moments, each release can include the features and enhancements that are ready. This gives teams a more consistent rhythm for planning, adoption, and communications without creating long gaps between releases.

For features that require admin action or configuration, the experience will remain similar to the standard release process customers are familiar with today. Admins will continue to have visibility into what’s changing and what, if anything, they need to do before a feature is available to users.

When each release goes live, you’ll get the full breakdown through Release Notes, in-app communications, and our release newsletter so you can quickly understand what’s new, what requires attention, and where to learn more.

With this more frequent release cadence, we’ll also no longer publish separate Early Access Release Notes. Instead, we’ll focus on sharing the most current information at the time of release, when features are ready for customers to use.

 

A New Home for Open Beta Features

As the release cadence becomes more consistent, we’re also updating how admins discover Beta features in Gainsight CS.

The Beta Feature Center will give admins one place to discover and manage eligible Open Beta features. Open Betas will align with the six-week release cadence, and their Beta toggles will be removed once the feature becomes generally available.

 

What’s Next?

The first release under the new cadence is September 19, 2026, followed by the next release on October 31, 2026. From there, you can expect a new Gainsight CS release every six weeks.

With each release, we’ll share details on what’s included and call out any setup, configuration, or preparation admins should be aware of. The goal is a release process that’s easier to follow throughout the year, with one consistent rhythm for what’s new and what comes next.

    42 replies

    jason_metzler
    Helper ⭐️⭐️
    September 8, 2026

    Appreciate the move toward one predictable cadence — the support-ticket step for On-Demand access was never great. My concern isn't speed, though, it's control.

    When changes land in my environment without me having reviewed them first, I lose trust with my own team. It's already hard enough to get CSMs to use the platform correctly. If new behavior shows up that I didn't flag or can't explain, it reads to them as coming from an unknown source, not from admin — and that undermines adoption more than a longer release wait ever would.

    For anything GA-level, especially features enabled by default or that change existing workflows, I'd still want the same advance notice we get today so we can review, prep our teams, and flag issues before it's live. Smaller enhancements probably don't need that same runway — those can move on the faster cadence without an issue.

    +1 to Jack's point above on in-app comms too — if end users see release messaging the same day it ships, admins need visibility into that content before it reaches our teams, not alongside them.

    darkknight
    Expert ⭐️
    September 8, 2026

    Smaller enhancements probably don't need that same runway — those can move on the faster cadence without an issue.

    I don’t entirely agree with this - it really depends on what the “smaller enhancements” are and how invasive they might be. I don’t necessarily trust Gainsight’s product team to be able to make that decision, especially when Gainsight is a platform that can be used in so many different ways.

    @Gainsight - As you can see, there are a lot of folks concerned with this approach and largely see it as a regression.

    Gainsight CS is not a lightweight, limited-purpose product like Loom, Calendly, Miro, etc. where a feature update or UI change has little to no impact on underlying data, integrations, or business logic. Gainsight is a mission-critical enterprise platform powered by complex data pipelines, processes and automations upon which businesses depend and expect to work with minimal to no disruption.

    Gainsight’s track record with release management, as ​@bradley alluded to in his comments above, have not justified or earned the level of trust these changes seem to demand. Moving forward with this approach without giving us the adequate lead time to evaluate impact will further erode the trust and confidence in the platform and Gainsight as a partner.

    Jeff Kirkpatrick
    romihache
    VIP ⭐️⭐️⭐️⭐️⭐️
    September 9, 2026

    I strongly echo the points made above!

    We are already juggling in-app comms and features being enabled by default… and now early release notes are being taken away? Without early release notes, we simply can't plan our roadmaps or flag potential system impacts in advance. This approach constantly forces us admins into reactive troubleshooting rather than proactive change management.

    A predictable cadence only works if admins hold the keys. Please reconsider keeping the early release notes and ensure that all future rollouts default to OFF or Private, letting us test and enable features when our teams are actually ready,

    Continuous improvement is better than delayed perfection
    Jef Vanlaer
    Helper ⭐️⭐️⭐️
    September 9, 2026

    While fast innovation always sounds nice, I have some concerns with this announcement as well:

    • As many people above have already pointed out, there’s only so much change people (admins and end-users) can handle. People need time to adapt their way of working, for enablement and getting used to changes (however small) to their workflow. We’re only a small CS team and pretty agile in reacting to change, but I can already see this play out here; the challenge for enterprise businesses will be a lot bigger.
    • Faster releases often come at a cost of lower quality, as the pressure to deliver in time increases. Will there be additional efforts to ensure proper testing and bug fixing, making sure the release meets customers' high quality standards?
    • Finally, the removal of the Early Release Notes is probably my biggest concern. If we don’t know what’s coming (and then I’m not talking about a high-level ‘this is what we plan to release at some point in the future’ story), we will be chasing product changes after the fact, turning our CS Ops teams into reactive firefighters instead of proactive value-creators.

    Gainsight moved from monthly to quarterly releases and introduced the early release notes before for exactly these reasons. This announcement sounds like taking a few steps back.

    Yes, the introduction of the beta releases might have had limited success, given the tedious approach of requesting access to beta features. The Beta Feature Center is a step forward here. But why not keep a quarterly release with early release notes for GA functionality and release beta features through this new Beta Center at a higher cadence? That feels like the best of both worlds to me...

    alizee
    VIP ⭐️⭐️⭐️⭐️⭐️
    September 9, 2026

    I echo much of what’s been said already. 

    On the one hand you state: 

    With this more frequent release cadence, we’ll also no longer publish separate Early Access Release Notes. Instead, we’ll focus on sharing the most current information at the time of release, when features are ready for customers to use.

    On the other: 

    With each release, we’ll share details on what’s included and call out any setup, configuration, or preparation admins should be aware of

     

    Everything and its contrary is being said in this post. Please clear this up. 

    Seems just a tad contradictory. How exactly are we to “prepare” if we don’t have EA release notes? Is every release going to be on-demand? That’s not what I’m reading in this post. You state standard and on-demand. We surely need EA release notes for standard releases. 

    And as others have said: please don’t advertise new features to end-users. That puts admins in an illegitimate uneasy position with you, Gainsight, and our end-users both pressurizing us to adopt something that’s potentially unfit for our needs or governance. 

     

     

     

    The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
    kstim
    Helper ⭐️⭐️
    September 9, 2026

    Echoing the concerns above. Losing Early Access Release Notes removes the only window we had to test changes against our own instance before they go live -- we’ve hit real production breakage before that we only caught because of that lead time. Without it, we find out the same way our end users do.

    Also concerned about end-user in-app comms going out at release time with no admin gating first -- especially for AI-related features, where several of us are still working through internal privacy/security reviews.

    The Beta Feature Center is a nice add for opt-in trials, but it’s not a substitute for advance notice on what’s mandatory in the next release. I’d like to see Gainsight commit to some minimum preview window before this cadence starts.

    nsimon
    Contributor ⭐️⭐️⭐️⭐️
    September 9, 2026

    Solo admin here, seconding many of the concerns above. 

    Nichelle S. - LeagueApps
    kelcijowalker
    Contributor ⭐️⭐️
    September 9, 2026

    I agree with the concerns of the other users here. I think Heather said it well, having more control on features to turn on/off helps with adoption and allows admins to determine whether or not they are useful for their teams or if it will cause problems.

    victoria_peeker_barry
    Contributor ⭐️⭐️⭐️⭐️⭐️
    September 11, 2026

    I agree with all the concerns above...and would really appreciate a discussion on this.
     

    • We need advance notice of what is coming - and need to be able to prepare and decide if OUR org is ready for it
    • Gainsight releases have not been trouble free lately - so trust needs to be earned back
    • Definitely NOT ok to reach out to our users in app to let them know about new functionality - as Gainsight does NOT know if it meets our use cases
    • We need to ensure enablement is aligned with roll out
    • we need ability to opt out of releases like we did before if this moves forward
    • More frequent - means MVP and not full functionality based on previous experience and many orgs will not be able to accept MVP for their use cases - especially if it does not connect to other critical components - like Goals were not connected to timeline   
    Victoria
    darkknight
    Expert ⭐️
    September 11, 2026

     @Andrew Brown I know Gainsight is OOO today for a “recharge day” but given that September 19 is only 6 business days away, we need a response (and preferably a conference call to discuss) from Gainsight on this ASAP.​

    Jeff Kirkpatrick
    manu_mittal
    Gainsight Employee ⭐️
    Gainsight Employee ⭐️
    September 11, 2026

    There have been plenty of instances where a feature has launched turned on & not gated to admin review.

     

    You’d have to hunt around to find what broke in your instance or workflows needed adjusting.

     
    It also allows me to get in front of any changes that will affect my stakeholders before panic comes about. 
     
    I also think there needs to be a way for customers to control when newly released functionality is exposed to their users.
     
    We need to know in advance what’s coming to be able to ensure it isn’t breaking something within our workflow or violating our Security/Privacy policies.
     

    This is exactly what I want us to be held accountable for, rather than assuming disruption. With these releases, anything deemed disruptive to existing workflows will have an admin gate, configuration, or feature flag so you can plan the rollout. I wanted to make sure this point doesn’t get missed.

    Making features available on demand but then turning them on with the main quarterly release (existing cadence) was a heads-up-based approach. With the new cadence, we’re instead focusing on no/low disruption as a principle.

    That said, there’s still appetite for knowing what’s coming and what’s planned. Let us come back with some thoughts on how best to do this. Maybe we can post or send an email covering what’s planned (not confirmed) to provide visibility and give people an opportunity to react.
    darkknight
    Expert ⭐️
    September 11, 2026

     ​@manu_mittal we “assume disruption” because of repeated past experiences where we have been bitten (or almost bitten had it not been for the 2-week advance notice).

    “anything deemed disruptive to existing workflows will have an admin gate” who is determining what is disruptive to existing workflows? Gainsight is a platform that can be used in many different ways - it seems impossible for Gainsight to be able to know and keep track of every customer’s use cases and ensure that every six week release won’t have impact.

    You’ve been around as long as, if not longer than, I have Manu, and you know the history with all the releases and the problems we’ve had over the years. Those detailed advance release notes have been critical for awareness, advance preparation and for us to give immediate feedback on changes that seemed amiss, would have impact, etc. and Gainsight pivoted at the last minute to minimize impact. One example that comes to mind was when they introduced the ability to have non-Objective CTAs used in Success Plans, and the plan to remove Objective Category, when business workflows were already heavily dependent on that field and removal would have had immediate impact. Had we not been able to give direct feedback through those release notes, resulting in the Objective Category field remaining in intact, this would have directly impacted users.

    The 2-week advance release notes is a critical component in any ability to have trust and confidence in the release process.

    Jeff Kirkpatrick