MSP Project Management Fees: Stop Giving Away the Work

Most MSP project management fees are not too high.

They are too hidden.

The work still happens. Someone chases approvals. Someone coordinates the vendor. Someone moves the cutover because the client forgot to confirm DNS access. Someone rewrites the project notes after the scope quietly changes.

Then the quote shows zero dollars for project management because it felt awkward to charge for "admin."

That is not generosity. That is margin leakage with better manners.

If the project itself is fuzzy, start with how to scope an MSP project. If the scope is clear and you still are not charging for management time, this is the next problem to fix.

The short answer

MSP project management fees should cover the labor and risk required to keep a project controlled: scheduling, communication, vendor coordination, client dependencies, change control, documentation, and acceptance management.

A 10% to 30% fee can make sense when PM work scales with project size. A fixed fee is cleaner when the coordination load is obvious. Hourly PM is safer when the client controls too many variables for you to own the risk.

FlexPoint's guide to MSP project-based billing frames fixed or milestone-based project work around defined deliverables, scope creep risk, cash flow timing, and estimation accuracy. Those are exactly the places project management protects margin.

What PM actually covers

Project management is not a decorative line item. It is the control layer between a signed quote and a project that eats itself.

It covers work like:

• Turning the approved quote into an internal project plan.
• Scheduling client-side and vendor-side dependencies.
• Tracking access, approvals, licenses, procurement, and shipping risk.
• Sending status updates before the client asks for them.
• Logging decisions, assumptions, and blockers.
• Managing change requests before they become free labor.
• Confirming acceptance criteria and handoff before the project is called done.

If nobody owns that work, the project still pays for it. Usually through unpaid coordinator hours, engineer distraction, or delivery chaos that gets explained away as "just one of those projects."

No. It was work. Quote it.

Pick the fee model that matches the risk

There is no magic percentage. Anyone selling one is trying to make a spreadsheet feel like strategy.

Use the model that matches how the PM work behaves.

Fee model	Use it when	Watch the risk
10% PM fee	Small, repeatable projects with few stakeholders	Easy to undercharge if the client needs heavy hand-holding
15% to 20% PM fee	Normal migration, onboarding, or infrastructure work	Works best when scope and acceptance criteria are already written
25% to 30% PM fee	Multi-vendor, multi-site, compliance, or after-hours work	Client pushback rises unless the line explains what PM covers
Fixed PM fee	Coordination work is predictable but not tied to project cost	Needs clear assumptions and approval gates
Hourly PM	Client approvals, access, or vendors are uncertain	Needs caps or approved blocks so it does not feel open-ended

ScopeStack's MSP pricing guide points to operating costs, service scope, complexity, client size, and uncertainty as pricing inputs. That is the useful lens. Do not price PM because another MSP uses a number. Price it because your project has real coordination work and real ways to drift.

When 10% is enough

A 10% project management fee is usually fine when the project is small, repeatable, and mostly inside your control.

Think firewall replacement with known hardware. A workstation refresh with clean inventory. A license cleanup with one decision-maker and fast approvals.

The test is simple: can one coordinator manage the project with a kickoff, a few status updates, basic scheduling, and a clean handoff? If yes, 10% may cover it.

But do not use 10% because the client is price-sensitive. Price sensitivity does not make scheduling work disappear. It just makes you nervous about showing the line.

If the phrase "project management fee" creates friction, rename it. "Project coordination and control" often lands better because it names the work instead of the department.

When 30% is not crazy

A 30% PM fee sounds high until the project includes three vendors, two client executives, an after-hours cutover, hardware lead times, compliance evidence, and a site manager who only answers email on Tuesdays.

That project is not just technical labor. It is dependency management.

Use the higher end of the range when:

• The client has multiple sites, departments, or approvers.
• A third-party vendor controls part of the timeline.
• Compliance or cyber insurance evidence must be captured.
• The work touches production systems after hours.
• Hardware, licensing, or subcontractor timing can delay delivery.
• The client has a history of slow approvals.

This is where MSP pricing and margin protection becomes practical. The goal is not to win the quote with a nicer-looking number. The goal is to deliver the project without donating the coordination work.

Quote language you can steal

The line item should explain what the client is buying. Not with consultant fog. With plain language.

For a fixed-fee project:

Project coordination and control covers kickoff, task scheduling, vendor coordination, client approval tracking, status communication, change-request management, and handoff documentation. This work keeps the timeline, scope, and deliverables controlled after the quote is approved.

For percentage-based PM:

Project management is billed at X% of services labor. This covers scheduling, vendor coordination, status communication, change control, and final handoff. Hardware and pass-through licensing are excluded from the PM calculation unless stated otherwise.

For hourly PM:

Project management is billed at $X/hour in approved blocks. The first block covers kickoff, scheduling, vendor coordination, status communication, and client dependency tracking. Additional blocks require written approval.

For client delays:

Project timeline and fee assume client approvals, access, and required information are provided within the agreed response window. Delays caused by missing access, late approvals, unavailable stakeholders, or third-party blockers may require schedule changes and additional project coordination time.

For change orders:

Work outside the approved scope will be documented as a change request before delivery. The change request will include the requested change, expected schedule impact, expected cost impact, and client approval before work begins.

This is not legal advice. Have counsel adapt the language for your MSA and SOW. But the operating principle is simple: if PM work has assumptions, write them down.

Adjust by client and project type

Do not use one PM rule for every quote.

Nonprofits: Budget sensitivity is real, but committee decision-making can add coordination. A smaller fixed PM fee plus strict approval windows may work better than a high percentage.

Small businesses: Fixed fees are often easiest to explain. Name what is included, name the approval expectations, and avoid a percentage that feels abstract.

Hardware-heavy projects: Exclude pass-through hardware from the PM percentage unless procurement is truly part of your delivery risk. If procurement is the hard part, charge for procurement and coordination directly.

Compliance projects: Charge more PM, not less. Evidence, owner assignments, audit timing, and client education are part of the work.

The same logic applies when comparing per-user vs per-device MSP pricing: price the thing that drives work, not the thing that happens to be easiest to count.

Build PM into scoping

The worst time to invent a PM fee is after the quote is already drafted.

For every project, answer these before pricing:

1. How many stakeholders need updates or approvals?
2. Who owns client-side access and scheduling?
3. Which vendors can affect timing?
4. What decisions must be made before work starts?
5. What would cause a change order?
6. What would delay the project without being your team's fault?
7. Is PM effort tied to labor, procurement, compliance, or client behavior?

That last question tells you whether to use a percentage, fixed fee, hourly PM, or a mix.

Scopable's angle is simple: cleaner scoping makes cleaner pricing possible. If your team captures assumptions, exclusions, approval gates, and dependencies before the quote goes out, the PM fee stops looking like padding and starts looking like the cost of control.

If you want to see how that workflow is taking shape, join the early access list. No fake urgency. No sales maze. Just the product as it becomes useful.

The rule

Charge for project management when you are actually managing the project.

Do not hide it in labor. Do not bury it in hardware margin. Do not pretend it is free because the client might complain.

If the work protects scope, schedule, approvals, vendors, documentation, and handoff, it belongs in the quote. Call it project coordination if that sells better. Use 10% when the project is simple. Use 30% when the project is messy. Use fixed or hourly when the percentage would lie.

But stop giving away the work that keeps the project from eating itself.