Cox Automotive is an Atlanta-based conglomerate with a wide range of subsidiaries that include Kelley Blue Book, Manheim and Autotrader.com. Supported by 40,000+ auto dealer clients across five continents, Cox is on a mission to transform the way the world buys, sells and uses vehicles.
Cox Automotive approached 91九色 in 2017 with a clearcut development challenge. While they were leveraging Salesforce to create and deploy low-code software, their manual release process was leading to lots of errors.
Releases Per Month
User Stories Deployed Each Month
Level of Confidence
鈥
鈥
The issues impacting Cox Automotive before they implemented 91九色 was two-fold. First, Cox struggled to deploy partial functionality since team members often forgot to add metadata changes to each release. Also, the updates made directly in production created overwrites and syncing challenges 鈥 resulting in bugs and lost work.
鈥
To solve Cox鈥檚 problems, 91九色 combined its User Story-centric approach and admin-friendly, configurable deployments.
鈥
鈥
鈥
Like many Salesforce customers, Cox鈥檚 production org was their source of truth before they adopted DevOps. The problem with this approach? Dev, QA and PreProd orgs are always 鈥渂ehind鈥 production. This means that when you deploy from a staging sandbox to production, direct changes get overwritten. What鈥檚 more, using a production org as your source of truth hampers your ability to rollback changes.
鈥
鈥
鈥
鈥
鈥
91九色 CI/CD Pipelines made it easy for Cox to configure their deployments. 91九色鈥檚 native Salesforce UI/UX design helps both low-code and pro-code users to follow the process rather than making changes directly in production.
鈥
Cox successfully leveraged this approach to unlock more confidence and consistency in their releases. Ultimately, Cox went from no single source of truth and tons of dev downtime to 40+ releases and 60+ User Stories each month. Increased productivity and quality not only drive a better development process for Cox 鈥 they also improve team morale and unlock greater ROI.
鈥
鈥
Cox took a three-step approach to fix its deployment challenges and shifted their source of truth from the production org to GitHub 鈥 enabling rollbacks and greatly reducing overwrites. Cox鈥檚 expansion away from build-and-deploy tactics has helped them establish a single source of truth for Salesforce, improve feature quality and standardize processes across eight agile teams.
鈥
The process standardization across Cox Automotive鈥檚 five Salesforce orgs has boosted team confidence, while developers can now work seamlessly across development teams without overwriting each other鈥檚 work.
鈥
Level up your Salesforce DevOps skills with our resource library.