Build / 02

Automation built around how you actually work.

Off-the-shelf automation assumes your business looks like everyone else’s. It does not. This is the service for the processes that are specific to you: the follow-up sequence you keep in your head, the handover that only works because you remember to do it, the report you rebuild every Monday.

How this starts

Not with tools. With a map of where your week goes.

I sit down with you and work out what actually consumes your time: the manual follow-ups, the copying between systems, the admin that piles up, and the decisions that stall because they wait on you. Most owners are surprised by what comes out of this. The thing eating your week is rarely the thing you would have guessed.

Then I automate the parts worth automating, in the order that pays back fastest.

What gets built

Those are patterns, not a menu. If your workflow does not look like any of them, that is exactly what this service is for. There are ten more examples on the blog, ranked by how fast they pay for themselves.

The five phases

  1. Time and bottleneck discovery. What is consuming your week, and what depends on you personally.
  2. System mapping and design. How the workflow should run: where the AI helps, and where a human still needs to be.
  3. Testing and fail proofing. Real scenarios and edge cases, before anything touches a live customer.
  4. Implementation. The system goes live and you watch it run.
  5. Support and scale. It grows with the business instead of needing a rebuild.

Built on tools you can keep

n8n, Claude, OpenAI, Make, Zapier, Twilio, Airtable, Google Workspace, GoHighLevel. I pick the stack that fits your business and budget, not the one that is fashionable, and everything runs in accounts you own. When the handover is done you can cut my access and the system keeps working.

That last part matters more than it sounds. Plenty of automation work leaves you renting your own processes back from whoever built them.

Common questions

What if my process is too messy to automate?

Messy is normal, and it is usually the point. Part of the work is untangling the process before automating it. What does not survive that conversation is a process that turns out nobody needed, which is a good outcome on its own.

Do I need to change the tools I already use?

Usually not. I build around your existing stack wherever it makes sense. If something you use genuinely cannot do the job I will say so and explain the trade-off, but replacing your tools is not the goal.

Who owns the system when it is finished?

You do. It runs in your accounts, and you get plain documentation for the parts you might want to change. You can cut my access the day handover is done.

How long does a custom build take?

Most take two to six weeks depending on scope. A single workflow can be live within days. You get a clear timeline before we start.

What happens when something breaks?

I test on real scenarios before launch and build in alerts, so you hear about a problem from the system rather than from a customer. After handover I offer ongoing support, and if something fails I fix it.

Every build is custom, so the price depends on scope. You get one fixed price before I start and you pay it when the system is running. The free 30-minute audit is where you get real numbers for your business, with no obligation either way.