MSP owner decision guide
How should an MSP price a new AI or security service in 2026?
Start with the buyer outcome and the fully loaded cost to deliver it, then set a floor that protects target gross margin. Do not price from vendor cost alone. Validate one package with one buyer segment before turning the price into a company-wide commitment.
Evidence reviewed July 27, 2026Evidence used for this decision frame
These sources establish market or operating context. They do not replace the company records named below.
Kaseya 2026 State of the MSP release
Reports that 48% of surveyed MSPs rank AI and automation as the top client need, while 13% report meaningful AI-service revenue. It also reports cybersecurity and BCDR revenue growth, supporting demand direction without establishing a price.
Open original sourceUse three gates before the commitment
Set the economic floor
Reconcile vendor cost, implementation labor, recurring service labor, sales engineering, exception load, support, compliance ownership, and target gross margin before naming a tier.
Package one measurable outcome
Define the buyer, risk or workflow being improved, included scope, exclusions, proof artifact, review cadence, and the event that triggers expansion or repricing.
Run a paid pilot before standardizing
Use a bounded customer cohort and retain delivery time, adoption, support load, gross margin, renewal intent, and expansion evidence before publishing a permanent price.
Evidence to collect before deciding
Market evidence sharpens the question. These company-controlled facts determine whether the move is supportable.
- Vendor and tooling cost per customer, user, endpoint, or workload
- Implementation, onboarding, and recurring delivery hours
- Sales-engineering and customer-success time
- Target gross margin and minimum contract value
- Buyer outcome, baseline, proof artifact, and review cadence
- Pilot adoption, exception load, support burden, and renewal evidence
Related questions
Should an MSP price AI services per user?
Only when users are a stable driver of cost and value. A workflow, tenant, endpoint, usage, project-plus-recurring, or outcome-linked model may fit better. The pricing unit should track the delivery obligation without making invoices unpredictable.
Should vendor cost determine the markup?
Vendor cost is one input, not the price. Delivery labor, risk ownership, onboarding, customer success, exception handling, proof, and target margin can be more important than the license itself.
When is the package ready to publish?
After a paid pilot shows that the intended buyer understands the outcome, delivery stays within the time and cost envelope, and the price supports the target margin without hidden exception work.
Apply the framework to one live MSP decision
See the public report example first, then request a free Three-Signal Preview for the business and decision you name.
Free introductory offer
Request the Three-Signal Preview
Send the MSP website and the live decision. We will reply within one business day with a public-data-only preview.