Automation support for the failures you can’t always see.

For the work your team already relies on

Care is for the point where your business expects the system to work without someone remembering to check it. An enquiry handover, a customer update or a scheduled report can become part of the working day quickly. The operating responsibility needs to be just as clear as the original build scope.

You may have several connected processes in n8n, Zapier or Make, with a CRM, Xero and other business software on either side. The monthly fee reflects how much you run and what your business loses if one of those processes stops. A task that can wait until tomorrow and an action holding up today's customer work need different escalation decisions.

For a system built elsewhere, we need to inspect the workflows, access, dependencies and existing failure handling before agreeing care. Taking responsibility for an unknown canvas without checking its behaviour would give you an incomplete picture of what support can cover.

Monitoring, repair and a useful monthly review

We watch failed runs, runs that produce nothing and runs that never fire. The checks depend on the actual process. A scheduled import can be checked against a time window and source count. An event-driven process needs a way to establish whether expected events arrived. The operating scope records what normal looks like.

When something breaks, we investigate the affected work and repair the cause within the agreed care scope. That may involve a connection, a changed field or a workflow rule. Before replaying work, we establish whether the destination already accepted any action. Recovery should restore the intended outcome without creating duplicates.

Your monthly report covers what ran, what failed, what we repaired and the one improvement worth making next. It should help you understand the system's condition and the unresolved work. A total number of successful runs without the exceptions is not enough to make a useful operating decision.

A recurring problem may reveal a process change rather than a small repair. A new application, a new department or a new approval policy can need a separate build scope. We make that distinction explicit so care does not become an undefined promise of unlimited development.

Make the handover between your team and ours explicit

We can maintain the automation logic and investigate failures under the care plan. Your business still owns the source records and the decisions that only you can authorise. If a customer name is ambiguous or a proposed action needs approval, the system needs a named person on your side to resolve it.

Subscriptions, account ownership and access also need owners. A revoked login can interrupt a connection even when the workflow has not changed. Tell us when software, permissions, forms or internal rules change so the operating picture stays accurate.

For self-hosted n8n, establish who owns infrastructure tasks such as updates, database operation, backups and restoration. Include them explicitly where they form part of the engagement. Do not assume every server responsibility comes with every care plan simply because n8n is involved.

Coverage hours, escalation channels, response expectations and any incident commitments belong in the written scope. Agree when a person will respond and what your team should do outside the agreed coverage.

Judge care by the work it can account for

Ask whether the system can explain a record from arrival to accepted output. Useful operating evidence includes the source reference, the current state, the destination record and any reason it is held. Logs should contain enough to troubleshoot while avoiding unnecessary copies of sensitive information.

A review should distinguish completed work from work still waiting on a person. It should also record what was repaired and what remains unresolved. Your operating report connects those findings to the records and agreed processes in your own business.

$750 to $2,500 AUD per month

Our ongoing care plans are priced on how much you run and what your business loses the day one of the systems stops. Care is month to month and you can cancel without penalty. The final scope establishes the included work and operating expectations.

The care fee is separate from the build. Automation builds start at $3,500 AUD, typical projects are $3,500 to $12,000 AUD and complex AI agent systems are $12,000 to $25,000 AUD. Your own platform subscriptions, hosting and AI usage are considered separately in the running budget.

A system with more volume is not automatically harder to care for than a smaller one. The consequences of failure, number of dependencies, sensitivity of the actions and difficulty of safe recovery matter. We assess those factors rather than sell a fixed quantity of workflows as though they all carry the same responsibility.

Confirm tax treatment, coverage and final commercial details in the written scope.

Fix the cause, then account for the affected work

An incident starts by understanding its boundary. Which process is affected, when did the problem begin and can any continuing action make the situation worse? If the system may write incorrect records, holding the affected branch can be safer than repeatedly attempting the same operation.

Next, establish the state of each affected item. A timeout might mean the destination accepted the write but the response did not arrive. A stable reference lets the maintainer check before trying again. Where the evidence is uncertain, a person should review rather than let an automated retry guess.

After repair, reconcile the backlog against the destination and watch the next ordinary runs. Update the check or documentation that would help catch the same issue sooner. The useful endpoint is restored business output and accounted-for exceptions, not simply a green execution in a dashboard.

You keep the system if you leave

You own the workflows, documentation and accounts. We build on your credentials, provide exported files and a recorded walkthrough, and do not resell subscriptions. If we stop working together, you retain those assets and the workflows keep running.

Continuity still needs an operator. Before care ends, decide who receives alerts, maintains access, pays dependencies and responds to held work. Your team or another maintainer needs the explanation of the business rules as well as the files.

A clear handover records the active processes, unresolved exceptions and operating responsibilities. You can revoke our access and retain control of the platform. No lock-in should mean practical control over the system, supported by documentation your next maintainer can use.