A worked example

Deliberately unglamorous.

This is the build that comes up most often. Nothing in it needs a new system, a migration, or a change in how anyone works. It just stops the same four things being dropped every week.

01An enquiry arrives
Website form, email, or a phone note typed into the inbox. Your client keeps using whatever they already use.
02It is read and classified
New job, existing client, supplier, or noise. The uncertain ones are flagged rather than guessed.
03A record is created
Straight into the CRM or practice-management system you already pay for, with the details filled in.
04A reply is drafted
In your own language, with the right next step. It waits in a queue for a human to approve.
05You press send
Approved in a few seconds from your phone. Nothing reaches a client without someone deciding it should.
06Nothing is dropped
Anything still unanswered after your chosen window comes back to a person, with the clock shown.

A heavy cast-steel desk press poised above a single blank sheet of paper — Step five is the whole argument. A person decides; the machine does the carrying.

Send me a sample Flow Map NO CALL REQUIRED · ONE PAGE · REAL EXAMPLE

The shape of it

Five stages, and you can stop at the quote.

01Fit call — 30 minutes, free
Where the hours go, what you already pay for, and whether this is worth doing at all.
02Flow Map — 3 to 5 days
One page: the leak, what to automate first, and what it will cost. Credited against a build booked within 30 days.
03Fixed quote — one page
Scope, price and dates on one page, signed before anything starts. The work is never billed by the hour.
04Build — 1 to 5 weeks
In your accounts, and you watch each workflow run as it is built, so there is nothing to reveal at the end.
05Handover — and a 14-day fix window
Documentation, a walkthrough with the team, and every login already in your name.

A workbench under a single lamp: an open notebook, a pencil, a steel rule and three machined parts — One person doing the work, which is why the intake is capped at two builds.

The rules we work to

Contractual habits, not marketing lines.

Ask any provider the same six questions. The answers tell you more than the portfolio does.

Ownership

You own everything. Accounts, keys, workflows, code and content sit in your name from the first day, not ours.

Scope

Fixed scope in writing before any build. Changes are priced as change orders before the work starts, never after.

Judgement

A human reviews anything that touches your clients or your money. Drafts wait for approval until you decide otherwise.

Fail-safe

A broken workflow stops and alerts. It does not guess, retry silently, or quietly corrupt your data.

Language

Plain Australian English. Every build is explained in the language your clients use; if we can't manage that, we don't ship it.

Intake

Two active builds at a time. Boutique means the person you met does the work. The waitlist is the honest answer.

At handover

What you walk away with.

The test is simple. If the engagement ended the day after handover, would everything keep running and would you be able to change it? Here that answer is yes, in writing.

Every account in your name. Automation platform, model providers, integrations. Set up under your billing and your logins from day one, not migrated to you later as a favour.
The workflows themselves, exportable, in a format the rest of the market can read. No proprietary wrapper, no licence to keep paying.
Written documentation: what each workflow does, what it touches, what to check when something looks wrong, and how to switch it off.
A trained team. A walkthrough with whoever will actually be using it, included in the price.
A 14-day fix window after handover, for anything that does not behave the way the documentation says it will.

Why this matters, at length →

A wall of dark metal archive drawers, one slightly open

Straight answers

The questions everyone asks.

Who owns the automations once they are built?

You do, unconditionally. Everything is built inside the client's own accounts, under their own logins and API keys. If the engagement ended the day after handover, every workflow would keep running and every login would already be yours.

Is it safe to use AI with confidential client information?

It depends entirely on what data goes where. Workflows are built so a human reviews anything that touches a client or money, sensitive data stays in systems you already control, and models run under your own accounts. Regulated practices should confirm their own privacy and professional-conduct obligations.

What happens if a workflow breaks?

It stops and alerts a person. It never guesses, never retries silently, and never writes half a record. Every build ships with a 14-day fix window after handover, and Care covers monitoring beyond that if you want it.

Do we have to change the tools we already use?

Almost never. The work goes on top of the CRM, practice-management system and accounting package you already pay for. A migration is a separate decision and we will tell you if we think one is warranted rather than quietly building it in.

Deliberately unglamorous.

Five stages, and you can stop at the quote.

Contractual habits, not marketing lines.

What you walk away with.

The questions everyone asks.

Thirty minutes. No deck.