MSP Annual Technology Planning: Stop Making the QBR Do Two Jobs

Most MSPs are trying to force two different conversations into one meeting.

Annual planning is where you decide the standards, the budget, the lifecycle work, and the roadmap for the next 12 months. A QBR is where you review what changed, what drifted, and what needs to be funded next.

When those two jobs share the same hour, the meeting gets sloppy. The annual plan becomes a status dump. The QBR becomes a budget debate. Nobody leaves with a clean decision.

If you have ever sat through a planning session that kept drifting back into last quarter's tickets, you already know the problem.

Why the combined meeting fails

The failure is not that MSPs care too much. It is that the meeting is trying to answer too many questions at once.

Annual planning asks:

• What standards are we setting for this client?
• What business goals matter this year?
• What risk are we willing to carry?
• What lifecycle replacements are due?
• What budget should exist before the work starts?

A QBR asks:

• What did we actually deliver?
• What changed since last quarter?
• Where did reality drift from the plan?
• What needs attention now?
• What should be funded next?

If you put both lists into the same meeting, the room spends half its time re-litigating context that should already be settled.

That is why QBR prep turns into a week of slide building. You are not just preparing a review. You are rebuilding the year.

What belongs in annual planning

Annual planning should feel like setting the operating rules for the year.

Keep it focused on decisions that do not need to be repeated every quarter.

1. Standards

What is the baseline for this client?

That might include device standards, security standards, backup expectations, account ownership, or support boundaries. If the standard changes, the year changes with it.

2. Budget

This is where you decide what gets funded and when.

Do not wait until the QBR to discover a major project, a license increase, or a lifecycle replacement. Put the budget in the annual plan so the later conversation is about timing, not surprise.

3. Lifecycle work

Old devices, old licenses, old assumptions. They all need a date.

Annual planning should surface what has to be replaced, upgraded, retired, or right-sized before it becomes an emergency.

4. Roadmap priorities

The roadmap is not a wish list. It is the sequence of funded work.

If the roadmap is not specific enough to survive a quarter, it is not a roadmap. It is a backlog with better branding.

For that reason, the roadmap should stay live. A static spreadsheet is only useful until the first surprise arrives. Client roadmaps work when they stay connected to actual decisions, not when they are rebuilt from memory every quarter.

What belongs in a QBR

A QBR should be about change, not reinvention.

It should answer a few simple questions:

• What did we finish?
• What moved?
• What slipped?
• What surprised us?
• What needs funding now?

1. Delivered work

Show the work that shipped, the risk that dropped, and the outcome that changed.

Not every ticket. Not every metric. The things the client will care about when they ask whether the partnership is working.

2. Drift from plan

This is the valuable part.

What changed since the annual plan was set? Did a merger happen? Did a key app break? Did headcount grow? Did compliance pressure show up? Did the budget get squeezed?

A good QBR makes drift visible early enough to act on it.

3. Open risks and exceptions

The quarterly review is where you surface the stuff that will hurt later if nobody names it now.

Patch gaps. Aging devices. License waste. Security exceptions. Unsupported systems. Anything that will become a more expensive problem if the client keeps ignoring it.

4. The next funded work

The point of the QBR is not to admire the last quarter.

It is to decide what gets funded next, who owns it, and when it starts.

If the meeting ends without a decision, it was just a report.

If you want a tighter structure for that review, start with the MSP QBR template. The template only works when the roadmap underneath it is already current.

A cadence that works for 5 to 50 person MSPs

You do not need a giant process. You need separate rhythms.

Annual planning

Run one deep planning session a year, plus a short midyear adjustment if the client changes fast.

Use that session to lock:

• Standards
• Budget ranges
• Lifecycle deadlines
• Major projects
• The first pass at next quarter's work

Quarterly review

Keep the QBR tighter.

The goal is to review drift, confirm priorities, and fund the next step. If the meeting starts turning into strategy theater, it is too big.

Monthly roadmap hygiene

This is the part most teams skip.

Update the roadmap monthly so the annual plan and the QBR are not based on stale guesses. If the plan stays live, the quarterly meeting gets shorter and much less annoying.

That is also where a client roadmap earns its keep. It is not just a pretty view. It is the memory of what was agreed, what slipped, and what is coming next.

How to turn planning into quotes without making it awkward

Planning breaks down when the follow-up work disappears into a vague promise.

The fix is simple: separate the conversation, not the relationship.

Use the annual plan to decide what should happen. Use the quote or scope of work to define what it costs. Use the QBR to confirm whether the work still matters.

That keeps the room from feeling like it got ambushed by sales halfway through a strategy meeting.

When the planning conversation turns into a real project, a scope of work template helps you capture deliverables, exclusions, assumptions, and acceptance criteria before the work starts. That is the line between a funded project and a support ticket with a budget problem.

What good looks like

A healthy MSP planning cadence is boring in the best way.

• The annual meeting ends with budget guardrails and clear priorities.
• The QBR ends with a decision, an owner, and a date.
• The roadmap reflects what is actually happening, not what someone remembers from last quarter.
• Quotes come from the live plan instead of being rebuilt from scratch.
• Nobody needs to spend all week making slides to explain work the client already approved.

That is the real job split.

Annual planning sets the year. QBRs keep the year honest.

If you keep those two jobs separate, the meeting gets shorter, the decisions get cleaner, and the client stops feeling like every quarter is the first time anyone has looked at their environment.

If you want the plan to stay live instead of living in a spreadsheet, join early access and test the workflow before the next QBR starts turning into prep theater.