No. 04
Ops Platform
Business-in-a-box on an OKR spine, where strategy and execution hang off one object model.
What it is
A system for running a company where the strategy, the outcomes, the factors that drive them, and the assets that get made all live on one spine, instead of in four disconnected tools.
Who it's for
Founders operating without an ops team, who have a strategy document and a task list and nothing connecting them.
Why I built it
Every tool I tried models tasks. Almost none model why the task exists. So within a quarter the strategy deck and the actual work drift apart, and nobody notices until planning season, when everyone rewrites the deck to match what happened anyway.
How it's built
The domain model came before any application code. What is an Outcome, exactly, and how does it differ from a Factor, and is a deliverable an asset or an outcome? Those rulings are written down and the glossary is the source of truth, because getting them wrong isn't a naming problem, it's the thing that makes the model stop holding weight six months later. Structural decisions are logged as rulings with their reasoning, so a future change has to argue with the original argument.