Data relay systems
Data that has to move between systems that were never designed to meet. You probably have a relay already — it is made of a person and a spreadsheet.
You are here if…
- Someone exports a file every morning and imports it somewhere else.
- Two systems hold the same numbers and disagree.
- A person is the integration, and they are on holiday next week.
- You found out something failed because a customer told you.
What we build
Scheduled transfers
On a clock, with a record of every run.
Event-driven transfers
The moment something changes, not four hours later.
Validation
Bad data stops at the door instead of poisoning the target.
Monitoring and alerts
You hear about a failure from us, not from a customer.
How it goes
01
Map the flow
What moves, from where, how often, and what must never move.
02
Fixed quote
Scope and price. Most relays are weeks, not months.
03
First route live in two weeks
The highest-volume route first.
04
Alerts and hand over
You get the runbook and the dashboard.
What it costs
[SUPPLY: £x–£y]
What projects like this have cost
Number of routes, how ugly the source format is, and whether either end has a real API. Old systems without one need middleware, which adds time.
Questions we get
What if one of the systems has no API?
Common. There is almost always a way in — a file drop, a database, a scraped export.
What happens to bad data?
It is quarantined and reported, never written through.
How do I know it is working?
A dashboard showing every run, and an alert the moment one fails.
Can it run both ways?
Yes, and then conflict rules matter. We agree those with you up front.