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 questions to ask anyone who builds integrations.
Here are our answers, in writing.
- 1
Idempotent by default
What happens when a sync fails halfway?
Ours re-run safely. Records are matched, not duplicated, however many times a job runs.
- 2
Tests before handover
What gets tested before you call it done?
The paths that actually break things: partial failure, replay, and malformed upstream data, not just the happy path.
- 3
Access enforced server-side
Where does access control actually live?
In server-side code, not in settings a teammate can widen by accident.
- 4
An audit trail per run
Can you show what ran and what changed, after the fact?
Every run leaves a record of what ran, what changed and what was skipped, before compliance ever asks.
- 5
Change without a release
What happens when the business needs to change a rule or a number?
Business numbers and rules live where the business can change them, so a changed target never waits on a release.
- 6
Runbooks your team can act on
What do we get once you leave?
Runbooks 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.
Whichever shape fits, the work itself runs through the same four steps.
Scope
A fixed scope you can hold us to.
Build
The people who scoped it build it.
Validate
Re-runnable, monitored, tested.
Handover
Runbook and access end up in your repo.
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.
- Vendor-led recommendations. When we name a tool it is because it fits your case, not because we are sponsored to name it.
- 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.
Location
Brisbane, QLD. Working across Australia.
Independent
The people who scope the work build the work.