How a Fractional COO Keeps Twelve Clients Moving Without Dropping a Ball

The operator

A fractional COO running twelve active client relationships bills somewhere between 150 and 500 hours a month across engagements that span e-commerce operations, SaaS scale-ups, and professional services firms. Each client has its own org chart, its own project cadence, its own cast of stakeholders with their own quirks. The fractional COO is not an employee of any of them — which means there is no institutional memory holding anything together except whatever that person carries in their own head.

The load looks like this: three inboxes (personal domain, one client's Microsoft 365 tenancy they were added to, and a shared ops alias), eighteen standing calls per week, a revolving set of action items extracted from those calls, and a constant background dread that something is cooling in an account they haven't looked at in four days. The work itself is high-value advisory. The overhead — reconstructing context, chasing follow-ups, spotting relationship drift — is not.

The breaking point

The felt problem rarely announces itself cleanly. It shows up on a Tuesday morning as a vague feeling that something is off with a particular account — a thread that went quiet, a deliverable that stopped getting updates, a champion contact whose replies got shorter. By the time the fractional COO opens that account's folder in their head and tries to pull the last few weeks back together, twenty minutes have disappeared and they still aren't sure what they missed.

The specific fear is renewal. With twelve clients on rolling quarterly or annual contracts, there are always two or three relationships at some stage of the retention cycle. A cooling account that goes unnoticed for three weeks does not feel like negligence day-to-day — it feels like being busy. It only looks like negligence in retrospect, when the client opts not to renew and names a reason that was legible in the email thread all along.

The broader problem is that context lives in six different places. Gmail has the threads. Google Drive has the SOWs and status decks. Google Calendar has the meeting history. The fractional COO's mental model holds the org chart, the political dynamics, and the prior decisions. None of these talk to each other. When something goes wrong, pulling them together is manual, slow, and imprecise — and it happens after the problem is already visible, not before.

The setup

The fractional COO connects their personal Gmail account and the Microsoft 365 inbox they share with one client. They connect Google Drive and OneDrive so Lodestar can ingest SOWs, project briefs, status decks, and shared working documents. Each client gets its own organisation inside Lodestar, and each active engagement gets a project under it — aligned to how they already think about the work, not to an unfamiliar CRM taxonomy.

Within a few hours of ingestion, Lodestar has extracted action items from recent threads and meeting recaps, surfaced per-contact sentiment trends for the contacts they interact with most, and assembled org chart sketches from the email signatures and CC patterns in the threads. Nothing new was entered manually. The operating picture that existed only in the fractional COO's head now has a structured parallel that can be queried.

The workflow

The workflow follows the Sense → Decide → Act → Close loop. The morning starts with a single question to Claude via the Lodestar MCP server. From there, the session runs without app-switching.

• ·Sense — Claude calls `dashboard_needs_attention` and `dashboard_sentiment` to surface what needs looking at. The response names one account with a sentiment drop of −0.3 over the past two weeks and two threads marked as tense. The fractional COO had not registered either thread as significant on their own.
• ·Sense — Claude calls `emails_list` and `emails_content` on those threads, then `knowledge_org_charts` and `contacts_retrieve` for the relevant organisation. The full picture comes back: the primary champion has been replaced by a more skeptical stakeholder; a deliverable shipped two weeks ago received no acknowledgment; a follow-up the fractional COO had mentally noted was never sent.
• ·Decide — Claude reasons over the assembled context: who the stakeholder is, what the last point of positive engagement was, what the open action items are, and what a reasonable recovery move looks like. It surfaces the dropped follow-up as the most concrete addressable gap.
• ·Act — Claude calls `emails_reply_link` to draft a recovery email grounded in the real thread history — referencing the delivered work, acknowledging the silence, proposing a brief check-in call. The draft opens in the fractional COO's compose window. They read it, adjust the tone for the specific relationship, and click send.
• ·Act — Claude calls `action_items_create` twice: one item to confirm the check-in call was scheduled, one to track whether the stakeholder responded within five business days. Both are linked to the account's project in Lodestar.
• ·Close — Claude calls `timeline_events_create` to log the recovery outreach against the account timeline. The event appears in the client's project alongside the original deliverable, the sentiment drop, and the new follow-ups. The history is now readable as a sequence rather than as scattered fragments.

What changes

The morning briefing becomes a genuine triage instead of a scroll-and-guess. The fractional COO sees which accounts need attention ranked by actual signal — sentiment trends, overdue action items, threads that have gone quiet — rather than by whichever client emailed most recently. The accounts that are healthy stay out of the way. The ones that need attention surface before the problem is visible to the client.

Follow-ups stop evaporating. Every commitment extracted from a call or a thread gets logged, assigned a due date where one exists, and surfaced in the daily plan when it's overdue. The fractional COO is no longer the sole repository of what was promised to whom and when.

Renewal conversations become easier. When a quarterly review arrives, the full account history is queryable in seconds: decisions made, deliverables shipped, sentiment over time, open items. The renewal prep that used to take an hour of archaeology takes minutes. The fractional COO walks into the call with a complete picture instead of a reconstructed approximation.