Strategy, written to be executed.

One plan, three parts that lock together: where you’re going, the AI architecture your business runs on, and in what order it gets built. Aligned, drawn to spec, and ready to act on.

design · the plan parts locked 3 / 3 01 STRATEGY where you’re going 02 AI ARCHITECTURE what your business runs on 03 ROADMAP in what order it ships aligned · drawn to spec ready to build →
§ 01 · One plan, three parts 01 / 04

One plan, three parts that lock together.

The why, the when, and the how – written as one. When the three agree, the work that follows stops contradicting itself: the plan matches the architecture, and the architecture matches where you said you were going.

The why & what

Strategy

Where the business is going, the few capabilities that win if you get them right, and the real choices in front of you – each named as a fork, with its options and what each one costs.

The how

AI architecture

How your business is arranged to run on AI – where the agents sit, where your data lives and how it moves, and where people stay in the loop. The shape of an AI-native business, drawn for yours.

The when

Roadmap

The order it gets built – the phases, what runs in parallel, and a clear, measurable test for the end of each phase. Not a list of dates you hope to hit.

§ 02 · What good looks like 02 / 04

Specific enough to say no.

A plan that can’t rule anything out isn’t a plan. The good ones draw hard edges – and survive contact with reality.

  • 01 It lets you refuse the wrong work Clear enough that some ideas are an obvious no. Vague plans say yes to everything.
  • 02 It names the real choices The forks in the road, with the options laid out – not just good intentions.
  • 03 It is measurable Each phase ends on a test you can check, not a date you hope to hit.
  • 04 It survives contact with reality The parts hold together under pressure – and stay current as things change.
§ 03 · Into the build 03 / 04

From plan to build.

Design is a handoff, not the finish line. The plan becomes a clear set of requirements – the point where intent starts turning into working software.

Design

The plan

Strategy, architecture, and roadmap, aligned

Requirements

What to build

The plan turned into clear, agreed requirements

Build

Working software

Specified, then built – rebuilt AI-native

Because the plan holds together, everything built after it has to stay true to it – nothing drifts off course. The handoff into the build is a clear contract. See The Method.

§ 04 · What comes next 04 / 04

Draw the target.

Whether you start from an Assess diagnosis or a blank page, the output is the same: one plan, specific enough to act on and ready to build from.