trio.so
MSP

Compliance as a Service: How MSPs Launch and Price a CaaS Offer

How MSPs launch and price a compliance as a service offer: frameworks clients face, packaging, pricing models, evidence and what not to promise.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on

Compliance as a service (CaaS) is a recurring service where an MSP runs the controls, monitoring and evidence a client needs for a framework such as HIPAA or CMMC. The client stays responsible for compliance itself. You sell the work and the proof of the work, not a certificate.

This guide is for MSP owners and MSSP leads deciding whether to launch a CaaS offer. It covers which frameworks clients bring, how to package the service, how to price it with a worked 20 client example, and what you should never promise in a contract.

What compliance as a service is and why clients pay for it

Small and mid size clients get pulled into frameworks by someone else: a healthcare partner asks for a business associate agreement, a defense prime asks about CMMC, an insurer sends a controls questionnaire, an enterprise customer sends a security review. The client has no one who can answer. They already pay you to run their devices, so you are the obvious person to ask.

That is the commercial case. Much of that work is already running in a managed client: patching, encryption, access control and backups are the technical controls every framework asks about. CaaS packages that work with a framework mapping, a gap list and a regular evidence report, and charges for it every month.

The offer works when it replaces a pile of one off requests with one steady service. It fails when it becomes unpaid questionnaire help bolted onto the existing contract.

Frameworks MSP clients face

Start with one framework, master it, then add the next. N-able's guide to launching CaaS gives the same advice: pick the framework that matches the industries you already serve (N-able, "How MSPs can successfully launch and deliver compliance as a service", read 12 Nov 2026). Here are five frameworks you are likely to meet:

FrameworkWho it hitsWhat the client asks the MSP for
HIPAA (US health privacy law)Healthcare providers and their business associates in the US. An MSP that can reach patient data is often a business associate itself.A signed business associate agreement, device encryption, access controls, risk assessment records
CMMC (Cybersecurity Maturity Model Certification)Defense contractors that handle controlled unclassified information. Level 2 follows NIST SP 800-171.Control mapping, a gap list, evidence for a self assessment or an assessor. Check the current phase dates on the DoD CIO CMMC page before you quote a client.
SOC 2 (a security report from an independent auditor)SaaS and service companies whose customers ask for a reportEvidence that controls run over time: patching, access reviews, device inventory
Cyber insuranceAny client renewing a policyAnswers and proof for the underwriter's controls questionnaire
NIS2 (the EU network and information security directive)Entities in the EU in covered sectors. IT service management for other businesses is itself a covered sector, so an MSP serving EU clients may be in scope as well as its clients, depending on its size.Risk management measures, incident handling records, supply chain security

Each of these deserves its own post. Check dates and scope in the primary source before you put them in a proposal. CMMC phase dates and NIS2 national rules are still changing.

Packaging: assessment, remediation, evidence, monitoring

Define the scope before you set a price. ScalePad's guidance is the same: scope, client profile, tooling and staffing drive the price, so write those down first (ScalePad, "Four pricing strategies MSPs should consider for compliance as a service", 26 Mar 2024). Four parts cover most offers:

  • Assessment. A one time gap review against one framework. It produces a gap list ranked by risk and a plan.
  • Remediation. The fixes: policies, device settings, access changes, patching. Quote it as a project, or fold the technical part into the managed service you already run.
  • Evidence. A recurring report per client that shows each control working. This is the product the client keeps paying for.
  • Monitoring and review. A scheduled check that nothing has drifted, plus a quarterly review with the client's owner.

Keep extras such as awareness training, incident response planning and penetration testing as separate priced options. Clients often want them after the first assessment, and bundling them hides the cost.

Pricing a CaaS offer

ScalePad lists four pricing models: fixed fee, hourly, monthly retainer and value based (ScalePad, 26 Mar 2024). A common setup for CaaS is a one time assessment fee plus a monthly retainer in tiers. The retainer is the recurring revenue. The assessment fee is paid once and covers setup.

We found no published market price range for CaaS, so we give none. Price from your own cost instead, with this floor price formula:

Minimum monthly revenue = monthly cost of the service divided by (1 minus your target margin).

At a 40 percent target margin the divisor is 0.6, so a cost of $10,500 a month needs $17,500 a month in revenue.

Worked example: 20 clients

