---
type: source-summary
title: 'Source: 13-PILOT-30-60-90.md'
modified: 2026-04-07
tags:
  - pilot
  - 30-60-90
  - gate-metrics
  - source
---

# Source: 13-PILOT-30-60-90.md

## What this source is

A 633-char structured pilot plan document that **closes multiple open questions** that have been accumulating across every prior pilot-related ingest. It's short but dense — it provides a phase-by-phase activity list for the 90-day pilot plus **four specific gate metrics** with quantified thresholds.

This is the 13th source in the Squire Executive Package v2 numbering, positioned between the three role briefs (10/11/12) and the module library (22). Per [[sources/15-start-here-async-standalone]], this is step 7 of Path B (the "30/60/90 Pilot Plan" step that precedes the Pilot Decision Memo).

## Key claims

1. **Day 1-30 phase: Setup and Baseline.** Three activities: (a) Assign sponsor and owner; (b) Select pilot clients and baseline current metrics; (c) Run preflight checks and acceptance review. → [[pages/concepts/pilot-30-60-90]]
2. **Day 31-60 phase: Controlled Execution.** Three activities: (a) Deploy field mapping and sidecar workflows; (b) Track weekly KPI pack; (c) Run compliance/evidence export checks. → [[pages/concepts/pilot-30-60-90]]
3. **Day 61-90 phase: Scale Decision.** Three activities: (a) Compile pilot ROI and case studies; (b) Hold go/no-go board; (c) Approve scale only if all gates pass. → [[pages/concepts/pilot-30-60-90]]
4. **Gate metric 1 — Time-to-integrate: at least 50% reduction.** First formally-ingested concrete KPI threshold. → [[pages/concepts/pilot-30-60-90]] and [[pages/role-briefs/coo]]
5. **Gate metric 2 — Error rate: at least 70% reduction.** Second concrete KPI threshold. → [[pages/concepts/pilot-30-60-90]] and [[pages/role-briefs/coo]]
6. **Gate metric 3 — Economics: trend within approved ROI range.** Third gate criterion — economics must be on track against the 25%–157% 3-year ROI model. Confirms the [[pages/role-briefs/cfo|CFO brief]]'s day-90 gate framing from a second source. → [[pages/concepts/pilot-30-60-90]] and [[pages/role-briefs/cfo]]
7. **Gate metric 4 — Governance: evidence package exported and reviewed.** Fourth gate criterion — the governance/compliance evidence must be exportable and actually reviewed. Confirms the [[pages/role-briefs/cto|CTO brief]]'s compliance evidence export requirement from a second source. → [[pages/concepts/pilot-30-60-90]] and [[pages/role-briefs/cto]]
8. **Sponsor and owner assignment is a Day 1-30 deliverable.** This partially resolves the "who leads approval" question from [[pages/synthesis/three-role-decision-frame]] — the pilot has a named sponsor AND a named owner, assigned in phase 1. The sponsor and owner may not be the same person. → [[pages/concepts/pilot-30-60-90]] and [[pages/role-briefs/coo]]
9. **Pilot client selection is a Day 1-30 deliverable.** The 5–10 pilot clients (from [[sources/12-role-brief-coo]]) are selected *during* the pilot's setup phase, not before. The selection criteria are still not specified. → [[pages/concepts/pilot-30-60-90]]
10. **Preflight checks and acceptance review are phase-1 activities.** Neither is defined in detail in this source but both imply formal gates BEFORE field-mapping deployment begins. → [[pages/concepts/pilot-30-60-90]]
11. **Weekly KPI pack is a Day 31-60 activity.** Confirms the COO brief's "weekly operating cadence" claim from a second source, with the specific artifact ("KPI pack") named. → [[pages/role-briefs/coo]]
12. **Compliance/evidence export checks are Day 31-60.** The export happens during controlled execution, not just at the end — the CTO should be seeing evidence exports weekly, not waiting until day 90. → [[pages/role-briefs/cto]]

## Pages updated by this ingest

**Created** (0 new pages): all claims land on pages that already exist.

**Updated** (5 existing pages):
- [[pages/concepts/pilot-30-60-90]] — major update with phase-by-phase activity list, four gate metrics with thresholds, sponsor/owner assignment, pilot client selection timing
- [[pages/role-briefs/cfo]] — confirms day-90 gate includes "economics within approved ROI range" from a second source
- [[pages/role-briefs/cto]] — confirms compliance/evidence export as a phase 2 activity (not just phase 3), with gate metric 4 "governance: evidence package exported and reviewed" adding specificity
- [[pages/role-briefs/coo]] — confirms weekly KPI pack, sponsor+owner assignment, pilot client selection as explicit phase-1 deliverables
- [[pages/synthesis/three-role-decision-frame]] — removes the "day-30 gate criteria still unspecified" caveat; the consolidated "what to ask for" list now has concrete answers for gate criteria

