The quarterly business review is the one meeting where managed IT stops being an invoice and becomes a relationship. Done badly it is a slideshow of ticket counts nobody asked for. Done well it is the meeting where the client decides the laptop refresh, approves the firewall replacement, and tells you about the office they are opening next spring.
Here is an agenda that fits in an hour, the data to bring, and what to leave out.
Start with what changed and what is at risk
Open with a one-page summary the owner could forward to a partner: what happened this quarter in plain terms, what is at risk, and what you are recommending. No charts yet. Three or four sentences per section is enough.
The risk register is the heart of the meeting. Keep a running list of things that could hurt the business, each with a plain description, a likelihood, an impact, and a proposed fix with a rough cost band. Review the list every quarter: what was closed, what is new, what has been sitting for two quarters without a decision. The items that keep getting deferred are the ones you should push on hardest.
- Single points of failure: one firewall, one internet line, one person who knows the ERP
- End-of-support dates coming within twelve months for hardware and software
- Backup gaps: systems not covered, restores not tested this quarter
- Security posture: MFA coverage, accounts without owners, unpatched devices
- Capacity: storage, licences, bandwidth approaching limits
Service performance, briefly
Show the numbers the agreement promised: response target attainment by severity, ticket volume trend, top ticket categories, and anything that missed. Keep it to one slide or one table. The owner does not care about the absolute count; they care whether things are getting better and whether their staff are being looked after.
The top ticket categories are the most useful part. If password resets are a third of the volume, propose self-service reset. If one application generates most of the pain, propose a conversation with the vendor or a replacement. Turn the ticket data into a decision, not a statistic.
- Response attainment by severity, with the misses explained in one line each
- Ticket volume this quarter versus last, and the trend line
- Top five categories and what you propose to reduce each one
- User satisfaction from ticket surveys, with any negative comments addressed
Assets, lifecycle and budget
Bring the inventory summary: devices by age band, warranty expiries in the next two quarters, servers and network devices approaching end of support. Then translate that into a rolling budget: what should be replaced this quarter, next quarter, and next year, with cost bands rather than quotes unless a decision is due now.
This is where the client sees you planning rather than reacting. A refresh they can see coming twelve months out is a line in their budget. The same refresh announced when the server dies is an emergency purchase at a bad price. Also review renewals: licences, domains, certificates, support contracts. A table with dates and owners prevents the expired certificate that takes the website down.
- Devices by age band, with the count past policy age
- Warranty and support expiries in the next two quarters
- Proposed refresh schedule with cost bands
- Renewals table: item, date, owner, decision needed
- Licence counts versus active users, to catch waste
Their plans, your roadmap, and the decisions
Ask about the business before you talk about the roadmap. New hires, new sites, new products, a merger, a move. Each of those is an IT project with a lead time, and hearing about it a quarter early is the difference between a smooth rollout and a rushed one. Write what they say into the notes.
Close with a short list of decisions you need from them and the dates by which you need them, and a list of what you committed to. Send the notes within a day. Next quarter, open by reviewing that list. If you want an outside view of how your reviews land with clients, RackLedge is happy to compare notes.
- Ask about business plans for the next two quarters
- Map each plan to an IT project with a lead time
- List decisions needed, with owner and date
- List your commitments, with dates
- Send notes within one business day and put the next review on the calendar
Frequently asked questions
Who should attend from the client side?
The person who approves spend and the person who feels the pain daily, usually the owner or a director plus the office manager or internal IT contact. Without the spend approver it is a status update, not a review.
How long should the review be?
Under an hour. If it runs longer, the material was not prepared well enough. Deep dives on a specific project get their own meeting.
What if the client keeps deferring decisions?
Record each deferral in the risk register with the date. When something breaks that was on the list, the record shows you raised it, and the conversation about priority becomes easier for both sides.
Takeaway
A good quarterly review is a summary, a risk register, one table of service numbers, a rolling asset budget, and a list of decisions. Ask about the business before you present the roadmap. Send the notes the next day and open the following review by checking what was promised.