NewActiValet is here. Introductory offer: 25% off your first 12 months when you sign up by December 31, 2026.See it →

Stop Itemizing AI. Start Packaging It Into Tiers

Ric Hall, CRO

Neat stacked storage crates beside a scattered pile of loose parts and cables

Pricing and packaging in 2026 isn't about finding the right hourly rate or seat price for AI tools. It's about structure, whether you sell AI capability as a line item a client can cut from an invoice, or build it into a tier they never see broken out. Get the structure wrong and a year of AI demand never turns into retained revenue.

Why is AI demand so far ahead of AI revenue?

Client appetite for AI is not the problem. According to Kaseya's 2026 State of the MSP Report, 48% of MSPs rank AI and automation as the top client need for 2026, ahead of security and backup. The same report finds that just 13% of MSPs are currently generating meaningful revenue from those services, according to Kaseya's 2026 State of the MSP Report.

That gap shows up on the supply side too. Informa's 2026 MSP 501 Survey Insights Report found that 91% of MSPs now offer or use AI solutions, up from 79% the year before. The share offering custom AI solutions rose to 36% from 21% over the same period, per the 2026 MSP 501 Survey Insights Report. Supply is rising faster than conversion. When almost every MSP has an AI story to tell but hardly any of them are billing meaningfully for it, the bottleneck isn't the technology or the demand curve. It's what happens between "we offer this" and "the client pays for this every month."

What's actually blocking the conversion: pricing model or packaging structure?

The pricing model usually isn't the issue. Per-user, per-device, tiered, bundled, and outcome-based pricing can all work, and MSPs run profitable books on each of them. What breaks conversion is packaging: whether the AI capability lives as its own line item the client can question, or as part of a tier they already trust and rarely renegotiate.

An itemized add-on invites a yes-or-no decision every renewal cycle. A named tier doesn't. If "AI-assisted ticket triage" shows up as its own line on next month's invoice, a client under budget pressure has an easy target to cut. If that same capability is simply part of what "Professional" or "Growth" tier clients get, there's nothing discrete to cut without downgrading the whole relationship, which most clients won't do over one feature. The distinction matters more for AI than for most services because AI capability improves and gets cheaper to deliver every quarter, which means an itemized AI SKU is a price you'll be renegotiating constantly. A tier absorbs that volatility instead of exposing it.

Hypothetically, say an MSP sells an AI ticket-triage feature as a standalone add-on, priced and invoiced as its own line, and only part of the client base opts in. Each of those clients now holds a distinct, attributable AI charge they can cancel at their next renewal without touching anything else on the account. Now say the same MSP instead folds that same feature into its existing mid-tier plan at no separate charge, and most clients already sit on that tier. None of those clients has a standalone AI charge to question, because there isn't one to point at. The first version produces a small amount of clean, attributable AI revenue on a spreadsheet. The second produces no line-itemized AI revenue at all, and a client base that can no longer treat AI as optional, because opting out means downgrading a tier they already rely on for everything else. The accounting looks worse for the bundled version. The retention exposure runs the other way.

How does tool sprawl work against your own packaging?

It's hard to sell your clients a clean bundle when your own stack behind it is a mess. Heimdal and FutureSafe's State of MSP Agent Fatigue report found that nearly nine in ten MSPs struggle with tool integration, and more than half experience alert fatigue every week. Only about one in five MSPs, per the same State of MSP Agent Fatigue report, have taken any real steps to consolidate their tool stack.

That sprawl bleeds into packaging whether you intend it to or not. Every disconnected tool in your stack tends to become its own line item on the client invoice, because it was purchased and provisioned separately, so it gets billed separately. White-labeled, pre-integrated tooling removes that structural pressure to itemize. When the tools your business runs on are already consolidated under one relationship, it's far easier to present clients with a small number of coherent tiers instead of a long list of individually priced capabilities.

Why does recurring packaging outperform project-based billing?

Because it compounds instead of resetting every time. ScalePad's 2026 MSP Trends Report found that 78% of MSPs reported increased recurring revenue this year, and the report states directly that offering clients more ongoing, monthly service packages outperforms more project-based models.

The same report shows where that recurring revenue is actually coming from. "Growing existing client accounts" climbed from the fourth most common 2026 growth driver to the second, cited by 49% of MSPs in 2026 versus 35% in 2025, according to ScalePad's 2026 MSP Trends Report. That's an account-expansion number, not a new-logo number. You don't expand an existing account by adding more itemized charges for the client to scrutinize. You expand it by moving them up a tier that already includes more of what they need, including the AI capability they said was their top priority for the year.

Building AI into tiers instead of itemizing it

A few changes tend to separate MSPs who are capturing AI revenue from MSPs who are still giving it away as a value-add.

  • Name the tier around the outcome, not the tool. "AI-Assisted Operations" or "Growth" reads as a capability level. "Copilot Add-On" reads as a vendor pass-through a client can price-shop.
  • Build the AI capability into the renewal conversation for every client, not just new logos. Expansion inside existing accounts is where the growth is actually coming from this year, not acquisition.
  • Keep the number of billable tiers small. A short, named set of tiers is easy to compare and upgrade between. A long list of itemized AI features is easy to negotiate down one at a time.
ApproachWhat the client experiences
Itemized AI add-onA new, separately approved charge they can decline or cut at renewal
Named AI-enabled tierA capability bundled into a level they already trust and rarely downgrade

How should the renewal conversation actually change?

It should stop being a conversation about whether to add AI and start being a conversation about which tier fits. Sales and account teams default to itemizing because it feels like the honest, transparent way to price something new. It's also the version most likely to get negotiated down or cut first, because it hands the client a single decision point instead of a tier comparison.

Train the renewal conversation around tier movement, not feature add-ons. Instead of "we'd like to add AI-assisted monitoring for an extra fee," the conversation becomes "the Growth tier now includes AI-assisted monitoring, and here's what moving up looks like." That reframes the decision from a yes-or-no on a new charge to a comparison between two tiers the client already understands. It also puts the expansion conversation in the hands of the account team managing the relationship, not a separate upsell motion bolted on afterward.

Packaging decisions compound with how you grow the account in the first place. If a chunk of your new business already comes through referral or technology partners, how those deals get structured at signing determines whether the AI capability starts inside a tier or gets bolted on as an afterthought SKU. Actiforge's AI University for MSPs covers how to build that referral and partner economics layer so AI capability is part of the package from the first conversation, not something negotiated in after the contract is signed.

Where to start this quarter

You don't need to rebuild your entire rate card to fix this. Start with the accounts where AI is currently billed as a standalone line, and model what happens to retention and ARPU if that same capability moves inside an existing tier instead. Actiforge's Stack Builder walks through that modeling, letting you test how a white-labeled AI tool fits into a tier structure before you change a single client contract. From there, Actiforge's full product lineup shows what else could fold into the same tier instead of staying its own billed-separately SKU.

The providers converting AI demand into revenue this year aren't the ones with the cleverest pricing formula. They're the ones who stopped selling AI as an extra and started selling it as part of what their business already is.

See the full stack