Integrations
System integration
Accounting, CRM, payments, public-sector interfaces and whatever your customer runs — connected so that the unhappy path is handled, not just the demo.
From £75/hrAn estimate before any work startsOne developer, start to finish
01
An integration is easy to demonstrate and hard to keep alive.
The demo runs against a working API on a good day. The production version has to survive rate limits, partial failures, a schema that changed without notice, and a token that expired at two in the morning.
02
What actually gets built
Accounting and finance
Invoices, payments and ledger entries moving between your product and the system the bookkeeping actually happens in.
CRM, sales and payments
So the record a salesperson sees and the record the product writes are the same record — including failed renewals, refunds and the reconciliation nobody demos.
Regulated and public-sector interfaces
Invoicing a public buyer, national login, and the submission formats that arrive as a specification rather than a developer portal.
Whatever your customer runs
The one-off integration blocking a deal — usually the one with the worst documentation and no sandbox.
03
How the work runs
A day of reading first
Does the API expose what you actually need, is there a sandbox, what are the limits, and is there an approval process with a lead time? Finding out in week one is cheap. Finding out in week six turns a fixed price into a conversation.
A scope and a price, inside 24 hours
Not a range with a shrug attached: what is in, what is deliberately out, what each stage costs and what it depends on. If something cannot be priced honestly yet, that is said rather than padded.
Built for the day it breaks
Retries with backoff, idempotency so a retry does not create the invoice twice, a queue so the other side being down means delayed rather than lost, and logging detailed enough to answer why a record did not arrive.
A screen that shows what it did
What was sent, what came back, what failed and what is waiting. That is the difference between a support question taking five minutes and taking a day.
- Rate
- From £75/hr
- Scope and price
- Inside 24 hours
- Written by
- The person who scoped it
Half of these projects should start with a day of reading, not a quote. Tell me which systems and I will tell you what the other side actually allows before anyone commits to a price.
Start a project →Common questions
How long does an integration take?
The well-documented ones with a sandbox are often a week or two. The range is wide because it is set almost entirely by the other side: whether there is a test environment, whether access needs approving and how long that takes, and how much of what you need the API genuinely exposes.
What happens when the other system changes?
It is assumed rather than hoped against. Their data shape is translated at the boundary, so a field moving or a version being deprecated is a change in one place. Alerts fire when calls start failing rather than when someone notices missing records a fortnight later.
Can you integrate with a system that has no public API?
Sometimes, and the honest answer depends on what it offers instead: a file export on a schedule, a database you are allowed to read, a partner API behind an agreement. Where the only route would be scraping a screen, I will say so and tell you what it will cost you in fragility.
04
Tell me what needs connecting
Name the two systems and what has to move between them. You get back what is genuinely possible on the other side, a scope and a price.