Integrations and automation

The work between your systems is where the money leaks.

Almost nobody runs one system any more. They run eight, and the gaps between them are filled by exports, retyping, a monthly reconciliation and somebody checking two screens against each other. That labour never appears on an invoice, and so it is almost never costed.

Start with a complimentary 20-minute fit call Start with the blueprint

Some integrations should never be written. If both vendors already support a native connection, or the volume is four records a week, a script is a liability rather than an asset. We will say so.

What this line covers

Making systems talk, and keeping them talking.

Plumbing wins no admirers, and it is precisely where reliability is won or lost. The design questions are about failure, not about the happy path: what happens when a call times out, when a record changes on both sides, when a vendor rotates a credential at two in the morning.

API integrations between platforms that were never designed to meet.
Data synchronisation with a defined direction, conflict rules and a way to prove both sides agree.
Billing and operations plumbing: usage into invoices, orders into provisioning, payments into the ledger.
Scripted automation for the recurring manual jobs that quietly consume a day a week.
Monitoring and alerting for the pipeline itself, so a silent failure does not surface as a customer complaint.

Signals you are in this line

A monthly export and import that only happens when someone remembers.
Two systems that disagree, plus somebody employed to settle which one wins.
Invoicing that lags the work because the numbers live somewhere else.
A vendor with an API you pay for and have never been able to use.

The cost of these is measured in hours a week, which is why they are easy to justify and easy to keep postponing.

The kinds of systems we build

Work the team has taken on in this line.

The shapes recur across industries even when the systems on either end are completely different.

Usage into billing

Pulling consumption or activity from the systems that record it, reconciling it against what was sold, and producing invoice lines that a finance team will actually sign off.

Operations pipelines

Orders, tickets, assets and accounts kept in step across several platforms, with a clear owner for every field and a defined answer for what happens on conflict.

Credential and access plumbing

The unfashionable half of integration work: rotating tokens, scoped keys, retries and back off, so the pipeline survives a vendor's maintenance window.

What we would talk you out of

The cheapest integration is the one you do not write.

Custom plumbing is a permanent maintenance commitment. Every connection you own is one you have to keep alive through both vendors changing their minds. That is worth paying for sometimes, and not others.

A native connector exists

Vendors ship supported integrations that they, not you, are obligated to keep working. Where one covers the need, taking it is the correct answer even when it is less elegant.

The volume does not justify it

Automating a task performed twice a month rarely repays the code, the testing, the monitoring and the day it breaks. Sometimes the honest recommendation is a documented manual step.

The upstream data is wrong

Synchronising bad records simply distributes them. Where the finding is that a source system needs cleaning first, the blueprint says so and scopes that instead.

Inside the blueprint

What the five days settle before any pipeline is priced.

Integration work fails on the details nobody agreed in advance. The blueprint pins those down while they are still cheap to change.

ItemWhat the blueprint settles for this kind of work

Which system owns which field. Decided explicitly and written down, because every unresolved ownership question becomes a data conflict later.

Direction, timing and volume. One way or both ways, near real time or scheduled, and how much moves, since those three answers determine most of the cost.

What the vendor APIs actually allow. Checked against the documentation and against reality, including rate limits, gaps and the operations that are quietly unsupported.

Failure behaviour. What happens on a timeout, a duplicate, a partial write or a credential expiry, and who finds out.

Native options ruled in or out. Existing connectors evaluated first, with the reason for rejecting each one recorded rather than assumed.

A fixed price for the pipeline. Including the monitoring, because a pipeline nobody watches is not finished work.

The other three lines

Most projects touch more than one.

Work rarely arrives in a single category. The blueprint is where we decide how much of each one your project actually needs.

Custom business software

Line of business applications, internal tools, dashboards and workflow systems.

AI and agent systems

Assistants, document and ticket automation, retrieval, agent workflows.

Web and ecommerce platforms

Storefronts, portals and customer facing web applications.

Book the call

Describe the gap, not the tool you had in mind.

Twenty minutes, no charge. Tell us which two systems refuse to agree and what somebody currently does about it by hand, and we will tell you whether this is a blueprint, a native connector or a five line script.

Start with a complimentary 20-minute fit call Read the blueprint in full