Pocket PMO
Sign In
Back to blog

Fractional PMO: how to run several clients solo

August 14, 2026
Fractional PMO: how to run several clients solo

Running a fractional PMO looks glamorous from the outside. In practice it is three or four clients, each convinced they are your only one, each with their own template pack, their own reporting cadence and their own idea of what a risk log should look like. The work that wins you the next contract is judgement. The work that eats your week is admin.

This is the operating model that keeps the two apart.

Table of contents

What a fractional PMO actually sells

Clients do not buy your spreadsheet skills. They buy confidence that delivery is under control and that someone will tell them the truth early. Everything in your operating model should protect the time you spend producing that confidence: reading the signals, having the awkward conversation, and making the call.

If you spend Thursday night rebuilding a steerco pack from five sources, you are being paid consultant rates to do administration. That is the trap, and it scales badly. Two clients is survivable. Four is not.

Rule one: hard separation between clients

Each client needs its own workspace with its own data, its own users and its own access rules. Not folders. Not a naming convention. Actual separation, so that a document, a lesson or a risk from one client can never surface in another. This matters commercially as much as legally, because the first time a client sees another logo in your tool your credibility takes a hit you will not recover.

In Pocket PMO this is the organisation model: one client per workspace, switched from the header, with strict data boundaries between them and a single login for you.

Rule two: one method, applied everywhere

Resist the urge to adopt each client's templates. You will end up maintaining four methods and being expert in none. Bring your own: a RAID log with real structure, stage gates, a decision log, a governance level that scales from light to full, and a status report format your sponsors can read on a phone.

The pitch is straightforward. Clients are not paying for their old templates. They are paying for a method that has already been proven on other engagements, and for the speed that comes with it. Most will take the trade happily once they see the first report.

A light governance level is usually right for small change portfolios. Full governance earns its keep on regulated or capital work. Deciding this in week one, and writing it down, prevents six months of drift. See the governance guide for how to pitch the difference.

Rule three: reporting is a rollup, not a rebuild

The single biggest lever in a fractional practice is making the report a by-product of the delivery data rather than a separate artefact.

If your plan, RAID log and decisions are maintained in one place, then a status report, a portfolio view and a board pack are all views of the same objects. Generating them costs minutes. If they live in different places, every report is a data reconciliation exercise, and you will do that exercise every week, for every client, forever.

Practical test: can you produce a shareable client snapshot in under five minutes, without opening a spreadsheet? If not, the operating model is the problem, not your diary.

Rule four: price the method, not the hours

Fractional work priced purely by day rate punishes efficiency. The better your system, the less you bill. Price the outcome instead: a monthly governance service that includes the portfolio pack, the steerco, the RAID assurance and the exec summary, delivered to a standard. Then keep improving the system, because every hour you save is margin rather than lost revenue.

This is also a cleaner sales conversation. Sponsors understand a monthly governance service. They rarely understand what two days a week buys them.

A week in the life

A workable rhythm for three clients:

  • Monday — review the delivery signals across every workspace. Attention goes where completion probability has dropped, not where the loudest email came from.
  • Tuesday and Wednesday — client days. Workshops, decisions, unblocking. No reporting.
  • Thursday morning — approve the drafted reports and snapshots, add the judgement layer, send.
  • Thursday afternoon — pipeline and proposals.
  • Friday — one improvement to the method, and lessons captured from anything that closed.

Nothing in that week is a data-gathering exercise. That is the whole point.

Related reading

Frequently asked questions

How many clients can one fractional PMO realistically hold?

Three to four active engagements is the usual ceiling when reporting is automated and the method is consistent. Without those two things, most people struggle past two.

How do I keep client data separated?

Use a tool with a real multi-workspace model, where each client has its own data boundary and access control, rather than separating by folder or file naming.

Should I use the client's templates or my own?

Your own, in almost every case. One method applied across every engagement is the thing that makes a fractional practice viable, and it is a large part of what the client is buying.

What should I automate first?

The weekly status report and the monthly board pack. They are the highest-frequency, lowest-judgement pieces of work in the practice.