Get through your first SOC 2 without guessing what the auditor wants.
Senior, hands-on help scoping your audit, closing control gaps, and getting your evidence in order, so your team can keep shipping while the report gets done.
Free 30-minute call. You leave with a scope recommendation whether or not we work together.
A customer asked for your SOC 2 report, and you don't have one yet.
Usually it shows up in a security questionnaire or a stalled enterprise deal. You need a credible plan and a date to give the customer, and you need it without hiring a full-time compliance team.
Startups selling to enterprises
First SOC 2, small team, cloud-native stack. You need the shortest credible path to a Type I and then a Type II.
Teams with a compliance platform
You bought Vanta, Drata or Secureframe, and the dashboard is still mostly red. You need someone to decide what the controls should actually be and get them working.
Companies facing their next audit
Last year's report came back with exceptions, or your environment changed. You want a cleaner observation period this time.
Five stages, in this order.
Timelines vary with your starting point. These ranges are typical for a small SaaS company starting a first audit.
Scope
1–2 weeksPick the system, the Trust Services Criteria, and the report type your customers will accept.
Gap assessment
2–3 weeksMap what you do today against the criteria and list every gap with an owner.
Remediation
1–4 monthsWrite the policies, configure the controls, and start producing evidence.
Type I audit
Point in timeA CPA firm tests whether your controls are designed properly as of one date.
Type II window
3–12 monthsThe auditor tests whether controls operated over a period. This is the report most buyers want.
Fixed-scope engagements, delivered by the person you talk to.
Readiness assessment
Scope, gap analysis against the 2017 Trust Services Criteria, and a prioritized remediation plan you can hand to engineering.
Details →Program build-out
Policies, control design, identity and access, logging, vendor management and evidence collection, built to fit how your team works.
Details →Audit support
Auditor selection, system description, evidence requests and walkthroughs, and responses to any exceptions.
Details →Learn the basics before you spend money.
Plain-language explanations of how SOC 2 works, written for founders and engineering leads.
What is SOC 2?
Who issues the report, what it covers, what it costs your team in time, and what your customers actually check.
Read the guide →Type I vs. Type II
The difference, how observation windows work, and when starting with a Type I makes sense.
Read the guide →The Trust Services Criteria
All five categories and the nine common-criteria series (CC1–CC9), with what each one means in practice.
Read the guide →Find out where you stand in 30 minutes.
Bring your stack, your customer's request and your deadline. You'll get a recommended scope, report type and a realistic timeline.