Done-with-you workflow build

For businesses where a classroom is the wrong shape. One job, built properly, running on real work before we finish.

Who this is for

Owner-operators and field businesses, mostly. Trades, cleaning and maintenance, small service businesses — anyone whose honest answer to “can you sit in a room for half a day” is no, and who has one specific job that's costing them money every week.

How it runs

We pick the one job. Usually same-day quoting, monthly client reporting, or follow-up that never happens.
We build it from your existing documents, so the output sounds like you rather than like a template.
We run it on live work together, and fix what breaks. This is the part that makes it stick.
We hand over with the setup, a one-page how-to, and the two follow-ups already written.

The jobs that pay for themselves fastest

Quote out the same day as the site visit rather than Thursday night.
Two follow-ups on every quote, which most businesses never send at all.
Job notes and variations dictated on the drive home and written up before invoicing.
The monthly client report that currently happens on a Sunday.

What stays with you

Certification, compliance sign-off and safety determinations don't move. Drafting speeds up; accountability doesn't shift.

How it differs from a workshop

A workshop is a room of people learning method. A workflow build is one job, constructed on real work, with the person who owns that job sitting next to you. Different shape, different outcome, and the two are not longer and shorter versions of each other.

This is the right engagement when there's one document that keeps costing you an evening, and the wrong one when the problem is that eight people are each doing something slightly unsafe.

Pick the jobOne job, named, that you do at least monthly and currently do yourself after hours. The tender. The monthly report. The quote follow-up.
Watch you do itScreen shared, your real work, no tidying up beforehand. The inefficiencies we're looking for are usually the habits nobody mentions.
Build it with youNot for you. Your hands on the keyboard for most of it, because a setup you didn't build is a setup you can't adjust when the format changes.
Run it on the next oneThe real test is the next live instance of the job, not the one we practised on. We stay for that.

Four steps, usually across two sessions with a week between them so the job comes around again naturally.

What you own at the end

A working setup — a project or saved instruction holding your context, your examples and your format — that produces the document from your inputs.
A written page explaining how it works and what to change when the template changes, so it isn't stranded with whoever was in the room.
The checking step, written down: what a person confirms before anything leaves the building, and who that person is.
The transferable part, which is the method. The second job you build yourself, and most clients do.

If you can name the document, we can usually tell you on a first call whether this is a two-session build or something smaller.

Start an enquiry

Jobs this works well on

Long, templated, repetitive, and currently done by someone senior at night. Tenders and capability statements. Monthly client reports. Scopes of works. Site instructions for a casual workforce. Standard letters that explain a process. Induction and policy documents that are permanently out of date.

Jobs it doesn't work on

Anything where the output is a regulated judgement rather than a document: clinical decisions, financial advice, tax positions as distinct from tax admin, safety sign-off. We'll say so on the first call rather than three sessions in.

The questions we get asked about this

Do you build it for us or with us?

With you, deliberately. A setup built for you breaks the first time your template changes and nobody knows which part to edit.

How long does it take?

Usually two sessions a week or so apart, so the job comes around again naturally and we're there for the live run. Some jobs are one session.

What do you need from us?

The job, a de-identified example of a good past output, and the person who actually does it. The last one is not optional.

Will this work if our template changes every year?

That's the normal case, and it's why you build it rather than us. The written page covers what to change when the format moves.

Talk it through before you commit. Tell us what the business does and what's eating the week. If we're the wrong fit we'll say so, and usually we can point you somewhere better.