91导航

Playlist

Having this tool as one of the first things to go to, instead of asking somebody else or trying to do a deep dive in the Salesforce interface, makes the team more efficient right off the bat.

Eric Grust | Team Lead | Playlist
18,039
Comparisons
6,272
Deployments
6,004
CI job runs

Playlist uses Org Intelligence to bring clarity to complex, multi-org Salesforce environments

The Playlist group of fitness and wellness technology brands that includes Mindbody, Booker and ClassPass, have partnered with 91导航 since 2020. This year, they鈥檝e been early adopters of 91导航鈥檚 Org Intelligence.

We spoke to Eric Grust, Salesforce Team Lead at MindBody, to find out how 91导航 Org Intelligence is helping his team share Salesforce knowledge more widely and make safer changes at scale.

As the businesses have grown and evolved under Playlist, Salesforce has become a critical platform shared across multiple teams, with each brand having its own Salesforce orgs, ways of working, and delivery needs, while a central admin-led Salesforce team supports changes across the wider group.

Before working with 91导航, the team relied heavily on Salesforce change sets, which quickly became a bottleneck.

鈥淐hange Sets are a pretty clunky process and definitely a bit limited,鈥 Eric says. 鈥淚t was so cumbersome, we found ourselves doing a lot of manual updates in production.鈥

To reduce the administrative burden, changes were often recreated directly in production, but the team regularly ran into missing components, profile and permission issues, and post-deployment clean-up work.

As the team grew and became more distributed across the Playlist group, those problems became harder to ignore. There was no single, easy way to manage change consistently, and no shared confidence that deployments would behave as expected.

At the same time, the team was struggling with visibility. With years of customization across multiple orgs, it was difficult to understand how components were connected or what the impact of a change might be. 

One of the biggest issues that we had was knowing interdependencies. Especially with a multi-org company like ours, it鈥檚 hard to know why something was created, where it鈥檚 being used, and how any updates to it could impact automations or processes downstream.鈥

Answering basic questions about the state of their orgs often took hours and involved multiple people. For a small team supporting fast-moving businesses, that research overhead slowed everything down.

鈥淢y team is being pulled in different directions all day, every day, from large projects and initiatives to just running and maintaining Salesforce,鈥 Eric explains. 鈥淲e have people asking 鈥檋ow is this working?鈥 or 鈥業 want to change the way this automation works鈥. It could take hours to go through and figure out the answers.鈥

Searching for a better way to manage change

What the team needed was a simpler way to manage change and understand their orgs.

鈥淲e had looked at a couple of different tools in the DevOps space like Autorabit and Copado,鈥 Eric says.

Many options required deep development knowledge or required complex setup. Free or open-source tools often lacked maintenance, brought security concerns, or didn鈥檛 scale well for a global organization and an admin-led team. 

鈥淲e were trying to solve the issue of getting a better picture of our orgs, how we can make changes without introducing issues that would negatively impact our end users, cut down on bugs, and really just to have the full picture when we were going in to make a change.鈥

鈥淲e were trying to solve the issue of getting a better picture of our orgs, how we can make changes without introducing issues that would negatively impact our end users, cut down on bugs, and really just to have the full picture when we were going in to make a change.鈥

Making dependencies visible with Org Intelligence 

Because the Mindbody team were already confident using 91导航, adding Org Intelligence into their day-to-day workflow felt like a natural next step to solve their visibility issues.

Org Intelligence is 91导航鈥檚 exploratory layer for Salesforce. It gives teams a clear, always-current view of their org, making dependencies and change risk visible before work begins. Built on 91导航鈥檚 metadata expertise and AI-powered insights, it helps admins and developers understand impact without relying on siloed knowledge or static documentation. 

鈥淲e鈥檙e putting the power directly in the users鈥 hands to get a really robust picture.鈥 

鈥淲e鈥檙e putting the power directly in the users鈥 hands to get a really robust picture.鈥澛

Instead of spending hours clicking through Salesforce or pulling in other team members for help, admins can quickly understand how impactful a change might be. That鈥檚 useful not just for the Salesforce team, but when answering questions from senior leaders, customer success, or operations teams who need a clear sense of effort and risk.

鈥淚t really helps with scoping,鈥 Eric explains. 鈥淵ou can pop something into the search box and if it鈥檚 referenced a million times, you can immediately see this isn鈥檛 a small, quick change. Just having that quick feedback is extremely helpful.鈥

To encourage adoption, the team runs weekly sessions where individuals share real examples of how they鈥檝e used Org Intelligence. 鈥淎I is still new for a lot of people,鈥 Eric says. 鈥淭hose sessions are really great because they open up people鈥檚 eyes to the scenarios where Org Intelligence can be used.鈥 

