Free operations review

Your team spends its week on work that doesn't need them

I find the repetitive work inside your operation and make it run on its own. Most things ship in three to five days, measured in hours and money — not in a deck.

Teams of 20–200. Three spots open this month.

10 hrsa week, guaranteed
If your team doesn't get at least ten hours a week back in the first month, you don't pay for the second. Not a projection — the number gets measured against your own baseline, and I write it down before we start so neither of us can move it afterwards. Published research puts data entry and collection at roughly 1.8 hours per person per day. Ten hours across a team is a low bar, and it should be.
Where the hours go

What this looks like in your industry

Seven operations I know well, and the process that eats the week in each.

Insurance brokerage

The same policy, keyed into three systems

18 minof keying, every single policy touch

Carrier portal, management system, CRM. None of them talk, so every policy touch is typed out again — around eighteen minutes, every time.

Fixed: captured once where it first exists, pushed to the rest, and renewals chase themselves instead of living in someone's memory.

Accounting practice

Two weeks of chasing before work starts

11.4 daysthe average time to fully onboard one client

Documents get asked for one at a time as someone realises they're needed. The client sends four of seven. Onboarding stretches past a fortnight.

Fixed: everything requested once, up front, with the chasing running itself and stopping the moment a document lands.

Creative agency

Feedback arriving in four different places

30%of agency hours lost to unbilled scope creep

A marked-up PDF, a Loom, a reply-all, a text to the account manager on Friday. Someone stitches it together before a designer can touch it.

Fixed: it all lands against one version, and contradictions get flagged before the revision is built, not after.

Logistics

The warehouse and the books disagree

35 hrsa week of manual entry between two systems

Two systems hold the same shipment and neither writes to the other. Somebody reconciles daily, and the misses show up as wrong invoices at month end.

Fixed: entered once at the operational end, and mismatches surface the same day instead of during close.

Clinic group

The Tuesday slot nobody refilled

$300–500lost for every empty chair hour

Recall lists get built by hand and worked between patients arriving — so they're dropped exactly when the schedule most needs filling.

Fixed: a cancellation offers itself to whoever wanted an earlier appointment, before the hour is lost for good.

DTC & wholesale

Finding out from the customer

35–45%of all support tickets are “where is my order”

A shipment stalls and nobody watches the tracking feed, so the first anyone hears is a support ticket that's already angry. Wholesale orders get retyped from PDFs.

Fixed: stalled shipments trigger contact before the complaint, and purchase orders arrive staged for one-click confirmation.

Professional services

Monday's numbers, made on Friday

1.8 hrsa day per person, just collecting and entering data

Utilisation, billing and pipeline live in three places. The weekly view is assembled by hand, so it's late — and decisions get made on a fortnight-old picture.

Fixed: the view builds itself continuously, and thresholds raise themselves before anyone has to notice.

Figures above are published industry benchmarks for each sector — they describe the size of the problem, not results I'm claiming. Sources available on request.

How it works
1

Find where the hours go

I map how work actually moves through your company and cost every repetitive step: hours a week, dollars a year.

2

Fix them, fast

Send me any repetitive process. One gets built at a time, most ship in three to five days. No scoping calls, no quotes.

3

Keep them alive

A vendor changes a form, someone adds a field — it stops silently. Everything I build stays owned and working.

The fair questions

The three I'd ask in your seat

You should be sceptical of a monthly fee from someone you've just met. These are the questions worth asking, answered straight.

"Couldn't we just build this ourselves?"

Probably. The tools are cheap and genuinely good now. That isn't the part I'd worry about.

The question is who does it, and what they stop doing while they do it. The person capable of building it properly is usually the one you can least afford to lose for three months — so it becomes an evenings-and-weekends project competing with the work you hired them for.

"Why not just hire someone for this?"

Because that's $120,000 a year and three to six months before you find out whether the person was right for it. If they weren't, you've spent both and you're starting over.

This is $3,500 a month, the first thing is running inside a week, and you stop the moment it stops being worth it. Hire when this becomes something your business does permanently — that's a real point, and I'll tell you when you reach it.

"What if we run out of things for you to do?"

Then you should stop paying me, and I'll say so first.

Most companies your size have more repetitive work than a year of my time — but if the queue empties, keeping a retainer for maintenance alone is bad value. You keep everything built, documented, running in your own accounts. Nothing is hostage to the subscription.

Who you're working with

One person, and that's deliberate

Fifteen years in operations, product and design — including running a business unit at a bank, where sales processes, reporting and the daily admin around them were mine to fix, and years building software for companies in the US and Canada.

You work with me directly. No account manager, no junior doing the build, no handover document between us. The trade is honest: I take a small number of clients at a time, because one person can only have one thing in the air per client and still ship it in a week.

Pricing

Three ways to work together

One thing
$4,500
once
  • One process, built and handed over
  • Documentation included
  • No ongoing support
Most take this
Ongoing
$3,500
a month
  • Unlimited requests, one at a time
  • Most ship in three to five days
  • Everything built stays maintained
  • Monthly hours-and-money report
Full operations
$8,000
a month
  • Several processes in parallel
  • Your team trained to run them
  • Leadership reporting
Start here

Start with a free breakdown

Forty minutes. You get a map of your operation with every repetitive process costed in hours and money, ranked by payback. Yours to keep, whether or not we work together.

No call script, no deck. You talk, I map.