--- type: source-summary title: 'Source: 16-PILOT-DECISION-MEMO-STANDALONE.html' modified: 2026-04-07 tags: - pilot-decision-memo - decision-artifact - source - preston-test --- # Source: 16-PILOT-DECISION-MEMO-STANDALONE.html ## What this source is **The decision artifact every review path delivers to.** Per the [[pages/concepts/three-review-paths|three review paths]], Paths A, B, and C all terminate in this page — the "Pilot Decision Memo." It's a copy-ready memo template that the executive sponsor (or the CEO reconciling all three role views) fills in to formalize the pilot decision. Read directly from the canonical Preston-Test HTML file at `public/Squire-Executive-Package-v2/16-PILOT-DECISION-MEMO-STANDALONE.html`. Text extracted; HTML scaffolding (Tailwind classes, JS for copy-to-clipboard) omitted. ## Key claims 1. **Recommended Decision (explicit)**: *"Approve a 3-month pilot for SuiteCentral 2.0 at $50K-$75K, limited to 5-10 Squire clients, with day-60 and day-90 go/no-go gates tied to measurable operating and financial outcomes."* This is the official recommended decision language, now formally ingested. → [[pages/concepts/pilot-30-60-90]] 2. **Three gate targets, displayed prominently at the top**: - Time-to-integrate: ≥ 50% reduction - Error-rate: ≥ 70% reduction - Economics: Track to approved ROI range These are the same three as Gate Metrics 1, 2, 3 from [[sources/13-pilot-30-60-90]]. Gate Metric 4 (Governance: evidence package exported and reviewed) is implicit in the "Conditions of approval" section. → [[pages/concepts/pilot-30-60-90]] 3. **Three decision options (NEW)**: - **Option A: Approve pilot now** — Proceed with full 30/60/90 plan and weekly steering cadence. - **Option B: Conditional approval** — Approve after one additional technical check or budget clarification. - **Option C: Defer** — Defer pilot; revisit after market or internal constraints change. Option B is notable: it frames the two kinds of conditional approvals as either "technical check" (CTO-flavored) or "budget clarification" (CFO-flavored), with the COO implicitly on board. → [[pages/synthesis/three-role-decision-frame]] — adds the three-option framing to the reconciliation view. 4. **Copy-ready memo text structure (NEW)** — the template the CEO actually fills in: - **Basis for decision** (3 bullets): production-ready evidence package reviewed, pilot scope bounded with gates, impact targets are measurable - **Conditions of approval** (3 numbered items): Weekly KPI reporting to executive sponsor, Governance evidence export and review by Day 90, Scale-up only if all gate criteria are met - **Decision Outcome** (3 checkboxes): Approve now / Approve with conditions / Defer - **Owners** (3 named roles): Executive sponsor, Technical owner, Operating owner - **Sign-off** (3 role signatures): CFO, CTO, COO 5. **Six named positions in the memo** (NEW): The memo names SIX total positions that need to be filled — 3 owner roles (Executive sponsor, Technical owner, Operating owner) PLUS 3 sign-off roles (CFO, CTO, COO). The **sponsor vs owner distinction** from [[sources/13-pilot-30-60-90]] is now fully resolved: the Executive sponsor is one specific person; the Technical owner and Operating owner are two other people. Plus the three approving C-level signatures. That's 6 distinct positions required to run the pilot. 6. **Supporting links** (from the memo page footer): Claim-to-Proof Matrix, 30/60/90 Pilot Plan, Watch Playlist. These are the three artifacts a reviewer opens from the memo itself. ## Pages updated by this ingest **Created** (0 new pages). **Updated** (2 existing pages): - [[pages/concepts/pilot-30-60-90]] — added the Pilot Decision Memo as the pilot's terminal artifact; added the three decision options (A/B/C) and the 6-named-position framing - [[pages/synthesis/three-role-decision-frame]] — added the Option B "conditional approval" framing (technical check OR budget clarification) as a third pathway in the synthesis ## Notable quotes > "Approve a 3-month pilot for SuiteCentral 2.0 at $50K-$75K, limited to 5-10 Squire clients, with day-60 and day-90 go/no-go gates tied to measurable operating and financial outcomes." > — Recommended Decision > "Option B: Conditional approval — Approve after one additional technical check or budget clarification." > — Decision Options section. Worth notice: conditional approvals are framed as requiring ONE additional check, not a list. ## Cross-references / contradictions found - **Six-position org chart for the pilot**: the memo explicitly names 6 positions (Executive sponsor, Technical owner, Operating owner, CFO sign-off, CTO sign-off, COO sign-off). Earlier sources implied the sponsor/owner distinction without naming all 6. This source is the first formal enumeration. - **"Day-60 and day-90 gates" wording vs phase-transition terminology**: this memo uses the older "day-60 and day-90 gates" phrasing. [[sources/13-pilot-30-60-90]] refined that to "only end-of-phase-3 is a hard gate; Day 30 and 60 are phase transitions." Not a contradiction — the memo is pointing at the same artifacts with less precise language. The gate metrics themselves are still the same four numbers. - **Three conditions of approval are NEW specificity**: "Weekly KPI reporting" (confirms COO brief), "Governance evidence export and review by Day 90" (confirms CTO brief), "Scale-up only if all gate criteria are met" (confirms COO brief's expansion rule). All three conditions align with prior-source asks from the role briefs. - **"Production-ready evidence package"** in the basis for decision language: reinforces the [[sources/09-claim-proof-matrix]] "Shipped" framing — the memo assumes the reviewer has already walked the evidence package. ## Notes - The copy-ready template is designed to be literally copy-pasted into an email or memo. The reviewer fills in the decision date, names, and initials, and ships it. - Supporting links are only 3 items (Claim-Proof Matrix, 30/60/90 Pilot Plan, Watch Playlist) — **NOT** the Pilot Decision Memo's own related docs (like ROI Calculator, Technical Proof, Oracle Comparison, Compliance Dashboard). The memo assumes the reviewer already walked those in earlier path steps. - This is an HTML page, not a markdown file. The text was extracted — HTML scaffolding (Tailwind classes, JavaScript for copy-to-clipboard) was omitted as non-content.