Custom Build

The same engine — discovery, drafting, an approval gate, sending, a reply handler — wired to whatever actually triggers work in your business.

By enquiry

Scoped per job · not an off-the-shelf product

What you're buying

The engine is built. The wiring is the work.

Nothing here starts from a blank page. What takes the time is learning your process well enough to automate it without breaking it.

Discovery first · build second

How an engagement runs

4 steps · 1 gate

STEP 01

Map

We sit with the process as it runs today — what starts it, who touches it, where it stalls, and what a good outcome looks like.

Your process as it is · not as the org chart says

STEP 02

Scope

You get the trigger, the stages, the rules and a fixed price in writing before anything is built. If the maths doesn't work, we say so here.

Fixed price agreed before build starts

STEP 03

The Gate

Built in by default

Every custom build ships with the approval gate unless you ask us to remove it — and we will argue before we do.

Approve, edit or kill · decision logged with timestamp

STEP 04

Run

It goes live on your accounts, with your rules. We watch it, fix what breaks, and hand you one number a week.

Monthly fee covers running it, not just hosting it

These are the steps of an engagement, not stages of a deployed pipeline — so unlike the other systems on this site, they carry no build status. What gets built at step 04 is a real running system, and it will have one.

Built on request

Not built yet · same engine, same gate

Four systems we'll build for the first client who needs them.

Each one is the same shape as the systems already running — something happens, a message is drafted, it's checked, you approve it. None of them exist yet, and we won't pretend otherwise. If one of these is your problem, you'd be the first, and that's reflected in the price.

InvoicesOverdue invoice → reminders at a steady cadence until it's paid. To be designed around Australia's debt collection guideline: limits on how often you make contact, no pressure tactics, and the amount always checked against the invoice.
ServiceService due → the customer hears from you first. For hot water, air-con, pest control, pools — anything that comes back every six or twelve months.
ReactivationA year since the last booking → one message. Usually a single seasonal campaign to your past two years of customers, which makes it a low-risk first job.
EnquiriesWeb form or marketplace lead → a reply within minutes. Best as part of a bundle; on its own it's a crowded, cheap category.

Why this matters

Most automation fails because someone automated the wrong step.

The bottleneck is rarely where people think it is. A business that believes it has a lead problem often has a follow-up problem; one convinced it needs faster quoting is really losing work to the four days before the quote gets written. Automating the wrong step makes things worse, because it adds volume to a process that was already the constraint. That's what step 01 is for, and it's the reason we won't quote a custom build off a phone call — a fixed price means nothing if the thing being priced is the wrong thing. If the mapping shows one of the standard systems already covers it, you'll be told that, and it'll cost you less.

Built on the same engine that's sent 797 emails for ClipZone since June 2026.1

Notes

Total emails sent from the outbound system for ClipZone between June 2026 and 23 September 2026. Counts sends, not recipients. A custom build reuses that engine; it does not inherit that result.

Start

Twenty minutes to see whether it fits.

Bring the process that's costing you time. If it isn't worth automating, that's a fine outcome for a first call.

Book a 20-minute call See a system in full

From $1,500 setup and $400/month, scoped up from there.

A floor, not an estimate — custom work is quoted per job