The Automation Audit

Your team is doing by hand what a machine should be doing at 3am.

Five days. Your ten most repetitive processes, mapped and costed. The top three designed. The first one built and running on your accounts before I send the invoice for the rest.

Book the audit → How it works ↓
How it works

Map. Design. Build the first one.

Most automation projects start with a proposal and end with a deck. This one starts with a 45-minute call and ends, five business days later, with something running.

01
The mapYour ten most repetitive processes, each with hours per week and what it costs you at your team's loaded rate. Built from one call and read-only access to your tools.
02
The top three, designedRanked by hours saved against build cost. Each one in plain English: the trigger, the steps, where it can fail, and what happens when it does.
03
Number one, builtA working workflow on your accounts, doing the job, with alerts to your Slack or inbox when anything breaks. Not a mockup.

If I can't find ten hours a week to automate, you get the $1,500 back.

The guarantee
Price
$1,500 · paid upfront · five business days

The audit fee is credited against the first build. Builds for processes two and three are fixed price, $2,500–5,000 depending on what they touch, with a review point after version one where either of us can walk. If you want it looked after, a care retainer covers monitoring, fixes when your tools change, and one new small automation a month.

Who this is for: owner-led agencies and service businesses with five to thirty people, where someone on the team spends their week retyping leads into the CRM, assembling reports, chasing invoices, or onboarding clients from a checklist.

How I work

I build with Claude Code and n8n. I don't pretend otherwise.

I make the decisions, I run it daily, and when it breaks I work the fix with the AI and make the call. I'm not a hand-coder. What I am is the person who designs the thing so that when it fails at 3am, it tells you exactly what failed instead of going quiet.

Everything I build has the same skeleton: one source of truth, a state for every record, a retry policy for every step, and an error path that logs what broke and alerts a human. That's the discipline, and it's the part most automation is missing.

The receipt

Hydra: a video factory that ran itself for 41 days.

Before I sold this, I built it for myself. Hydra is an autonomous pipeline that plans, scripts, voices, illustrates, edits, captions, uploads and schedules long-form YouTube episodes with nobody in the loop. Fourteen stages, twelve external services, every one with retries, a spend cap and an incident log.

41days unattended
22episodes published, 3 channels
25,668actions taken
61 / 61incidents opened / resolved
$13median cost per episode
0silent failures

Every number comes from the system's own database. The output is public: youtube.com/@PlimsollShow. I stopped it because faceless YouTube doesn't pay well enough, not because it didn't work. The pipeline is the asset. Now it runs for other people's businesses.

Start

One email. Five days.

Tell me what your team does by hand that you're tired of paying for. I'll reply within a day with a time for the call and a payment link.

evan@agenbroad.com →