The Integration Tax: What Disconnected Systems Really Cost
Every institution running a student-information system and a CRM that don't talk to each other is paying a tax. It just doesn't show up as a line item.
There's a cost that never appears in a budget review, never gets its own vendor invoice, and never shows up when a board asks where the money went. We call it the integration tax — the compounding price an institution pays when the systems it already owns refuse to talk to each other.
It's paid in re-keyed data. In the staff member who exports a report from the SIS, reformats it in a spreadsheet, and pastes it into the CRM by hand — every week, forever. It's paid in the decisions made on numbers that were already stale by the time anyone saw them.
Where it hides
The integration tax is invisible because it's distributed. No single person pays all of it, so no single person flags it. A few hours here, a reconciliation there, a "let me just double-check that figure" everywhere.
- In admissions, when a lead's status lives in the CRM but their enrollment lives in the SIS, and nobody's sure which one is true.
- In finance, when aid disbursement and student accounts are reconciled by hand because the two systems were never wired together.
- In compliance, when an audit request means assembling from four sources what should have been one query.
Each is survivable on its own. Together, they're a full-time job nobody was hired to do.
Why it persists
Because replacing a core system feels enormous, and integrating two systems feels like someone else's problem. So institutions live with the gap, and the gap quietly widens as each new tool gets bolted on beside the last.
The fix is rarely a rip-and-replace. More often it's connective tissue — an integration layer that lets the systems you already paid for finally behave like one. That's most of what we build: the wiring between the boxes, not another box.
The number that matters
When we assess an operation, the integration tax is one of the first things we put a real figure on. It's almost always larger than leadership expects, and almost always recoverable — because the work was never adding value, only friction.
If your systems are making your people do what software should, that's a conversation worth having.