Senior practitioners scope the work and then do it, alongside engineers who build. What you keep at the end is a working capability — a system, a workflow, a decision mechanism — rather than a document describing one.
Complex enterprise problems rarely fit neatly inside a software product or a predefined consulting workplan. The expertise required is specific, it is scarce, and historically it had to be assembled person by person — which is slow, expensive, and dependent on who happens to be available.
fdX is how EXOS deploys expertise around the problem instead. It combines experienced practitioners, engineers, AI and proprietary technology around a client problem, so that expertise which normally has to be assembled person by person becomes a capability the organization keeps.
This is an operating model rather than a staffing formula. Not every engagement needs the same weight of each component, and none of them is a fixed headcount. What stays constant is the shape set out above.
The same delivery model carries very different expertise depending on the problem. What is being deployed changes completely; how it is deployed does not.
Expertise deployed conventionally leaves when the engagement does, and the reasoning goes with the people who did the work. fdX is designed so that does not happen. As the work is produced, EXOS captures the context it was done in, the evidence behind it, the reasoning applied, the decisions taken and by whom, the workflows built, and the methods used. That capture is the job of Tacit OS, and it is why an engagement can leave a working capability rather than only recommendations.
This is not a claim that the capability runs itself afterwards. It is a claim that your team can interrogate it, extend it, and act on it without the people who built it — which is a different and more achievable thing. What that looks like in practice differs by capability, and each solution page says what you keep.
That difference is economic rather than a matter of care. A firm staffed on leverage has to put people on engagements who are learning on them, and a firm that does not build technology has to hand the building to someone else.
EXOS is structured differently, so an engagement is designed to leave behind something that functions. The analysis is not the deliverable — it is what justifies the thing you keep.
The delivery model does not change by sector. What changes is the governance constraint, how fast the organization can absorb change, and who holds authority over the decision. Those differences are covered on the industry pages — healthcare, manufacturing, government, higher education and private equity.
From a publicly verifiable healthcare advisory acquisition to a federally funded program that survived fiscal review, the case library shows the same pattern in different settings.
Tell us the problem. We'll come back with a scoped engagement, the senior practitioners who'll do the work, and what the leave-behind looks like — a governed system you own, not a static deck you reference.