Training a COO on AI Tools: SOPs, Vendor Reviews, Escalations

The single biggest mistake I see SMB owners make in COO training is treating it like CFO training. The COO doesn't live in numbers — they live in process. Train them on SOP rewrites first; the rest follows.

Why COO training looks different

A COO's day is the most heterogeneous in the C-suite — headcount issues at 9am, vendor renewal at 11, an escalated customer at 2, a process gap at 4. Training that's calibrated for any single one of those misses the point.

What COOs actually need is a tool that compresses the prep time on every artefact they own. SOPs are the cleanest entry point because every COO has at least 20 of them — half outdated, half undocumented. AI is the first tool that genuinely helps with that backlog.

Definition: Augment, don't replace — the COO drafts the SOP with AI, but the process owner signs and the team trains on it. AI never owns a process.

The arc that works runs over six weeks: SOPs first (week 1-2), vendor reviews (week 3), escalation triage (week 4), weekly business review automation (weeks 5-6).

How do you start with SOP rewrites?

Pick one SOP that's clearly overdue — onboarding, customer escalation, vendor approval, IT-incident response. Don't pick a perfect one; pick a sloppy one. The model can't fix what's already crisp, but it can compress the work of fixing what isn't.

The 90-minute SOP starter

Sit shoulder-to-shoulder with the COO and the process owner. Paste the existing SOP (or transcript of how it actually runs) and use this prompt:

You are a senior operations manager. Below is the current SOP for
[PROCESS] at a [INDUSTRY] company with [X] FTEs. (1) Identify any
step that is ambiguous, missing an owner, or missing a measurable
outcome. (2) Rewrite the SOP with: numbered steps, named role
owner per step, clear input/output per step, escalation path,
measurable success criteria. (3) Flag any step where the company
likely has compliance/regulatory exposure given [INDUSTRY]. Do not
invent steps that are not in the source — if a gap exists, mark
it "needs owner input" and propose the question.

The COO sees a draft that's 70% of the work in 10 minutes. The remaining 30% is judgment — which is exactly what the COO is paid for. That ratio is the entire pitch.

Tool tip (Course for Business): In our 6-week program the operations track always opens with SOPs because COOs convert from skeptic to advocate fastest on artefacts they already own. The framing is Augment, don't replace — AI compresses the rewrite, the COO and the process owner still sign. We pair the COO with one ops-manager AI Champion (1:15-20) so the SOP backlog actually clears after the workshop ends. → https://course.aiadvisoryboard.me/business

How does AI help with vendor reviews?

Vendor reviews eat COO time disproportionately. A renewal pack lands; the COO has 30 minutes to form a view; instead they spend 3 hours reading. Replace that with a 20-minute AI-assisted teardown.

Workflow:

1. Paste vendor's deck/SOW/proposal into the model
2. Ask for: TL;DR, top 5 questions to ask the vendor, top 3 risks given the company size, comparison table vs the previous renewal
3. COO reviews the output, runs the questions in the next call

The win isn't speed — it's that the COO walks into vendor meetings with sharper questions, which compounds across every renewal cycle.

How does AI help with escalation triage?

This is where Stanford's 51-deployment study matters: escalation-routing yields ~71% productivity gain vs ~30% for approval-routing. Translation: train the COO to use AI to triage and route escalations, not to approve them.

The pattern that works:

1. Customer/operational escalation lands in COO inbox
2. COO pastes the thread into the model with: "summarize the issue, classify severity 1-5 using [criteria], identify the right owner, draft a 3-line interim response to the customer"
3. COO reviews, sends, owns the routing decision

The escalation queue clears in 20 minutes instead of 90. The COO doesn't lose context because the model is summarizing, not deciding.

Weeks 5-6: weekly business review automation

By week 5 the COO is ready for the highest-leverage artefact: the weekly business review (WBR). Most SMB WBRs are either skipped, late, or shallow. AI fixes the prep without touching the meeting.

Workflow:

