Illustrative example only.

“ExampleCo” is a fictional 60-person B2B software company. It is not a RALLY GRC client, and every detail below is invented to show the format. Real engagements are confidential.

The situation

ExampleCo is close to signing its largest customer. The customer’s security team has asked for a SOC 2 report before contract signature and wants an answer within 90 days. ExampleCo has capable engineers and a few good practices, but no formal program, no named owner and no evidence anyone could hand to an auditor.

1. Current-state assessment

The assessment rates each domain against what the customer will ask for, and ranks the gaps by buyer risk rather than by how many controls they touch.

DomainCurrent stateBuyer riskFirst move
Governance and ownershipPartial Roles are informal and no policies are approvedHighName an executive owner; approve the core policy set
Access controlGap Shared admin accounts; no periodic access reviewHighEnforce MFA, remove shared accounts, schedule quarterly reviews
Change managementPartial Code review happens but is not documentedMediumDocument the existing workflow and tie approvals to tickets
Vendor riskGap No inventory of vendors that touch customer dataMediumInventory and tier vendors; review the critical few first
Incident responsePartial On-call rotation exists; no written planMediumWrite the plan and run a tabletop exercise
Data protectionIn place Encryption at rest and backups are configuredLowDocument the configuration and retain evidence
Evidence collectionGap Screenshots gathered on requestHighAssign evidence owners and a recurring cadence

2. Prioritized 90-day roadmap

Every item has an owner by role, so nothing depends on someone remembering it.

  1. Days 1–30 — Foundation. Name the executive owner and confirm scope (CEO and CTO). Approve the core policies (executive owner). Enforce MFA and remove shared accounts (IT lead). Inventory the systems and vendors in scope (engineering lead).
  2. Days 31–60 — Operate. Run the first access review (IT lead). Document change management in the existing ticketing tool (engineering lead). Review the critical vendors (executive owner). Run an incident response tabletop (CTO).
  3. Days 61–90 — Prove. Start recurring evidence collection (named evidence owners). Run an internal readiness check before the audit. Select the auditor and set the start of the observation window (executive owner).

3. Buyer-ready trust narrative

A short, honest statement the sales team can use in the next customer conversation, instead of improvising.

Sample statement

“ExampleCo has completed an independent readiness assessment against the SOC 2 security criteria. Core controls such as encryption, backups and code review are already operating. We have a funded 90-day plan to close the remaining gaps, with a named executive owner and an auditor engagement planned. We are happy to share the plan and progress updates under NDA.”

4. Executive readout and decisions

The sprint ends with a working session where leadership makes the decisions the roadmap depends on:

YOUR TURN

Bring the trigger.

Tell us what prompted the request and when you need an answer. We’ll confirm whether the Readiness Sprint is the right starting point.

Schedule a strategy call →