The pipeline, end to end

From a name on a list to a renewed account.

Fourteen stages across five phases. Every stage says who owns it, what the customer does, what we do, what the systems should do without being asked, and the checks that have to pass before the deal is allowed to move on.

14 stages 0 actions 0 exit checks 3 forms Volumes as supplied — monthly

Show

Three forms, three jobs

Ask once, ask early, never ask twice.

Each form exists to unlock the next thing: v1 opens the data room, v2 sends the contract, v3 builds the tenant. A field that appears in two forms is a field we failed to carry forward.

The stack behind the pipeline

What each system owns, and where it hands over.

The handovers are where deals leak — a reply that never becomes a calendar item, a signature nobody sees, a roster re-typed into AWS. Each card names the stages that system touches.

Machine work vs people work

Everything a person should stop doing by hand.

Pulled from every stage and sorted by how close it is to being real. The target shape is one event per milestone with several consumers: a signature provisions the tenant, raises the invoice and issues v3 without anyone remembering to.

Decisions outstanding

What has to be settled for this process to run itself.

The two from the pipeline sheet, plus what the numbers and the handovers raise. Each carries a recommendation rather than just a question mark.