How to Connect Business Tools That Don't Talk to Each Other
- Emilio | EG3 Digital
- 6 days ago
- 2 min read
Connecting two business tools means deciding three things: which system holds the truth, what event causes information to move, and what happens when the two disagree. The technical connection is the easy part. Most integrations that fail were never wrong about the plumbing — they were wrong about which system was in charge.
Pick the system of record
For every piece of information, one system is authoritative and the others are copies. If a customer's phone number differs between your booking system and your accounting package, which one wins? Answer that per field, once, and write it down. Skip it and you will spend the next year investigating why two screens disagree.
Prefer one-way over two-way
Two-way sync sounds better and is significantly harder to keep honest, because every edit on either side has to be reconciled. Most businesses need information to flow one direction — booking creates invoice, enquiry creates contact — and are far better served by a simple, predictable one-way flow they can reason about.
When a tool has no way in
Some software genuinely cannot be integrated — no API, no export, no webhook. You have three honest options: replace the tool, accept a manual step and make it a scheduled one rather than a remembered one, or use whatever export it does have on a rhythm. What you should not do is build something fragile that scrapes a screen. It works until the vendor changes a button, and then it fails silently, which is worse than not having it.
Sometimes the correct answer really is to change the tool. If a system that cannot connect sits in the middle of your daily work, its true cost is not the subscription — it is every hour spent moving data around it.
Decide what happens when it breaks
It will break — an API changes, a password expires, a plan lapses. The question is whether anyone finds out. An integration that fails loudly, notifying a named person, is worth more than a more elegant one that fails quietly. Quiet failures are how businesses discover in March that nothing has synced since January.
Start with the one that costs you money
You do not need everything connected. Find the one handoff where information failing to move costs you jobs — usually enquiry to follow-up, or job complete to invoice — and connect that. Tidiness is not a business case; a recovered booking is.


Comments