What we do / Integration and systems
Stop typing the same thing twice.
If someone is retyping the same information into two systems, that is a job a computer should be doing.
Built so somebody other than us can understand and maintain it.
// sync.js
from: "bookings"
to: "accounts"
every: "5m"
onFail: "alert + retry"
retype: false
logged: true
handover: "documented"
The problem
Most of it is invisible until someone leaves.
Businesses accumulate software. A booking system here, an accounts package there, a spreadsheet somebody built in 2019 that everything secretly depends on. None of it talks to anything else, so people become the glue, copying and pasting and checking.
It works, in the sense that the business keeps running. But every week somebody is still copying information, checking it and fixing mistakes the systems ought to handle themselves.
The same goes for the ground underneath. Email set up in a hurry years ago, staff who have come and gone taking mailboxes with them, and an important quote that occasionally just does not arrive.
What we build
Fewer moving parts.
- Systems that talk to each other. Bookings into the diary, orders into the accounts, enquiries into the customer list, without anyone retyping.
- Migrations done carefully. Google Workspace or Microsoft 365, without losing years of email on the way.
- Email that actually arrives. The authentication records that decide whether you land in an inbox or a junk folder, configured and verified.
- The repetitive jobs automated. The weekly report, the reminder chase, the spreadsheet someone updates every Monday morning.
- Sensible security. Two factor authentication, a proper joiners and leavers process, and shared passwords out of the group chat.
- Backups that have been tested. An untested backup is not a backup, it is a hope.
- Honest advice on what to drop. Often the answer is fewer systems rather than cleverer ones, and we will say so.
Each of these is a project with an end. At handover you get the logins, a written note of what was set up, and what to check and how often. If you want someone keeping an eye on it after that, we agree it in the scope, or your IT support firm picks it up from our notes.
Someone retyping every week?
Tell us which two systems do not talk to each other. That is usually where we start.