The Three-Role Decision Frame

What each of Squire’s three functional leaders sees when they look at SuiteCentral 2.0 — and how those three views reconcile into one decision.

What this page is

This is a comparison-lens page, not a fourth role brief. It exists for one specific reader: someone who has to reconcile all three role views into a single decision — typically Jonyce Bullock as CEO of Squire & Company, or any leader holding the ultimate approval gate.

In the live demo flow, the CFO / CTO / COO role briefs are step 6 of Path B and are presented as a parallel choice — each functional leader reads the one brief that matches their job. That’s the right design for functional review. But it leaves a gap: nobody has read all three and reconciled them.

This page fills that gap. It is the artifact a CEO carries into the final approval meeting after the functional leaders have each reported back.

Why the three lenses exist

SuiteCentral 2.0 has to satisfy three independent decision criteria simultaneously, and no single functional leader owns all three:

• Cost — Is the financial exposure bounded, and does the ROI model hold up? (CFO concern)
• Correctness — Does the technology actually work, fail safely, and produce auditable evidence? (CTO concern)
• Throughput — Will the platform actually move operational work, and can Squire’s team run the pilot without disruption? (COO concern)

Any ONE of these failing is enough to veto the pilot. Approval requires all three to clear. The three role briefs divide the decision space cleanly so each functional leader can evaluate their slice efficiently, in parallel.

This is also why the live demo’s Path B presents the role briefs as a parallel choice: a reviewer who is the CFO doesn’t need to re-read the CTO’s concerns to make the CFO decision. They only need to read the one that matches them. Cross-role reconciliation happens later, at the CEO level, using THIS page.

The three decision frames side by side

Each role brief follows the same two-bucket format: a Decision Frame (the numbers the role anchors on) and Validate (the evidence that role should ask for before approving). Here they are together.

	CFO (Cost)	CTO (Correctness)	COO (Throughput)
Anchor number 1	Pilot ask: $50K–$75K	9,038/9,061 tests passing (slide vintage) or 9,207/9,237 (Talking Points vintage) — see production-proof	Improvement target: operational acceleration in setup and sync work
Anchor number 2	3-year ROI range: 25%–157%	95%+ AI accuracy (specifically field-mapping, per ai-governance-layer-video)	Pilot scope: 5–10 clients
Anchor number 3	Payback signal: ~6 months	Governance evidence available in dashboard flows	Gate checkpoints: day-60 and day-90
What to validate 1	Pilot cost is capped before scale decision	Production behavior via watch clips	Baseline and pilot KPI definitions defined before pilot starts
What to validate 2	Scenario inputs adjustable and transparent (the ROI model is a knob, not a fixed projection)	Compliance evidence export and SOC 2 Trust Services Criteria mapping	Weekly operating cadence with named owners
What to validate 3	Day-90 gate includes economics and adoption proof	Failure-path visibility and fallback handling	Expansion only on measurable outcome attainment

Source pointers: CFO numbers from 10-role-brief-cfo; CTO numbers from 11-role-brief-cto and sharpened by ai-governance-layer-video and read-elevator-pitch; COO numbers from 12-role-brief-coo.

What each role uniquely contributes

The three lenses are not interchangeable. Each one has a specific job the other two can’t do:

The CFO is the only one who can say “no, this is financially reckless.”

Everything else on the platform might work, but if the ROI model can’t be stress-tested and the pilot cost isn’t capped, the CFO will veto on financial grounds alone. The CFO brief is engineered to give the CFO everything they need to say yes in ~5 minutes of reading, because the CFO is usually the bottleneck approver.

The CFO’s key judgment call: does the 25%–157% ROI range hold up when I stress-test the assumptions? The source material explicitly tells the CFO that scenario inputs are “adjustable and transparent” — meaning the CFO should actually play with the numbers (in what we infer is 04-ROI-CALCULATOR.md, not yet ingested) rather than accepting the headline range.

The CTO is the only one who can say “no, this is engineering-reckless.”

Finance can’t catch engineering failure. The CTO has to actually look at the failure-path behavior, verify the SOC 2 Trust Services Criteria mapping exists as a real document (not just a summary slide), and validate the four named safety mechanisms (Reasoning Trace Engine, Governance Pacer, DLP PII Shield, Approved To Apply) are each actually shipping and not roadmap features.

The CTO’s key judgment call: does the governance layer actually do what it claims when things break? This is the “watch clips and look at traces” work that can’t be delegated to finance. For a CPA-firm customer, the SOC 2 TSC mapping is especially load-bearing — audit posture is non-negotiable and the CTO is the only one who can sign off on it.

The COO is the only one who can say “no, this will break operations.”

Neither finance nor engineering owns delivery throughput. The COO has to ensure KPIs are defined before the pilot starts (to prevent the post-hoc “we measured what worked” trap), that a weekly operating cadence exists with named owners on both sides, and that expansion is pre-committed to be gated on measurable outcome attainment — no momentum-based decisions.

The COO’s key judgment call: which 5–10 clients become the pilot cohort? Pilot client selection is a decision in itself — easy clients to maximize pilot success, or representative clients to maximize signal. The corpus doesn’t answer this question; the COO does.

The consolidated “what to ask for” list

