Reliable DevOps powers Intercom’s success
Intercom’s team overcame deployment challenges by adopting Gearset and transforming their entire Salesforce DevOps process. Within only two weeks, the team had been fully onboarded and had begun setting up their automation pipelines. Since adopting Gearset the team has grown to over 30 and are continuing to deliver on major projects, including CPQ. Gearset has armed Intercom with the tools needed to stay agile and deliver big projects without disruption.
Scaling success by adapting Salesforce
Intercom, the world’s first conversational relationship platform, began using Salesforce a couple of years after launching in 2011, and adopted Gearset in 2020.
To find out about Intercom’s DevOps process for Salesforce, we caught up with Dan Pietersen, a software engineer on the Business Systems team. Intercom makes good use of the ability to customize Salesforce, as Dan explains: “Salesforce has had to grow with us and we’ve had to adapt it in many ways”.
Dan’s team is responsible for Intercom’s entire Salesforce instance and is made up of a mix of business systems analysts (admins), business systems engineers (devs) and their managers.
Inadequate tooling led to inconsistent processes
Right from the get-go, the Business Systems team opted for an agile release process for their Salesforce deployment pipeline. “We adopted the philosophy that the rest of Intercom uses,” Dan explains. “We continuously ship. We don’t do biweekly or monthly release cycles. We don’t have a release manager per se.”
But the team had a problem:
When deployments worked, the release process was okay. But for Dan and his team, the situation was fast becoming unsustainable. “The biggest pain point was definitely reliability. When the tool broke, deployments took several days.” This unreliability was blocking progress, and Dan’s team were planning to deliver two important projects: CPQ and Interconnected, Intercom’s community forum hosted on Salesforce communities.
The search for a better solution
Dan was the driving force behind the search for a better Salesforce deployment solution. Once he spoke up about the issues he was facing with the old tool, colleagues began contacting him about the problems they were also experiencing. It was clear to Dan that it was time to move on.
One of the Salesforce engineers had previous experience of Gearset and recommended it as a reliable DevOps solution which could provide automation and CPQ deployments. Dan and his team evaluated several options to make sure they found the solution that ticked every box.
For Dan, a few things stood out about Gearset: its modern UI, the problem analyzers that solve common deployment issues, and Gearset’s change log showing daily updates and improvements to the app. It looked like Gearset was the answer to the team’s problems.
GitHub was already used extensively throughout Intercom, and so the Business Systems team decided to adopt GitHub alongside Gearset in order to build a Git-based development workflow. Getting started was straightforward and the team felt fully supported by Gearset’s dedicated onboarding managers.
Firing on all cylinders with Gearset and GitHub
Intercom’s Salesforce DevOps process is now running smoothly. The Business Systems team ships at least 3-4 times a day, a cadence that was previously interrupted whenever their old tool broke.
The team have two Git branches, “full” and “main” — corresponding to their full sandbox and production org. Admins and developers develop in their own sandboxes, deploy to branches off “full” and open a pull request (PR) to be reviewed and merged. Creating that PR triggers a validate-only CI job in Gearset, which runs tests against the full sandbox. Merging the PR kicks off another CI job to deploy the changes. Once changes have passed UAT in the full sandbox, changes are promoted from the “full” branch to the “main” branch, using the same PR review process — triggering CI jobs that test and then release changes to production.
For select metadata types, the Business Systems team allows changes to be made via the UI in production. They use CI jobs that run every 4 hours to deploy these simple changes back from production to their Git repo, keeping everything in sync.
Freed up to focus on projects not process
“We’ve definitely seen the benefits from switching over to Gearset,” says Dan.
One of the other benefits of a robust and reliable process is that the team now pays closer attention to their testing results.
Intercom recommends Gearset for Salesforce DevOps
Gearset has enabled the Intercom team to build the Salesforce DevOps process they envisioned, while seamlessly scaling to support their team of 30. “If you want to get your projects done in a time-efficient way, I’d definitely recommend Gearset,” says Dan.