04 / RESOURCES / PLAYBOOK
What a systems audit covers (and why it comes first)
Before building anything, map what you have. What a good systems audit looks at, how the session runs, the questions it asks, and what you should walk away with.
A systems audit is a short, structured look at the tools, data, and processes a business runs on. Its job is to find where time and information are being lost, and to turn that into a clear plan before anyone builds anything.
Skipping it is how teams end up with a new tool that solves the wrong problem.
What gets reviewed
An audit looks at four layers, from the work people do down to the tools underneath.
The four layers of an audit
- Pain pointsTasks people dread, reports nobody trusts
- WorkflowsHow a lead becomes a customer, how work is handed off
- DataWhere information lives and how it moves
- ToolsEvery app, what it is for, who uses it, what it costs
- Tools: every app the team uses, what it is for, who uses it, and what it costs.
- Data: where customer and operational information lives, how it moves, and where it gets copied by hand.
- Workflows: how a lead becomes a customer, how work gets assigned, and how handoffs happen between people.
- Pain points: the tasks people dread, the reports nobody trusts, and the questions nobody can answer quickly.
How it usually runs
- 01Working session
With the people who do the work, not only the people who manage it.
- 02Tool walkthrough
The real tools on screen, including spreadsheets and inbox rules.
- 03Flow map
How information moves today, workarounds included.
- 04Prioritized plan
Improvements ranked from quick wins to larger builds.
Questions a good audit asks
- Walk me through the last new customer, from first contact to first invoice.
- Where do you type the same information more than once?
- Which report do you look at every week, and do you believe it?
- What happens when someone is out sick for a week?
- Which tool would you cancel tomorrow if you could?
The answers are usually more revealing than any settings page.
What you should walk away with
- A plain-language map of your current systems.
- A short list of the changes that would save the most time or reduce the most risk.
- A clear scope for the first project, so there are no surprises later.
Example: part of a current-state map
- Website formSends email
- Shared inboxCopied by hand
- CRMMissing source field
- SpreadsheetWeekly report
A good audit is useful even if you never hire the person who ran it. If you cannot act on the findings yourself, ask for them in a form someone else could pick up.
Common questions
How long does an audit take?
For a small team, usually a week from first session to written plan, with a few hours of the team's time.
Do we need to prepare anything?
A list of the tools you pay for and a couple of recent examples of work moving through the business. Messy is fine. That is the point.
What if the audit says we do not need to build anything?
Then it did its job. Sometimes the fix is a setting, a cleanup, or a change in habit.