When to connect your tools — and when to consolidate them
Integration or consolidation? A decision framework for messy software stacks: where webhooks and APIs are the right glue, and where a single platform ends the glue entirely.
I spend a lot of my week connecting software that was never meant to talk. Sometimes that's exactly right. Sometimes it's a sign the stack itself is the problem. Here's how I decide.
Connect when the tools are best-in-class and stable
If each tool is genuinely excellent at its job and rarely changes, glue them with webhooks and APIs and move on. Integration is cheap insurance against lock-in when the pieces are strong.
Consolidate when you're syncing the same data five ways
The tell is duplicated data. If a contact exists in your form tool, your CRM, your email platform and your spreadsheet — and you've built automations to keep all four agreeing — you're not integrating, you're papering over a structural gap. That's the boundary tax, and no amount of clever automation removes it.
The middle path
Consolidate the core — records, marketing, automation and reporting on one spine — and integrate the specialist edges (accounting, e-sign, telephony) around it. You get one source of truth and still keep the tools that are genuinely irreplaceable.
How to actually decide
List every place a customer's data lives. For each, ask: is this tool irreplaceable, or is it here because migrating felt hard? The honest answers usually draw the line for you.
This is the work I do with clients — mapping the stack, then building the connections or the migration. Learn how I can help →, or read about switching CRM cleanly.