Data and integrations that keep your systems in step

Integrations and syncs that keep your systems in agreement, and dashboards that update themselves, so the numbers you act on say the same thing everywhere.

Most manual work lives in the gaps between tools. I build the plumbing behind the business: pipelines, syncs and API integrations that keep your systems agreeing with each other, and dashboards that make the numbers trustworthy.

Who it is for

You have systems that each work on their own but don't know about each other: booking system, point of sale, bookkeeping, email and spreadsheets. Data is exported from one system and keyed into another, and someone enters the same information into two systems every week. The report is rebuilt by hand: someone exports, pastes into a spreadsheet, formats it and sends it.

Closing the gap is usually less work than people think, and it removes a whole category of copy errors.

What I build

• API integrations. Two systems that should agree are connected, with field mapping, conflict rules and a sync log you can inspect.
• Pipelines and syncs. Data is moved and transformed automatically instead of being exported and pasted by hand.
• Links between the tools you already have. Booking, point of sale, bookkeeping and email get a link that moves the right information in the right direction, with a log of what was moved and what went wrong.
• Dashboards that update themselves. The numbers come from the source, so nobody has to compile them every week. The report becomes a by-product of the numbers already being in one place, instead of a task of its own.

The result is that both systems stay in agreement, and errors become visible instead of silent.

What is included

An integration is done as an automation sprint: one process, automated end to end, scoped, built, documented and handed over.

• One integration, workflow or AI automation per sprint.
• A fixed scope and a fixed price.
• Typically one to two weeks.
• Documentation and handover included.

For ongoing work, such as more links or improvements to the ones you have, the ongoing partner gives an agreed amount of capacity each month, with priority response and 30 days' notice.

How it works

First a free call about which systems should be talking to each other, and whether it is worth building at all. Then you get the scope and a fixed price in writing before anything is built. The whole way of working is on the home page.

You need to contribute access to the systems to be connected, meaning accounts, permissions and API keys where they exist, real examples including the awkward ones, and one person who owns the process and can answer questions during the build. Twenty real cases say more about what is needed than a description of how it usually looks.

Price

Common questions

Which systems can be connected?

What decides it is access: accounts, permissions and API keys where they exist. Every system that is connected is also its own set of failures to handle, and its own provider that can change its mind. That is why we go through them before the price is set.

Who owns the integration and the data?

You do. Everything is delivered into your repository with documentation, and it runs on your accounts and infrastructure. I work under an NDA by default when data is involved. What a handover should contain is in Who owns the code?.

Can AI be used in an integration?

Yes, when the material is messy, like documents that look different every time. The machine reads and suggests, and a person approves what is uncertain. That is described under AI automation. For what is predictable, rules are enough, and they are cheap to build and easy to test.

When is it not worth it?

When the process keeps changing, when nobody owns it, or when the material is too poor. Automate once the process has settled, or you will be rebuilding every month. Rubbish in gives rubbish out, faster than before.

How long does an integration take?

A single automation or integration is usually one to two weeks. You get a fixed scope and a date before anything starts. A change to the scope means a new proposal and a new fixed price before it is built.