---
type: source-summary
title: 'Source: 12-ROLE-BRIEF-COO.md'
modified: 2026-04-07
tags:
  - role-brief
  - coo
  - source
---

# Source: 12-ROLE-BRIEF-COO.md

## What this source is

A 298-char talking-points sheet aimed at the COO of Squire — the executive who must validate that SuiteCentral 2.0 will actually move operational throughput, not just sit in a dashboard. Third in the role-brief set ([[sources/10-role-brief-cfo|CFO]] / [[sources/11-role-brief-cto|CTO]] / COO), with the same two-bucket structure: **Decision Frame** and **Validate**.

It is the most operationally specific of the three briefs — it names the pilot scope in clients, anchors gate checkpoints to dates, and names the operating cadence.

## Key claims

1. **Operational acceleration in setup and sync work.** → NEW claim. Identifies the *category* of operational improvement the pilot is aiming at: time-to-setup and ongoing sync between systems. Lands on [[pages/role-briefs/coo]] and forward-links to the integration-pain narrative on [[pages/entities/squire]].
2. **Pilot scope: 5-10 clients.** → NEW: this is the first concrete pilot-scope number in the corpus. The 01-executive-summary and 10-role-brief-cfo both gave the *cost* envelope ($50-75K) but not the *operational* scope. Lands on [[pages/concepts/pilot-30-60-90]] and [[pages/role-briefs/coo]].
3. **Controlled rollout with day-60 and day-90 gates.** → NEW: explicitly names two gate checkpoints. The CFO brief named the day-90 gate but did not mention day-60. Lands on [[pages/concepts/pilot-30-60-90]] and [[pages/role-briefs/coo]].
4. **Baseline and pilot KPI definitions.** → NEW: implies KPIs are defined *before* the pilot starts (not invented after the fact to justify the result). Lands on [[pages/role-briefs/coo]].
5. **Weekly operating cadence and owner assignment.** → NEW: there is a weekly check-in rhythm and named owners — implies a pilot operating model exists, not just a contract. Lands on [[pages/role-briefs/coo]].
6. **Expansion only on measurable outcome attainment.** → NEW: ties directly back to the [[pages/role-briefs/cfo|CFO]] day-90 gate (economics + adoption proof). Expansion = scale-out beyond pilot, gated on measurable outcomes hitting their targets. Lands on [[pages/role-briefs/coo]] and [[pages/concepts/pilot-30-60-90]].

## Pages updated by this ingest

**Created** (1 new page):
- [[pages/role-briefs/coo]]

**Updated** (1 existing page):
- [[pages/concepts/pilot-30-60-90]] — added pilot scope (5-10 clients), day-60 gate row, expansion criterion

## Notable quotes

The full text of the source:

> COO Brief — Decision Frame: Operational acceleration in setup and sync work. Pilot scope: 5-10 clients. Controlled rollout with day-60 and day-90 gates. Validate: Baseline and pilot KPI definitions. Weekly operating cadence and owner assignment. Expansion only on measurable outcome attainment.

## Cross-references / contradictions found

- **Pilot scope is a NEW dimension**: previous sources gave the cost envelope ($50-75K) and the time envelope (3 months / 90 days) but not the operational scope. "5-10 clients" is the first time the pilot is sized in clients. Important for the COO because it's what determines the operational load on Squire's team — running a pilot across 5 clients vs 10 clients is a different staffing question.
- **Day-60 gate is now explicit**: [[sources/01-executive-summary]] said "Months 1-3 controlled execution" and "End of pilot board go/no-go" — implying only a single gate at day 90. [[sources/10-role-brief-cfo]] specified the day-90 gate criteria but didn't mention day 60. This source confirms day-60 is also a gate, not just an internal milestone. The day-30 gate is still unspecified across the three role briefs.
- **"Operational acceleration in setup and sync work"** maps to the [[pages/entities/squire|Squire]] page's existing "fragmented workflows and duplicated overhead" framing from [[sources/01-executive-summary]]. The COO brief is naming the *fix* (acceleration in setup and sync) for the *problem* (fragmentation and duplication) that the executive summary already identified.
- **Single-source for the operating model**: weekly cadence, owner assignment, and KPI definitions are all single-source claims from this 298-char brief. The deeper version is presumably in `13-PILOT-30-60-90.md` (not yet ingested).

## Notes

- The COO brief is the most "this is what running it would actually look like" of the three. The CFO brief talks about *what to approve*, the CTO brief about *what to verify*, and the COO brief about *how it will run inside Squire's operations* once approved.
- The phrase "expansion only on measurable outcome attainment" is the cleanest statement in the corpus so far of what scale-up looks like after a successful pilot. It implies the path is: pilot → measure → only-then expand. This is consistent with the [[pages/concepts/pilot-30-60-90|pilot]]'s "evidence-based and reversible" framing.