FAQ
Questions, answered
without the waffle.
If yours isn't here, ask it on the call — we'd rather tell you no early than sell you something that won't work.
It depends on how many systems have to talk to each other, and we will not pretend otherwise. What we do promise is a fixed number before anything gets built — you approve scope and price, then we start. No hourly surprises.
Less than the build, and you get the number before you commit. There are two parts: the infrastructure it runs on, which is usually tens of dollars a month, and support if you want it. Take the handover and run it yourself and the hosting is the only ongoing cost.
A single workflow is usually live within two to three weeks of the first call. Bigger programmes ship one workflow at a time, so you see something working every few weeks rather than waiting for a big-bang launch.
Most of it lands in the first week — a discovery call, then a few hours showing us how the job gets done today. After that we bring back something working and you tell us where it is wrong. Expect a couple of hours a week, not a second job.
n8n handles branching logic, error recovery and custom code that the simpler tools choke on, and you can self-host it — so your automations are not hostage to a per-task price rise. If your job genuinely suits Zapier, we will tell you and save you the money.
Anything with an API, and a surprising amount without one — email, spreadsheets, accounting systems, CRMs, booking tools, SQL databases, plain file drops. If a system is genuinely sealed shut we find that out in discovery and tell you before you have spent anything.
No. The workflows are yours, running on infrastructure you can own, and we record the handover walkthrough. Plenty of clients take the keys and run it themselves. We would rather you stay because it is useful.
Onto infrastructure you can own, in the region you choose. We do not copy your data into our own systems to work on it, and anything we touch during a build is covered by a signed agreement. If you have a compliance requirement, bring it to the first call — it shapes the design rather than the invoice.
No. Most of the saving comes from plain logic — moving data, checking it, chasing it — and that runs cheaper and more predictably with no model involved. We reach for AI where it genuinely wins, like reading messy documents or drafting text, and we tell you when your data leaves for a model and when it does not.
Not usually. If it can export a file, send an email or expose an API, we can work with it. If it truly cannot, we will say so at the discovery call rather than three invoices in.
No, and most of our clients do not have one. What you do need is someone who understands how the work actually gets done, because that is the part we cannot guess. If you already have a developer, better still — we hand over properly and stay out of their way.
That is your call, not ours. In practice most clients redeploy the hours rather than the person — the admin was stopping someone from doing the work they were hired for.
Every build ships with error handling and alerting. On a hosted plan we see the failure before you do and fix it. On a handover build you get the alerts and the runbook.
Probably not. The test is not headcount, it is whether someone is losing hours a week to something a machine should be doing. If the sums do not work at your size we will say so on the first call rather than sell you a small version of the wrong thing.
Yes, though we keep most calls inside Australian business hours. Async works fine for build updates.