Article · · 4 min read

The Disconnect Tax: Retyping the Same Fact Four Times

// Opening

A client moves office. You update the address in the CRM. Then in the invoicing tool. Then in the project tracker. Weeks later, a delivery goes to the old address anyway, because the fourth copy lived in a spreadsheet nobody remembered.

Nothing broke. No tool failed. Everyone did their job. And you still paid for it.

That payment has a name: the disconnect tax. If your business runs on more than a handful of tools, you may already be paying it without ever seeing a bill.

// Part 2

What the tax is made of

Re-entry. The same fact typed into several systems by hand. A new client's details go into the proposal, the CRM, the accounts package and the onboarding email. Four entries, one fact. Each one costs skilled attention and is a fresh chance for a typo.

Drift. Copies that quietly stop agreeing. One system spells a contact's name one way, the invoice another, and the project tracker still lists someone who has left. Each copy was right the day it was typed. The cost lands later: a wrong name on a proposal, a quote built on last year's rates.

The between. Work that falls into the gap where one system's job ends and another's begins. The form was submitted, so the website's job is done. The task was never created, so the tracker never knew. When it goes wrong there's no one to blame, which is exactly why it keeps going wrong.

// Part 3

Why it survives

Software vendors bill you for what their product does. Nobody bills you for the seams between products, so the seams never appear in a budget review. The tax is paid in attention, small errors and the low-level worry of "did that actually go through?"

And because each instance is small, a few seconds here or a corrected email there, it never feels worth fixing.

But it's easy to check. Not with an audit or a dashboard: with a pen. For one ordinary week, keep a note and mark every time someone:

  • re-enters a fact that already exists somewhere
  • notices two systems disagreeing
  • chases a piece of work that fell between handoffs

We won't guess your total; we haven't measured your business, and any number would be invented. Your note measures the only set of tools that matters: yours. By the end of the week you'll know whether the tax is real for you, and which seam stings most.

// Part 4

What has changed

Connecting tools isn't a new idea. For years the standard answer was to rent a recipe: a subscription platform where you wire up "when this happens there, do that here". Those platforms are genuinely useful, and for plenty of seams they're still a sensible answer.

For a long time, though, renting was the only realistic option for a small team, because building your own meant hiring a developer.

That's what has changed. Today's AI models are good at writing exactly this kind of small, well-defined software: the piece that notices a change in one system and carries it to another. A connector: the kind of thing that used to be too small to hire for and too technical to do yourself.

So the question is no longer "can we afford to connect these?" It's "should we rent this connection, or own it?"

  • Rent when the seam is simple and an off-the-shelf recipe fits.
  • Own when the seam is close to how your business actually works: the rules are yours, the edge cases are yours, and you'd rather the logic lived somewhere you can read it.
// Part 5

What owning a connector looks like

A model can write the connector, and that's most of the distance. An agent with access to both systems can also take over the re-entry, and watch for drift and flag it.

What it needs from you is the rule:

  • which copy of a fact is the truth
  • what should happen when two systems disagree
  • what "done" means for this handoff

Those are decisions about your business, and they stay with you. Once they're written down, the connector and the checks can follow them consistently.

What you end up owning is modest and durable: a small piece of written-down logic your team can read, that does one job, that can be checked when something looks wrong, and that doesn't disappear if you cancel a subscription. Readable. Keepable. Auditable. It's closer to a well-written operating procedure that runs itself, while you keep saying what it's for.

// Part 6

What to do next

Not "integrate everything". Not "pick a platform". Something smaller.

Keep the week's note. At the end of the week, don't fix all of it. Pick the one seam that stings most, and ask three questions:

  1. What is the event? What actually happens that should trigger something else: a form submitted, an invoice paid, a status changed?
  2. Who needs to know? Which person or system is finding out late, by accident, or not at all?
  3. Where should the truth live? Of all the places this fact is copied, which one should be the master, so every other copy answers to it?

If you can answer those three, you've done the hard part. The connector, rented or owned, is the follow-through.

If you'd rather not think that seam through alone, that's exactly the kind of problem we run The Catalyst on. We find the one real problem in your business worth solving, chosen together. We build it with you, with AI doing what it's good at and people making the decisions. And we hand you the keys, not a black box: one seam, working, and yours to run without us.

Or simply start with the note. It costs a pen, and it's the last week the tax stays invisible.

← All posts