How we deliver use cases
One hub, every agreed use case, every deliverable with its status and its link. Whoever builds, the stages, gates and documents are the same, so everyone knows where things stand and what "done" means.
What this hub is
Each use case lives here from the moment it is agreed until it is retired. It carries a delivery mode, a stage, a health, an owner on each side, a next step with a date, and thirteen deliverables. Each deliverable has a status, an owner, a version, and a link or an attached file. The activity log records stage changes, acceptances and decisions with who and when.
Documents are edited where they are best edited and linked from here. At acceptance the signed version is attached, so the record is complete without leaving the hub.
The lifecycle and its gates
| Stage | You are here when | You leave when |
|---|
Stages move forward one at a time. Moving back is allowed and is logged.
Three delivery modes
| Activity | Client builds | We build | I build for the client |
|---|---|---|---|
| Assessment and scope (D0) | Provider | Provider | Provider |
| Design (D1) | Client drafts, provider reviews | Provider | Provider, with the client in the room |
| Build (D2) | Client | Provider team | Provider, personally, inside the client's environment |
| Quality (D5) | Client runs, provider sets the method | Provider | Provider |
| Documentation (D3, D4, D7, D10) | Client writes to the provider's templates | Provider | Provider |
| Data and security (D6) | Provider drafts, client's security or legal contact signs, in every mode | ||
| Training (D8) | Client | Provider | Provider |
| Acceptance (D9, D12) | Provider drafts the protocol, client executes and signs, in every mode | ||
| Value tracking (D11) | Client's sponsor owns the numbers; provider fills the baseline | ||
| Run phase | Client, provider on call | Provider retainer or handover | Handover to the client, retainer optional |
The deliverables
| Code | Deliverable | Purpose | Accepted when |
|---|
Statuses: Not started, In progress, In review, Accepted (the hub records who and when), Not applicable. A use case reaches Production only when every applicable deliverable is accepted.
Operating rhythm
- Weekly, per client, 30 minutes. Health, next step, due date for each use case. Deliverables in review get a reviewer and a date. Decisions are logged.
- Monthly, portfolio, 45 minutes. Export the CSV. Which use cases are stalled, red, or waiting on a signature. Decide what to stop.
- At every stage change. The gate criteria are shown in the panel; the move is logged with your name.
- Quarterly. Review the template and the gates against what happened.
Who changes what
Provider staff maintain clients, use cases, scope, stages and owners. Client editors accept deliverables, attach signed documents and log decisions. Client viewers read. Machines (the hub's other systems, Claude through the MCP server) use API keys with the same roles.