Skip to main content
DocsWalkthrough playbooksWalkthrough playbook: MSPs and vCISOs

Walkthrough playbook: MSPs and vCISOs

A walkthrough of CMDash for MSPs and vCISOs, run in the live sandbox in about 18 minutes. It is written for the CMDash sales team and for partners who present the product.

Who this is for

The owner or practice lead of an MSP, MSSP, vCISO practice or CMMC Registered Provider Organization. They sell security oversight to several clients and bill for the report. This is a margin conversation: they are working out what CMDash costs per client and what they can charge.

What they are tired of

  • "I run twelve clients and I bill for the report."
  • "Twelve tenants, twelve spreadsheets, and no way to compare them."

What it costs them: The deliverable is assembled by hand for each client, and the client that slipped this month is found late.

The line to open with: "Stop running every client from a separate spreadsheet." It is the headline of their page. Say it, then ask whether it is true for them before you show anything.

Before this call

  • The sandbox is one sample company and has no client organizations. For steps 1 and 2 use a demo practice you have prepared (a Command organization with three or more client organizations created at /vciso), or the roll-up screenshot on www.cmdash.com/for/msps.
  • Have www.cmdash.com/for/msps open in a second tab for the cost table and the margin calculator.

The walkthrough

1. Every client on one screen (4 min)

  • Go to: Security → vCISO (/vciso), in your demo practice
  • Show: The client list with each client's posture grade and score, open risks, the Proof column and template drift, with the averages above.
  • Say: "This is your Monday. Every client, its grade, its open risks, whether its signed proof is fresh, and whether it has drifted from your template. The one that slipped shows in its grade here, instead of hiding in tab nine."

2. Into a client and back (2 min)

  • Go to: Open a client from its row, then return
  • Show: The same Home page, for that client, and the way back to the practice.
  • Say: "One login. Each client is its own organization, so its data is separate, and it looks the same as every other client. Moving from client three to client nine does not mean relearning the screen."

3. The same program for each (3 min)

  • Go to: Security → Security program (/program), in the sandbox or a client
  • Show: Charter, objectives, committees and management reviews.
  • Say: "You run the program the same way for every client instead of rebuilding your method per engagement. A template sets the starting point for a new client, and the roll-up shows who has drifted from it."

4. The report you bill for (3 min)

  • Go to: Reports → Exports (/exports) and Reports → Report builder (/reports/builder)
  • Show: The Board Pack and where white-label branding is set (Settings → General & branding (/settings/branding)).
  • Say: "This is the deliverable. It is built from the client's live data, and on Command the CMDash footer comes off the client's exports, so the report goes out as yours."

5. What it costs you (4 min)

  • Go to: www.cmdash.com/for/msps, the partner plan and cost sections
  • Show: The cost-at-your-size table and the margin calculator; enter their client count and their price per client.
  • Say: "Here is the arithmetic, with your numbers. Command includes five client organizations, and the table shows the cost at several practice sizes. The per-client partner plan is in early access and is set up with you rather than at checkout." Read the figures off the page; do not quote them from memory.

6. Client proof under your name (2 min)

  • Go to: Compliance → Proof receipts (/proof)
  • Show: A signed receipt and its freshness.
  • Say: "When your client's customer or insurer asks for proof, the client sends a signed receipt. The Proof column on your roll-up tells you which client's proof has lapsed before their customer notices."

Questions you will get

"What does it cost per client?"

Open the table on www.cmdash.com/for/msps and read it with them. Do not quote a figure the page does not show, and do not offer terms or discounts that are not published.

"Can my client log in too?"

Yes. A client organization has its own members, and a technician's access can be limited to named clients.

"Can I host it for my clients myself?"

CMDash Cloud is the production service. A self-hosted install is offered on the Enterprise plan in early access, and an MSP that runs it for clients signs a partner agreement first. Route that to sales.

"Whose data is it if a client leaves?"

The client's. Partner terms are available on request; send the request through www.cmdash.com/contact rather than describing the terms yourself.

Command. The reasons, as they appear at the foot of the public page:

  • The vCISO practice: each client is its own managed organization under one login, with the cross-client roll-up.
  • Five managed client organizations are included, with more at the published per-client rates.
  • White-label exports: client reports go out without the CMDash footer.

A small client book may cost less on the per-client partner plan (early access, set up with CMDash).

Next step: Book the partner conversation through www.cmdash.com/partners/apply. Offer a 30-day trial on Command so they can create two or three real client organizations before that call.

This page is the product manual, published from the repository at docs/user/playbooks/msps.md. Customers read the same text inside CMDash under Help. Last updated November 15, 2026.

Walkthrough playbook: MSPs and vCISOs — CMDash Docs