Integrations and data,explained.

Everything we publish about systems that do not talk to each other, and about the person and the spreadsheet currently standing between them.

The questions a company asks once it notices how much of its week is spent typing the same thing into a second system.

Deciding whether to build something? The service page is the one to read. Reading around the subject? Stay here.

Published on this topic

Everything filed underintegrations and data.

The scope of this index

What a manual bridge costs to keep, counted properly, including the hours nobody logs and the errors nobody attributes to it.
What happens when two systems disagree about the same number, and how a business decides which one is allowed to be right.
What a connection to an accounting package can and cannot do, which is rarely what the vendor page implies.
What has to be written down first, before anything that runs unattended can be trusted with your data.

A post sits under exactly one topic. Nothing is cross filed, because a piece that appears in three places is a piece nobody can find a second time.

Where to go next

I know what I need to build.

A free conversation, then a written proposal with scope, price, and timing.

One process creates too much manual work.

We map it, then define what a connected system should do next.

My website is underperforming.

A written report and a prioritized plan of what to fix first.