# Pilot scope

<!-- Prompt to Prototype, Pilot the paved road with real builders, https://prompt-to-prototype.com/roadmap/pilot/, as of October 2026. Licensed CC BY-SA 4.0. Using or adapting it inside your business isn't distribution under the licence. -->

Pilot ID, start date, end date (about 90 days), day-45 checkpoint date
Sponsor, evaluator, enablement lead, champions, technical reviewer, intake responder

Builders in the pilot (how they were chosen, including any who didn't volunteer)
Training waves: which teams are wave 1 and wave 2, and which managers train at the start
App streams: builders' own apps, normal intakes from pilot units, discovered apps
Critical apps: how they are tiered and counted, and the gates they must meet before going live
Out of scope: named systems, named data sets

Paved-road pieces in use: tools, sign-in, hosting, secrets, registry, intake
Baseline: where it is recorded and the date taken

Measures: each with the assumption ID, a threshold and a "proves it wrong" result
  (see https://prompt-to-prototype.com/roadmap/pilot-measures.csv)
Value: the process measure for each app, and its baseline
Cost plan: people-hours by role, AI budget and caps, platform costs
Go rules, and kill criteria with who decides
Decision rights: scope changes, tool additions, pause (who and by when)
Review cadence: weekly office hours, fortnightly readout, checkpoint, retrospective