Journal

Playbook

6 min read

What an automation audit actually measures

Twenty minutes, one workflow and a stopwatch. A look at the numbers we collect and the ones we ignore.

Ines Kovač

Delivery lead

An audit is a short call with a long tail. In twenty minutes we walk through one workflow with the person who does it every day, and we leave with enough to price the build and estimate what it would save.

What we write down

  • How often the task happens, per day or per week.

  • How long one run takes, from opening the first tool to closing the last.

  • Where the information comes from, and where it has to end up.

  • What goes wrong today, and how anyone finds out.

What we ignore

Tool wish lists, and how impressive a demo would look. If the numbers don’t show a payback within a year, we say so, and we suggest a cheaper fix when there is one.

Next post

Field notes

Keep a human on the loop, not in it

Free audit · 20 minutes

Want this applied to your team?

We map it with you, price it and tell you what it would save. If it isn’t worth automating, we’ll say so.

Free audit · 20 minutes

Want this applied to your team?

We map it with you, price it and tell you what it would save. If it isn’t worth automating, we’ll say so.

Free audit · 20 minutes

Want this applied to your team?

We map it with you, price it and tell you what it would save. If it isn’t worth automating, we’ll say so.

Create a free website with Framer, the website builder loved by startups, designers and agencies.