Every disconnected tool is a tax. Someone exports a CSV, cleans it, and pastes it somewhere else — every week, forever, until it breaks at the worst possible time.
You don't need a platform migration to stop the bleeding. You need to pick the single worst manual handoff and wire it shut.
Find the handoff that costs the most
Not the biggest system. The most repeated moving of data by hand. Ask the team one question: "What do you re-key or re-export on a schedule?" The answer is your first target.
Tip
Score handoffs by frequency × blast radius. A five-minute copy-paste done daily, feeding revenue reporting, beats a painful-but-rare quarterly export every time.
Wire it as a governed sync, not a script
A cron job that moves data is not an integration — it's a new thing that breaks silently. A governed sync has three properties a script usually doesn't:
- A contract. Both sides agree on the fields, types, and what "valid" means.
- Idempotency. Running it twice doesn't create duplicates or double-count.
- Observability. When it fails, someone knows — before the numbers are wrong.
Watch out
The most dangerous integration is the one that fails quietly and keeps reporting success. If you can't answer "how would we know this broke?", you haven't finished building it.
One handoff is a foothold
Fix one and two things happen: the team gets time back, and you've proven the pattern. The next handoff is easier, and the one after that. That's how a stack grows a spine — incrementally, with governance, not in a big-bang rebuild nobody has the budget for.
That progression — map what exists, wire what matters, own what comes next — is the whole idea behind the Integration Spine™.
Related tipFormAssembly → Salesforce: the mapping mistake that silently drops leadsMore Bytes
Integration & RevOpsInstrument one lifecycle stage before you automate it
Automation applied to a process you can't measure just makes the mistakes faster. Add the measurement first, then automate.
Integration & RevOpsBuy vs. build: when a custom integration actually pays off
Off-the-shelf connectors are the right default. Here's how to tell when your case is the exception that justifies building.
Integration & RevOpsFormAssembly → Salesforce: the mapping mistake that silently drops leads
Your form submits, the connector says success, and the lead never lands. Here's the field-mapping trap that swallows records without an error.
