FOUNDATIONS

Agentic deployment method

The route an enterprise follows, and what lands at each step

Five workstreams, six blocks, fifty-two deliverables. Each one names what the customer receives, who produces it, and the evidence that closes it. Not a status report — a route.

5workstreams 6blocks 52deliverables 14customer-owned
Start here

Deployment path

The fifty-two deliverables in sequence, with dependencies and completion tracking. Walk it step by step.

Open the path → Track

Readiness board

The same deliverables grouped by workstream, with status per item and a status export for steering.

Open the board → Present

Method and deliverables

The customer-facing document: what each workstream covers, what you receive, and what acceptance means.

Read the method → Use

Phase 1 Discovery template

The fill-in record for Piloting, in the Role / Skills / Context / Technology / Trigger structure.

Open the template →

The six blocks

Block 1
Piloting

What is the work, and what is the smallest version worth putting in front of someone?

Block 2
Evaluating

How do we know it is any good, and would we notice if it got worse?

Block 3
Integrating

What does it connect to, acting as whom, and with how much reach?

Block 4
Deploying

Does it survive production, load, failure and misuse?

Block 5
Calibrating

Now that it is live, is it the right size, cost and shape?

Block 6
Scaling

Who owns it, and what carries across to the next use case?

Listed in the order they usually start, but several run at once — a specialist is calibrating what shipped last week while still piloting the next slice. The arc runs from Piloting to Scaling and has to end in a decision: widen, hold, or stop, taken on the number by named people.