# How fractional COOs structure a week across five clients

Source: https://founder.nexxascreen.com/articles/fractional-coo-week-five-clients  
Updated: 2026-11-20  
Publisher: Sentient AI Inc

> A workable week with five clients gives each one a fixed anchor block, keep short daily windows for urgent requests from all clients, and protect one block a week for their own admin and review. The structure works when clients know the rhythm, requests are gathered in one place, and nothing waits for the anchor day.

A week across five clients works best with three layers: one anchor block per client for deep work, two or three short daily windows for urgent requests from all of them, and one protected block for your own review and admin. The anchor blocks give each client real attention. The windows keep anyone from waiting days. The review block keeps the whole thing from drifting.

## The key points

- Give each client a fixed anchor block, and tell them when it is.
- Keep short daily windows for urgent requests from every client.
- Protect a weekly block for your own review, invoicing and planning.
- Agree in writing what counts as urgent.
- Keep one list of what is waiting on you, grouped by client, so the windows are quick.

## Why a fixed structure

Five clients means five sets of people, priorities and tools. Without a structure, the loudest client gets your week, and the quietest gets your Friday afternoon. Clients notice the unevenness before you do.

A fixed rhythm solves three problems at once. You go deep on one company at a time. Clients know when to expect you. And you can see at a glance whether the week has room for a sixth engagement. Usually it does not.

## The three layers

### Anchor blocks

An anchor block is a half day or a full day where one client has you. Meetings with their team, the hard thinking, the documents that need focus. Some fractional COOs give a full day to their largest client and half days to the others. Others give each client one morning and keep afternoons flexible.

What matters is that the block is fixed and known. "Tuesday mornings are Acme's" is a promise both sides can plan around.

### Response windows

Two or three short windows a day, often 30 minutes each, where you look at every client's requests and clear the quick ones. Approvals, short replies, a decision that is blocking someone. The windows are what let you keep fixed anchor blocks without being slow.

The windows only work if you can see every client's requests quickly. Opening five Slack workspaces and five inboxes takes most of the window. A single view of what is waiting on you, still grouped by client, turns the window into actual work. That can be a list you keep by hand, or a board such as Operators that gathers it from each client's tools.

### The review block

Once a week, a block for you: reviewing each client's open work, invoicing, updating your notes, planning next week. Without it, the admin of five engagements leaks into every evening.

## A sample week

This is one possible shape, for five clients of different sizes. Adjust the hours to your engagements.

| Day | Morning | Midday window | Afternoon | Late window |
|---|---|---|---|---|
| Monday | Client A anchor | All clients | Client A meetings | All clients |
| Tuesday | Client B anchor | All clients | Client C anchor | All clients |
| Wednesday | Client A follow-ups | All clients | Client D anchor | All clients |
| Thursday | Client E anchor | All clients | Client B meetings | All clients |
| Friday | Weekly review and admin | All clients | Buffer, sales, rest | |

Client A is the largest, with most of two days. Clients B to E get one anchor each, and B a meeting slot. Friday morning is the review block. Friday afternoon is buffer, because something always overruns.

## Agree what urgent means

Every engagement needs a short written line on urgency. For example:

- **Urgent:** a production incident, a payroll problem, a legal deadline, a board member's request with a date. Answered within the next window.
- **Normal:** everything else. Answered on the client's anchor block or within two working days.

Put it in the contract or the kickoff note. It saves arguments later and makes the windows calm.

## How do you keep clients apart?

Five clients means five sets of confidential information. A few habits keep them apart:

- Separate logins and workspaces per client, never forwarded into one shared account.
- Notes kept per client, not in one long document.
- Before a screen share, show only that client's work.
- AI assistants given access to one client at a time, not all five.

The [guide to keeping clients' data apart](/guides/keep-client-data-apart) shows how to set this up in Operators. The same principles apply whatever tools you use.

## Watch for the signs of overload

The structure tells you when you are full. Look for:

- Anchor blocks moving more than once a month.
- Response windows that run long every day.
- The review block skipped two weeks in a row.
- A client asking where you have been.

Any one of these means the week is past capacity. The answer is usually a smaller engagement, a higher rate or one fewer client, not longer days. The [fractional rate calculator](/tools/fractional-rate) helps you see what the week is really earning.

## Make switching cheaper

Each move between clients costs you a few minutes of reloading context. Two habits shrink it:

- **Leave a line.** Before you leave a client's block, write one line on where you stopped and what comes next.
- **Start from the list.** Begin each client's block by reading what is waiting on you there, and what is due.

The article on [the cost of context switching](/articles/cost-of-context-switching) explains why this matters more across companies than within one.

## Adapting it

Not every fractional COO works on fixed days. Some work in sprints, two weeks on one client and then the next. Some work entirely asynchronously. The three layers still help: deep time per client, a regular way to clear urgent requests across all of them, and a weekly look at the whole.

## What to do next

- [Operators for fractional COOs](/for/fractional-coo)
- [Fractional rate calculator](/tools/fractional-rate)
- [The real cost of context switching](/articles/cost-of-context-switching)

## Questions

### How many clients can a fractional COO handle at once?

There is no fixed number. It depends on how deep each engagement is and how many hours each one needs. The limit shows up in your week when anchor blocks start to slip and response times stretch.

### Should I give each client a fixed day?

A fixed anchor block per client helps both sides. Clients know when you are theirs, and you go deep on one company at a time. Keep short daily windows for urgent requests so nobody waits a week.

### How do I handle urgent requests from a client on another client's day?

Use short response windows each day for every client, and agree in your contract what counts as urgent. Anything that is not urgent waits for that client's anchor block or the next window.

### How do I keep five clients' work from mixing up?

Keep each client's tools, notes and assistants separate, and keep one view of what is waiting on you that is still grouped by client. Before calls, show only that client's work on screen.
