The Three Layers of a Business
On why most strategy frameworks are missing the middle layer, and what changes when you name it.
Most of the way businesses get described, in books and frameworks and consulting work, treats the company as a single thing operating on a single layer. The questions are tactical — what should we do, who should we hire, what should we build, where should we focus. The questions are answered with strategy. The strategy is supposed to make the company successful.
This is incomplete. A business is not one layer; it is three. Confusing them produces most of the frustration that founders feel when they cannot explain why smart advice does not produce the results it promises.
I have come to see businesses as operating on three structural layers, and I want to lay them out plainly, because once you can see them you can see why the work I do happens where it happens, and why most consulting works at the wrong altitude.
The three layers
Substrate is what the company actually is. The structural reality underneath every description, every pitch, every org chart. It is what the company does when nobody is watching, what the customer actually pays for, what the team mobilizes for when an emergency hits. It is the layer the rest of the business is built on, whether the founder has named it or not. Most companies have a substrate they have never articulated, and the gap between the named version and the actual one is where most operational friction lives.
Experience is how the company is lived. The felt reality of being inside it, working in it, buying from it, leading it. It is the layer where founders burn out. It is the layer where employees decide whether they want to be there. It is the layer where customers decide whether to renew. Experience is not the same as substrate — a company can have a sound substrate that is being lived as friction (because the systems are wrong) or a fractured substrate that is being lived as smoothness (because the people are heroic). Experience is the lived translation of the substrate, mediated by everything that sits in between.
Strategy is what the company decides to do. The expansion plans, the hiring decisions, the product roadmap, the market positioning. Strategy is downstream — it depends on having a clear picture of what the company is (substrate) and what the company feels like to run (experience). Without those two layers settled, strategy floats free of reality. It produces decisions that look reasonable on paper and then quietly fail to materialize when the company tries to execute them.
Most consulting works at the strategy layer. Some excellent coaching works at the experience layer. Almost nothing works at the substrate layer. This is what Substrate is for.
Why missing the middle layer matters
The reason I want to name the experience layer separately, rather than collapsing it into substrate or strategy, is that experience is where founders feel the friction first. The substrate gap shows up in lived experience long before it shows up in strategic failure.
A founder who is exhausted by their own company is rarely exhausted by the work itself. They are exhausted by the gap between how the company is supposed to feel (according to the deck) and how it actually feels day to day. The deck says they are running a high-growth software company; the daily experience is that they are running a high-touch services business with software as the delivery mechanism. The gap between those two pictures is what produces the exhaustion. It is not a strategic problem. It is not a substrate problem. It is an experience problem caused by a substrate problem.
If you only have two layers — substrate and strategy — you cannot see this. The founder's exhaustion looks like a personal problem. Hire an executive coach. Read a book about resilience. The actual cause — that the company's lived experience does not match its stated structure — never gets named.
A team that is underperforming relative to what the strategy says they should be producing is rarely underperforming because they are lazy or incapable. They are underperforming because the experience of doing the work does not match the experience the strategy assumes they are having. The strategy assumes a coordinated team working from a shared picture of the company. The experience is that the team is operating from three different pictures and translating between them constantly. The output looks like a strategic failure. The cause is in the experience layer.
A customer that signed up enthusiastically and is now churning is rarely churning because the product got worse. They are churning because the lived experience of being a customer has drifted from what they thought they were buying. The substrate may have shifted under them. The strategy may have changed without anyone telling them. The experience layer is where they notice. The experience layer is also where they leave.
Naming experience as its own layer makes these failures visible. It lets you ask: is this a substrate problem, an experience problem, or a strategy problem? That question alone surfaces things that consulting frameworks calibrated to two layers cannot see.
What an audit does at each layer
The audit phase of an engagement reads the company at all three layers simultaneously, because they reveal different things and the divergences between them are where the real work is.
At the substrate layer, the audit reads what the company actually is. The four signals I have written about elsewhere — what the founder says in private, what the operators say separately, what the customer reports buying, what the company mobilizes for under pressure. The output of this part of the audit is a clear articulation of the company's underlying structure.
At the experience layer, the audit reads how the company is lived. What it feels like to be the founder day to day. What it feels like to be on the team. What the customer reports experiencing in the months after purchase. The output is a picture of the company's felt reality — where it is smooth and where it is friction, where the experience matches the substrate and where it has drifted.
At the strategy layer, the audit reads what the company has been deciding to do. What initiatives are in motion. What hires are queued up. What roadmap items are scheduled. The output is a picture of what the company is actively pointed at.
Then the audit reads across the three. The most valuable findings are usually in the gaps. The substrate says you are a knowledge-transfer business. The experience says you are operating like a software company. The strategy says you are scaling the software platform. That is why everyone is exhausted. Or: The substrate is sound. The experience is excellent. The strategy is mismatched — you are deciding to do things that the substrate and experience would not naturally support. Or, most commonly: The substrate has drifted, the experience knows, and the strategy is calibrated to the old substrate. The friction will compound until one of the three is corrected.
This is what I am actually doing when I audit a company. Not running a diagnostic. Reading across the three layers and surfacing the divergences. The audit document explains what is there, in plain language, with the structural reasoning visible enough that the founder can carry the picture forward themselves.
What the install does
Once the audit is signed off, the install operationalizes the corrected picture. The architecture I build maps to the substrate the audit surfaced — but it does more than that. It creates a daily operating layer that materializes the substrate into experience. The team works from files that reflect the corrected ontology. The decisions get made inside a system calibrated to what the company actually is. The customer encounters a company that operates from a single coherent picture rather than three competing ones.
The install does not change the substrate. That was already there. The install also does not change the strategy directly. What it changes is the experience layer — the daily lived reality of working inside the company. Once the experience matches the substrate, strategy becomes simpler, because the questions strategy is supposed to answer become clearly tractable. Given who we are (substrate) and how we are lived (experience), this is the obvious next move. Strategy collapses into clarity rather than spiraling into options.
This is why I describe the practice as working the layer underneath strategy. The strategic decisions that get made after an engagement are usually obvious. The hard work happened at the substrate layer (the audit) and the experience layer (the install). Strategy follows from those two being settled.
Why this changes how to think about consulting
Most consulting today works at the strategy layer with occasional excursions into the experience layer. The strategy frameworks of the 1980s and 90s — Porter, SWOT, BCG matrix — assume the substrate is settled and the experience is downstream of execution. In stable industries this assumption was approximately correct. In modern businesses, where categories blur and companies drift faster than they can rewrite their decks, the assumption breaks down. Most consulting fails at the strategy layer because the strategy layer is downstream of two layers nobody was looking at.
The next generation of consulting will work at the substrate layer first. Some practitioners will start there explicitly, like Substrate does. Others will arrive there through different paths — phenomenologists, ontologists, structural designers, organizational theorists who have read enough philosophy to know that "what is this company" is a non-trivial question. The ones who succeed will be the ones who can do three-layer reading without overcomplicating it. The ones who fail will either stay at the strategy layer (and produce work that does not land) or get lost in the substrate layer without a way to operationalize what they find (which is what most philosophical consulting looks like).
The advantage of installing AI operating architecture is that the install gives substrate work a concrete output. The audit produces the corrected picture. The architecture encodes the picture into the daily operating layer. The team begins working from the corrected picture immediately, and the experience layer shifts within weeks rather than months. The substrate becomes lived, not just named. That is what most substrate-level consulting cannot deliver, because it ends at the document. The install is what closes the loop.
The deeper claim
What I want to leave you with is this: most of the work a founder needs done is not where most of the work a founder gets done is happening. The strategy layer is where founders go for help, because that is where the frameworks live and where the consultants gather. The substrate layer is where the actual problem usually is. The experience layer is where the problem first shows up as a feeling.
If you have read this far and recognized your own company in any of the descriptions — exhausted by the gap between stated and felt reality, frustrated by smart advice that does not produce results, sensing that something is off without being able to name what — the layer you need worked is probably not strategy. It is one of the two underneath.
That is the layer this practice works first.