## Notable quotes

The source is compact enough to quote in full:

> "30/60/90 Pilot Plan. Day 1-30 Setup and Baseline: Assign sponsor and owner. Select pilot clients and baseline current metrics. Run preflight checks and acceptance review. Day 31-60 Controlled Execution: Deploy field mapping and sidecar workflows. Track weekly KPI pack. Run compliance/evidence export checks. Day 61-90 Scale Decision: Compile pilot ROI and case studies. Hold go/no-go board. Approve scale only if all gates pass. Gate Metrics: Time-to-integrate at least 50% reduction. Error rate at least 70% reduction. Economics trend within approved ROI range. Governance evidence package exported and reviewed."

## Cross-references / contradictions found

- **Closes prior open questions**:
  - Day-30 criteria: *previously "no gate named in corpus yet"*. This source names phase-1 activities as Setup and Baseline (sponsor/owner assignment, client selection, preflight checks, acceptance review). There is not a formal gate at Day 30 — Day 30 is the *end* of the setup phase, with a transition into controlled execution. So the earlier "day-30 gate criteria" framing was slightly mis-stated — it's a phase transition, not a gate.
  - Day-60 criteria: *previously "named as a gate but criteria not detailed"*. This source shows Day 31-60 is the Controlled Execution phase; the phase-2-to-phase-3 transition is tracked via weekly KPI pack and compliance/evidence export checks. Again, not a formal gate at Day 60 — it's a phase transition.
  - Day-90 gate criteria: *previously "economics + adoption proof"*. This source specifies the gate as the **four Gate Metrics** (time-to-integrate, error rate, economics, governance) ALL passing. "Adoption proof" from [[sources/10-role-brief-cfo]] is captured implicitly in the error rate and time-to-integrate thresholds (which can only be measured if real users are actually using the system). The CFO brief's framing is consistent with this source, just less specific.
  - KPI list: *previously "not named"*. Now partially resolved — the KPI pack exists and is tracked weekly, and the four Gate Metrics name specific KPIs (time-to-integrate, error rate, economics, governance evidence). Whether there are MORE KPIs beyond the four gate metrics is still unclear.
  - Pilot client selection: *previously "timing unspecified"*. Now resolved — selection happens in phase 1 (Day 1-30). Selection *criteria* are still unspecified.
- **"Gate" terminology refinement**: prior sources used "day-60 gate" and "day-90 gate" as if they were formal gates. This source clarifies that the ACTUAL formal gate is at Day 61-90 (Scale Decision phase), and "Day 60" is really the transition between Controlled Execution and Scale Decision phases. The only hard gate in the pilot is the end-of-phase-3 go/no-go board meeting.
- **Confirms the 30-day evaluation precedes the 90-day pilot**: this source starts at "Day 1" which is the beginning of the pilot proper — not the beginning of the evaluation phase. The 30-day evaluation framework from [[sources/read-talking-points]] happens *before* Day 1 of this plan. Total elapsed time from first-review to pilot-decision is therefore ~4 months (30-day evaluation + 90-day pilot).
- **50% time-to-integrate reduction is a massive claim**: [[sources/ai-governance-layer-video]] claims 15 hours → 30 seconds for field mapping, which is a ~1,800× reduction (vastly more than 50%). So the 50% threshold here is the *floor* the pilot must clear, not the expected improvement. The video pitches the full improvement; the pilot plan asks for the minimum to clear the gate. This is coherent and honest.

## Notes

- The 50% / 70% reduction thresholds are **unusually honest**. They set a realistic minimum that is well below the hero claim (1,800× from the video) but still high enough to represent meaningful value. A pilot that delivers only 50% time-to-integrate reduction clears the gate even though the aspirational target is much higher.
- The source is **structurally the CFO / COO hybrid view of the pilot**: it has economics gate metrics (CFO-flavored) AND KPI-and-governance gate metrics (COO/CTO-flavored). It reads like a program management artifact, not a pitch artifact.
- The "preflight checks and acceptance review" in phase 1 are undefined — likely described in a separate `Live Demo Setup` or `Preflight` source. Flag for future ingest.