Which process should you automate first?
Most automation projects pick the wrong workflow. They pick the one that is annoying, or the one someone saw a demo of, rather than the one that is both expensive and stable enough to build against. This audit separates those two things, because they are the two that decide whether a build holds.
Enter your workflows to see the time and cost snapshot instantly. Request the full ranking and practical next steps by email when you are ready.
The prize
How many hours a year the workflow eats, and what those hours cost at your staff rate. A process that runs 25 times a week for 12 minutes is 240 hours a year. That is the number worth arguing about, not whether the tool is impressive.
The readiness
Whether the process is the same every time, whether it is written down, and whether anyone would own it once it runs. A workflow can be worth a fortune and still be unbuildable this month.
The blast radius
What happens if it produces a wrong output and nobody notices. This never rules a workflow out. It decides whether a person approves the result before it leaves the building.
Start with one workflow you know well, such as responding to new enquiries or preparing quotes. Add more to compare them. The snapshot updates immediately; the full recommendation arrives by email if you request it.
Wages plus on-costs for whoever does this work. Used to turn hours into dollars.
a year, worth $0
The full report ranks this workflow by value and readiness, then gives you a next step.
Your snapshot
hours a year across every workflow listed
of estimated staff time, at $55 an hour
ready to build now, holding 0 hours ($0)
These figures describe time spent. They are not a promise of savings from automation.
Get your full report
Get each workflow ranked by value and readiness, with the reason behind its result and a practical next step. We will email the report based on your answers.
Name each workflow and enter how often it runs and how long it takes to request your report.
The audit is the easy part
Knowing which workflow to build is worth something. The next step is deciding who will build it and who will own it. We can scope and build the workflow with a clear handover, or train your people to build and maintain automations themselves.
Bring your report. It gives us a useful starting point for a first conversation.
Questions
Do I need to give you my email to use this?
No. You can enter workflows and see your hours and cost snapshot without an email address. To receive the detailed ranked report and next steps, enter your email and request delivery. Your workflow names and answers are sent to 13Labs only when you request the report. Our audit analytics events contain usage and headline numbers, not your email or workflow names. The report email includes one relevant 13Labs offer; we do not add you to a mailing list or send follow-up emails.
What counts as one workflow?
A sequence of steps with a beginning and an end that produces one outcome, like turning an enquiry into a booked job, or turning a completed job into a paid invoice. If you cannot say what finishing it looks like, it is probably two workflows.
Why does a high-value workflow sometimes say to fix the process first?
Because a build can only be as consistent as the process it copies. If the same job is done three different ways by three people, an automation will encode one of those ways and quietly break the other two. Running it manually the same way three times and writing down what you did is usually a fortnight of work, and it is what makes the build hold.
Does a high blast radius mean I should not automate it?
No. It means the output needs a human approving it before it goes to a customer. Plenty of the highest-value automations in a business are draft-and-review rather than fully unattended, and that is a design decision rather than a failure.
What do I do with the result?
Use the free snapshot to understand the size of the work. Request the emailed report for a ranked list, the reasoning behind each result and next steps you can discuss with your team or a developer.
Read next
The AI Readiness Audit
The people side of this: the twelve questions that surface which workflows are bleeding time in the first place.
Break a workflow into tasks
Automation decisions are made at the task level, not the workflow level. How to split one and mark the human steps.
A prompt pack is not automation
Why a documented prompt library is still a person doing the work by hand, and what has to change for it to count.
Run it manually three times first
What to do with a workflow the audit says is valuable but not ready to build against yet.