What our engagements actually look like.
Public case studies are coming as our founding cohort engagements complete and clients sign off on attribution. In the meantime, the patterns below are anonymized previews of how our typical engagements actually run.
Each pattern describes a real engagement shape: industry, company stage, framework stack, engagement structure, and the specific work we did. Names and identifying details are stripped because the clients prefer it that way during active engagement; full case studies follow with attribution where the client opts in.
Four patterns from across our work.
One per major industry vertical we serve. Real engagements; client-identifying details removed.
Series A B2B SaaS
- Size
- 60 employees
- Framework
- SOC 2 Type I + Type II
- Engagement
- Sprint converted to Embedded retainer
Series A SaaS company with Vanta running and a folder of policy templates. Auditor surfaced 11 findings two weeks before fieldwork. First $400,000 enterprise deal gated on the SOC 2 attestation and a buyer security questionnaire. We ran the 2-week Sprint: traced the auditor findings to actual production controls, surfaced a missing MFA configuration on three SaaS admin accounts, ran a focused pentest on the auth flow that caught two real bugs, and shipped policy rewrites that match how their engineering team actually deploys. Enterprise deal closed three weeks later. Sprint converted to an Embedded retainer for Type II maintenance.
Healthtech
- Size
- 45 employees
- Framework
- HIPAA + HITRUST e1
- Engagement
- Sprint plus 6-month Embedded retainer
Digital health company processing PHI on AWS, with HIPAA covered. Hospital system buyer started asking for HITRUST certification with a 90-day timeline. Auditor draft surfaced 11 findings. We ran the gap analysis with their engineering team in week one and shipped policy fixes in week two: BAA library cleanup, MFA enforcement on three forgotten admin accounts, PHI data-flow diagrams from their real architecture. Auditor cut findings from 11 to 2 between draft and final. Sprint converted to Embedded retainer to lead them through HITRUST e1 certification over the following six months.
Fintech (Series B)
- Size
- 120 employees
- Framework
- PCI DSS 4.0 + SOC 2 Type II
- Engagement
- Embedded retainer, sponsor bank diligence
Series B fintech building an embedded payments product on AWS. Sponsor bank deal required SOC 2 Type II plus PCI DSS scoping in 90 days. Drafts of policy package from a previous consultancy. Customer security questionnaire backlog had been untouched for six weeks. We mapped the cardholder data flow first, designed them into SAQ-D scope (instead of the full ROC their QSA had been quoting, which would have doubled audit cost), and surfaced three IAM misconfigurations that would have failed PCI requirement 7. Security questionnaire turnaround dropped from 3 weeks to 2 days. Bank deal closed on schedule. SOC 2 Type II ran in parallel through the next six months.
Defense sub-prime
- Size
- 50 employees
- Framework
- CMMC Level 2 + NIST SP 800-171
- Engagement
- Readiness review plus 9-month Embedded retainer
50-person defense sub-prime building software for a tier-1 prime. Received a CMMC Level 2 flowdown clause with a 9-month deadline. Outdated SSP from a prior contract, tabletop exercise no one had run in two years. We started with a 4-week readiness review: gap analysis against the 110 NIST SP 800-171 controls, scoping decision (most of corporate IT was out of CUI scope; engineering environment was in), and an SSP rewrite reflecting their actual AWS GovCloud setup. We drafted the POA&M, prioritized the 14 partial-implementation items, and ran a mock C3PAO audit. They passed the prime's pre-assessment six months later. Engagement continued as a retainer through the actual C3PAO assessment.
Most security firms publish a logo wall on day one and call it social proof. We are not doing that.
The clients above are mid-engagement or recently completed. Some have not finished the case study review process yet. Some prefer permanent anonymity because their security posture is competitive intelligence. Some agreed to attributed case studies and we are working through the editorial cycle.
Our founding cohort agreement asks for case study rights with a written approval gate before publication. That means clients see and approve the exact copy before anything goes live, including whether their company name appears at all. The patterns above describe the shape of our work without putting any client in a position they did not consent to.
Attributed case studies will appear here as engagements complete and clients approve. If you want a reference call from an existing client, ask on the discovery call. We can usually arrange one.
Not ready to talk? Score your SOC 2 readiness.
Twenty questions, a scored PDF in your inbox, a realistic timeline to audit. Free.
Want to see what your engagement would look like?
Three doors. Take the 4-minute SOC 2 Readiness Scorecard, apply for a founding retainer slot, or book a discovery call to scope a Sprint or retainer.