How we work

You will know exactly what you are buying before anyone writes a line of code.

Automation projects usually fail in one of two ways: an open-ended build that never quite finishes, or a system nobody uses because it fights how the business actually works. Our process is designed around avoiding both.

Book a free discovery call

01

Discovery call
30–45 minutes

We walk through how your business actually runs — where time disappears, where enquiries leak, what you keep meaning to fix. No pitch. If automation is not the right answer for your situation, we say so on this call.

You leave with

A clear read on what is worth automating first
02

System blueprint
3–5 days

We map the specific systems, how they connect to the tools you already use, what changes for your team day to day, and what it costs. You see exactly what you are buying before you commit to anything.

You leave with

Written scope, timeline and fixed price
03

Build
2–6 weeks typically

We build in visible stages rather than disappearing for a month. You see working pieces early, and we adjust while adjusting is cheap. Your feedback shapes the system as it is made, not after.

You leave with

A working system, reviewed as it is built
04

Launch and tune
2 weeks

We go live carefully, watch real usage closely, and fix the rough edges that only appear with real customers. Your team gets trained on the parts they touch, in plain language.

You leave with

Live system, trained team, tuned behaviour
05

Run and improve
Ongoing, optional

Systems that touch live business need someone watching. We monitor, maintain, and extend as your process changes — or hand over full documentation and access if you would rather run it yourself.

You leave with

Monitoring, maintenance and extensions

Setting expectations

The honest version of what working together looks like.

What you get

A written scope with a fixed price before any work starts
Working pieces to review during the build, not one reveal at the end
Plain-language training for whoever touches the system
Full documentation and access to everything we build

What we need from you

An honest walkthrough of how your business actually runs
Access to the relevant accounts and tools
Feedback at review points — usually a few hours across the project
One person who can make decisions without a committee

What we will not do

Quote a price before understanding your process
Build something we think you will abandon in a month
Automate a decision that should stay with a human
Hold your system, data or accounts hostage

Build principles

The rules that decide whether a system is still running in a year.

Technology is rarely why automation projects fail. These are.

Your process first, our system second

We map how you actually work before proposing anything. A system that fights your process gets abandoned in a month, no matter how clever it is.

Outcomes, not dashboards

Success is measured in hours returned, enquiries answered and revenue recovered — not in how many features got built.

Humans stay in the loop where it matters

Anything touching money, claims, clinical judgement or an unhappy customer routes to a person. Automation handles the volume, not the judgement.

You own what we build

Your infrastructure, your data, your accounts. Full documentation and access handed over. No hostage situations, no per-seat rent.

Honest about limits

Some things should not be automated, and some are not worth the build cost. We will tell you which is which, including when the answer is "do not do this".

Built to be changed

Your business will not run the same way in two years. Systems are built so a new stage, field or channel is an edit, not a rebuild.

Questions

About how the work happens

How long does a build take?

A focused single system is typically two to four weeks. Larger multi-system builds run six weeks or more. You get a firm timeline in the written blueprint before work starts, and we build in visible stages so you are never waiting in the dark.

Will this integrate with the tools we already use?

In most cases yes. WhatsApp, Instagram, Google Workspace, calendars, ad platforms, e-commerce stores, POS systems, accounting software, payment gateways and most CRMs are all integrable. If a tool has an API, an export, or even a report we can read on a schedule, we can usually work with it. We confirm every integration during discovery rather than assuming.

What do you need from us during the build?

Access to the relevant accounts, a walkthrough of your process, and reasonably prompt feedback at review points. Typically a few hours total across the project — the build work is ours.

What happens if we want changes after launch?

Small tuning in the first weeks is part of the project. Beyond that, changes are either covered by a maintenance arrangement or quoted as a small piece of work. Systems are built to be extended, so changes are rarely expensive.

Next step

Step one costs nothing and takes thirty minutes.

We walk through your week, find where the time actually goes, and tell you what is worth automating first. If the answer is 'nothing yet', we will say that too.