when an MSSP wants to build a service on your product

When an MSSP wants to build a service on your product, it is not asking to resell a licence. It wants to turn your product into one input of its own service, run for dozens of customers from one team, sold per seat per month, often under its own brand. That works when your licensing, your console and your price fit how the provider runs its business. When they don’t, the provider signs, runs a pilot with two customers, and quietly standardises on someone else.

a reseller and an MSSP buy different things

a reseller

sells your licence

• Buys per deal, usually annual or multi-year
• Your product is a line on the customer's invoice
• Earns margin on the licence plus project services
• Registers individual deals
• Grows when it wins new customers for you

an MSSP

sells an outcome built on your product

• Buys monthly, across all its customers
• Your product is a cost line inside its service fee
• Earns margin per seat on the whole service
• Rarely registers individual customer deals
• Grows when it rolls the service out to its base

The MSSP’s buyer is its owner, service manager or SOC lead. The questions they ask are about margin per seat, technician time saved, and whether they can sell a service built on you at a price their customers accept. Feature comparisons come later, if at all.

why this matters now

Managed services are where much of the security channel is heading. Canalys estimated managed services at about USD 610 billion by the end of 2025, with channel partners generating about 98% of that revenue, in research for an MSP software vendor’s 2025 report. In the survey behind that report, 451 partners, 90% expected their cybersecurity sales to grow, security services filled the top four expected revenue sources, and managed detection and response was the most planned new service. Canalys separately lists MDR and cyber-insurance compliance among the drivers of managed services growth.

Europe adds a regulatory push. NIS2 pushes security requirements down the supply chain, so IT and managed service providers of entities in scope get security clauses in their own contracts. That makes them buyers and channel partners at once.

ENISA’s 2025 analysis of the managed security services market adds two caveats worth knowing. Most buyers in its sample spend less than 10% of their security budget on managed services, so the market is still early. And ENISA flags a possible gap between what small firms need and what the market offers. For a vendor, that gap is the opportunity: a product that makes a managed service affordable for a 50-person company.

what the provider needs from your product

An MSSP runs many small customers from one operations team. That turns a few technical features into commercial requirements.

• Multi-tenancy. One console across all customers, with each customer’s data and configuration separated.
• Role-based access per tenant. The provider’s analysts see what they need for each customer, and the customer’s own admin sees only their tenant.
• APIs. Provisioning, alert handling and reporting have to be automated, or the provider’s cost per customer never falls.
• Integration with its operating tools. The remote monitoring and management (RMM) and professional services automation (PSA) tools it uses to run tickets, billing and endpoints.
• White-labelling, where the service is sold under the provider’s brand. Reports and portals that carry the provider’s name.

A product without multi-tenancy can still be sold through an MSSP, one customer at a time. It just won’t become a service.

pricing that fits a monthly business

The provider bills its customers monthly, and its customer count changes every month. So it needs four things from your price.

Monthly billing. Annual prepaid licences lock it into capacity it may lose when a customer leaves.

No minimum per tenant. Many of its customers are small. A per-tenant minimum can cost more than the service is worth for a 20-seat customer.

A unit that matches its own. If the provider charges its customers per user and you charge per gigabyte, it carries the mismatch as risk.

A commitment across its whole base. The common structure is an aggregate monthly commitment across all its customers, in exchange for volume tiers. It gives you a revenue floor and the provider flexibility per customer.

Structure	Typical for	Watch out for
Per device per month	Endpoint, patching, backup of servers and workstations	How an “active device” is counted: monthly peak or daily average
Per user per month	Identity, email security, awareness training	Shared mailboxes, service accounts, departed users
Per tenant	A platform fee per managed customer	Prices out the provider’s smallest customers
Per gigabyte or consumption	Backup, logging, security data	The provider carries usage it does not control
Committed monthly spend with tiers	Any of the above, across the whole base	A provider that overcommits in a good quarter

Monthly flexibility costs you something, because it removes the certainty of annual terms. Vendors usually price it in one of two ways: a higher unit price for month-to-month than for annual commitment, or monthly terms available only above a minimum aggregate volume. Public data on the right premium is thin. A reasonable rule is to price it at roughly the cost of the extra churn and collection risk you take on.

where distributors come in

Many small MSPs and MSSPs buy through a distributor’s cloud platform instead of directly. The distributor puts many vendors on one monthly invoice, extends credit and handles currency and tax. It can also aggregate commitments across many small providers and carry the commitment itself, so a small provider buys without a minimum and you still get a floor.

That makes the distributor’s platform part of your price architecture. Your MSP price list, minimums and billing frequency have to be expressible in its system, and its margin has to fit between your MSP price and what providers will pay.

the provider’s sales motion is your demand

An MSSP grows your revenue when it signs new end customers or adds your service to existing ones. That changes what demand generation means here.

1. 1first tenantShort cycle. The provider runs the service for one or two customers to learn it.
2. 2service packagedThe provider prices its own offer, per seat, with your product inside.
3. 3rolled out to its baseGrowth comes here. Your job is to help the provider sell the service: content, sales training, campaigns under its brand.
4. riska platform bundleThe main churn risk: the provider standardises on a bundle that covers your category at a lower cost.

Count the right things: new providers activated, seats or tenants added per provider per month, time from signing to the first end customer, and net revenue retention per provider. Deal registrations and MQLs fit this channel poorly, because providers rarely register individual end-customer deals.

raising prices on a provider

A provider that sells a managed service at a fixed monthly price per seat often cannot pass a mid-contract price increase on to its own small customers. Your increase comes straight out of its margin. Give longer notice than you would to direct customers, so providers can reprice their own contracts at renewal. Otherwise the price increase becomes the reason they look at the platform bundle.

the question for your product and channel teams

If your best MSSP rolled your product out to all its customers next quarter, how much of its margin per seat would be left after your price?