The Efficiency Stack: How to Fix Business Systems Before Automating Them

The fastest way to waste money on business software is to start with the software.

That sounds backwards, especially coming from someone who builds custom systems, portals, dashboards, and automation. But the pattern is painfully consistent: businesses buy tools before they understand the work those tools are supposed to support.

The Efficiency Stack is the framework I use to avoid that. It is a simple way to work out what needs fixing first: Foundation, Standardisation, Automation, then Visibility.

The four layers

Foundation is understanding how the business actually works. Not the brochure version. Not the version in the owner's head. The real version, including the awkward handovers, duplicate data, approvals, spreadsheets, and "ask Sarah" moments.

Standardisation turns that messy reality into repeatable operating patterns. This includes process maps, SOPs, permissions, data conventions, and agreed ways of working. It is not glamorous. Neither is plumbing, until it fails.

Automation is where software starts doing the repeatable work. That can mean workflow automation, a custom portal, an internal system, integrations, AI-assisted steps, or a reporting pipeline.

Visibility is the owner-level outcome. The business should produce useful information as work happens, not after someone spends Friday afternoon building a spreadsheet report and quietly hating everyone.

Why most businesses jump too high

Most automation vendors sell Layer 3. That is where the demo is. You can show a workflow firing, a dashboard updating, an AI assistant classifying something, or a shiny portal doing portal things.

But if the business is actually weak at Layer 1 or Layer 2, Layer 3 will struggle. The tool ends up carrying unresolved decisions. Who owns this task? What counts as complete? Which customer record is the source of truth? Who can approve exceptions? Why are there four spreadsheets named final?

This is why the companion article why business automation fails focuses so heavily on the layers underneath the tools.

Layer 1: Foundation

Foundation work means getting the truth onto the table. The business may think it has a sales process, onboarding process, fulfilment process, or reporting process. The first job is to check whether that process is real, consistent, and understood by the people doing the work.

This is where process mapping before automation matters. You are not trying to produce a museum-grade diagram. You are finding the places where time, data, and accountability disappear.

Layer 2: Standardisation

Standardisation is where the business agrees on how work should happen. This includes SOPs, naming conventions, document templates, roles, approvals, and permissions.

Without this layer, automation becomes fragile. One staff member enters data one way, another uses a different status, and a third has a private workaround. The system cannot enforce consistency if the business has not chosen what consistency means.

If this sounds familiar, the article on escaping tribal knowledge is the painful but useful next read.

Layer 3: Automation

Automation is where the work starts moving faster. Repeated admin can become a workflow. Client updates can move into a portal. Spreadsheet logic can become a proper internal system. Manual reporting can become a dashboard.

This is where custom software often makes sense, especially when the workflow crosses several tools or forms part of the service experience. It does not mean everything should be custom. It means the system should fit the business, not force the business into weird little knots.

Layer 4: Visibility

Visibility is the layer many owners are really asking for, even when they describe the problem as automation. They want to know what is stuck, what is due, what is profitable, what needs attention, and where the team is spending time.

A good system makes that visible naturally. It does not require a manager to chase five people, export three CSVs, and sacrifice a perfectly good afternoon to Excel. Read building your first business dashboard if this is the layer causing the most pain.

How to use the stack

The stack is a diagnostic tool. If a workflow is unclear, do not start with software. If the process is clear but inconsistent, standardise it. If the process is standard but manual, automate it. If automation is running but the owner still cannot see what is happening, improve visibility.

This is also how I scope projects. A Technology Strategy Session should identify which layer is weakest, what order the work belongs in, and which parts are worth building properly.

The point is not to make a grand digital transformation plan. The point is to stop guessing, fix the lowest weak layer, and build systems that make the business easier to run.