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.
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.
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.
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.
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.
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.
Yes, though we keep most calls inside Australian business hours. Async works fine for build updates.