Run a Technology Business Review Around the Client Plan

Tell the Client What You Want to Decide

Try this invitation: "We'd like to review your business plans and the technology work they may require. Please bring the person who sets the budget and anyone responsible for the changes we'll discuss." Name the proposed outcome so the client can decide who should attend.

Ask what planning dates matter to the client. A budget submission or intended office change can determine when a decision is needed. Schedule from those actual dates rather than picking a convenient meeting slot and hoping the work will fit afterward.

Keep the annual planning session distinct from the rest of account management. Paul Green favors an annual technology review for many smaller clients, while TruMethods illustrates quarterly formal reviews with monthly contact and adjustments for complexity. Those are conditional operating recommendations, not proof that one cadence fits every client.

The MSP model allows three vCIO hours per client per month as a workload cross-check, including five hours a quarter for QBR work. That is total planned work, not a promised meeting length or extra hours to add again. Fit the annual planning focus into the account's agreed review work rather than deleting contact to make room.

Check Delivery Before You Walk Into the Meeting

Have the technical owner check the environment and give you the findings that matter to the proposed plan. The model separates the TAM's standards work from the vCIO's business and budget conversation. Use that handoff so the recommendation has evidence behind it.

Ask delivery whether an unresolved service issue needs attention before the planned discussion. Erick Simpson describes making that check before client reviews and, where appropriate, addressing the issue or rescheduling. That is his operating practice, and it's a useful preparation question.

If a service issue needs its own follow-up, say: "This deserves an answer from delivery. Let's agree who will handle it and when, then decide whether today's planning discussion should continue." Don't talk past a problem the client came expecting you to resolve.

Ask About the Business Before Filling the Roadmap

Need a question that produces useful planning detail? Ask: "What has to be possible for your team when this change happens?" Write down the required outcome and the date or dependency the client gives you.

Say a hypothetical client is considering another location. Establish what work people would do there and what is still undecided. The technology recommendation should follow that information rather than start with a standard equipment bundle.

You can ask: "Who will make this decision, and what do they need to compare?" Then record the answer beside the candidate work. A conversation with someone who cannot approve the budget still needs a route to the person who can.

I don't buy generic sales advice that turns every review into a tour of what the client hasn't bought. An MSP must cost and deliver the resulting promise. Start with the business requirement so you can recommend work your team can actually support.

Paul Green distinguishes a service-gap sales conversation from a business-goals review and roadmap. He warns against treating the client only as a selling opportunity. Keep that distinction visible when you decide which recommendations belong in this meeting.

Turn the Discussion Into a Working Budget

I'd keep the plan in a table the client can amend. Use their planning horizon, including later years where they have enough information to discuss them. Mark a later idea as provisional instead of pretending it is an approved project.

Include relevant technology spending beyond your own bill. Stuart Holtby recalls a client wanting to discuss its wider spending when he was presenting only his MSP charges. His example includes business software and other services, which is a useful prompt to ask what your view currently omits.

Have the technical and commercial owners check an estimate before presenting it as dependable planning input. Erick Simpson recommends stating that forecast prices are current at the time of discussion and keeping clients informed when planned costs change. A future budget line is not a fixed future quote.

Handle the Objection Without Forcing a Commitment

If the client says, "We can't commit to all of this," try: "You don't need to approve every future item today. Let's separate the decision that is ready from the ideas that still need work." Keep the unapproved items visible with their assumptions.

If they say, "This looks like a sales pitch," answer: "Which recommendation doesn't connect to your plan? We can remove it or establish the missing reason before asking you to fund it." Be willing to change the plan when the connection is missing.

Don't manufacture urgency for a later project. Explain an actual dependency and its consequence where you can support them. If timing remains uncertain, assign the investigation and agree when the client needs an updated view.

Confirm What Was Decided Before You Finish

Close with: "This is what you approved, this is still provisional, and these are the next actions we each own. Have I recorded that correctly?" Give the client room to correct the record before it becomes the basis for a quote or schedule.

Send the agreed plan and transfer authorized work through normal scoping and approval. A planning discussion doesn't itself authorize a technical change. Keep the decision record linked to the work so delivery can see what the client actually agreed.

Book the next planning review around the client's calendar and keep the ongoing account actions assigned between meetings. Before that review, check what changed in the assumptions and what the completed work achieved. Bring those results back into the conversation rather than opening the same presentation again.