Strategy as infrastructure.
Strategy has been a deliverable for as long as professional services have existed. A deck. A document. A workshop output. The problem is that decks don't reason, documents don't update, and workshops don't persist.
Stratafy treats strategy as machine-readable infrastructure instead — a structured ontology of mission, principles, decisions, and signals that AI agents can query, update, and reason against.
The schema.
Why the organisation exists.
The future the organisation is pursuing.
The convictions that shape decisions.
The rules that constrain choices.
How the organisation will compete.
What the organisation will actually do.
What winning looks like.
How winning is measured.
The choices made and the rationale behind them.
The bets each strategy and initiative rests on.
What could go wrong, surfaced and tracked.
What the world is telling you, routed to relevant strategies.
How Stratafy composes with your stack.
Stratafy speaks Model Context Protocol natively. Any MCP-aware agent — Claude, ChatGPT, Gemini, Microsoft Copilot, or a custom build — can read from and write to the substrate using a standard interface, without bespoke integration.
Anthropic's persistent Memory tool stores agent state. Stratafy stores strategic state. The two compose: Memory remembers what happened in a conversation; Stratafy remembers what the organisation is trying to do. Different layers, complementary roles.
Stratafy plugins are live in the Anthropic Cowork marketplace. Claude agents in Cowork reason against Stratafy substrate to know not just how to execute a task, but why — and against which strategy.
Advisory firms, fractional executives, and internal strategy teams contribute methodology as Stratafy Experts (CTO, CHRO, CFO, and others). The firm's framework becomes a runtime alongside the substrate, not a deck stored alongside it.
Why machine-readable matters.
Every AI agent built today has the same problem at the strategy layer: it has no idea what the organisation is actually trying to do. It can fetch documents, summarise meetings, draft proposals, and execute tasks — but it cannot answer the question that should come before all of those: why are we doing this?
The answer to that question lives in slide decks, board minutes, off-site notes, and the heads of senior leaders. It has never been structured. It has never been queryable. And so every agent every team builds has to reconstruct it on the fly, every time, from scratch — or simply do without.
Stratafy makes the answer addressable. An MCP query against a Stratafy workspace returns the active strategies, the objectives they roll up to, the assumptions each rests on, the metrics that measure them, and the signals currently affecting them. Agents stop reconstructing context and start reasoning against it.
Strategy stops being a deliverable. It becomes infrastructure.
What's actually built
The schema is the foundation. Running on top of it: alignment scans, signal intelligence, briefings, organisational design, financial planning, document and presentation, workflow cadence, and the agent runtime. The full capability manifest is mapped against the architecture.
See the capabilities manifest