You watch the system run. Then we work your situation.
The first conversation is a working session, forty-five minutes, no deck and no discovery script. It opens with the system operating live on a demonstration portfolio shaped like yours: the Watch delivering a morning read, the roadmap rendering its confidence tiers, a skill facilitating the kind of decision your organization finds hardest to make well. Then we put your real situation against it: the portfolio you are ordering, the planning event you are preparing, the office you are transitioning, or the stack you would run this on.
You leave knowing three things: what the system would look like operating on your work, what the first ninety days would involve, and whether this is your path. If it is not, the forty-five minutes still leaves you with a sharper read of your own delivery system than most paid assessments produce. There is no follow-up sequence.
The whole path is published, so you can price it before you start.
After the working session, the next step is a fixed-scope pilot on your real work: one value stream, timeboxed against a six-week target, with the exact duration set jointly to fit your organization’s context, and deliverables named before anything is signed. You keep your own artifacts, produced by the system operating on your portfolio: your backlog ordered with its rationale recorded, your planning event run with its trade-off log, the morning read arriving daily, and the rollout shape for going wider. The pilot exists so the decision to install is made on your own evidence rather than on ours.
The third step is the install engagement: the Delivery OS live on your stack, the chain running your events, adoption just in time, and your people holding every decision right. It is described in full on the consulting page. Nothing obligates the next step; each one produces something you keep either way.