Stop Waiting for QBRs to Find Your Next Upsell

Ric Hall, CRO

A dated incident report resting beside a blank wall calendar with no meetings marked

Most MSPs still wait for the quarterly business review to surface upsell and cross-sell opportunities, but the events that actually predict a client's readiness to buy more, a security incident, a coverage gap in what they already pay for, happen on their own schedule, not the calendar's. Catching those signals as they occur converts more reliably than waiting for the next scheduled meeting.

MSPs are already sitting on the evidence, they just aren't using it

Every MSP has a running record of exactly where a client's current service footprint has gaps, most just never turn it into a sales trigger. Kaseya's 2026 State of the MSP report found that 72 percent of MSPs offer security services and 79 percent offer backup and recovery, yet only 52 percent rank security and 41 percent rank backup among their top revenue sources. That gap between what is offered and what is actually monetized as a leading revenue line is whitespace sitting inside accounts an MSP already serves, not a prospecting problem.

The same report found that AI and automation services are offered by only 38 percent of MSPs in the first place, well behind core categories like security and backup. For MSPs that do offer AI-driven services, the cross-sell motion does not require a new logo. It requires surfacing to an existing client that a service they do not yet have is directly relevant to something that already happened to them.

Why does an incident make a better upsell trigger than a calendar date?

An incident makes a better trigger because it replaces an abstract pitch with a concrete, recent fact the client already cares about. The same Kaseya research found that 44 percent of MSPs report at least 10 percent of their clients experienced a cyberattack in 2025. Every one of those incidents is a specific, dated, client-side event that justifies a conversation about expanded coverage, and that conversation lands differently than a generic security upsell slide shown on a fixed quarterly schedule.

A calendar-based review cannot replicate that timing by design. It happens whenever the calendar says it happens, regardless of whether anything relevant occurred in the client's environment that quarter. An incident-triggered outreach happens exactly when the client's own risk tolerance is at its most receptive, which is also when the upsell is easiest to justify internally to whoever signs off on the client's budget.

How are most MSPs actually running their account reviews today?

Mostly on a fixed calendar, not on client-specific signals. ScalePad's 2026 MSP Trends Report, based on survey data from more than 1,100 MSPs, found that quarterly business reviews remain the dominant cadence, with 49 percent of MSPs running them quarterly, 23 percent monthly, 15 percent bi-annually, and 8 percent annually. The same research found that MSPs spend meaningful effort on these reviews, with 41 percent reporting 3 to 5 hours of preparation time per review.

That is a lot of structured effort pointed at a fixed date rather than at the moment an opportunity actually exists. The same ScalePad research found that 55 percent of MSPs track renewals as part of their customer success metrics, which is a start toward signal-based tracking, but renewal date is still a calendar event, not a client behavior or incident.

Which existing clients should get the first calls?

Account growth has already moved up the priority list for most MSPs, even without a formal trigger-based process behind it. ScalePad's 2026 MSP Trends Report found that growing existing client accounts rose from fourth to second place on the list of top growth drivers MSPs reported for the year, trailing only new service introductions. The appetite for expansion revenue is already there. What most MSPs lack is a reliable way to decide which existing client gets the call first.

Incident history is one filter. Category demand is another. GTIA's State of the Channel 2026 research found that 77 percent of North American IT service providers expect AI services and cybersecurity to be their leading revenue growth categories over the next two years. Cross-referencing that expected growth category against which specific clients already have a documented coverage gap in security or AI-driven services turns a broad market trend into a short, prioritized call list instead of a mass campaign sent to the entire client base at once.

What is actually holding most MSPs back from doing this?

The gap is not awareness, it is infrastructure. The same ScalePad research found that 60 percent of MSPs report having a formal Customer Success program, while another 33 percent say they do not have one but want to build one. That is a meaningful share of the market already recognizing the need for structured account growth practices without yet having built the system to run them.

Building that system from scratch client by client is exactly the kind of manual, bespoke work that never gets prioritized over paying tickets. An MSP without a formal program is not going to spontaneously start flagging incidents as sales signals in a spreadsheet. It needs the gap surfaced automatically, in a format a salesperson or account manager can act on without building a tracking process first.

How does a service-gap report change the conversation?

A written, client-specific gap report turns an abstract upsell pitch into a concrete finding the client can see for themselves. Instead of a generic slide about why backup coverage matters, the conversation starts from a dated assessment showing exactly which systems in that client's environment fall outside current coverage, which is a materially different sales motion than a scheduled check-in.

This is where a white-labeled diagnostic tool changes what is realistic for a smaller MSP to run consistently. A platform like ActiScore can generate that client-specific gap assessment on its own cadence tied to the client's actual environment, rather than requiring an account manager to notice the gap manually and build a one-off deck to present it. The MSP still owns the conversation and the relationship. The tool just makes sure the evidence exists before the meeting instead of being assembled the night before.

For an MSP without a dedicated sales engineer or account manager on every book of business, that distinction is the difference between an upsell motion that happens consistently and one that depends on whichever technician happened to notice the pattern. A white-labeled report under the MSP's own brand also reinforces the relationship the MSP is trying to protect, since the client sees it as their provider's own diligence rather than a vendor's marketing material.

What should an MSP change about its process this month?

Start by pulling the list of clients who had a documented security incident, even a minor one, in the last two quarters, and check whether that incident led to a scoped upsell conversation or just a resolved ticket. Most MSPs will find a meaningful number of incidents that closed without any follow-on sales conversation at all.

Hypothetical example: consider an MSP with 80 managed clients, where 9 experienced a minor security incident resolved without escalation in the past six months. If even half of those clients received a documented gap assessment and a scoped upsell conversation tied directly to what happened to them, that is a defined, timely pipeline the MSP would not have generated by waiting for the next quarterly review cycle.

Pair that incident-driven process with a broader audit of where your current clients' paid services stop and where your white-labeled catalog could pick up the next tier. Use the Actiforge stack builder to map your existing accounts against the full Actiforge product catalog and see where a documented, client-specific trigger already exists in your ticket history, waiting for a sales conversation instead of a calendar date. See the full stack to put real evidence behind your next account review.