The consulting market has had two layers for fifty years, and most observers still talk about it as if those are the only two. The first layer is strategy: McKinsey, BCG, Bain, the firms that sell architecture and recommendation to senior executives at large enterprises. The second layer is industrial-scale integration: Accenture, Deloitte, IBM, Capgemini, the firms that handle large standardized deployments and the implementation work that follows the strategy recommendation. The handoff between the two layers, and the second handoff from the integrator to the customer's internal team, is where transformation engagements have always landed. It is also where they have always failed, because nobody in the chain owns the question of whether the recommended system is actually running in production a year later.
The third layer of consulting that has not been named
A third layer has been forming under the AI wave, and it does not yet have a category name, a standard business model, or a talent pipeline. Diogo Santos's April 2026 analysis of the Palantir forward-deployed engineering model named the layer in language that flowscope's positioning depends on, even though Santos does not name flowscope or any of the other firms building it. The third layer, in his framing, is the set of teams that "wire AI into live systems, govern it in production, and remain accountable for what happens six months after the platform vendor has moved on." The line is precise enough that it is worth quoting again: the layer is the only one of the three "willing to operate inside the institutional complexity that neither the strategists nor the integrators are prepared to enter."
Why the third layer is forming now, under AI
Why this third layer is forming now, after fifty years of stable two-layer market structure, is a question with a specific answer. The eighty-to-ninety-nine-percent problem from the previous post created the demand. Foundation models created the supply. The institutional gap between strategy and integration finally has a discipline to fill it, because the work is now mostly engineering rather than analysis (the foundation models do the analysis), and the engineering has to happen in the customer's environment because the unwritten rules and the edge cases only show up there. The two existing layers cannot do this work. The strategy firms have the wrong people; the integrators have the wrong access. The third layer exists because neither of the existing layers can absorb it.
What a third-layer firm looks like structurally
What it actually looks like, structurally, is worth being precise about. A team of three to ten engineers, on the customer's stack, with permission to write to the customer's systems. Outcome-aligned pricing, because the engagement is metered against units of work processed rather than against time billed. A delivery model that compresses discovery into days rather than months, because the engineers can install observation infrastructure on day one rather than spending twelve weeks interviewing stakeholders. A go-to-market motion that does not look like a Big-4 sales process, because the customer is buying delivery rather than analysis and the sales conversation is about which workflow to ship first rather than about which strategic framework to apply.
How the FDE role spread from Palantir to OpenAI to Ramp
The Pragmatic Engineer documented the spread of the FDE role through 2024 and 2025: from Palantir's internal Delta role (created in the early 2010s), to OpenAI, Ramp, ElevenLabs, Commure, Matta, broadly across the fintech space. Until 2016, Palantir had more forward-deployed engineers than software engineers. The model has been quietly proven at scale by Palantir for fifteen years, and is now being adopted explicitly by the venture-scale companies building the new layer of enterprise AI delivery. Marketboost's framing of the role is the operationally important one: the FDE is the product, at least until the product can stand on its own; it is a go-to-market strategy as much as an engineering one; the service layer, done right, is the most durable competitive advantage a startup can build.
Why boutiques default to the first or second layer
Why most boutique consulting firms are sitting in the first or second layer by default is a question worth answering, because the answer explains why the third layer is not just a Big-4 critique but also a critique of the firms that present themselves as alternatives to the Big-4. The compensation structure of a traditional consulting firm pays partners and senior consultants for selling and analyzing, not for engineering. The org chart is built around the leverage model (one partner, three principals, ten consultants, twenty analysts) which assumes the work is fundamentally analytical with engineering as a downstream activity that can be offshored. The sales motion is built around producing recommendations that the customer's internal team will execute. Each of these structural commitments maps cleanly to the first or second layer of Diogo Santos's framing. None of them is what the third layer requires.
Building the third layer requires building a different kind of firm. Engineering DNA, where the senior staff are engineers who have shipped production systems rather than consultants who have produced decks. Embedded delivery, where the team works in the customer's environment rather than against an offshore delivery center. Outcome-aligned pricing, where the firm only gets paid when the customer captures the value. These are not minor adjustments to the consulting model; they are a different model entirely. The firms that have tried to bolt them onto a traditional consulting structure have generally failed, because the legacy P&L pulls the firm back into the leverage model that the old structure rewards.
A reasonable counter is that the FDE role is a Palantir-specific staffing model that does not generalize into a category. The argument has a historical version (Palantir was unique, the role does not transfer) and a present version (it has not generalized yet, so it might not). The historical version is being refuted in real time. OpenAI runs the playbook. Ramp runs the playbook. ElevenLabs scaled enterprise voice AI through hundreds of FDE accounts. The Pragmatic Engineer documents the spread. Foundation Capital is explicitly building a thesis around it. The model is generalizing fast, and the firms that recognize this earliest will hold the positions that the firms recognizing it later will not be able to win back.
The third layer of consulting is the layer where this decade's category-defining services-firm-shaped companies are forming. It is also the layer that the existing consulting industry cannot reach into, because reaching it requires a different commercial structure, a different talent profile, and a different sales motion. The Big-4 firms are aware of this and are restructuring. The question for an operator looking at AI delivery in 2026 is not which of the existing five delivery vehicles to buy. It is whether the firm they are talking to is structurally in the third layer or structurally in the first or second. The next post walks through what an engagement in the third layer actually looks like end to end, because by this point in the sprint the negative-space description of the layer has been written across nine posts and the positive description is finally worth landing.