The numbers below are invented to show the arithmetic. Replace every input with your own.

TierClientsPrice per client per monthRevenue per month
Essentials: one framework, quarterly evidence report10$400$4,000
Standard: one framework, monthly evidence report, quarterly review7$800$5,600
Advanced: two frameworks, monthly report, monthly review3$1,500$4,500
Total20$14,100
Monthly costAmount
One compliance analyst, fully loaded$7,500
Tooling and evidence collection$1,200
Outside specialist review$1,000
Insurance and overhead share$800
Total$10,500

Revenue of $14,100 less cost of $10,500 leaves $3,600, a margin of 25.5 percent. For a 40 percent margin the floor formula says you need $17,500. The revenue shortfall is $3,400 a month, or $170 per client. You can close it by raising prices (the average has to go from $705 to $875 per client, which is $14,100 and $17,500 divided by 20), by cutting analyst hours with automation, or by moving clients from Essentials to Standard. Do the math before you publish a price list, not after the first quarter.

Add the one time assessment on top. At $2,500 per new client, ten onboarded clients bring $25,000 up front. That covers setup work and is not part of the monthly margin above.

The evidence problem and how to automate it

Evidence is where CaaS margin disappears. An analyst who collects screenshots and exports by hand for 20 clients spends the month on collection and has no time for advice. Auditors and insurers ask for proof that a control ran over time, so a one off screenshot is weak.

The technical part of that evidence comes straight from the endpoint tool you already run: which devices exist, which are encrypted, which are patched, which policies apply. trio.so is a multi tenant console for MSPs: one console for all your client fleets. For the technical side of a framework, it covers the controls a device management tool can enforce, such as encryption, patching and policies, in frameworks like SOC 2, ISO 27001 and NIST. It helps you work toward those frameworks and exports compliance evidence per client, including a patch audit trail, which supports external audits. It does not certify anyone, and the administrative controls (policies, training, vendor reviews) sit outside any device tool. See MDM for MSPs for how the multi tenant console works. Plans start at $5 per device.

What not to promise

Certification and compliance belong to the client and the auditor. Your contract and your sales language should say so.

  • Never write that you "make the client compliant" or "guarantee compliance". You deliver defined work and evidence. The client's regulator or assessor decides the result.
  • Name what is out of scope: legal advice, the client's own staff behavior, systems you do not manage.
  • Do not promise a passed audit or a pass date. Promise the deliverables and the dates you will hand them over.
  • Put the client's duties in writing: they supply policies, approvals and access on time.
  • Have a lawyer review the liability clause.

Apply the same rule to yourself. Assess your own MSP against the framework first, as the N-able guide suggests, and you will find the gaps before a client does.

Where to start in 30 days

  1. Week 1: pick one framework from the clients you already have. Count how many are affected.
  2. Week 2: build the scope and three tiers on one page. Write what each tier excludes.
  3. Week 3: run the assessment on your own MSP. Use it as the pilot and the sales story.
  4. Week 4: offer the assessment to three existing clients, with the retainer as the next step. Check your numbers against the floor price before you quote anyone else.

For the groundwork this builds on, read what an MSP is, the MSP software stack, managed IT services and the MSP security stack.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently asked questions

Compliance as a service is a recurring MSP offer that runs the controls, monitoring and evidence a client needs for a framework such as HIPAA, SOC 2 or CMMC. The client remains responsible for compliance. You supply the work and the proof.

Charge enough to cover your cost at your target margin. Minimum monthly revenue is monthly cost divided by one minus the target margin. We found no published market range, so price from your own inputs and test them with the worked example above.

Offer the one most of your current clients already face. HIPAA suits healthcare clients, CMMC suits defense suppliers, and SOC 2 suits SaaS firms. Start with one, then add the next.

You do not need a certificate, but you should run the framework on your own business first. It tests your process, gives you a pilot and often shows the MSP is in scope itself, for example as a HIPAA business associate.

It depends on the contract. Write the deliverables, the scope limits and the client's duties down, avoid promising an audit result, and have a lawyer review the liability clause.

They ask for proof that controls ran over a period: device inventory, patch status, encryption status, access reviews, policy documents and incident records. Collect it on a schedule, per client, so it exists before the audit is announced.

Related

From the blog

The related industry news, interviews, technologies, and resources.