“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.
| Domain | Current state | Buyer risk | First move |
|---|---|---|---|
| Governance and ownership | Partial Roles are informal and no policies are approved | High | Name an executive owner; approve the core policy set |
| Access control | Gap Shared admin accounts; no periodic access review | High | Enforce MFA, remove shared accounts, schedule quarterly reviews |
| Change management | Partial Code review happens but is not documented | Medium | Document the existing workflow and tie approvals to tickets |
| Vendor risk | Gap No inventory of vendors that touch customer data | Medium | Inventory and tier vendors; review the critical few first |
| Incident response | Partial On-call rotation exists; no written plan | Medium | Write the plan and run a tabletop exercise |
| Data protection | In place Encryption at rest and backups are configured | Low | Document the configuration and retain evidence |
| Evidence collection | Gap Screenshots gathered on request | High | Assign 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.
- 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).
- 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).
- 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.
“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:
- Who owns the program, and with what authority
- Which systems and data are in scope
- Whether to pursue a point-in-time report first or go straight to an observation period, given the customer’s date
- Whether a compliance platform is needed—decided after the roadmap, not before it
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 →