Strategy is Downstream
On why most strategy fails, what it is downstream of, and the layer that has to be settled first.
There is a moment that happens in almost every advisory engagement I have observed, mine or someone else's, where the founder asks the strategic question that brought them to the table — should we expand into this market, should we hire this role, should we launch this product — and the advisor gives a clean, well-reasoned answer, and the founder nods and writes it down, and three months later nothing has happened.
The advice was sound. The reasoning was solid. The founder agreed in the room. And yet the company did not move.
This happens too often to be coincidence. It happens with smart founders and smart advisors. It happens with high-end consulting firms and low-end ones. It happens with experienced advisors who have been giving strategic advice for decades. The pattern is consistent enough that it has to mean something structural.
What it means is that strategy is downstream. Strategy assumes that a more fundamental question has already been answered — what is this company, structurally — and when that question has not been answered, strategy has nothing to attach to. The advice goes in, the founder agrees with it, and then the actual operating reality of the company quietly fails to absorb it, because the strategy was built for a company that does not quite exist.
This essay is about that layer underneath strategy. What it is, why most advisors don't work it, what it costs when it is left unworked, and what changes when it is settled.
What strategy actually assumes
When you sit down to make a strategic decision — should we expand, should we hire, should we launch — you are implicitly answering several smaller questions first:
- What is this company, primarily? - Who is our customer, and what are they actually buying? - What are we good at, structurally, versus what are we trying to be good at? - What does the team actually do, versus what the org chart says it does? - Where is the company headed, given its current shape and momentum?
If you have clear answers to these questions, strategy is straightforward. The decision practically makes itself. Given who we are and where we are pointed, this is obviously the right move. The hard part is execution, not the decision.
If you do not have clear answers — if there is real disagreement, or vague consensus that papers over real disagreement, or a stated answer that does not match the company's actual behavior — then strategy becomes guesswork. The decision feels heavy because each option implies a different answer to the underlying questions, and nobody has agreed on the answers, so the decision is actually several decisions stacked on top of each other.
Most strategic confusion is downstream of unresolved ontological questions. The strategy is hard because the substrate is unsettled. Settle the substrate, and the strategy collapses into clarity.
Why most advisors skip the substrate layer
Advisors who work at the strategy layer are working at the level where their training applied. McKinsey, Bain, BCG — the entire management consulting industry — was built on strategy frameworks. Porter's five forces. SWOT analysis. The BCG matrix. These are tools that assume the question of what the company is is already settled, and that the remaining work is figuring out what the company should do given what it is.
This worked for a long time, because in the era these frameworks were designed for — large industrial companies in stable industries — the question of what the company was was, in fact, usually settled. A steel company knew it was a steel company. An airline knew it was an airline. The strategic questions were genuinely strategic.
But modern businesses are different. Software companies sell services. Service companies sell software. Hardware companies sell subscriptions. Subscription companies sell hardware. The categories blur. A founder who started a "marketing agency" wakes up five years later running what is effectively a media company. A founder who started a "SaaS platform" finds out their customers are actually paying for a community. The category drifts faster than the founder can rewrite the deck. The strategy frameworks assume settled ontology, but in real companies, ontology is rarely settled anymore.
Most advisors do not address this because they were trained in an era when they did not have to. They learned to apply strategic frameworks to companies whose categories were stable. When they encounter companies whose categories have drifted, they apply the frameworks anyway, and the frameworks deliver advice that is locally coherent but globally misaligned. The advice would have been correct for the stated ontology. It is incorrect for the actual ontology. The founder cannot articulate why the advice feels off, because the founder cannot articulate the gap between stated and actual ontology either.
This is the dynamic that produces the moment I described at the start of the essay. The advisor gives sound advice. The founder agrees. Three months later nothing has happened, because the company is structurally incapable of absorbing advice calibrated to the wrong picture of itself.
What it costs to skip the substrate layer
When the substrate layer is skipped, the costs compound in specific ways.
Strategic initiatives launch and quietly fail. The initiative was launched against the stated ontology. The execution happens in the actual ontology. The two do not align. The initiative produces motion without progress, activity without outcomes, and after six or twelve months it gets quietly deprecated. Nobody can fully explain why it did not work. The retrospective concludes with vague language about "execution challenges" or "market timing." The actual cause — that the initiative was calibrated to a company that does not exist — is never named.
Hiring decisions produce friction. A company hiring against its stated ontology recruits people who fit the deck. Those people walk into a daily reality that does not match the deck. They struggle. They underperform. They get blamed for being the wrong hires. They leave. The cycle repeats with the next batch, because the company has not corrected the gap that caused the misalignment in the first place. The hires are not the problem. The job description is the problem. The job description is downstream of the stated ontology, which is the problem.
Founders burn out from carrying the gap. This is the most expensive cost. The founder is the one person in the company who has access to both pictures — the stated one they wrote, and the actual one they are operating in. Every day, they translate between the two. Every meeting requires holding two versions of the company at once. Every decision involves choosing which version to optimize for. The cognitive load is real, and it does not get lighter. Over time, the founder either rebuilds the company to match the actual ontology (rare), forces the actual ontology to match the stated one (usually catastrophic), or burns out trying to hold both (most common). Most "founder burnout" is ontology gap burnout. It is the price of running two versions of the same company simultaneously without ever naming the gap.
Strategy meetings produce decisions that do not stick. A strategy meeting is supposed to align the company on a direction. But the alignment is at the level of stated ontology, while the daily work happens at the level of actual ontology. So the meeting produces decisions that everyone agrees with in the room and that nobody operationalizes after. The team leaves the meeting with renewed clarity that quietly evaporates over the following weeks, because the operating reality of the company has not changed. The strategy was real. The substrate it was applied to was not.
What changes when the substrate is settled
When the substrate is named clearly and the company aligns to it, several things change immediately.
Strategic decisions become easier, because the underlying questions are no longer unresolved. Given that we are this kind of company, the answer is obvious. The hard work moves from deciding to executing, which is where it should have been all along.
Hiring becomes clearer, because the job descriptions can be written against the actual ontology. The candidates who fit the company show up. The ones who don't, screen themselves out. Onboarding is shorter because new hires walk into a daily reality that matches what they signed up for.
Marketing copy starts to write itself, because there is now a clear thing to write about. The founder can describe the company in private and in public using the same language. Customers self-qualify by recognizing themselves in the description. Conversion rates improve, not because the funnel got better, but because the front of the funnel now describes the actual company.
Strategy meetings become productive, because the substrate is no longer the hidden disagreement under every decision. The team aligns faster. The decisions stick. The actions follow through.
And the founder experiences relief. Not because the company is suddenly easy, but because the company is no longer fighting itself. The work that was supposed to be exciting becomes exciting again, because the founder is now operating the company they actually have, instead of translating between two versions of it.
What this means for the practice
This is the layer the practice works first. Not because strategy doesn't matter. Strategy matters enormously. But strategy is downstream — it depends on having a settled answer to the question of what the company actually is, and most founders do not have that answer settled, even if they think they do.
The audit phase of an engagement does not produce strategy. It produces the input that strategy is built on. A written articulation of the company's actual ontology, surfaced across the founder, the team, and the customer, with the structural fractures identified and the corrections named. For most founders, this is the first time they have seen their company described accurately. The strategic decisions that follow are often easy by comparison, because the hard work was already done at the layer underneath.
The architecture install operationalizes the corrected ontology — encodes it into the AI operating layer of the business, so the team is daily working from the accurate picture instead of the stated one. This is what closes the gap permanently. Without the architecture, the audit is a document that can be remembered or forgotten. With the architecture, the audit is encoded into the system the team uses to actually do work, and the corrected picture becomes structurally inescapable.
This is why I do not offer strategy consulting. There are plenty of people who do that well, and most of them are working at the wrong layer to address what most founders are actually stuck on. I work the layer underneath strategy, because that is the layer that has to be settled before strategy can do its work. If a founder reads this and finds that strategy is genuinely their problem — that their ontology is already clear and they just need help deciding what to do — they should hire a strategist, not me. But if they read this and recognize the dynamic I described at the start of this essay, where strategic advice keeps coming in and somehow not landing, the layer they need worked is the substrate.
The deeper claim
The deeper claim of the practice, when you boil it down, is this: most of what looks like a strategy problem is actually an ontology problem. Most of what looks like an execution problem is actually a structural alignment problem. Most of what looks like a hiring problem is actually a question-of-what-this-role-is-for problem. The advisors who get hired to solve these problems are working one layer too high, applying frameworks designed for a different era, and the founders who hire them keep getting smart advice that does not change anything.
The work at the substrate layer is what makes the work at the strategy layer effective. You do not have to choose between the two — you have to do them in the right order. First the substrate. Then strategy on top of it. When you do them in that order, strategy actually works. When you skip the substrate and start with strategy, strategy spins. The motion looks like progress. The outcomes do not match the motion.
If you are a founder who has been frustrated by smart advice that does not produce results, this is likely what is happening. The advice was correct for a company that doesn't quite exist — the version of yours that lives in your deck. The actual company is operating on a different ontology, and the gap is where the advice is getting absorbed and lost. The fix is not better strategy. The fix is settling the layer underneath.
That is the layer this practice works first.