KNOWLEDGE 5 min READ

PART OF STRATEGY OPERATIONS

The word audit makes people think of accountants and compliance. This is a different animal. A business systems audit is what you run when something is clearly off but the reports disagree about what, and before you commit budget to a fix nobody has stress-tested.

Why it matters

Most expensive projects are not the wrong service. They are the right service bought for the wrong problem. A rebrand commissioned for a pricing problem. A CRM migration commissioned for a process problem. The audit is the cheapest point in the sequence at which to discover that, because nothing has been built yet.

What it examines

• The numbers: revenue, margin, acquisition cost, retention, and, crucially, whether the reports that carry those numbers agree with each other.
• The workflows: how work actually moves between people and tools, as opposed to how the process document says it moves.
• The brand and offer: whether a stranger can understand what is sold, to whom, and why it is different. See brand positioning.
• The customer journey: one real customer, followed from first contact to repeat purchase, including every handoff and every tool. See customer journey mapping.
• The technology: what is connected, what is duplicated, and where a person is quietly doing the job software was bought to do.
• The team: who owns which decision, and which decisions have no owner at all.

What it usually finds

Patterns recur. Departments optimising for numbers that contradict each other. A spreadsheet that has become load-bearing. A best-selling product with no reason for a second purchase. A sales team that has quietly written its own deck because the official one does not land. And, more often than anyone expects, the discovery that the project in the original brief is not the project the business needs.

How it runs

1. 01 Frame

   Agree the symptom, the number attached to it, and the constraints that cannot move. Deliberately not the solution. How to brief this is its own note.

2. 02 Gather

   Reports, dashboards, existing research, and access to the systems. Then time with the people doing the work, because the workflow lives in their heads more than in the tools.

3. 03 Follow the customer

   Walk one real journey end to end. Count the handoffs. Note where the story the brand tells and the experience the customer gets diverge.

4. 04 Separate evidence from belief

   For each finding: what the data shows, what still needs testing, and what is simply a strongly held opinion. All three are useful; only the first is a basis for spending.

5. 05 Rank and sequence

   Findings ranked by cost to the business, then a plan that names owners and says what happens first. If the plan cannot be acted on the following Monday, it is not finished.

When to run one

• Growth has flattened and nobody can say precisely when it started.
• Every department is individually hitting targets while the business is not.
• You are about to spend seriously on a fix, and the only case for it is that it feels decisive.
• You are preparing for a funding round, an acquisition or an audit of the accountant's kind, and diligence will ask questions the reports cannot answer consistently.

When not to

If you have a single, clearly defined problem with a capable owner and no cross-department dependencies, skip the diagnosis and hire the specialist. An audit earns its fee when the problem crosses functions or when nobody agrees what the problem is. It does not earn its fee as a ritual.

Common failure modes

• Auditing the org chart instead of the work. Interviews about process produce the official version; observation produces the real one.
• Producing observations without a decision. A deck of forty findings ranked equally is a way of avoiding the argument about what matters.
• Letting the provider's rate card shape the diagnosis. The invoice should not be the strategy.
• Skipping the customer. Internal data describes what the company did; only the journey shows what the customer experienced.

Prescription follows diagnosis. Your business deserves at least the same courtesy as your headache.

How long does a business audit take?

Typically two to four weeks, depending on how many functions are in scope and how accessible the data is. Longer than that usually means the scope has quietly become a build.

What do we get at the end?

Prioritised findings ranked by cost, a clearly defined problem, named owners, and a sequence for what happens first. Not a menu of services.

What if the audit says we do not need the project we planned?

Then you keep the money. A diagnosis that converts a guess into a defensible decision is a good outcome, including when the decision is to do less.

What does it need from our team?

Access to the reports and the systems, time with the people who do the work as well as the people who manage it, and one decision maker who agrees the frame at the start and the sequence at the end. The evidence does most of the talking, so the meetings can stay short.

GO DEEPER

Reading is free. The diagnosis is a conversation.

Say Hi

NEXT TOPICS TO LEARN