SOC 2 Cost and Timeline Benchmarks by Company Size
Typical SOC 2 costs and timelines for startups, mid-sized companies and enterprises, by report type. Compare planning, readiness, observation, fieldwork and reporting, plus related costs in USD.

Typical SOC 2 costs and timelines for startups, mid-sized companies and enterprises, by report type. Compare planning, readiness, observation, fieldwork and reporting, plus related costs in USD.

For a startup actively working towards its first report, the typical planning figures here are $6,500 and 10 weeks for a Type 1, or $9,000 and 22 weeks for a Type 2 using the short observation-period assumption explained below. Mid-sized and enterprise engagements generally involve more systems, stakeholders and coordination.
This guide compares company sizes and report types. For what each budget category covers, use the all-in SOC 2 cost guide; for choosing report coverage against a customer deadline, use observation periods and deadlines. These guides answer different questions and should be read together.
All figures are indicative market estimates in US dollars, not Throughline quotes, guaranteed delivery dates or a formal statistical survey. Confirm scope, inclusions and timing with the firm you engage. For Throughline's own fixed annual fees, see Throughline SOC 2 pricing.
These benchmarks draw on Throughline founder Paul Wenham's first-hand client experience as founder of AssuranceLab, a peer-reviewed CPA firm that served more than 1,200 clients. Paul worked directly with many clients; that firm-wide portfolio is not a claim that he personally audited every company.
Paul cross-checks the estimates through compliance-platform partnership networks, including Vanta and Drata, and peer relationships with other CPA firms. Related costs are also informed by published 2026 platform, penetration-testing and consulting pricing. The source does not supply firm-by-firm verification, a sample size or a linked pricing dataset, so the figures should be treated as practitioner estimates rather than independently verified market statistics.
Outliers are excluded. An experienced startup prioritising a live enterprise deal can sometimes move exceptionally quickly; other companies pause for months or years. Neither is a useful planning baseline. The figures reflect companies actively working through the process.
Source dated 3 November 2026. Revised content reviewed on 10 November 2026.
For the work behind these numbers, read SOC 2 for startups: the journey, timeline and cost, stage by stage. It explains each step, AI-assisted preparation, founders-only controls and keeping a first report on track.
For existing controls, multiple products, regulatory drivers and switching providers, read SOC 2 for mid-sized companies.
For governance, procurement, ISO 27001 reuse, multi-entity scope and customer deadlines, read SOC 2 for enterprises. Each guide links back to these benchmarks and to the other company stages.
These are working comparison bands, not SOC 2 thresholds. Scope and complexity matter more than headcount alone. A small company with several products and sensitive data may need a more involved audit than a larger company with one straightforward service.
| Segment | Typical profile |
|---|---|
| Startup | Up to 100 staff; one product; cloud-hosted; small engineering team |
| Mid-sized | About 101–1,000 staff; several teams or products; a dedicated security or IT owner |
| Enterprise | 1,001+ staff; multiple systems, locations or business units; a formal GRC function |
Costs cover the external engagement as a whole, including a separately priced readiness assessment where applicable. They do not allocate fees by step. Internal staff time is excluded; platforms, penetration tests, consultants and tool upgrades appear separately.
Time is measured in elapsed weeks. The typical median is a practitioner planning estimate, not a calculated sample median. Each step has its own elapsed time; end-to-end totals are separately estimated and may differ from adding the steps because work overlaps. Do not add individual low, median or high columns and assume they represent one company's schedule.
The source uses 12 weeks as an approximate three-month comparison period, and 24 weeks for six months at the enterprise high end. Calendar months are not exactly four weeks: agree actual start and end dates with your auditor. Stable row IDs retain the source's identifiers.
| Step | What it covers | Applies to |
|---|---|---|
| Planning | Scoping, choosing criteria and systems, selecting the auditor, setting up the engagement | Type 1 and Type 2 |
| Readiness | Gap assessment, remediation and preparing evidence | Type 1 and Type 2 |
| Observation period | The period controls must operate before Type 2 testing, typically 3–12 months | Type 2 only |
| Audit fieldwork | Testing control design (Type 1) or operation across the period (Type 2) | Type 1 and Type 2 |
| Reporting | Draft report, management responses, review and issuance | Type 1 and Type 2 |
The table shows external engagement costs and end-to-end elapsed time. Type 1 tests design and implementation at a point in time; Type 2 also tests operation over an agreed period. Type 2 totals here use a short first-period assumption, not Throughline's recommended default.
A $9,000, 22-week startup Type 2 benchmark is not a promise of a six- or twelve-month report in 22 weeks. Choose coverage first, then adjust the plan. Our Type 1 versus Type 2 guide explains when an early Type 1 can help while a longer Type 2 period runs.
| ID | Size | Report | Cost low (USD) | Cost median (USD) | Cost high (USD) | Time low (weeks) | Time median (weeks) | Time high (weeks) | Notes |
|---|---|---|---|---|---|---|---|---|---|
| total-t1-startup | Startup | Type 1 | $3,000 | $6,500 | $10,000 | 5 | 10 | 18 | Readiness is often included in the audit fee |
| total-t2-startup | Startup | Type 2 | $5,000 | $9,000 | $15,000 | 18 | 22 | 38 | Assumes a 3-month first observation period |
| total-t1-mid | Mid-sized | Type 1 | $5,000 | $11,000 | $20,000 | 5 | 13 | 24 | More systems and control owners than a startup |
| total-t2-mid | Mid-sized | Type 2 | $7,500 | $13,500 | $25,000 | 18 | 24 | 40 | Assumes a 3-month first observation period |
| total-t1-ent | Enterprise | Type 1 | $11,000 | $18,000 | $35,000 | 9 | 18 | 52 | Procurement, legal review and many control owners extend planning and readiness |
| total-t2-ent | Enterprise | Type 2 | $12,000 | $22,000 | $50,000 | 23 | 32 | 78 | Assumes a 3-month observation period at the median, up to 6 months at the high end |
Planning covers systems and Trust Services Criteria, report type, auditor selection, any platform choice, terms and deadlines. It is mostly decisions, so it moves as quickly as the company can settle them.
Startups often move quickly when a deal is waiting. Mid-sized companies and enterprises add procurement, legal review and stakeholders. The typical case assumes a clear reason to begin and no long pauses between decisions.
Scope should reflect your services and commitments. See the Trust Services Criteria explained and how to check an auditor's credentials.
Readiness includes assessing gaps, addressing them and preparing evidence for access, changes, vendors, policies and other relevant controls. Existing controls, another framework such as ISO 27001, team capacity and the number of owners all affect the time.
Startups have simpler environments but less spare capacity. Enterprises may have mature controls but more systems and people to coordinate. This is where stalls occur most often; the estimates assume a team actively working through gaps.
Throughline includes readiness free with every audit. The auditor assesses and gives feedback; management owns control decisions and implementation. Our readiness guide explains that distinction.
A SOC 2 Type 2 tests controls over an observation period, typically 3 to 12 months. We recommend 6 to 12 months. A 3-month period can suit a specific timing requirement when that is the maximum coverage available and the buyer accepts it. Readiness work and audit testing affect the report date, so the observation period is not the whole timeline.
For like-for-like comparison, the Type 2 tables use a three-month first period across sizes, with six months allowed at the enterprise high end. This normalises the comparison; it is not a recommendation to choose three months or evidence that buyers will accept it. Enterprises often want longer coverage, and ongoing annual reports usually cover 12 months.
The period is an agreed coverage choice, but its evidence requirements still matter. Confirm which controls operated and what the buyer needs before committing. Read how to time your Type 2 report for deadlines and buffers.
The auditor tests control design for Type 1 and operating effectiveness across the covered period for Type 2. Evidence availability, owner responsiveness, systems and sample sizes affect elapsed time.
Many firms quote one to two weeks of fieldwork, but it can stretch to a month or more when evidence or answers are delayed. Type 2 work often happens near period end; final procedures must support coverage of the complete period. A prepared team with available owners tends to finish closer to the agreed plan.
Reporting covers the draft, management review, responses to exceptions, the auditor's review and issuance. Exceptions and additional evidence can add review cycles. Once audit work is complete, many firms issue within one to two weeks, but the range grows with multiple reviewers or unresolved matters.
Keep time for management review and the customer's own review. See what makes a SOC 2 report quality for how findings and explanations affect usefulness.
Type 1 has no observation period. These are step-level elapsed weeks, not figures to add into a guaranteed delivery date.
| ID | Size | Step | Low (weeks) | Typical median (weeks) | High (weeks) | Notes |
|---|---|---|---|---|---|---|
| t1-startup-planning | Startup | Planning | 1 | 2 | 3 | |
| t1-startup-readiness | Startup | Readiness | 2 | 4 | 8 | |
| t1-startup-fieldwork | Startup | Audit fieldwork | 1 | 2 | 4 | |
| t1-startup-reporting | Startup | Reporting | 1 | 2 | 3 | |
| t1-mid-planning | Mid-sized | Planning | 1 | 2 | 5 | |
| t1-mid-readiness | Mid-sized | Readiness | 2 | 6 | 10 | |
| t1-mid-fieldwork | Mid-sized | Audit fieldwork | 1 | 3 | 6 | |
| t1-mid-reporting | Mid-sized | Reporting | 1 | 2 | 3 | |
| t1-ent-planning | Enterprise | Planning | 3 | 4 | 14 | |
| t1-ent-readiness | Enterprise | Readiness | 3 | 8 | 24 | |
| t1-ent-fieldwork | Enterprise | Audit fieldwork | 2 | 4 | 8 | |
| t1-ent-reporting | Enterprise | Reporting | 1 | 2 | 6 |
The observation rows retain the source's approximate 12-week comparison assumption. Longer agreed coverage changes the schedule; enterprise high-end observation is 24 weeks in this dataset.
| ID | Size | Step | Low (weeks) | Typical median (weeks) | High (weeks) | Notes |
|---|---|---|---|---|---|---|
| t2-startup-planning | Startup | Planning | 1 | 2 | 6 | |
| t2-startup-readiness | Startup | Readiness | 2 | 4 | 14 | |
| t2-startup-observation | Startup | Observation period | 12 | 12 | 12 | 3 months used for consistency; common for startups that skip the Type 1 |
| t2-startup-fieldwork | Startup | Audit fieldwork | 2 | 2 | 5 | |
| t2-startup-reporting | Startup | Reporting | 1 | 2 | 3 | |
| t2-mid-planning | Mid-sized | Planning | 1 | 2 | 7 | |
| t2-mid-readiness | Mid-sized | Readiness | 2 | 5 | 15 | |
| t2-mid-observation | Mid-sized | Observation period | 12 | 12 | 12 | 3 months used for consistency |
| t2-mid-fieldwork | Mid-sized | Audit fieldwork | 2 | 3 | 5 | |
| t2-mid-reporting | Mid-sized | Reporting | 1 | 2 | 3 | |
| t2-ent-planning | Enterprise | Planning | 3 | 4 | 14 | |
| t2-ent-readiness | Enterprise | Readiness | 5 | 10 | 24 | |
| t2-ent-observation | Enterprise | Observation period | 12 | 12 | 24 | 3-month median used for consistency; enterprises more often choose 6 months or more |
| t2-ent-fieldwork | Enterprise | Audit fieldwork | 2 | 4 | 10 | |
| t2-ent-reporting | Enterprise | Reporting | 1 | 2 | 6 |
These are first-year hours your team spends on planning, readiness, fieldwork and reporting. The observation period is excluded because operating controls during it is part of normal business. Totals are the sum of the four steps.
Startup effort ranges from 28 to 474 hours, mid-sized effort from 45 to 598 hours, and enterprise effort from 150 to 2,460 hours. Readiness accounts for the largest spread because starting controls, compliance knowledge and coordination vary.
Hours grow faster than elapsed weeks as companies scale. Larger teams devote more of their time to compliance, while startup owners fit it around other roles. These are experience-based planning ranges, not guaranteed workloads.
| ID | Size | Step | Hours low | Hours high | Notes |
|---|---|---|---|---|---|
| hrs-startup-planning | Startup | Planning | 2 | 10 | |
| hrs-startup-readiness | Startup | Readiness | 15 | 400 | Depends heavily on starting point and compliance knowledge |
| hrs-startup-fieldwork | Startup | Audit fieldwork | 10 | 60 | |
| hrs-startup-reporting | Startup | Reporting | 1 | 4 | |
| hrs-startup-total | Startup | Total | 28 | 474 | Hours spread thin across people wearing several hats |
| hrs-mid-planning | Mid-sized | Planning | 4 | 12 | |
| hrs-mid-readiness | Mid-sized | Readiness | 25 | 500 | Much existing work can be mapped rather than built |
| hrs-mid-fieldwork | Mid-sized | Audit fieldwork | 15 | 80 | |
| hrs-mid-reporting | Mid-sized | Reporting | 1 | 6 | |
| hrs-mid-total | Mid-sized | Total | 45 | 598 | |
| hrs-ent-planning | Enterprise | Planning | 8 | 40 | Procurement and approvals add hours |
| hrs-ent-readiness | Enterprise | Readiness | 80 | 2,000 | Work split across many parties, so less efficient |
| hrs-ent-fieldwork | Enterprise | Audit fieldwork | 60 | 400 | |
| hrs-ent-reporting | Enterprise | Reporting | 2 | 20 | |
| hrs-ent-total | Enterprise | Total | 150 | 2,460 | More hours, but a larger share of people's time is dedicated to compliance |
An independent audit fee is the unavoidable external cost of obtaining the report. A platform, external consultant or outsourced internal audit is not mandated by SOC 2. Operating suitable controls still needs time and may require spending based on risks and commitments.
Penetration testing is commonly expected by auditors and enterprise buyers, although SOC 2 does not prescribe it in every case. Assess methodology and scope; price alone does not distinguish a genuine human-led test from a scan.
Security is included in every SOC 2 audit. Additional criteria and SOC 3 reports can change the fee. Throughline includes Availability and Confidentiality by default; add-on estimates describe other market arrangements, not Throughline charges.
Read the all-in cost guide, whether you need a compliance platform and enterprise security reviews for these choices.
These are separate market estimates, not a bundle to buy or a total to add automatically. Annual platform and incremental tool costs are labelled; testing, consulting and report add-ons depend on scope and engagement.
| ID | Size | Cost item | Low (USD) | Typical median (USD) | High (USD) | Notes |
|---|---|---|---|---|---|---|
| rc-startup-platform | Startup | Compliance platform (annual) | $6,000 | $10,000 | $15,000 | Priced by headcount and number of frameworks |
| rc-startup-pentest | Startup | Penetration test | $3,000 | $5,000 | $8,000 | Human-led test of one web app and API; below this is usually an automated scan |
| rc-startup-consultant | Startup | Compliance consultant | $10,000 | $20,000 | $40,000 | Optional; often in place of an in-house compliance lead |
| rc-startup-internal-audit | Startup | Internal audit (outsourced) | $2,000 | $4,000 | $8,000 | Not required for SOC 2; a self-assessment can be done in-house |
| rc-startup-tools | Startup | Tool licensing upgrades | $1,000 | $3,000 | $10,000 | Incremental annual cost, such as enforced code review, identity and HR tools |
| rc-startup-security | Startup | Security criteria | $0 | $0 | $0 | Included in every SOC 2 and covered by the base audit fee |
| rc-startup-availability | Startup | Availability criteria | $0 | $500 | $1,000 | Included free by some firms, including Throughline |
| rc-startup-confidentiality | Startup | Confidentiality criteria | $0 | $500 | $1,000 | Included free by some firms, including Throughline |
| rc-startup-processing-integrity | Startup | Processing Integrity criteria | $1,000 | $2,000 | $4,000 | Almost always an add-on |
| rc-startup-privacy | Startup | Privacy criteria | $2,000 | $4,000 | $8,000 | Almost always an add-on; adds significant scope |
| rc-startup-soc3 | Startup | SOC 3 report | $2,000 | $3,000 | $6,000 | Public summary report, issued alongside the SOC 2 |
These are separate market estimates, not a bundle to buy or a total to add automatically. Annual platform and incremental tool costs are labelled; testing, consulting and report add-ons depend on scope and engagement.
| ID | Size | Cost item | Low (USD) | Typical median (USD) | High (USD) | Notes |
|---|---|---|---|---|---|---|
| rc-mid-platform | Mid-sized | Compliance platform (annual) | $15,000 | $30,000 | $50,000 | Rises with headcount and added frameworks |
| rc-mid-pentest | Mid-sized | Penetration test | $8,000 | $15,000 | $30,000 | Several apps, APIs and cloud infrastructure |
| rc-mid-consultant | Mid-sized | Compliance consultant | $25,000 | $45,000 | $80,000 | More systems and teams to implement across |
| rc-mid-internal-audit | Mid-sized | Internal audit (outsourced) | $5,000 | $10,000 | $20,000 | Not required for SOC 2 |
| rc-mid-tools | Mid-sized | Tool licensing upgrades | $5,000 | $15,000 | $40,000 | Scales with headcount |
| rc-mid-security | Mid-sized | Security criteria | $0 | $0 | $0 | Included in every SOC 2 and covered by the base audit fee |
| rc-mid-availability | Mid-sized | Availability criteria | $0 | $750 | $1,500 | Included free by some firms, including Throughline |
| rc-mid-confidentiality | Mid-sized | Confidentiality criteria | $0 | $750 | $1,500 | Included free by some firms, including Throughline |
| rc-mid-processing-integrity | Mid-sized | Processing Integrity criteria | $2,000 | $3,500 | $7,000 | Almost always an add-on |
| rc-mid-privacy | Mid-sized | Privacy criteria | $3,000 | $6,000 | $12,000 | Almost always an add-on; adds significant scope |
| rc-mid-soc3 | Mid-sized | SOC 3 report | $2,000 | $3,500 | $8,000 | Public summary report, issued alongside the SOC 2 |
These are separate market estimates, not a bundle to buy or a total to add automatically. Annual platform and incremental tool costs are labelled; testing, consulting and report add-ons depend on scope and engagement.
| ID | Size | Cost item | Low (USD) | Typical median (USD) | High (USD) | Notes |
|---|---|---|---|---|---|---|
| rc-ent-platform | Enterprise | Compliance platform (annual) | $40,000 | $60,000 | $100,000 | Often multi-framework enterprise plans |
| rc-ent-pentest | Enterprise | Penetration test | $20,000 | $40,000 | $80,000 | Several applications and networks; red team exercises cost more |
| rc-ent-consultant | Enterprise | Compliance consultant | $50,000 | $90,000 | $150,000 | Complex scopes start around $50,000 |
| rc-ent-internal-audit | Enterprise | Internal audit (outsourced) | $10,000 | $20,000 | $40,000 | Often covered by an in-house internal audit function |
| rc-ent-tools | Enterprise | Tool licensing upgrades | $10,000 | $30,000 | $100,000 | Incremental only; enterprises usually license the core tools already |
| rc-ent-security | Enterprise | Security criteria | $0 | $0 | $0 | Included in every SOC 2 and covered by the base audit fee |
| rc-ent-availability | Enterprise | Availability criteria | $0 | $1,000 | $2,000 | Included free by some firms, including Throughline |
| rc-ent-confidentiality | Enterprise | Confidentiality criteria | $0 | $1,000 | $2,000 | Included free by some firms, including Throughline |
| rc-ent-processing-integrity | Enterprise | Processing Integrity criteria | $3,000 | $6,000 | $12,000 | Almost always an add-on |
| rc-ent-privacy | Enterprise | Privacy criteria | $5,000 | $10,000 | $20,000 | Almost always an add-on; adds significant scope |
| rc-ent-soc3 | Enterprise | SOC 3 report | $3,000 | $5,000 | $10,000 | Public summary report, issued alongside the SOC 2 |
Audit fees usually stay the same. Firms often invest more effort in year one expecting renewal, and fees do not necessarily fall when their own workload does. The source estimates that the client's overall effort falls by about 40 to 50%.
Planning often becomes confirmation of the prior plan. Readiness becomes a tidy-up and stock-take of controls. Expect additional readiness work if products, system components, criteria or other scope change. These reductions are practitioner estimates, not promised fee discounts or effort savings.
| Item | Year two compared with year one |
|---|---|
| Audit fee | Usually unchanged |
| Audit firm effort | About 20–30% less |
| Client effort, overall | About 40–50% less |
| Planning | Close to zero; often confirming last year's plan |
| Readiness | Close to zero; a tidy-up and stock-take of controls |
| Audit fieldwork | About 30% less |
| Reporting | About 30% less |
Start with the report your customer needs, the covered service and the deadline. Choose the observation period, assess readiness, identify owners, and ask for a proposal that states inclusions and assumptions. Budget for tools and services that actually help your team, rather than purchasing every line.
Our SOC 2 services explain Throughline's calibrated approach, included readiness and Type 1 included at no extra cost with a Type 2 engagement. Benchmark fees remain market estimates, not our engagement prices.
Related reading: Type 1 versus Type 2, readiness assessments, observation periods and deadlines, all-in SOC 2 costs and SOC 2 for AI-native companies.