For a CEO-level reviewer who is reading all three role briefs together, here is the union of every piece of evidence the three roles collectively ask for. If all of these are produced and verified, the pilot clears on all three dimensions.

Economic evidence (from CFO):

1. The ROI calculator (04-ROI-CALCULATOR.md) with adjustable scenario inputs
2. A breakdown of the 25–157% ROI range into best-case / base-case / worst-case
3. The payback-model assumptions that produce the ~6 month signal
4. Explicit confirmation that pilot cost is capped before scale decision

Technical evidence (from CTO): 5. Watch clips showing production behavior (from the live demo Watch track) 6. The actual SOC 2 Trust Services Criteria control mapping document (not just a summary) 7. Failure-path trace examples showing what happens when providers fail 8. The 95% field-mapping accuracy methodology (which dataset, which evaluation harness) 9. Verification that each of the four safety mechanisms is shipping, not on a roadmap

Operational evidence (from COO): 10. The complete KPI list — partially resolved by 13-pilot-30-60-90, which names four Gate Metrics (time-to-integrate ≥50% reduction, error rate ≥70% reduction, economics within ROI range, governance evidence exported and reviewed). The “weekly KPI pack” implies more KPIs beyond the four gate metrics — those are still unspecified. 11. The phase-by-phase activity list (now specified in 13-pilot-30-60-90: Day 1-30 Setup and Baseline, Day 31-60 Controlled Execution, Day 61-90 Scale Decision). The only formal gate is at the end of Day 61-90. 12. The named sponsor and owner (assigned in Day 1-30 per 13-pilot-30-60-90), plus a weekly operating cadence calendar 13. The client selection criteria for the 5–10 pilot clients (selection happens in Day 1-30, criteria still unspecified) 14. A pre-committed expansion rule gated on measurable outcome attainment — the four Gate Metrics all being in their pass thresholds (AND gate, not OR)

Cross-cutting (addresses all three roles): 15. The Pilot Decision Memo at /Squire-Executive-Package-v2/16-PILOT-DECISION-MEMO-STANDALONE.html (not yet ingested)

Open questions that sit between roles

These are the questions that don’t cleanly live in any single role brief, because they span two or three of them:

• Who leads the approval? The CFO is usually the budget approver (suggesting CFO leads), but the COO is the one whose team has to run the pilot (suggesting COO leads), and the CTO can veto on technical grounds. The corpus doesn’t name a lead approver explicitly. The /19-DECISION-PATH-STANDALONE.html artifact (not yet ingested) may resolve this.
• What if one role says yes and another says no? None of the role briefs describe a tiebreaker procedure. For a 50-year-old CPA firm with a flat three-role approval structure, the practical answer is probably that the CEO (Jonyce Bullock) makes the call — which is exactly why this synthesis page exists.
• Who owns the 30-day evaluation timeline? pilot-30-60-90 describes a 30-day evaluation phase that precedes the 90-day pilot, with Week 1 = demo review, Week 2 = technical deep-dive, Week 3 = pilot client selection, Week 4 = decision checkpoint. This is operationally mixed: Week 2 is CTO-heavy, Week 3 is COO-heavy, Week 4 is CFO-heavy. The corpus doesn’t name a program manager.
• Are the three briefs internally consistent on the pilot shape? Yes, after careful reading: all three agree on $50–75K, 3 months, 5–10 clients, day-60 and day-90 gates. None of them contradicts another. The only structural refinement is the 30-day evaluation phase that was added post-role-briefs (it’s not in the role briefs themselves, but is in read-talking-points and read-elevator-pitch).

How this page relates to the live demo

In the live demo’s Path B, a reviewer walks: Demo Hub → Storyboard Clips → Module Library → Claim-Proof Matrix → Objections → Role brief (one of the three) → 30/60/90 Pilot Plan → Pilot Decision Memo. Each functional leader walks this path individually and reports back with a role-specific recommendation.

Once all three reports come in, the CEO walks a different path:

1. Read THIS synthesis page for the reconciliation view
2. Check the consolidated “what to ask for” list against what each functional leader actually received
3. Look for any role where the answer was “no” or “not yet” — the pilot clears only if all three lanes clear
4. Make the final approval call

This means the synthesis page is NOT on the live demo site at all. It is a Brain1 wiki-level artifact for the CEO’s reconciliation workflow. If a future version of the live demo adds a “Decision Path” that serves the CEO specifically, this page’s structure is a good template for what should go on it.

Sources

• 10-role-brief-cfo — CFO decision frame (cost lens)
• 11-role-brief-cto — CTO decision frame (correctness lens)
• 12-role-brief-coo — COO decision frame (throughput lens)
• 15-start-here-async-standalone — confirms the role briefs are a parallel choice in Path B
• read-talking-points — adds the “the three lenses are not interchangeable” framing implicitly (by tailoring the talking tracks for Jonyce vs Reuben)
• read-elevator-pitch — adds the “SOC 2 Trust Services Criteria” framework specificity that sharpens the CTO lens
• ai-governance-layer-video — adds the four named safety mechanisms the CTO should validate and the 95%-is-field-mapping-specifically clarification
• 13-pilot-30-60-90 — adds the phase-by-phase activity list and the four Gate Metrics with thresholds, closing several previously open questions about pilot gates and KPIs