Throughline.
    Insights
    Compliance Planning · Audit & Assurance

    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.

    Paul Wenham
    Updated 10 November 2026

    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.

    Where do these SOC 2 benchmarks come from?

    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.

    Which detailed SOC 2 guide should you read for your company stage?

    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.

    How is company size defined in these benchmarks?

    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.

    SegmentTypical profile
    StartupUp to 100 staff; one product; cloud-hosted; small engineering team
    Mid-sizedAbout 101–1,000 staff; several teams or products; a dedicated security or IT owner
    Enterprise1,001+ staff; multiple systems, locations or business units; a formal GRC function

    What do the cost and time figures include?

    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.

    StepWhat it coversApplies to
    PlanningScoping, choosing criteria and systems, selecting the auditor, setting up the engagementType 1 and Type 2
    ReadinessGap assessment, remediation and preparing evidenceType 1 and Type 2
    Observation periodThe period controls must operate before Type 2 testing, typically 3–12 monthsType 2 only
    Audit fieldworkTesting control design (Type 1) or operation across the period (Type 2)Type 1 and Type 2
    ReportingDraft report, management responses, review and issuanceType 1 and Type 2

    How much does SOC 2 cost and how long does it take by company size?

    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.

    IDSizeReportCost low (USD)Cost median (USD)Cost high (USD)Time low (weeks)Time median (weeks)Time high (weeks)Notes
    total-t1-startupStartupType 1$3,000$6,500$10,00051018Readiness is often included in the audit fee
    total-t2-startupStartupType 2$5,000$9,000$15,000182238Assumes a 3-month first observation period
    total-t1-midMid-sizedType 1$5,000$11,000$20,00051324More systems and control owners than a startup
    total-t2-midMid-sizedType 2$7,500$13,500$25,000182440Assumes a 3-month first observation period
    total-t1-entEnterpriseType 1$11,000$18,000$35,00091852Procurement, legal review and many control owners extend planning and readiness
    total-t2-entEnterpriseType 2$12,000$22,000$50,000233278Assumes a 3-month observation period at the median, up to 6 months at the high end

    What happens during SOC 2 planning?

    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.

    Why does SOC 2 readiness take different amounts of time?

    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.

    How does the Type 2 observation period affect the timeline?

    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.

    What determines SOC 2 audit fieldwork time?

    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.

    How long does SOC 2 reporting take after fieldwork?

    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.

    How long does each Type 1 step take by company size?

    Type 1 has no observation period. These are step-level elapsed weeks, not figures to add into a guaranteed delivery date.

    IDSizeStepLow (weeks)Typical median (weeks)High (weeks)Notes
    t1-startup-planningStartupPlanning123
    t1-startup-readinessStartupReadiness248
    t1-startup-fieldworkStartupAudit fieldwork124
    t1-startup-reportingStartupReporting123
    t1-mid-planningMid-sizedPlanning125
    t1-mid-readinessMid-sizedReadiness2610
    t1-mid-fieldworkMid-sizedAudit fieldwork136
    t1-mid-reportingMid-sizedReporting123
    t1-ent-planningEnterprisePlanning3414
    t1-ent-readinessEnterpriseReadiness3824
    t1-ent-fieldworkEnterpriseAudit fieldwork248
    t1-ent-reportingEnterpriseReporting126

    How long does each Type 2 step take by company size?

    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.

    IDSizeStepLow (weeks)Typical median (weeks)High (weeks)Notes
    t2-startup-planningStartupPlanning126
    t2-startup-readinessStartupReadiness2414
    t2-startup-observationStartupObservation period1212123 months used for consistency; common for startups that skip the Type 1
    t2-startup-fieldworkStartupAudit fieldwork225
    t2-startup-reportingStartupReporting123
    t2-mid-planningMid-sizedPlanning127
    t2-mid-readinessMid-sizedReadiness2515
    t2-mid-observationMid-sizedObservation period1212123 months used for consistency
    t2-mid-fieldworkMid-sizedAudit fieldwork235
    t2-mid-reportingMid-sizedReporting123
    t2-ent-planningEnterprisePlanning3414
    t2-ent-readinessEnterpriseReadiness51024
    t2-ent-observationEnterpriseObservation period1212243-month median used for consistency; enterprises more often choose 6 months or more
    t2-ent-fieldworkEnterpriseAudit fieldwork2410
    t2-ent-reportingEnterpriseReporting126

    How much internal team time does SOC 2 take by company size?

    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.

    IDSizeStepHours lowHours highNotes
    hrs-startup-planningStartupPlanning210
    hrs-startup-readinessStartupReadiness15400Depends heavily on starting point and compliance knowledge
    hrs-startup-fieldworkStartupAudit fieldwork1060
    hrs-startup-reportingStartupReporting14
    hrs-startup-totalStartupTotal28474Hours spread thin across people wearing several hats
    hrs-mid-planningMid-sizedPlanning412
    hrs-mid-readinessMid-sizedReadiness25500Much existing work can be mapped rather than built
    hrs-mid-fieldworkMid-sizedAudit fieldwork1580
    hrs-mid-reportingMid-sizedReporting16
    hrs-mid-totalMid-sizedTotal45598
    hrs-ent-planningEnterprisePlanning840Procurement and approvals add hours
    hrs-ent-readinessEnterpriseReadiness802,000Work split across many parties, so less efficient
    hrs-ent-fieldworkEnterpriseAudit fieldwork60400
    hrs-ent-reportingEnterpriseReporting220
    hrs-ent-totalEnterpriseTotal1502,460More hours, but a larger share of people's time is dedicated to compliance

    Which costs sit outside the SOC 2 audit engagement?

    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.

    What related SOC 2 costs should startups budget for?

    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.

    IDSizeCost itemLow (USD)Typical median (USD)High (USD)Notes
    rc-startup-platformStartupCompliance platform (annual)$6,000$10,000$15,000Priced by headcount and number of frameworks
    rc-startup-pentestStartupPenetration test$3,000$5,000$8,000Human-led test of one web app and API; below this is usually an automated scan
    rc-startup-consultantStartupCompliance consultant$10,000$20,000$40,000Optional; often in place of an in-house compliance lead
    rc-startup-internal-auditStartupInternal audit (outsourced)$2,000$4,000$8,000Not required for SOC 2; a self-assessment can be done in-house
    rc-startup-toolsStartupTool licensing upgrades$1,000$3,000$10,000Incremental annual cost, such as enforced code review, identity and HR tools
    rc-startup-securityStartupSecurity criteria$0$0$0Included in every SOC 2 and covered by the base audit fee
    rc-startup-availabilityStartupAvailability criteria$0$500$1,000Included free by some firms, including Throughline
    rc-startup-confidentialityStartupConfidentiality criteria$0$500$1,000Included free by some firms, including Throughline
    rc-startup-processing-integrityStartupProcessing Integrity criteria$1,000$2,000$4,000Almost always an add-on
    rc-startup-privacyStartupPrivacy criteria$2,000$4,000$8,000Almost always an add-on; adds significant scope
    rc-startup-soc3StartupSOC 3 report$2,000$3,000$6,000Public summary report, issued alongside the SOC 2

    What related SOC 2 costs should mid-sized companies budget for?

    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.

    IDSizeCost itemLow (USD)Typical median (USD)High (USD)Notes
    rc-mid-platformMid-sizedCompliance platform (annual)$15,000$30,000$50,000Rises with headcount and added frameworks
    rc-mid-pentestMid-sizedPenetration test$8,000$15,000$30,000Several apps, APIs and cloud infrastructure
    rc-mid-consultantMid-sizedCompliance consultant$25,000$45,000$80,000More systems and teams to implement across
    rc-mid-internal-auditMid-sizedInternal audit (outsourced)$5,000$10,000$20,000Not required for SOC 2
    rc-mid-toolsMid-sizedTool licensing upgrades$5,000$15,000$40,000Scales with headcount
    rc-mid-securityMid-sizedSecurity criteria$0$0$0Included in every SOC 2 and covered by the base audit fee
    rc-mid-availabilityMid-sizedAvailability criteria$0$750$1,500Included free by some firms, including Throughline
    rc-mid-confidentialityMid-sizedConfidentiality criteria$0$750$1,500Included free by some firms, including Throughline
    rc-mid-processing-integrityMid-sizedProcessing Integrity criteria$2,000$3,500$7,000Almost always an add-on
    rc-mid-privacyMid-sizedPrivacy criteria$3,000$6,000$12,000Almost always an add-on; adds significant scope
    rc-mid-soc3Mid-sizedSOC 3 report$2,000$3,500$8,000Public summary report, issued alongside the SOC 2

    What related SOC 2 costs should enterprises budget for?

    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.

    IDSizeCost itemLow (USD)Typical median (USD)High (USD)Notes
    rc-ent-platformEnterpriseCompliance platform (annual)$40,000$60,000$100,000Often multi-framework enterprise plans
    rc-ent-pentestEnterprisePenetration test$20,000$40,000$80,000Several applications and networks; red team exercises cost more
    rc-ent-consultantEnterpriseCompliance consultant$50,000$90,000$150,000Complex scopes start around $50,000
    rc-ent-internal-auditEnterpriseInternal audit (outsourced)$10,000$20,000$40,000Often covered by an in-house internal audit function
    rc-ent-toolsEnterpriseTool licensing upgrades$10,000$30,000$100,000Incremental only; enterprises usually license the core tools already
    rc-ent-securityEnterpriseSecurity criteria$0$0$0Included in every SOC 2 and covered by the base audit fee
    rc-ent-availabilityEnterpriseAvailability criteria$0$1,000$2,000Included free by some firms, including Throughline
    rc-ent-confidentialityEnterpriseConfidentiality criteria$0$1,000$2,000Included free by some firms, including Throughline
    rc-ent-processing-integrityEnterpriseProcessing Integrity criteria$3,000$6,000$12,000Almost always an add-on
    rc-ent-privacyEnterprisePrivacy criteria$5,000$10,000$20,000Almost always an add-on; adds significant scope
    rc-ent-soc3EnterpriseSOC 3 report$3,000$5,000$10,000Public summary report, issued alongside the SOC 2

    What changes in SOC 2 renewal cost and effort in year two?

    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.

    ItemYear two compared with year one
    Audit feeUsually unchanged
    Audit firm effortAbout 20–30% less
    Client effort, overallAbout 40–50% less
    PlanningClose to zero; often confirming last year's plan
    ReadinessClose to zero; a tidy-up and stock-take of controls
    Audit fieldworkAbout 30% less
    ReportingAbout 30% less

    How should you turn these benchmarks into an audit plan?

    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.

    Paul Wenham
    Written by
    Paul Wenham

    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.

    More from Paul
    Audit & Assurance
    How Australian Companies Should Choose a SOC 2 Audit Firm

    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.

    Compliance Planning · Audit & Assurance
    How Much Does SOC 2 Cost? The True All-In Cost, Category by Category

    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.

    Audit & Assurance
    SOC 2 Isn't Pass/Fail: What It's Really For

    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.

    Compliance Planning
    SOC 2 Readiness Assessments: Your Questions Answered

    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.

    SOC 2
    What makes a SOC 2 report quality?

    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.

    SOC 2
    What makes a SOC 2 audit high quality

    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.

    Audit & Assurance
    Getting Through Enterprise Security Reviews

    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.

    Agentic Compliance
    Agentic Compliance: AI-Native, Human-Led

    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.