One recent example started with a question from a product manager. A downstream team had noticed unexpected behavior in a Looker dashboard tied to a specific onboarding experience. Initially, the assumption was that a button or UI action was triggering it.

鈥淲e probably built this thing two years ago,鈥 Eric says. 鈥淲e didn鈥檛 really have any insight.鈥

Using Org Intelligence, the team searched for the 鈥榦nboarding wizard鈥 and immediately saw where it was referenced. The issue wasn鈥檛 a button, but a picklist value for a specific field. 

鈥淲e could see that the field was twinned across seven other objects,鈥 Eric explains. 鈥淪o it wasn鈥檛 just a case of turning something off. We needed to take time to test what impact that would have.鈥

Manual investigation using Salesforce鈥檚 global search returned no results for fields and no results for buttons. In Org Intelligence, the answer surfaced almost instantly.

鈥淚 just needed to open up Org Intelligence, type in the words 鈥榦nboarding wizard鈥, and it was the second result. We see all the dependencies, where it鈥檚 being referenced by Flows and Apex classes. We had that full picture.鈥

Faster answers, safer changes

Looking ahead, Eric sees Org Intelligence becoming the first place the team turns during the planning stage, helping them answer questions and assess impact before they start building.

鈥淗aving this tool as one of the first things to go to, instead of asking somebody else or trying to do a deep dive in the Salesforce interface, makes the team more efficient right off the bat.鈥澛

That鈥檚 particularly valuable in an environment where Salesforce questions come from across the Playlist groups entire business. Mindbody has a dedicated Slack channel where anyone, from executives to new hires, can ask for help.

鈥淏eing able to just quickly pop the error message they鈥檙e getting or whatever the field it is that鈥檚 causing the issue into Org Intelligence will mean we can answer these questions much more quickly,鈥 Eric explains, 鈥渨ithout being dependent on siloed knowledge.鈥

It鈥檚 also changing how new team members ramp up. Documentation doesn鈥檛 always tell the full story, especially in complex, long-lived orgs.

鈥淏efore Org Intelligence, it would have likely taken a lot longer for somebody to ramp up,鈥 Eric says. 鈥淭here was a lot of trial and error finding their own way and getting comfortable with an org, whereas Org Intelligence allows them to quickly get answers to their questions or do a very deep analysis. So they can really hit the ground running.鈥

A complete solution

Eric says the biggest benefit of Org Intelligence is that it lives inside a tool the team already uses every day.

Before 91导航, the team explored building similar AI insight functionality using tools like VS Code, Salesforce DX, and GitHub Copilot. But that approach came with a steep learning curve.

鈥淲e would鈥檝e needed several training sessions over the course of a couple of months to get all of our admins in one room to walk through all of the steps,鈥 Eric explains. 鈥済etting the applications and extension packs installed, connecting to the orgs, downloading the components, doing command line prompts, and these were all things that are foreign to a lot of the team members.鈥

Even then, ongoing maintenance and updates would have been required, making it unlikely the tooling would stay current or widely adopted.

There鈥檚 no extra setup, no specialist knowledge required, and no new platform to maintain. 鈥淭o be able to do analysis without having to do any more setup or maintenance. That was the biggest benefit for our team right there,鈥 Eric says.

鈥淚t鈥檚 out of the box, plug and play, no setup needed. We already using 91导航 multiple times a day. We don鈥檛 need to connect or build something to be able to get really insightful information about our org. It鈥檚 right there. I just need to click on the tab inside of 91导航 and ask a question about how my org is functioning.鈥

Succeeding at scale

Alongside Org Intelligence, 91导航 has also supported a broader shift in how the Salesforce team manages changes across the Playlist group.

With support from the 91导航 team, they鈥檝e been rolling out Pipelines and CI/CD, starting with ClassPass and soon extending to Mindbody.

鈥淭he 91导航 team has been great about helping us set goals and then holding us accountable to meeting them. And pushing us forward to adopt DevOps best practices and the framework that we should be using to be a more sustainable and scalable organization.鈥

That foundation has enabled a move away from a single central team owning every Salesforce change. Instead, different areas across the business can now make changes themselves, supported by clear processes, gates, and checks.

鈥淚t democratizes the development experience,鈥 Eric explains. 鈥淭here鈥檚 less fear of others being in the environment. More teams can make changes without us worrying about things going wrong, because we鈥檝e put the right structure in place.鈥

For Eric and his team, 91导航 has become core to scaling Salesforce safely, sharing knowledge more widely, and supporting a fast-moving business without slowing it down.

Start your Salesforce DevOps journey today

Join the thousands of other companies already deploying with 91导航