🎁Free pack, video 010

The Leak Worksheet

Price the leak before you price the build: how many hours a month go to work a system could do.

Unlock this pack

One email opens this pack and every other one in the library, now and later. No card, no course.

Inside: Steps, Worked example (made-up business), Is the job ready to automate?, The question the total answers, 1 file to download.

You get the library link by email, then a few short emails on real builds. One click unsubscribes. See our privacy policy.

You're in. The pack is open below.

Unlocked before on another device? Enter the same email and it opens straight away.

Steps

  1. Open leak-worksheet.csv below in a spreadsheet, or copy the columns onto paper.
  2. List the repeating jobs in your business that are done by hand. One job per row. Start with the ones that annoy you most.
  3. For each job, write how many times a month it happens and how many minutes each time takes.
  4. The hours_per_month column does the math for you: times per month, times minutes, divided by 60.
  5. Answer the two readiness questions for each row: is it done the same way every time, and does it repeat every month. Write yes or no.
  6. Add up hours_per_month for the rows where both answers are yes. That total is your leak.
  7. Multiply the total by 12. That's the hours a year the leak costs you. Divide by 8 to see it in working days.

Worked example (made-up business)

Worked example (made-up business)
Job: check each vendor invoice against what was spent
Times per month: 40
Minutes each time: 20
Hours per month: 40 x 20 / 60 = 13.3
Same way every time: yes
Repeats every month: yes

Job: prepare the yearly tax pack
Times per month: 1
Minutes each time: 300
Hours per month: 5.0
Same way every time: yes
Repeats every month: no  (it happens once a year, leave it out of the leak)

Leak = 13.3 hours a month = 160 hours a year = 20 working days.

Is the job ready to automate?

Run every job you counted through these four checks before you spend anything on it.

Is the job ready to automate?
1. Written down. Can you write the steps on one page? If you can't, the process isn't ready. Write it down first.
2. Same way twice. Do two different people do it the same way? If not, agree one way first. Automating a mess only makes the mess faster.
3. Stable. Has the process stayed the same for the last few months? If it changes every few weeks, wait. A moving target costs a lot to build and even more to keep fixing.
4. Frequent. Does it happen often enough to matter? A job you only do once in a while stays by hand until it happens more.

If a job fails any one of these, fix that first. Then it counts toward your leak.

The question the total answers

The question the total answers
Not: what does the build cost?
But: what does the leak already cost me every month, and is it worth more to fix it once?

If you'd like the written audit to run this math on your own business: otimizagency.com/audit

Files in this pack

📬Free audit

Want this running without you?

This pack does the job by hand. If you would rather it ran on its own, send us your stack and your biggest time-sink. A written audit comes back by email, usually within two working days. Free, and no call.

Get my free audit