COOs see across the company, own operational efficiency, and have the political authority to drive change. They're also overworked. This is the workflow for using Claude to recover hours and amplify operational leverage.
Top COO Claude workflows: meeting synthesis & action capture, process documentation, cross-functional brief drafting, vendor evaluation, performance review prep, dashboard narrative. Set up 5 Projects; use them daily. COO is often the natural internal owner of AI rollout — lean in.
Paste raw notes or transcript into a Meeting Synthesis Project. Get structured outputs: decisions made, action items (with owners and dates), open questions, executive summary. Cuts post-meeting work 80%.
Convert tribal knowledge into documented process. Have the SME describe; paste into a Process Doc Project; get a structured doc to refine. Build the company's operational knowledge base over time.
Draft updates, decision memos, and cross-team requests in a consistent voice. Get to clear ask quickly.
Synthesize vendor pitches; draft questions; prep for negotiation calls.
Paste KPI dashboards; get a draft narrative explaining what changed, why, and what to do. Saves CFO/COO joint time monthly.
If you are a COO of a $5M-$50M company without a defined AI initiative, you should probably own it.
COO usually. CEO sponsors; COO owns. At very small companies (under 30 people), founder/CEO can own it directly.
8-12 hours/week during active rollout (first 90 days), then 4-6 hours/week ongoing for governance and expansion.
No. The COO sets up the platform and supports; each function's owner builds Projects for their workflows.
Get fluent fast — it's now a core operating skill. Take a structured training course; use it daily for personal work for 30 days.
Yes, especially the first one. The COO is the long-term owner of what the engagement produces.