How we work
Our definition of done, in public.
Most of what separates an integration that lasts from one that gets quietly replaced is decided before any code ships. This page is the standard we hold ourselves to, written down so you can hold us to it too.
The standard
Six things every delivery includes before we call it done.
It holds when something breaks
A job that runs twice, or a feed that arrives malformed, ends in a clean state — because that failure path is the one we build and test for first.
- Idempotent by default
- Every write is create-or-update against a stable key. Re-running a job is a non-event.
- Tests before handover
- Coverage on the paths that matter: partial failure, replay, and malformed upstream data. The happy path is the easy part.
Accountable by design
Security and traceability are written into the code, ready before anyone asks.
- Access enforced server-side
- Authorisation lives in code that runs on the server, not in configuration that someone can widen by accident.
- An audit trail per run
- What ran, what changed, what was skipped and why. Compliance asks eventually; the answer should already exist.
Yours to run
The engagement ends with your team operating the system without us.
- Change without a release
- Business numbers and rules live where the business can change them. A changed target never waits on a release.
- Runbooks your team can act on
- Written for the person on call at 2am who did not build it, and does not have our phone number.
Engagements
Four shapes of engagement, one destination: handover.
Discovery, scoped delivery, embedded capability, or specialist support inside your systems integrator. The services page walks through all four and where each fits.
What we don’t do
Saying no is part of the standard too.
- Body-shop staff augmentation. We sell outcomes, not seat-warmers.
- Big-bang replatforms. We make what you own work together before recommending you buy anything.
- Licence reselling. Platform recommendations earn us no commission, so when we name a tool it is because it fits your case.
- Black-box delivery. If your team can’t run it without us afterwards, we haven’t finished.
Tell us what’s not right between your systems.
No obligation, no pitch deck. We reply within one business day.