• Pull last week's KPI dashboard, OKR tracker, escalation log
• Paste into model with WBR template
• Get a draft: what changed, what's at risk, what to discuss
• COO edits in 30 minutes instead of building from scratch in 3 hours

This is also where you start showing up as the founder — once the WBR is reliable, the operating cadence of the company tightens noticeably.

Team scan (what AI champions report after week 1)

A typical 30-500-employee operations team after week 1:

• Adoption: COO + 1 ops-manager Champion daily; 4-6 others experimenting
• Use case #1: SOP rewrite — clears 2-3 SOPs from the backlog in week 1
• Use case #2: vendor pack teardown — saves ~2 hours per vendor review
• Use case #3: escalation triage — clears queue in 20 min vs 90
• Use case #4: WBR draft — cuts prep from 3 hours to 30 min
• Use case #5: team policy comparison (PTO, expense, remote-work)
• Friction: "the SOP draft sounds generic" — fixed with paste-in of company examples
• Risk flag: confidential SOP content — 46% of employees admit uploading sensitive data to public AI; ops must use approved tiers
• Saved time: typically 5-7 hours/week per COO once Champion is up
• Honest miss: documenting the 20+ undocumented SOPs takes the full 6 weeks

Tool tip (Course for Business): Most COOs we train inside the 6-week program finish with: 6-10 SOPs cleared, vendor-review rubric, escalation-triage template, WBR draft generator, and a weekly Shoulder-to-Shoulder review with the ops-manager Champion. Augment, don't replace is what stops the team from blindly trusting model output on compliance-sensitive SOPs. → https://course.aiadvisoryboard.me/business

Micro-case (what changes after 7-14 days)

A typical 220-FTE services company trains its COO and senior operations manager together in week 1. By day 7, three SOPs that were blocking onboarding for new hires are cleared. By day 14, vendor reviews take 30 minutes instead of 3 hours, and the COO has cleared a 6-week backlog of escalations that were drifting. The WBR moves from "sometimes-Tuesday" to a fixed 45-min Monday slot because prep is reliable. Most of the saved time gets reinvested in the SOP backlog and one new operating-rhythm artefact (skip-level reviews, pulse surveys) that nobody had bandwidth for.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30-500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

FAQ

Should the COO learn to write prompts? Yes, lightly. The COO writes prompts to compress drafts of artefacts they already own. The Champion writes prompts to build reusable templates. Different jobs.

What about compliance and regulatory SOPs? Always require a named human reviewer with regulatory accountability. AI is a draft tool; sign-off is human. The EU AI Act has fines up to €35M or 7% global turnover for high-risk misuse — the COO is the right person to set the guardrail, but only after they understand the workflow personally.

Will AI replace operations FTEs? Not in 30-500-employee SMBs. The realistic pattern is the same FTEs running tighter operations, with the COO redirecting time from rework to operating rhythm. The $1B logistics co. 7→2 FTE invoice example is not the COO's job — it's a specific repetitive workflow that AI happens to compress dramatically.

How is this different from a generic "AI for ops" course? Generic courses optimize for tool literacy. This optimizes for clearing the SOP backlog by week 6. BCG found programs under ~5 hours produce no behavior change, but the deeper issue is artefact selection — train on what the COO already owns.

What if the COO refuses to engage? Start with the senior operations manager and let one cleared SOP do the talking. COOs who watch their own team clear three SOPs in a week typically join in week 2.

The takeaway

COOs absorb AI fastest through their own backlog — SOPs, vendor packs, escalations, WBR prep. The training works when it compresses real artefacts, not when it teaches abstract prompt craft. Pair the COO with one operations-manager Champion, run six Shoulder-to-Shoulder weeks, and operations becomes the function pulling AI hardest across the company.

Next step: pick the one SOP that's been overdue for the longest and book the 90 minutes.

If you want every employee — including your COO — to ship their first AI automation in five days, book a 30-min call and we'll map your operations team's first week. → https://course.aiadvisoryboard.me/business