Why do we type the same thing into three places?
Most businesses run on four or five systems that do not talk to each other, and a person carries the work between them. We build the connections, including the steps where an AI reads a document, extracts the fields or drafts the reply, and we leave your systems as the systems of record.
Fixed per integration, quoted in writing from the scope. Simple connections from A$1,800; connections with an AI reading or drafting step from A$3,500.
Connections that run unattended, a log of everything that moved, validation before any write, and a shorter list of things only you can do.
Retained support by the month if you want it; no lock in.
What it is
The courier problem is the most expensive quiet cost in a small business: a person reading an email and typing it into the job system, reading the job and typing it into Xero, reading Xero and typing a reply. Each hop takes minutes and each hop is a place a mistake enters.
We connect the hops. Where the data is structured, the connection is deterministic and needs no AI. Where a document has to be read or a reply drafted, an AI step does that part and a validation rule checks it before anything is written. Nothing writes to a system of record without a check.
This is for you if
- The same information is entered in more than one system
- You already pay for the systems and do not want to replace them
- You want a log of what moved, not a promise that it did
Not for you if
- You want to replace your core systems; that is a different project
- There is no agreed owner for the process on your side
- You need real time trading integrations at scale; we would refer you
How it runs
- 1 · no charge
Map
Which systems, which fields, which direction, what happens on failure. One page.
- 2 · 1 to 3 weeks
Connect
Deterministic where possible, an AI step where reading or drafting is needed, validation before every write.
- 3 · 2 weeks
Prove
Run alongside the manual process, compare the log against reality, then switch.
- 4 · included
Hand over
Documentation, credentials in your accounts, a runbook, and a training session.
In writing, before we start
Three sentences that hold on every engagement. They are the method, written as promises.
The measure, the budget cap and the point at which we stop are set in the written scope before anything is billed. Nothing moves the goalposts afterwards.
Everything we build runs in your accounts and is yours: code, configuration, documentation and measurements. We hand over; there is no dependency on us.
If the pilot does not hit the measure we agreed first, we keep working at no further cost until it does, or we stop and say so in writing. You will not be sold the next step by the first one.
Systems we connect most often
- Xero, MYOB and QuickBooks
- HubSpot, Pipedrive and Zoho
- Microsoft 365 and Google Workspace
- Booking and practice management systems
- Job management tools common in the trades
What the log shows
- Every record moved, with source and destination
- Every validation that failed and what happened next
- Cost per run where an AI step is involved
What you receive
Questions
Do you need access to our systems?
Yes, scoped to what the connection needs, in accounts you control. Credentials stay in your accounts; we do not hold them after handover.
What happens when a connection breaks?
The log says so and a person is told. Under managed operations we fix it; otherwise the runbook tells your IT provider what to do.
Can our IT provider do this?
Often yes, and we are glad to scope it for them. Where an AI reading or drafting step is involved, that is the part we usually build.
Which two systems should be talking?
Tell us the pair and what travels between them. The map comes back within three business days at no charge.