Your 2027 Compliance Quote Should Start With Scope, Not Seats

Share Article:

Table of Contents:

Two 30-person companies ask your MSP for a 2027 compliance quote. Before you open the pricing sheet, ask each prospect to show you the last piece of evidence a customer requested and walk you through how they produced it. The difference between their answers may tell you more about the engagement than their employee counts ever will.

Same headcount, different work

Consider two hypothetical prospects. The first, a design agency, stores client briefs and contact information in one cloud tenant. Its largest customer asks for an annual security questionnaire. The agency’s operations director shows you last year’s answers, the supporting records, and the policies she approved. She wants someone to keep those records current and flag gaps before renewal. You can quote a limited onboarding review, a quarterly check-in, and support for one annual questionnaire.

The second, a software company, hosts customer data in a production environment separate from its corporate systems. Two enterprise customers have signed security addenda with different reporting requirements. One asks for quarterly evidence of access reviews. To produce the last review, an engineer exported cloud permissions, HR checked the roster, and a hosting partner supplied a list of privileged accounts. Nobody can find the record of who approved the exceptions. The founder wants your MSP to coordinate the next review and explain unresolved exceptions to leadership each month.

Both clients may need 30 training licenses. Quote those by the seat if that is how you buy them. But don’t charge the agency year-round for the software company’s coordination work, or promise the software company that work for the price of an annual questionnaire.

A discovery checklist for the quoting call

If a prospect asks for “NIST alignment,” ask what the buyer expects to receive. NIST’s guide to CSF 2.0 Organizational Profiles distinguishes current and target cybersecurity outcomes and ties them to the organization’s objectives, stakeholders, and requirements. Preparing a current-state profile is one deliverable; implementing the changes needed to reach a target is another.

  • Obligations and deadlines: Which framework and version, contract clause, or customer request are we supporting? Ask to see the relevant language, the due date, and an example of an accepted submission. If two requirements overlap, identify what evidence you can reuse and what needs separate treatment.

  • Data and systems: What data is covered, where does it go, and who administers those systems? Name the entities, sites, tenants, and production environments in scope. Write down exclusions so the client can correct them before signing.

  • Evidence and cleanup: Pick one recurring control and trace the evidence from source to sign-off. What can your team retrieve directly? What requires an interview, a manual export, or a vendor request? Distinguish a missing record from a control that never operated; don’t quote a plan to recreate proof that doesn’t exist.

  • Third parties: Which providers hold sensitive data or operate critical services? That distinction is central to CIS Control 15 on service provider management. Name the vendors the MSP will review, the evidence it will request, and who at the client can escalate a stalled request.

  • Frequency and ownership: How often will the client need evidence reviews, leadership meetings, or questionnaire responses? Who supplies records, approves policies, decides whether to accept risk, and signs external representations? Put a name or role and a due date against each client dependency.

If the prospect cannot answer the questions that drive the fee, quote a bounded discovery engagement first. Give it a useful output: an agreed scope, a list of missing inputs, and a proposal for the work you can now estimate.

Put three kinds of work on the proposal

Onboarding pays for establishing the starting point. For the agency, that might mean validating the existing evidence folder, updating its index, and agreeing on a review calendar. For the software company, it might include reconciling the two addenda, mapping each evidence source to an owner, and documenting missing approvals. Define “done” as a client-reviewed baseline and prioritized backlog, not a promise that every finding will be fixed before the first monthly invoice.

Recurring program management pays for a defined schedule of work. Estimate staff time by role for one cycle, multiply by the number of cycles, then add the agreed advisory time and any seat-based costs. Use your own delivery history: who prepares the evidence, who reviews it, and how long did comparable work actually take? Check the busiest month as well as the annual total. Four reviews spaced across the year are a different staffing commitment from four submissions due the same Friday.

Separately scoped remediation pays for changing what the review found. Suppose the software company’s review reveals that its hosting partner cannot produce individual administrator records because staff share an account. Documenting the gap, assigning an owner, and tracking it can sit in the recurring service. Designing named access, coordinating the cutover, and testing the change are implementation work. Check the existing managed-services agreement first: if that work is already covered, route it there rather than charging twice. Otherwise, obtain approval for a separate project.

Give the client a clear reason to reopen the quote

“Compliance support included” leaves both sides guessing when a new request lands. A short scope statement gives the client something concrete to buy. For the hypothetical software company, it could read:

The recurring fee covers one corporate tenant and one production environment, one quarterly access-evidence review, and one monthly leadership call. We collect available records, document exceptions, and track agreed actions. Your operations lead supplies the personnel roster and obtains the hosting partner’s records by the agreed cutoff; your designated executive approves exceptions. If inputs are late, we flag the gap and agree on a revised delivery date. Control implementation and independent assessment fees are excluded unless separately approved.

Agree on the triggers for a scope review: a second production environment, a new customer addendum that requires monthly rather than quarterly evidence, or a request for the MSP to take over vendor coordination. A trigger starts a conversation, not an automatic surcharge. Explain what changed, identify any work the current fee already covers, and obtain written approval for the revised deliverables, timing, and price before starting the additional work.

At your next renewal, put last year’s proposal beside the work your team actually delivered. If the client still has 30 people but now asks your advisor to reconcile three systems and brief the board, the number that stayed the same is the least useful one on the page.

Schedule a Demo of Blacksmith!

Check Out Our Compliance Podcast on Spotify!