API development and system integration

The symptom is always the same

Somebody in your business is a human copy-and-paste machine. A job comes in through the website, gets typed into the scheduling system, then typed again into the accounting software, and someone updates a spreadsheet because neither of those tracks the thing you actually care about. It takes hours a week, it goes wrong under pressure, and the person doing it was hired to do something else.

That's an integration problem, and it's one of the few pieces of software work where you can calculate the return on a napkin. Six hours a week of re-typing, at any plausible hourly cost, pays for a £1,200 integration inside a year — and then keeps paying, quietly, forever.

What we build

• Integrations between systems you already use. Website, CRM, booking system, accounting software, stock control, payments, email marketing — connected so a record entered once appears everywhere it's needed.
• APIs for your own product or app. A clean, secure, documented layer your mobile app, website or customers' systems can talk to — with authentication, versioning and rate limits done properly.
• Automated data flows. Scheduled syncs, imports, exports and reports that run on their own and shout when they can't, replacing the manual routine somebody currently does every Monday.
• Legacy system connections. Getting data out of, and into, the old software your business genuinely depends on and isn't about to replace.
• Webhooks and real-time updates. Something happens in one system and the others know immediately — rather than up to an hour later, or whenever someone remembers to press sync.
• The plumbing under AI work. Every AI assistant and custom AI build needs to see your real data. This is how it does that.

How we build it

Integrations have one job — be boringly reliable — and most of the engineering goes into what happens when things go wrong rather than when they go right. Every build we ship assumes the other end will be down at some point, that a record will arrive malformed, and that a vendor will change something without telling anyone.

• Retries that don't make things worse. Transient failures retry with sensible backoff; operations are built so a retry can't create a duplicate invoice or a second booking.
• Alerts to a person. When something genuinely can't succeed, you hear about it that day. Nothing fails quietly.
• A real log. Every sync recorded, so "why is this job not in the system?" is a question with an answer instead of a shrug.
• Credentials handled properly. Secrets in a secrets manager, scoped to the minimum access needed, never buried in code.
• Documentation you could hand to someone else. What connects to what, which fields map where, and how to change it. You're not buying a black box.

The process is short: a free call to map what you have and where the double entry happens, a fixed proposal, then a build that typically takes one to two weeks for a single integration and three to six for something spanning several systems. We test against your real data — with a copy, not your live records — before anything goes live.

What it costs

A single integration between two well-behaved systems starts at £1,200. Multi-system work, or anything involving software without a proper API, is typically £3,500 to £12,000. Building an API for your own product or app is £4,000 to £15,000. Hosting and monitoring afterwards is £29–£99 a month, and it's included if you're on a website care plan.

You own the code, the documentation and the credentials. Every integration is written to be picked up and changed by someone else — because the point of removing a bottleneck is not to create a new one called us.