Skip to main content
DocsWalkthrough playbooksWalkthrough playbook: Technology and SaaS

Walkthrough playbook: Technology and SaaS

A walkthrough of CMDash for technology and SaaS companies, run in the live sandbox in about 17 minutes. It is written for the CMDash sales team and for partners who present the product.

Who this is for

A head of security, a CTO or an engineering lead at a software company. Enterprise buyers send a security review before signing. They have or want SOC 2, ISO 27001 follows, and AI governance questions have started.

What they are tired of

  • "Every enterprise deal stops at the security questionnaire."
  • "We did SOC 2, and now a customer wants ISO 27001 and I am starting again."

What it costs them: Deals that wait while an engineer fills in the same answers again.

The line to open with: "Get the security review out of the way of the deal." It is the headline of their page. Say it, then ask whether it is true for them before you show anything.

The walkthrough

1. Start on Home (2 min)

  • Go to: Overview → Home (/home)
  • Show: The grade and frameworks in scope.
  • Say: "One page for where you stand. Then SOC 2, then how the next framework reuses it, then what the buyer sees."

2. SOC 2 from your stack (4 min)

  • Go to: Compliance → Frameworks (/compliance), open SOC 2; then Integrations → Connections (/integrations)
  • Show: Control status, then the cloud, identity, code and ticketing connections.
  • Say: "SOC 2 control by control, with evidence from your cloud, identity, code and ticketing tools on a schedule. The auditor asks how you know; the answer is attached."

3. The next framework (3 min)

  • Go to: Compliance → Control mappings (/control-mappings)
  • Show: The mapping from SOC 2 to ISO 27001.
  • Say: "When the customer asks for ISO 27001, you are not starting again. On Command the status you recorded for SOC 2 carries to the ISO 27001 controls it maps to."

4. What the buyer reads (4 min)

  • Go to: Settings → Trust center (/settings/trust-center), then Compliance → Document room (/document-room)
  • Show: The Trust Center settings, the posture badge switch and the document room.
  • Say: "This is the page you send instead of filling in a spreadsheet: your security posture, with a live badge if you turn it on, and documents behind an NDA. The buyer reads it before deciding what to ask."

5. AI governance (2 min)

  • Go to: Compliance → AI governance (/ai-governance)
  • Show: ISO 42001 and the NIST AI RMF as controls.
  • Say: "When the questionnaire asks how you govern AI, these are two more frameworks on the same evidence. It governs the AI systems you register; it does not discover them or test a model." If the page is locked in the sandbox, describe it and move on.

6. The auditor (2 min)

  • Go to: Settings → External assessors (/settings/assessors)
  • Show: A scoped, expiring grant.
  • Say: "Your auditor gets a read-only login for the frameworks in scope, with an end date."

Questions you will get

"We are a ten-person startup."

Then start lower. Starter tracks SOC 2 with a posture grade and SSO. Command is the recommendation once a second framework or the Trust Center matters.

"Does it answer questionnaires for us?"

Do not promise that. Describe the Trust Center and the document room, which reduce how many questionnaires arrive.

"Do you have an API?"

Read-only API access is on Starter and up. API writes, webhooks and SCIM are on Enterprise.

"Do you have a SOC 2 report yourselves?"

Send them to www.cmdash.com/trust, which states CMDash's own status. Read it with them.

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

  • The framework crosswalk engine: collect evidence for SOC 2 once and the status carries to the ISO 27001 controls that overlap.
  • The full Trust Center: a public page with a posture badge that a prospect can read before sending a questionnaire.
  • Unlimited frameworks, so GDPR, FedRAMP or ISO 42001 can join without a change of plan.

Enterprise adds SCIM provisioning, API writes and webhooks.

Next step: Offer the 30-day trial on Command and suggest connecting the cloud account and identity provider first. Ask which deal is waiting on a security review.

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

Walkthrough playbook: Technology and SaaS — CMDash Docs