Skip to main content

Technology Strategy Meeting (TSM) Process

How to run Technology Strategy Meetings with your clients, how often to meet each one, and what happens before, during and after.

A Technology Strategy Meeting (TSM) is a recurring meeting with each client about their business and their technology: what they're trying to achieve, how healthy their IT is, and what you recommend next. Many MSPs call it a Quarterly Business Review (QBR), a Technology Business Review (TBR) or a Strategic Business Review (SBR). Running TSMs like clockwork is one of the habits of MSPs with best-in-class EBITDA (earnings before interest, taxes, depreciation and amortization).
​

This guide covers the process. The Report Cycle covers the steps in Strategy Overview.
​

How often to meet each client

How often you meet a client comes down to two things: their monthly recurring revenue (MRR) and how good a fit they are for your MSP. Meet your larger, best-fit clients more often, for example quarterly, and your smaller or weaker-fit clients less often, for example once a year.
​

Plan each client's meetings for the year in the Schedule, where Per Year holds the number of meetings and the target months show when they're due. Set Up Your Schedule covers it.
​

Clients who rarely meet with you should still get their Report. Sending every client their Report as a PDF, including the ones who don't book a meeting, means each one at least sees the health of their IT.
​

Who takes part

A TSM works best with the people who make decisions on both sides:

  • Preparing: the vCIO, with a project engineer, senior engineer or architect for the technical review.

  • Your side of the table: the vCIO, plus an account manager or a principal for larger clients, and an engineer when technical topics are on the agenda.

  • The client's side: the people who make decisions about the business and its budget, such as the owner or CEO, the CFO, the office manager or primary contact, and an IT lead if they have one.

Keep the conversation strategic when executives are in the room. Delivering Great TSMs covers knowing who you're talking to.
​

Before the meeting

Book about 90 minutes for the meeting, and keep each vCIO to one TSM a day so there's time to prepare and follow up. Then get the Report ready:

  1. Create the client's new Report, carrying over the data from their last one.

  2. Ask your technical team what they've seen with the client since the last meeting: recurring tickets, problems and anything that worries them.

  3. Update the Assessment, grading what has changed against your Health Standards.

  4. Review the client's Goals, Technology and Initiatives, and add or update the Initiatives you'll recommend, with timing and a budget.

  5. Write the executive summary: what changed, what matters most, and what you'll ask the client to decide.

During the meeting

Walk the client through the Report with Present. A typical agenda:

  1. Introductions, and why you hold these meetings.

  2. The client's goals: for this quarter, this year and the longer term.

  3. The health of their IT: the Health Score and the findings that matter most.

  4. The Roadmap and Budget: the Initiatives you recommend and when. In the first quarter, ask what major plans they have for the year. In the last quarter, ask about any year-end purchases they want to make for tax reasons.

  5. Feedback from your technical team.

  6. How your MSP is doing, and what you could do better.

  7. Announcements, and whether they know other businesses you could help.

  8. If you're on site, a look at the network room.

After the meeting

Follow up while the meeting is fresh:

  1. Update the Report with what you agreed: Goals, Initiatives and their timing.

  2. Send the client the Report as a PDF.

  3. Turn the work the client approved into projects or tickets in your PSA.

  4. Complete the Report.

Finishing and Presenting the Report covers the after-meeting steps in Strategy Overview.
​

Did this answer your question?