Skip to main content

When your tools don't talk to each other

Most companies don't have one broken tool — they have five good ones that don't talk to each other. Orders arrive by e-mail, stock lives in one system, invoicing in another, and a person retypes between them. The honest answer isn't always "build something custom": if a ready-made connector exists for your combination of tools, use it — it's cheaper. Custom only earns its keep when no connector fits your tools or your process is genuinely non-standard. This guide is about telling those two cases apart — and what we build when it's the second.

What do you do when your business tools don't talk to each other?​

First, resist the urge to build. Check whether a ready-made connector already exists for your combination of tools — many accounting, e-shop and CRM systems ship off-the-shelf integrations, and if one fits your data, use it: it's cheaper than anything custom. A custom bridge or AI agent earns its place only when no connector covers your specific tools, or your process is non-standard enough that a generic integration can't express it. The goal is fewer hours retyping and fewer errors — not more software.

Buy or build? The honest fork​

Buying beats building far more often than vendors admit. Buy the ready-made connector whenever one exists for your exact tools and it covers the data you move. Build custom only when the connector doesn't exist for your combination, when it moves only part of the data, or when the work is a judgement step — reading a document, deciding where an entry belongs — that no fixed connector performs.

Three situations where no ready connector fits​

1. The tools are standard, but your combination isn't​

Who has it: a wholesaler taking orders in a niche e-shop platform and invoicing in a local accounting system nobody wrote a connector between. Each tool is fine; the pair has no bridge, so someone retypes every order.

A ready connector assumes a supported pair. When your two tools aren't a supported pair, the "integration" the vendors advertise simply doesn't exist for you — and that's the honest case for a small custom bridge over their APIs.

2. A step needs judgement, not just moving fields​

Who has it: orders that arrive as free-text e-mails or PDF attachments, in no fixed format. No import routine handles them, because there's nothing structured to import — someone reads each one and keys it in.

This is where plain automation stops and AI starts: an agent reads the e-mail or document, extracts what's needed, posts it into the system and escalates only the ones it isn't sure about. It's the same shape as invoice approvals that don't get stuck — capture, route, and keep a human on the exceptions. Two concrete versions of this: orders that arrive as e-mails and delivery notes as PDFs going into your warehouse.

3. The connector exists, but only moves half of what you need​

Who has it: a company using a supported connector that syncs invoices but not the line items, or contacts but not the order history — so the "integration" still leaves a daily manual gap.

Here the fix is usually not to replace the connector but to extend it: a thin bridge that carries the missing data alongside the one you already bought.

Where AI helps — and where it stops​

Plain automation moves data between systems on fixed rules. AI is only worth adding where a step needs to read and decide: understanding a free-text order, classifying an expense, matching a supplier that's spelled three different ways. Everywhere else, a plain API or file bridge is simpler, cheaper and more predictable — and we'll say so.

The line we keep is the same one across our work: AI proposes or drafts, a human confirms anything that matters. No silent bot posting the wrong order into your accounting.

Why this beats a bigger all-in-one system​

The usual pitch is "replace your five tools with one platform." That's expensive, slow, and throws away tools your people already know. Connecting what you have keeps the tools that work and removes only the retyping between them. You don't migrate; you bridge. And you start with one connection you can measure, not a company-wide rollout.

This is the practical side of business process automation: connect the tools, automate the steps, and build custom only where nothing off-the-shelf fits. Where a step needs judgement, our AI solutions overview shows how an agent fits into a controlled process with a human deciding — and AI agents for business covers what those agents actually do.

Who it makes sense for​

  • you use several tools that don't share data, and someone retypes between them,
  • a ready connector for your exact tools doesn't exist — or only moves part of the data,
  • orders, invoices or requests arrive in a form no import routine handles,
  • you've been quoted a big all-in-one system to solve what is really a bridging problem.

Want to know which case you're in? Get a free diagnostic — we map how your tools move data today, tell you honestly whether a ready connector already solves it, and if not, show exactly what we'd bridge, the impact and the cost. No obligation, and no build for the sake of building.