How Many Projects Should One PM Actually Be Able to Run?

From Handy Ventures

Your best project manager has three active jobs and looks like a person running eight. They're behind on schedule updates, two subs still haven't confirmed for Monday, and the office is waiting on them to approve invoices they haven't opened. When you ask how they're holding up, they say what every good PM says: I'm at capacity.

So you do what everyone does. You start writing a job posting.

Before you spend $110,000 a year on the next PM, it's worth asking a question that sounds almost rude: at capacity doing what?

Where the week goes

Take a good PM through a normal week and write down what they do in half-hour blocks. Not what the job description says. What they do.

Monday opens with the schedule. Two crews got rained out Friday, so the sequence is wrong now, and fixing it means calls. The framer can come Wednesday instead, but only if the lumber package lands Tuesday, so now the PM is on the phone with the yard. The electrician's office doesn't pick up. They text the electrician directly, who answers at 6:40 that night.

Tuesday is timecards, because payroll runs Wednesday and two guys text their hours in whenever they remember. One of the numbers doesn't look right, so that's a call to the foreman to check whether it was eight hours on the Patterson job or six on Patterson and two on the warehouse. Then the estimate for a job that just sold needs to move: line items into the project software, budget into the accounting system, a materials list into an email to the supplier. Same numbers, typed three times.

Wednesday a customer calls the PM directly about moving a wall. It's a real change, maybe $9,000. Notes on a legal pad, a promise to price it, and one more entry on a list of change orders owed to people. There are four on the list. Two are for work the crews already did.

Thursday is invoices. Coding vendor bills to jobs, matching them against what was ordered, forwarding the confusing ones to the bookkeeper with a note. Friday the PM finally walks all three jobs, which is the part of the week where they earn their money, and they spend half of it on the phone.

Add it up and the picture is roughly this: eight hours coordinating subs and suppliers, four hours on schedule repair, three chasing time, four retyping information from one place to another, five on invoices and paperwork, six answering texts and emails about things somebody else could have known, and a few hours of meetings about all of the above. Out of a 45-hour week, they might spend eight on the work that requires them: walking jobs, catching problems early, making calls on sequence and quality and money.

Your PM is not at capacity as a project manager. They're at capacity as a courier. The judgment that justifies their salary is getting maybe a day a week. The rest is moving information between people and systems that don't talk to each other.

Hiring doesn't fix this. It photocopies it.

Here's what happens when you hire the second PM. You now have two people spending 80 percent of their time on coordination. Your overhead went up $110,000 and your capacity for judgment went up eight hours a week. Worse, you've added a new coordination problem: the two PMs now have to stay synced with each other.

This is the quiet reason contractor overhead grows faster than contractor revenue. Nobody decides to build an expensive office. They just keep solving an information problem with headcount, one reasonable hire at a time.

Software was supposed to fix it, and mostly it moved the problem. The scheduling tool is only right if someone updates it after every phone call. The project management platform is only useful if the field enters things into it, which they won't, because they're holding a nail gun. So the PM becomes the person who types reality into the software. That's not a management job either. That's data entry with a better title.

Measure decisions, not administration

The question in the title has a standard industry answer. Depending on the type of work, you'll hear that a PM can run three jobs, or five, or one big one. All of those answers measure the same thing: how many projects one person can administrate before the paperwork buries them.

That's the wrong unit. A PM's real capacity is how many projects they can make good decisions about. And decisions are cheap in hours. Deciding whether to accept the framing, whether the change is worth pricing, whether to pull the plumber forward, whether a job that's trending over needs a hard conversation this week instead of next month: that might be two or three hours per project per week, if the information arrives already organized.

Run that math. A PM with 40 usable hours, spending three hours of judgment per project, can carry a dozen or more projects. Not by working harder. By not being the person who retypes the estimate, chases the timecard, and calls the electrician's office that never picks up.

Whether the number is 12 or 15 or 9 depends on your work. The point isn't the number. The point is the ratio, and right now the ratio in most contracting businesses is upside down: the most expensive judgment in the company, priced by the hour, is spent on tasks a system should absorb.

The audit that should come before the job posting

So before the next PM hire, do the half-hour-block exercise for a week. It costs nothing and it's clarifying in a way no org chart discussion ever is. Then sort the list into two piles. Pile one: things that required their judgment. Pile two: things that required their phone.

If pile two is bigger, and it will be, you don't have a headcount problem yet. You have an operating problem. Hiring into an operating problem doesn't solve it. It gives the problem a second salary.

The businesses that scale well figure this out early, sometimes by accident, usually because an owner got stubborn about it. They build the systems that move information on their own, and they save their PMs for the work that deserves them. Then, when they do hire the next PM, the hire buys them ten projects of capacity instead of three.

That's the version of the question worth asking. Not how many projects can a PM survive. How many could they run if their week belonged to them?

If it's a question you're sitting with right now, we'd rather talk it through than have you read about it.