The AI automation questions everyone asks

An AI automation agency connects the software your business already runs (job management, accounting, email, calendars) so repetitive admin happens automatically. Most automation agencies build it and hand it over; HushCog will also manage and look after your tools as an AI automation service. For a monthly fee we will also improve it. If you'd rather we only build it and hand it over, we do that too, at a fixed price with full documentation.

A consultant tells you what to automate; an agency builds it. We do both, plus the part everyone skips: running it afterwards. If you just want advice, feel free to message us or book a call with Rob.

Ask five things.

• Who runs it after go-live. Plenty of AI automation companies hand over the logins and leave, and the running is where automation lives or dies.
• Whether you own the workflows and the documentation, so you can leave and take it all with you.
• What happens when a flow breaks on a Tuesday. Who sees it happen, and who fixes it.
• Which parts of the build are genuinely AI. A good deal of what gets sold that way is conditional logic that's been around for years.
• What the AI itself costs to run. Model usage is billed in US dollars, and a properly set up automation keeps that bill small.

There are two failure paths, and the silent one is the dangerous one. A flow that breaks should be loud: it stops, we're alerted, we fix it, and you hear about it from us rather than from a customer. A flow that's quietly wrong is not loud at all. A filter starts returning nothing, a field gets renamed on one side, and the sync keeps reporting success while the numbers drift. So anything moving records between systems gets a reconciliation check as well as a running one: counts and totals compared on both sides after each run, with a loud alert when they disagree. Where a step uses a model rather than a rule, we keep it out of decisions nobody can check, and anything it writes on your behalf either follows a form we agreed or waits for a human yes.

Less than the name suggests. Most of what saves you time is plumbing: one system telling another that something happened, on a schedule, without a person retyping it. We reach for an AI model where the work genuinely needs judgment about language, like reading an email and working out which job it belongs to, turning a messy voice note into a record, or drafting a reply for you to approve. Where a rule will do, we write a rule: they are cheaper, faster, testable, and they behave the same on Tuesday as they did on Monday. Ask us which parts of your build are AI and we'll point at them on the plan.

Everything keeps running, and everything is documented. Every flow we build comes with plain-English documentation, and every workflow is exportable. If your setup runs on your own subscriptions, nothing changes at all. If it runs on infrastructure we manage, the handover terms are in your agreement: you get the exports and the documentation, and any competent automation person could pick it up from there.

No. You don't need to log in unless you want to.

Automations break. Apps update, passwords change, someone renames a spreadsheet column. DIY workflows break a handful of times a year, and each break silently costs you leads or invoices until someone notices. The monthly amount is us noticing first, fixing it, and improving things as your business changes. It isn't compulsory. If you'd rather pay for a project, own it and run it yourself, that's an option and everything is documented and exportable. The monthly is available as a low-cost option and for convenience.

It depends on whether the job is simple or complex, and the price has three parts: two one-off costs and one monthly. The Blueprint comes first, from $380 incl GST for simple automations on common software, or from $1,370 for complex work across several systems, and it's yours to keep either way. The build is a fixed price quoted from the Blueprint and approved before anything starts; simple builds usually run $1,500 to $3,000. Keeping it alive is the monthly, from $190 incl GST on our infrastructure, or more on your own accounts, where every subscription is billed to you at cost and we don't clip that ticket. No minimum term, and nothing is billed by the hour.

No, and it's the most common version of this conversation. We do a Blueprint for this reason and it can be done with you or around you. With you is usually quicker and cheaper. Around you is for when your week genuinely has no room in it: we work out how the place runs from the systems themselves and can then explain your technology back to you in plain English so you can correct the bits we got wrong. You do not need to understand your own software to hire us. Not knowing how it all fits together is the normal condition of running a business.

No minimum term on Keeping it alive: the build was paid for as its own fixed price, so everything that exists when you leave is already yours. Cancel with a month's notice, settle the last invoice, take the documentation and exports of everything we built, and part as friends. One mechanical note: automations running on infrastructure we manage run while a plan is on. If you leave, winding down cleanly costs nothing: flows switched off properly, access revoked, your exports and documentation handed over. Moving everything under your own subscriptions instead is a piece of work like any other, quoted before it starts, and the documentation is written so that any competent person can do it, not only us. The one exception to no minimum term is a build paid off in instalments, where the total is agreed up front and the payments run until it is paid. That is a payment plan rather than a subscription, and we will name it as one before you sign.

Your data stays in your own accounts and flows directly between your own apps. We design the plumbing. We don't store your data. We work within the Australian Privacy Principles and will happily walk your compliance person through any flow.

Carefully, and with transparency. Before we connect anything we do an access check with you: two-factor on where it matters, old staff accounts retired, shared passwords replaced where they shouldn't exist. Where a system supports it we don't take a password at all, we connect through OAuth, which is the mechanism behind every "sign in with Google" button you've used. So you can see exactly what you granted, and you can withdraw it yourself if required. Where OAuth isn't offered, any key or login we hold is created in your name, limited to what the job needs, kept in a password vault, and documented so you can revoke at any time. On the monthly plans we also cycle keys on a schedule, replacing them and reconnecting everything, so nothing stays valid longer than it needs to. Worth knowing that arranging all this properly takes real time, and on some systems it means waiting on a vendor approval; that's priced into the plan or monthly. We're not a cybersecurity firm and we don't sell security audits. We believe this is just how anyone touching your systems should behave.

Honestly? Maybe. And if your business is one person and one app, we'll say so. The gap isn't building an automation, it's running fifty of them reliably while you're on the tools or with patients. You could also do your own bookkeeping. Most people don't.

Yes, and we're not competing for their work. They stay, we plug the gaps between the systems they set up.