Systems we build and run
Systems that join up what you already run
Your accounts package, your payroll, the weighbridge, the thing the office bought in 2019. If it has an export or an interface, the same figures can stop being typed in twice.
What it is, and where it fits
Where this kind of system fits
- Waste, skips and recycling
- Manufacturing and fabrication
- Transport, haulage and logistics
- Wholesale and distribution
- Legal, accountancy and professional services
Integration work makes software you already pay for behave like one system. The work gets recorded once, and the invoice, the payroll hours, the stock movement and the customer record follow it instead of being entered again.
It suits any business running three or four good systems that don't talk to each other, where somebody's Friday afternoon is spent moving figures between them.
One link done properly is weeks. A system holding the operation with several others either side of it, and a log of every message, is a bigger job built the same way.
What it usually grew out of
It usually grows out of a Friday afternoon and a CSV.
Somebody exports, opens it, fixes the columns, imports, checks a few rows, and does it again next week. When they're away it waits, and at month end somebody checks the two systems still agree.
None of that is a failure of the software. It's the gap between two pieces of it, and the gap is where the work is. Closing it is usually cheaper than replacing either side, and a good deal less disruptive.
What it does
One place each fact lives
A deliberate decision about which system owns which record, made at the start, so nothing is overwritten by whichever ran last.
Invoices without retyping
A finished job raising its invoice in your accounts package, with the lines, the customer and the references already right.
Records kept in step
Customers, suppliers and price changes flowing one way, so the same detail isn't corrected in three places.
Hours and costs moving
Approved time out to payroll and costs back onto the job, on a schedule, with no export and import in between.
Plant and site data in
Weighbridge tickets, telematics, meter readings and anything else with an interface, landing against the job as it happens.
A log somebody watches
Every message recorded, failures alerted rather than discovered, and a plain answer to what synced and what didn't.
Interfaces we have built to, and would again: Xero and QuickBooks for accounts; Microsoft 365 for mailboxes and calendars; the DVLA for vehicle details from a registration; postcode lookup for addresses; Companies House; Google Ads for what a campaign cost and what it brought in; SMS and WhatsApp gateways; and the plainer kind, a CSV or XML file dropped on an SFTP server every night for a partner who has nothing newer. If yours is not on the list, the question is only whether it has an interface or an export.
Where the information arrives as an email, a PDF or a photo rather than through an interface, an AI feature can read it and put it on the right record, ready to confirm. More on AI and automation.
Usually built alongside job and works trackers, management reporting or multi-site and multi-depot operations. The rest are on the services page.
How it gets built, and how it gets run
| Fixed price | Scope, price and dates in writing before anything starts, with what isn't included written as plainly as what is. It doesn't move because the job turned out harder than we thought. |
|---|---|
| Timescale | One link done properly is weeks rather than months. Several take longer, and each goes live on its own rather than all at the end. |
| Onboarding and training | We run the new link alongside the manual routine until the figures agree, then stop doing it by hand, and train whoever did it to watch it instead. |
| Hosted in the UK | UK infrastructure, backed up nightly to somewhere that isn't the machine running it, kept thirty days, and checked every few minutes that it's up and answering. |
| Changes | A new field, another system, a changed format at the far end. What that covers is agreed at the start, so nobody works it out on the day. |
Ask about our free Business Systems Assessment
An hour with whoever runs the day to day. Clear recommendations to act on.
We look at how the work actually runs and what it runs on, then send you a list of what we would change, what each change would do for the business, and what it would take. In person or online, whichever suits you. Nothing to pay, nothing to sign.
- One hour
- In person or online
- Recommendations we talk you through
Honest answers
- Our other software has no API.
- Often true, and rarely the end of it. Scheduled exports, files dropped in a folder and read-only database access all work. If there is genuinely no way in, we'll tell you that rather than build something that won't last.
- What happens when the other side is down?
- The work carries on and the messages queue. We build for the other system being unavailable, because at some point it will be, and we'd rather that be a delay than a lost figure.
- Who holds the credentials?
- You do. We use accounts you own, scoped to what the link needs and documented, so you can revoke them without ringing us first.
Talk to us
Tell us which systems you run and where the same figures get typed in twice. That's usually enough for us to say whether we can help.
Ring, 8am to 6pm Monday to Friday and Saturday mornings, or use the form below. Pick what you'd like to keep track of, add a line if you want to, and leave a name and a way to reach you.