"We know we need a PMO. We just cannot justify hiring one yet."
I hear this most often from founders and engineering leaders somewhere between 80 and 250 people, and the instinct behind it is sound.
What they are describing is a real timing problem. It is worth separating into its two halves, because they have different answers.
What is a fractional PMO? A fractional PMO is a senior project or portfolio management professional who owns your governance function on an ongoing, part-time basis rather than as a full-time employee. Unlike a consulting project, it does not end. It is sized to the real volume of the work, which at most scaling companies is a few hours a week of senior judgement.
Building It and Keeping It Alive Are Different Jobs
Establishing an operating model is a project.
You map how work actually flows, find where it stalls, agree who owns what, design the governance, build the reporting, get it adopted. That is intensive senior work over a bounded period, it produces artefacts, and then it is done.
You can buy that as a consulting engagement, and most companies should.
Keeping it alive is something else entirely. It has no end date, it runs at much lower intensity, and it is the part almost nobody plans for.
Frameworks decay by default.
New requests arrive to add a field, split a workflow, create a project for a team that does not need one. Each of them is individually reasonable. Status reports get skipped during a busy quarter and then never resume. A team reorganises and nobody updates who owns which initiative.
Six months of small, sensible decisions, none of them wrong on its own, and the thing you paid to build no longer reflects how the company works.
Frameworks erode one individually reasonable exception at a time, and nobody notices until the reporting stops being true.
Preventing that takes someone senior enough to say no and close enough to notice. It also takes about half a day a week.
The Job Is Real, Senior, and Genuinely Part-Time
Here is the mismatch that fractional exists to solve. It is worth stating plainly, because "fractional is the future of work" is the kind of claim that invites scepticism.
The person who keeps an operating model healthy needs to look at a request for a new custom field and understand the second-order effect on reporting across thirty projects.
They need enough standing to tell a department head that their exception is not justified. They need to run the governance cadence and be believed in the room.
That is a senior profile. And at a company of a hundred to two hundred people, it amounts to a few hours a week.
So companies pick one of two bad options.
They hire a full-time PMO lead, who spends perhaps a fifth of their week on the work that actually required their seniority, and the rest of it absorbing operational firefighting or inventing process to justify the role.
Or they hand it to someone internal who already has a job, usually an engineering manager or an IT administrator. It then becomes the thing that slips whenever anything else is urgent.
The second failure is quieter and more common. It presents eighteen months later as "our Jira is a mess again."
Fractional is the third option: the senior person stays, at the actual size of the work. It is a correctly sized version of a real hire.
The Build and the Run Are Complementary
These two are not alternatives, and the strongest version is usually both, sequenced. A bounded consulting engagement to build the thing, then an ongoing fractional arrangement to run it.
This is the sequence we followed with our automotive client. The build side is written up in What Needs to Happen Before You Implement Jira.
We ran the discovery, designed the operating structure, and built the connected Jira and Confluence ecosystem underneath it. That was the project.
The run side is far lighter: a weekly hour with every initiative owner, going line by line through the active global initiatives, updating status and surfacing what is drifting.
It is not a large commitment, and it is what keeps a framework accurate rather than decorative.
There is a second advantage that only exists in this sequence. The person running it is the person who built it, so there is no context-loading cost and no handover gap.
A permanent hire brought in after the build inherits someone else's design, and spends their first two quarters deciding whether to trust it.
How to Know If Fractional Fits You
Five signals. You want most of them rather than one.
• The build has happened, or is happening, and you can see that maintaining it is going to fall between existing jobs.
• Your bottleneck is senior judgement rather than capacity. If you need more hands running projects, this is the wrong instrument and you should hire project managers.
• You have an executive sponsor prepared to back decisions in rooms the consultant is not in.
• Your governance requires a regular cadence that nobody currently owns, and the last three times it slipped, nothing bad happened until suddenly it did.
• You cannot yet write a permanent job description you would be confident hiring against.
That last one matters more than it sounds. If the spec is vague, hiring converts the vagueness into a person's mandate, and they will spend a year litigating it.
The Drawbacks, Stated Properly
A fractional lead has no positional authority. Everything depends on a sponsor who will spend political capital. Without one you get well-argued recommendations and no change. I would rather lose an engagement at scoping than take one where the sponsor is nominal, because the outcome is predictable and bad for both sides.
You cannot escalate at six on a Thursday. A fractional arrangement is a defined commitment. If your environment genuinely needs constant senior presence, that is a legitimate argument against the format, and you should take it seriously rather than hoping it will work out.
There is a dependency risk, and it is the honest one. An arrangement with no path to internal ownership has rented you a dependency rather than built you a capability.
There are two acceptable answers to this, and you should insist on one of them. Either an explicit plan to hand the running of it to a named internal person on a stated horizon, or a conscious decision that this is an outsourced function you intend to keep outsourced, priced and reviewed accordingly.
What is not acceptable is drifting into the second while believing you are in the first.
Some decisions need someone who will live with the consequences. Restructuring a team, changing how people are evaluated, removing a layer. A fractional lead can design those. They should not own them.
When You Should Just Hire
If the running work is genuinely full-time, hire. That is usually the case once you have multiple project managers to line-manage, a portfolio large enough to need daily attention, or a governance function with real headcount underneath it.
If you already know exactly what you need, and have someone internally who can evaluate candidates for it, hire.
If the role requires standing authority over people rather than over process, hire.
A consultancy that never tells you to hire instead is optimising for its own utilisation. It is worth asking directly, and listening to how the answer is phrased.
What Good Looks Like
The operating model is accurate, because someone with authority reviews it on a cadence and pushes back on the requests that would erode it.
Leadership has a single view of active work that they trust enough to make decisions from. Problems surface while they are still adjustments rather than escalations.
And the arrangement is sized to the work rather than to the org chart.
The question I find most useful to put to leaders considering this: if you hired a permanent PMO lead next month, could you write down what you would expect them to have achieved by the end of their first year?
If that comes easily, hire. If it does not, the answer is not that you need more budget.
Frequently Asked Questions
What is a fractional PMO?
A senior project or portfolio management professional who owns your governance function on a part-time, ongoing basis rather than as a full-time employee. The distinguishing feature is that it continues, unlike a consulting project, and it is sized to the real volume of the work.
How is fractional different from interim or consulting?
Consulting is a bounded project with deliverables and an end. Interim is a full-time temporary occupant of a role, usually covering a gap. Fractional is a permanent arrangement at partial capacity. They combine well: a consulting engagement to build the operating model, a fractional arrangement to run it.
How much time does a fractional PMO engagement take?
It depends on portfolio size, rate of change and governance cadence, and anyone quoting a standard package before understanding those three is guessing. For a company of around a hundred people with a settled framework, a weekly governance session plus implementation time is a realistic shape.
When should a company hire a permanent PMO lead instead?
When the running work is genuinely full-time: multiple project managers to line-manage, a portfolio needing daily attention, or a governance function with headcount underneath it. Also when the role requires standing authority over people rather than over process.
Does a fractional PMO work without an executive sponsor?
No. A fractional lead has no positional authority, so every decision depends on someone senior backing it in rooms the consultant is not in. Without that, the engagement produces recommendations and no change.
We do both halves. See how the build worked for a hundred-person automotive client, and tell us which half you need.