The five layers under the one you want to buy

The build order

Six layers, in the order they get built

Each layer produces what the next one needs. Skipping one does not save time. It moves the cost forward, to where the fix is more expensive. Open any layer to see what building it gives you in teal, and what its absence costs you in amber.

The foundation, layers one to five

Map the processes

How the work operates today, from the people who do it. Not how the manual says it works and not how the owner believes it works. The gap between those three is usually where the money is going.

What it costs to skip this

You automate the process the owner described, which is not the process the team runs. The automation is correct and the business is not. Every exception comes back as a complaint nobody can trace.

What you get from this

A picture of how the work really runs, drawn from the people doing it, with the steps nobody mentions written down. Most owners find money in the gap between that and what they believed was happening.

Write the procedures

So the work survives the person doing it, and a new hire can follow it on day one. These written rules are also what a model reads to learn how your business actually decides things.

What it costs to skip this

Nothing written down means nothing for a model to read. The tool is given the average of the internet instead of the way your business decides, and it answers confidently in somebody else's voice.

What you get from this

Procedures a new hire can follow on day one, so the work survives the person doing it. Training stops being an apprenticeship and quality stops depending on who picked the job up.

Separate the repeatable from the exceptions

The workflows that run the same way every time, and the ones that need a human decision. This layer is what says what may be automated and what may not.

What it costs to skip this

The system cannot tell a routine order from the one that needs a person, so it treats them alike. Either a human checks everything, which is the job you were removing, or nobody checks and the misses surface at the customer.

What you get from this

A clear line between the work that can run itself and the work that needs a person. That line is what makes handing something over safe rather than hopeful.

Design the data

Every record with one home and one owner. Two spreadsheets that disagree about a customer will produce two answers forever, and clean data is the one input every automated tool depends on absolutely.

What it costs to skip this

Two systems disagree and the automation picks one. It now produces wrong answers faster than people did, and with more authority, because it came out of a machine.

What you get from this

One home and one owner for every record, so the business has a single answer instead of two. Reporting becomes worth reading, because the numbers agree with each other.

Set the indicators and put a queue under the work

Standards, a knowledge base and a ticket queue, so the work is visible and countable. Until work sits in a queue, nobody can say how much of it there is or whether it got better, and there is nothing for a rule to route.

What it costs to skip this

The work is invisible, so the saving is unprovable. Twelve months later nobody can say whether the spend earned anything, which is how a pilot quietly dies.

What you get from this

The work visible and countable. You can see how much there is, where it is sitting, and whether this month beat last month, which is the first point at which improvement is provable rather than felt.

All five of those have to hold before this one works

Automate, then run delegated workflows

Automate the repetitive parts, with AI where it earns its place and nowhere it does not. Then take over the workflows the owner wants off their plate and run them as a service. This is the layer everybody wants to buy first, and it is the one that arrives last.

What happens when you start here

Each of the five failures above looks like a tooling failure and gets treated as one. The next tool is bought, and it fails in the same place, because the missing part was never in the tool.

What you get from this

The repetitive work running without a person on it, and the workflows you choose handed over and run to an agreed standard. This is the layer where the owner's week comes back.

Layers one to five are the foundation. All six together are your operating system.

Layers and phases

What gets built, and what you buy

The layers are what gets built. The phases are what you buy. They are not the same list and they do not compete. Layers one to five are mapped in phase one, designed in phase two and implemented in phase three. Layer six is automated in phase four and run in phase five.

Operations audit

What this does to the layers

Finds which layers exist, which are missing, and what that is costing. Two weeks, one workflow, from a named start to a named end.

System architecture and design

What this does to the layers

Builds layers one to five on paper. The blueprint, and yours to keep whether anything is built on it or not.

System implementation

What this does to the layers

Loads that blueprint into the software the business runs in, so layers four and five stop being documents.

Workflow automation

What this does to the layers

Layer six, and only ever on top of the five below it.

Process management

What this does to the layers

Fulcrum runs the workflows you hand over, and keeps every layer current while it does.

See the five phases in full

Six layers, in the order they get built

Map the processes

Write the procedures

Separate the repeatable from the exceptions

Design the data

Set the indicators and put a queue under the work

Automate, then run delegated workflows

What gets built, and what you buy

Operations audit

System architecture and design

System implementation

Workflow automation

Process management

Find out which layers you have