Service · Implementation

Automation Build.

We configure what your practice already owns. Then we build the integration and exception handling around it. One to three workflows per engagement. Fixed-price from the Workflow Audit.

Start with the Audit → How the Audit works

The implementation phase after the Audit. Configure native first. Then build the exception handling around it. One to three workflows per engagement. Most practices prefer one workflow running reliably to three half-finished.

What a Build includes

Six deliverables. Every time.

Configuration

Native automation your platforms already support. Karbon templates, Salestrekker pipeline rules, Rex triggers.

Step 01 Platform-native
Exception-handling runbook

The operational guide for what happens when the happy path breaks, who's alerted, what the fallback is, how data is preserved.

Step 02 Written doc
Documentation you own

Process map, runbook, credentials inventory, change log, delivered at handover. No proprietary black boxes.

Step 03 Yours forever
30-day stabilisation

Post-handover window included in the Build price. We monitor the workflow live, tune any edges, and field questions from your team. After that, a monthly Support plan is optional.

Step 04 Included
Team training

A walkthrough for the people who'll operate the workflow day-to-day. They leave the session confident, not bookmarking a PDF.

Step 05 Live session

Pricing

Fixed at the end of the Audit.

Single workflow

Starting from $5,000

One focused workflow, inside one platform

Two to three workflows

Starting from $12,000

Multiple workflows, related or sequenced

Complex orchestration

Scoped per engagement

Four or more tools, multi-path flows

The figures above are indicative starting prices, not committed quotes. Your specific Build price is fixed at the end of the Workflow Audit once the scope is agreed. We don't issue change orders for work that wasn't scoped.

Compliance built in

Every Build carries four commitments.

Signed into every engagement. Every workflow we ship meets all four before handover.

Commitment 01

Audit trail

Every automated action logged, exportable, with retention appropriate to your industry. Seven years for accounting and AML-scoped real estate. Per-aggregator for broker work.

Commitment 02

Reversibility

Every change documented. Every workflow can be rolled back without losing data. No destructive-by-default operations.

Commitment 03

Named operator surfaces

Dashboards and notifications so your team sees what's happening without ever needing access to the automation platform itself.

Commitment 04

Runbook for failure modes

What happens when APIs change, tools update, or data arrives malformed. Named alerts, fallback flows, clear escalation paths.

Boundaries

What we don't do in a Build.

replace native features. If Karbon, Salestrekker, or Rex already ships it, we configure it.

build proprietary platforms. You own the docs and the credentials.

deploy autonomous AI agents. That's a separate service line with its own review model.

Common questions

Before you book the Audit.

Can we start without an Audit?

Occasionally, if the scope is genuinely simple (a one-workflow build, clearly defined, inside a platform we know well), we'll quote direct. In most cases the Audit is worth the two weeks. It prevents scope creep during build and ensures the workflow we ship is the right workflow.

What platforms do you integrate with?

The platforms listed on our industry pages: major AU mortgage, real estate, and accounting tools, plus the orchestration layer (Zapier, Make, n8n, Power Automate). If your practice runs something niche, say so in the scoping call. We'll tell you honestly whether we can help.

Can we change scope mid-Build?

Small adjustments inside the agreed scope, yes. Changes that expand scope become a new engagement with new fixed pricing. We'd rather ship the original workflow cleanly and price the addition separately than absorb changes that turn the original into something else.

What happens at the end of the Build?

Handover (documentation, training, access), then a 30-day stabilisation window included in the Build price. After that, most practices move onto a monthly Support plan. You are not obligated to. If the workflow is stable and your team is confident running it, stopping is fine.

Related services