Consolidating two sales-engagement systems into one: 22 cadences rebuilt one-to-one

The problem

The play

1. 1
   Cadence migration, one to oneGong

   Rebuilt all 22 cadences in Gong Engage, matching steps, timing, subject lines, threading and copy, and standardised exit rules on the platform's default ruleset instead of carrying over the per-cadence exceptions that had accumulated in the old tool.

2. 2
   Governance so the sprawl does not rebuild itself

   Shipped a cadence-governance plan covering naming, ownership and approval for new cadences. A one-to-one migration without governance just relocates the problem to a newer tool.

3. 3
   Consent-compliant conversation-intelligence rolloutGong

   Configured recording-consent profiles region by region to match each operating region's requirements, completed the Gong–Salesforce integration, and activated contact creation and activity sync so the CRM and the conversation-intelligence platform reconcile against one activity record.

4. 4
   Pilot to general-availability readiness

   Moved the conversation-intelligence pilot to GA readiness with proactive monitoring and a full documentation and FAQ set for reps, so rollout support did not depend on a single admin answering questions.

5. 5
   Transcript access decoupled from seat cost

   Built an automation-platform pipeline from the conversation-intelligence tool into shared cloud storage, using a dedicated integration account and a shared credential vault, so approved non-sales users can read raw call transcripts without a paid seat, with retention aligned to the company's existing privacy obligations and legal review in progress.

What it moved

From a LeanScale case studyRead the full case study →