Make your systems talk
Client details, jobs, invoices and documents flowing between the tools you already pay for. Entered once, correct everywhere. Where a tool has no proper connection point, we find the side door - or tell you there isn't one.
connect, automate & migrate
Type it once. Everywhere.
Your software is fine. The gaps between the tools are the problem: the client entered three times, the invoice filed by hand, the person who IS the integration. We connect what you own, automate the busywork, and move you calmly off anything being wound down. Fixed price, days not months.
in plain terms
iterate connects the software NZ small firms already run so data moves once instead of being re-typed, automates the jobs a person still does by hand - onboarding, filing, chasing, drafting - and handles migrations off tools that are being retired. No new platforms to learn, no eighteen-month project. One small fix at a time, each one working before the next is discussed.
the three jobs
Connect. Automate. Migrate.
Make the busywork do itself
New-client onboarding that runs itself. Documents read, figures extracted, evidence filed where the auditor looks. Routine letters drafted from your data. AI where it earns its place, a person approving what matters.
Move off dying tools, calmly
Old WorkflowMax, MYOB Practice, tools absorbed or retired by their vendor. We map what you had, move the data, rebuild the connections and test on real work - on your timetable, not the vendor's.
where the hours go
The leaks we fix most.
- Re-typing between systemsThe same client, job or invoice entered into two or three tools that don't talk. The most common leak in every small firm we've looked at.
- Onboarding by checklistNew client, eleven manual steps across five systems. Connected properly, it runs from "proposal accepted" to "folders filed" on its own.
- The spreadsheet that became a systemFragile, undocumented, one person understands it. We rebuild it as something real - auditable, shared, backed up.
- Documents handled by handReports, contracts, statements read by a person and re-typed into another system. AI reads them now, reliably, with your data kept private.
- Chasing - clients, documents, sign-offsReminders and follow-ups that a system should be sending, sent by a person who has better things to do.
- The tool being wound down under youThe vendor sold, the product changed, the old connections broke. Someone has to work out stay-or-go - that's a fixed-scope job, not a crisis.
built, then kept alive
We don't build it and vanish.
An automation runs against software that changes without warning: a vendor updates an API, a form gains a field, a login flow shifts. Left alone, it quietly breaks at the worst moment. So the build is only half of it.
Fixed price, up front
Each fix is quoted as a fixed price before we start, based on what it's worth to you - the hours it hands back, not a meter running. You approve it, we build it, you see it working. No open-ended discovery, no surprise invoice.
A small monthly, so it stays alive
Once it's live we monitor it and fix it when something upstream changes, so you never find it silently stopped. A small monthly line per automation, scaled to how much it matters and how much can break. It's your tool, documented, no lock-in - stop any time.
common questions
Answered straight.
What does 'integration' actually mean for a firm our size?
It means the things you type into one system show up in the others without anyone re-typing them. A new client entered once, everywhere. An invoice that files itself. Two systems that used to disagree, agreeing. No new software to learn - the tools you have, connected.
Our tool doesn't have an API. Are we stuck?
Usually not. Plenty of NZ software is closed, but there's often another way in - the SharePoint underneath your document system, a spreadsheet import the tool already supports, scheduled exports. Closed changes the route, not the destination. If something genuinely can't be automated, we say so before you spend anything.
We're on software that's being wound down. How does a migration work?
Calmly, and in a fixed scope: we list what you actually had connected (there's always one nobody remembered), map what data moves and what gets archived, rebuild the connections on the new platform, and test against real jobs before your team switches. Days of focused work, not a quarter of disruption.
Where does AI fit, honestly?
Where it earns its place: reading documents and pulling the figures out, drafting the routine email or report from your own data, answering plain-English questions over a folder of files. Always with a person approving anything that matters, and your data kept out of AI training sets. Where it doesn't earn its place, we'll tell you.
What does it cost?
Each fix is a fixed price, agreed before we start and based on what it's worth to you - the hours it hands back, not an hourly meter. We deliberately start with one small, painful problem so you can judge us on a working result, not a proposal. Once something's built, keeping it monitored and running is a small monthly line per automation. If the first fix doesn't earn the second, no hard feelings.
Which tools do you know?
The NZ small-firm stack: Microsoft 365, Xero and its ecosystem, XPM and WorkflowMax, FYI, SuiteFiles, Dext and Hubdoc, First AML, Annature, Tax Traders, job-management tools like ServiceM8 and Tradify, and plenty more. We published our homework - see the integration map of which practice tools actually talk to each other.
start small
Tell us what you re-type.
That's usually the worst leak, and the best first fix. A no-obligation chat, then we find where the hours are going and start with the fix that pays back fastest.