Former PwC manager, founder of AssuranceLab and former Sensiba partner and Chief Innovation Officer. Now founder of Throughline, focused on compliance and assurance for AI-native companies.
Beyond credentials, frameworks and pricing, ask who will do the work, how offshore teams operate, when auditors are available, whether controls fit your business and what happens when plans change.
Paul Wenham explains the proposed 2027 SOC 2 criteria, AI points of focus, governance and change management updates, transition effort and Throughline's approach to fees.
How certification bodies set ISO 42001 audit days under ISO/IEC 42006, how AI roles and in-scope headcount drive the price, and when scoping to engineering and product makes sense.
SOC 2 for startups, from planning to reporting: typical USD audit fees, timelines, internal team hours, AI-assisted readiness and keeping a first report on track.
SOC 2 for mid-sized companies: typical USD costs, timelines and team hours, plus existing controls, multiple products, regulatory drivers and auditor changes.
SOC 2 for enterprises: typical USD costs, timelines and team hours, plus ISO 27001 reuse, multi-entity scope, vendors, procurement and customer deadlines.
Three worked SOC 2 examples: AI-written code, agent-led access reviews and agents changing customer data. Follow each risk through its control, audit test and evidence.
Build an AI management system around your real use cases: an agent register, risk and impact assessments, shared responsibilities, governance policy and Statement of Applicability.
ISO 42001 isn't yet an enterprise requirement. What it covers, how it compares with SOC 2 and AIUC-1, and when it's worth it for an AI company.
How to cover production AI agents in SOC 2: governance, access, change management and monitoring, with indicative criteria mappings, customer responsibilities and practical audit expectations.
Australian companies need a SOC 2 report issued under the AICPA standards by a US-licensed CPA firm, delivered by a strong local team in Australian time zones. Here's how the provider options compare, and what to check.
Experienced CTOs don't choose a SOC 2 audit firm on price or speed. They look for tech stack expertise, a tailored approach, flexible scheduling, responsiveness and year-round partnership, because those factors decide how much time the audit really costs.
What Security, Availability, Confidentiality, Processing Integrity and Privacy each cover, how often they're included, and how to decide which belong in your SOC 2 report.
Which SOC 2 report should come first? Six client cases, practical decision tables and an illustrative 18-month cost comparison explain when to start with Type 1 and when to go straight to Type 2.
How long a SOC 2 Type 2 observation period should be, how to work backwards from a customer deadline, when auditors test, why reports run late and how much buffer to build in.
A category-by-category SOC 2 budget in USD, covering audit fees, readiness, platforms, penetration testing, consultants, internal assessments and operational costs. Learn what is required, what is optional, and what a quote can leave out.
Five signals of real quality in assurance and security, with practical guidance on building a compliance program that supports customer TPRM, repeatable enterprise reviews and revenue growth.
The person leading your SOC 2 audit is the most underrated factor in choosing an audit firm. Companies compare price, timelines and platform integrations, then barely ask who will actually do the work.
SOC 2 is a risk report, not a certificate. Understand how enterprise customers use it, why having a report is only base camp, and how to turn your audit into a trust asset for growing revenue.
What readiness should cover, when to involve your auditor, which gaps matter most, and how readiness, Type 1 and Type 2 can work as one continuous engagement. A practical guide to preparing for a report your customers can rely on.
CPA firm registration, signing licenses and peer review are the starting point, not proof of quality. A practical guide to checking credentials and asking the questions that matter before choosing your SOC 2 auditor.
Neither is better for everyone. The right choice depends on your customers, how you run security and where you are headed. For AI-native and AI-centric companies, SOC 2's flexible criteria usually make it the stronger starting point.
There's a basic psychology behind why most people don't like audits. Fix this, and people are surprisingly happy to do them again.
Enterprise buyers use SOC 2 as an initial qualifier, then look deeper. A quality report is what carries you through that assessment and turns your compliance investment into real trust.
Audit quality isn't service quality, and it isn't only professional standards. The real test is whether a reader of your report thinks: this tells me what I need to know.
Enterprise security teams review you in the background and rarely give feedback. What they look at beyond SOC 2, what counts as a genuine pen test, and how a quality report does the heavy lifting.
Compliance from first principles, the 95% problem, the compliance metadata AI needs, rethinking screenshots, spreadsheets and policies, and why audits should meet clients where they are.