Before you automate, audit: a practical guide to mapping how work actually flows through your company
Most companies automate the wrong thing first. A 90-minute audit maps how work really flows and shows what to hand to people, apps, and AI agents first.
4 min read
Updated
Key takeaways
- Automating before auditing usually moves the bottleneck instead of removing it.
- Audit your two or three money paths, like quote-to-cash or procure-to-pay, not every process in the company.
- For every handoff, capture who touches it, where it happens, how long it waits, and what someone has to know to do it.
- Your automation backlog is the work that waits, the work that gets re-entered, and the work only one person knows how to do.
- Score candidates by frequency, time saved, and the damage if they break, then fix the top one first.
Most companies automate the wrong thing first. They pick the task that annoys someone the loudest, wire up an integration, and discover three weeks later that the bottleneck moved instead of disappearing. The fix isn't better automation tooling. It's a short operations audit before a single workflow gets built.
This is a practical guide for startups and small businesses: how to map the way work actually flows through the business, and how to turn that map into the first things worth automating, whether the work goes to people, apps, or AI agents.
Why teams skip the audit, and what it costs
Automation feels like progress. Auditing feels like homework. So teams jump straight to building, and run into three predictable failures.
- Automating a broken process. If quotes sit in someone's inbox for two days before anyone opens them, a faster quote generator just produces faster pile-ups.
- Automating in the wrong order. The most visible task is rarely the one with the biggest downstream impact. The highest-leverage fix is often an unglamorous handoff nobody owns.
- Automating without a home. Scripts and agents built in isolation (in a chat window, a notebook, a forgotten Zap) die when their author gets busy. An audit tells you what to automate and where that automation has to live to become part of how the company runs.
The 90-minute operations audit
Block an hour and a half with the people who actually touch the work, and go through four steps.
Step 1: List your money paths
Every company has two or three end-to-end flows that revenue depends on: quote-to-cash, procure-to-pay, onboard-to-renew. Name them. You're auditing those, not everything.
Step 2: Walk each path, handoff by handoff
For each step, capture four things: who touches it, what tool it happens in, how long it waits, and what someone has to know to do it. A few rows of a quote-to-cash path might look like this:
| Step | Who | Tool | Waits | What you need to know |
|---|---|---|---|---|
| A quote request arrives | Nobody owns it | Shared inbox | Up to 2 days | Which customer, which products |
| Price the quote | Sales rep | Spreadsheet | Half a day | Current supplier prices, the customer's discounts |
| Approve a discount | Sales manager | Chat | 1 day | Margin rules, the customer's history |
| Turn it into an order | Operations | ERP | Same day | Stock and delivery dates |
The last column is the one everyone skips, and it's the one that matters most once AI agents enter the picture. An agent can only do a step if it can reach what the step requires.
Step 3: Mark the three queues
On every path you'll find the same three patterns:
- Work that waits: handoffs with no owner.
- Work that's re-entered: the same data typed into two systems.
- Work held hostage by one person: "ask Marco, he knows."
Together, these are your automation backlog.
Step 4: Score before you build
Rank the candidates by how often they happen, times the time they'd save, times the damage if they break. A daily 20-minute reconciliation that three teams depend on beats a weekly report nobody reads. Fix the top one first, and only the top one.
Turning the audit into a running system
Here's what most guides leave out: an audit is only useful if its output doesn't rot in a slide deck. The map you just built, with its flows, owners, tools, and knowledge, should become the foundation your automations run on.
That's how a programmable business works, and it's what Opser is built for.
- The paths become apps. Quote-to-cash runs through Sales, Customers, and Finance on one shared record, so re-entered work disappears instead of getting a sync job.
- Every handoff gets an owner. Each step has a person or an agent on it, and agents act under the permissions and approvals you set.
- The "ask Marco" knowledge gets a home. The answers go into the Wiki and the records, and agents answer from them instead of interrupting Marco.
- The gaps get built. If a step needs a tool nobody sells, describe it and it's built into the same workspace, on the same data.
- The fix sticks. When the process changes, you change the system once, and every person and agent works the new way from then on.
Your first week after the audit
- Days 1 and 2: rebuild the highest-scoring handoff as an explicit workflow with a clear owner and trigger.
- Days 3 and 4: give an agent the lookup work, the "ask Marco" questions, so your experts stop being a search engine.
- Day 5: re-run the audit on that one path. If the queue moved instead of shrinking, you've found the next constraint.
Then put the audit on a schedule. An agent can pull the same numbers every month, so you can see whether each money path is actually getting faster.
Getting better at how your business runs compounds. The companies that win aren't the ones with the most automations. They're the ones that got honest about how work actually flows, then built a system that keeps getting better at it.
Frequently asked questions
- What should a company automate first?
- The handoff that scores highest on frequency, time saved, and damage if it breaks, usually a step where work waits with no owner or gets typed into two systems. It's rarely the task that annoys people the most.
- How long does an operations audit take?
- About 90 minutes with the people who do the work. You map each handoff on your money paths, mark where work waits, gets re-entered, or depends on one person, and score what to fix first.
- What is a money path?
- An end-to-end flow your revenue depends on, like quote-to-cash, procure-to-pay, or onboard-to-renew. Most companies have two or three.
- Where do AI agents fit after the audit?
- In the work the audit uncovers: answering questions only one expert can answer today, chasing handoffs nobody owns, and keeping records in sync, working from the same context as the team and under its approvals.
Founder · Senior Software Engineer
Simone Zamparini is a founder and senior software engineer.
