A growing IT company hits a familiar wall.
The founder or CTO has been running projects directly. It worked when the team was eight people. With twenty people and four concurrent projects, it does not work anymore. Deadlines slip. Clients ask for status updates that nobody has time to write. Engineers get pulled into client calls instead of building.
The obvious move is to hire a full-time project manager. Eighty thousand to a hundred and twenty thousand pounds a year, plus benefits and the time to recruit, onboard, and figure out if they are good. For a company that needs PM leadership but does not need it forty hours a week, the math does not work.
This is where a fractional PM fits.
What a Fractional PM Is
A fractional PM is a senior project manager who works with your business on a part-time, ongoing basis. Usually one to three days per week. Sometimes more during a specific project, less during quieter periods.
They are not a contractor brought in for a single project. They are a long-term member of your operational leadership, just at a fractional commitment.
The key word is senior. A fractional PM is not someone who is junior trying to grow into the role. They have run projects for ten or fifteen years across multiple companies. They bring a level of experience that a full-time hire at your stage probably could not afford.
The trade-off is the time commitment. They are not in your Slack all day. They are not on every internal call. They focus on the work that requires senior project leadership and step back from the work that does not.
What a Fractional PM Does Day to Day
The specifics depend on the company, but the core work falls into five categories.
Running the PM Function
Someone needs to own how projects are run across the business. What tool gets used. What the project intake process looks like. How estimates are made. How risks are tracked. How client communication is structured. How retrospectives happen.
A fractional PM owns this. Not just for one project but for the function as a whole. They build the playbook the team uses on every project.
For an IT company running multiple client engagements, this is often the highest-leverage thing a fractional PM does. One person setting the standard means twenty engineers do not each invent their own way of running projects.
Leading the Highest-Stakes Projects Personally
For the project that is most strategic, most complex, or most at risk, the fractional PM runs it directly. They are the day-to-day project lead. They run the client meetings, manage the engineering team, track the risks, and own the outcome.
This is where the senior experience pays off. A complex enterprise project with a difficult client benefits from a PM who has run that exact pattern before, not from one who is figuring it out for the first time.
Coaching Junior PMs and Project Owners
For the projects the fractional PM is not running directly, they coach the people who are. That might be a junior PM, a tech lead acting as PM, or an engineer running their first project.
Coaching looks like a weekly thirty-minute one-on-one. Looking at the project together. Asking questions about risks the project owner has not surfaced. Suggesting the next move when something is stuck.
This is how the PM function scales. The fractional PM does not personally run every project, but every project benefits from senior PM thinking through the people they coach.
Client Relationship Management at Key Moments
Not every client interaction. The kickoff, the major escalations, the difficult negotiations, the executive-level reviews.
A fractional PM with fifteen years of client experience handles a kickoff differently than a junior PM. They set expectations more clearly. They surface risks earlier. They build trust faster. The client relationship benefits from senior involvement at the moments that matter.
For ongoing weekly status calls, the project owner runs them. The fractional PM is involved when something needs senior attention.
Operational Reporting to Leadership
Founders and CTOs need to know what is happening across all projects without sitting in every meeting.
A fractional PM produces the operational view. Which projects are on track. Which are at risk. Where the team is over-capacity or under-utilised. Which clients are at risk of churning.
This view is updated weekly and reviewed in a thirty-minute leadership sync. It is the difference between leadership feeling in control and feeling reactive.
When a Fractional PM Makes Sense
The signal is usually structural.
You have between five and forty people on the delivery side. Below five, the founder or a tech lead can run projects without dedicated PM. Above forty, you need a full-time head of delivery, not a fractional PM.
You are running between three and ten concurrent projects. With one or two projects, anyone can manage them. With more than ten, you need a delivery team, not one fractional person.
The founder or CTO is currently doing PM work and that is becoming a constraint. They are pulled into project meetings instead of strategic work. They are the de facto escalation point for every client. They are writing status updates instead of building product or selling.
You have at least one significant client engagement where senior PM judgement would have prevented or fixed a problem. If the answer is yes, the cost of a fractional PM probably pays for itself in one project.
You cannot justify a full-time hire yet. Either the volume of work does not require forty hours, or the company is not ready to commit to the salary, or you want to test whether dedicated PM leadership actually solves the problem before making a bigger investment.
If three or more of these are true, a fractional PM is probably the right move.
How the Engagement Works
A typical fractional PM engagement looks like this.
Discovery phase, two to four weeks. The fractional PM joins the company, meets the team, reviews current projects, identifies the operational gaps, and produces a plan. This is not billable client-facing work. This is them learning the business well enough to add value.
Stabilisation phase, six to eight weeks. The fractional PM picks the most urgent issues and fixes them. Usually that is one specific project that is at risk, plus the foundational PM systems (tool, process, reporting). Visible improvements happen in this phase.
Steady-state phase, ongoing. The fractional PM is now a regular part of operations. They run the most important projects, coach the others, produce the operational view, and handle senior client moments. The engagement continues as long as the company benefits.
Time commitment varies. Some companies need three days a week initially and one day a week after stabilisation. Some need one day a week throughout. The right answer depends on the volume of work and how much senior judgement is required.
Cost typically ranges between four and ten thousand pounds per month, depending on time commitment and seniority. Compared to a hundred thousand pound full-time salary plus benefits, recruitment cost, and the risk of a wrong hire, the math usually works.
What a Fractional PM Is Not
A fractional PM is not a virtual assistant for projects. They do not take notes in your meetings. They do not chase status updates from engineers. They are not a low-cost replacement for a full PM.
A fractional PM is not a temporary fix. They are an ongoing part of operations. Companies that engage a fractional PM and treat it as a stopgap usually do not get the full value, because the value compounds over time.
A fractional PM is not a substitute for a full-time hire when you have outgrown fractional. There is a stage where the volume of project work justifies a full-time delivery lead. When you reach that stage, you hire one. The fractional PM was the right call at the right stage, not forever.
Why IT Companies in Particular
The pattern fits IT services, software agencies, and product companies for the same reason.
These businesses run on projects. The quality of project leadership directly affects the quality of delivery, which directly affects client retention, which directly affects revenue. PM is not back-office work. It is operational core.
But IT companies between ten and fifty people often cannot justify a full-time senior delivery lead. They are too small for the salary, too big for the founder to keep running PM directly. The fractional model bridges that gap.
For larger IT companies, fractional PM also fits as targeted senior reinforcement. Add a fractional PM specifically to handle the most complex client or the most critical project, while the in-house PM team handles everything else.
The Bottom Line
If you are running an IT company and you are doing PM work yourself, or you are watching projects struggle because nobody senior owns them, a fractional PM is probably the right next step.
The cost is manageable. The impact is fast. The commitment is reversible. And the senior experience you get is more than you could afford full-time at this stage.
Most companies that try fractional PM never go back. They either grow into a full-time hire or stay fractional indefinitely. Both work. What does not work is leaving the founder as the de facto PM for too long. That is the move that limits how much the business can grow.