The Three Review Paths
SuiteCentral 2.0’s executive package supports three guided review paths — A (Executive, 11-12 min), B (Leadership, 25 min, recommended), and C (Deep Proof, 50 min) — each engineered to deliver the reviewer to the same artifact: the Pilot Decision Memo.
What it is
The package’s async-first review experience. Squire executives are not always available for a live presenter walkthrough, so the package provides three pre-built guided paths a reviewer can walk through on their own. Each path is structured as an ordered list of steps, each step is timed, and every path terminates in the same place: a pilot decision.
The entry point is the Start Here page at /Squire-Executive-Package-v2/15-START-HERE-ASYNC-STANDALONE.
Why it matters (to the adoption case)
The structure reveals something important about the pitch: the package is designed to function without a salesperson in the room. That is unusual and load-bearing for the adoption case. It signals:
- Confidence in the artifacts. If the package needed a presenter to land, having three guided async paths would be a liability. They aren’t.
- Respect for executive time. Path A is engineered for the busiest reviewer (12 minutes); Path C is for the most thorough (50 minutes). The three paths let each role spend exactly as much time as their job requires.
- A pre-committed decision shape. The target outcome is named upfront: “capture a clear approve, defer, or deep-dive next step.” This is anti-FOMO framing — the reviewer is told the only acceptable outcomes, none of which is “I’ll think about it.”
The three paths
Path A: Executive (11-12 minutes)
For the executive who has 12 minutes between meetings.
| # | Step | Time |
|---|---|---|
| 1 | Executive Outcomes | 2 min |
| 2 | Executive Reel (Narrated) | 4 min |
| 3 | Context Sidecar Highlight (Narrated) | 1-2 min |
| 4 | Claim-to-Proof Matrix | 2 min |
| 5 | Pilot Decision Memo | 2 min |
Source: 15-start-here-async-standalone. None of the named source artifacts (Executive Outcomes, Executive Reel, Context Sidecar Highlight, Claim-to-Proof Matrix, Pilot Decision Memo) is yet ingested as a wiki page — they are flagged as high-priority next ingests.
Path B: Leadership (25 minutes, RECOMMENDED)
The path the email template asks reviewers to take. This is the canonical “leadership team walkthrough” experience.
| # | Step | Time |
|---|---|---|
| 1 | Demo Hub (Watch / Click / Read entry) | — |
| 2 | Watch playlist: Storyboard Clips | 8 min |
| 3 | Module Library (16 modules) — footprint validation | 3 min |
| 4 | Claim-to-Proof Matrix | 4 min |
| 5 | Objections and Answers | 2 min |
| 6 | Role page — pick one: CFO, CTO, or COO | 4 min |
| 7 | 30/60/90 Pilot Plan | 2 min |
| 8 | Pilot Decision Memo | 2 min |
Source: 15-start-here-async-standalone. Step 6 is a parallel choice: each reviewer reads the role brief that matches their job, not all three. This is a meaningful detail — see “Role briefs as a parallel choice” below.
Path C: Deep Proof (50 minutes)
For the technical reviewer or skeptic who needs to verify everything.
| # | Step | Time |
|---|---|---|
| 1 | Full Watch playlist | 20 min |
| 2 | Module Library (16 modules) — verify breadth by function area | 5 min |
| 3 | Technical Proof | 10 min |
| 4 | Compliance Dashboard + Oracle comparison | 10 min |
| 5 | Pilot Decision Memo | 5 min |
Source: 15-start-here-async-standalone.
Role briefs as a parallel choice
This is the most consequential structural insight in the source. The CFO/CTO/COO role briefs are presented as step 6 of Path B, and they are a parallel choice — a reviewer picks the one that matches their role rather than reading all three.
This contradicts an earlier wiki framing (now corrected): the CFO, CTO, and COO role brief pages were originally written as if the three were a triptych “designed to be read together.” The actual product positions them as alternatives.
The synthesis-style “read all three” view is still useful for one specific case: a reader who must reconcile all three perspectives — for example, the CEO of Squire & Company, who has to satisfy all three role concerns simultaneously. But in the standard async review flow, each person reads the one that matches their job.
The 6-URL email template
The Start Here page also defines a canonical 6-URL flow for distributing the package by email. The recommended subject line is “SuiteCentral 2.0 package review - decision requested” and the body asks the recipient to walk through Path B. The 6 URLs are:
/Squire-Executive-Package-v2/15-START-HERE-ASYNC-STANDALONE.html/squire-v2-media-demo/index.html(Demo Hub)/squire-v2-media-demo/watch/videos/index.html(Watch playlist)/Squire-Executive-Package-v2/22-MODULE-LIBRARY-STANDALONE.html/Squire-Executive-Package-v2/09-CLAIM-PROOF-MATRIX-STANDALONE.html/Squire-Executive-Package-v2/16-PILOT-DECISION-MEMO-STANDALONE.html
The template asks for “pilot approval decision after completing the review” as the requested outcome.
NotebookLM Companion
Each of the three paths is paired with a “NotebookLM Companion” link for external Q&A. This is the same notebook this wiki is built from (ca3bd54b-c240-4432-93c3-545099bf719b). The product positions the notebook as the deeper Q&A layer underneath the curated path — when a reviewer has questions the path doesn’t answer, they go to the notebook (or, soon, this wiki).
Sources
- 15-start-here-async-standalone — primary source, all 11 path-structure claims