Throughline.
    Insights
    Compliance Planning · Audit & Assurance

    SOC 2 for Mid-Sized Companies: Timeline, Cost and What's Different at Your Stage

    SOC 2 for mid-sized companies: typical USD costs, timelines and team hours, plus existing controls, multiple products, regulatory drivers and auditor changes.

    Paul Wenham
    2026-11-10

    A typical mid-sized company, with about 100 to 1,000 staff, gets a SOC 2 Type 1 report in about 13 weeks and a first Type 2 in about 24 weeks. At the median, the audit costs about $11,000 for a Type 1 and $13,500 for a Type 2.

    That's close to a startup's timeline, but for different reasons. A mid-sized company starts with more already in place, and spends that head start on extra complexity and coordination. This guide covers what's different at your stage; for how each stage works, see SOC 2 for startups. Figures come from our SOC 2 cost and timeline benchmarks.

    Which guide fits your company stage?

    Use the cost and timeline benchmarks for the cross-company comparison. This detailed guide explains the work behind the numbers.

    Compare stages: SOC 2 for startups, SOC 2 for enterprises.

    All costs are indicative US-dollar market estimates, not Throughline quotes. For our own fixed annual fees, see Throughline SOC 2 pricing. These are practitioner planning medians with outliers removed, not a formal statistical survey. Type 2 medians assume an approximate three-month observation period; longer coverage changes the schedule.

    Type 2 periods typically run three to 12 months. Throughline recommends six to 12 months; three months may suit a specific accepted timing requirement when that is the maximum coverage available. Agree actual calendar dates and buyer acceptance with your auditor.

    How long does SOC 2 take for a mid-sized company?

    Figures are in weeks: the median, with the typical range in brackets.

    StageType 1Type 2
    Planning2 (1–5)2 (1–7)
    Readiness6 (2–10)5 (2–15)
    Observation periodNot applicable12 (3 months)
    Audit fieldwork3 (1–6)3 (2–5)
    Reporting2 (1–3)2 (1–3)
    End to end13 (5–24)24 (18–40)

    Compared with a startup, the medians are only slightly longer, but the high end stretches further. More stakeholders and more complexity leave more room for a stage to stall.

    How much does SOC 2 cost for a mid-sized company?

    The audit typically costs $5,000–$20,000 for a Type 1 (median $11,000) and $7,500–$25,000 for a Type 2 (median $13,500). It's priced to the finished report, not by stage.

    Related costs scale with headcount and the number of systems in scope:

    CostMedianTypical range
    Compliance platform (annual)$30,000$15,000–$50,000
    Penetration test$15,000$8,000–$30,000
    Compliance consultant$45,000$25,000–$80,000
    Internal audit (outsourced)$10,000$5,000–$20,000
    Tool licensing upgrades$15,000$5,000–$40,000
    Availability or Confidentiality criteria (each)$750$0–$1,500
    Processing Integrity criteria$3,500$2,000–$7,000
    Privacy criteria$6,000$3,000–$12,000
    SOC 3 report$3,500$2,000–$8,000

    Many mid-sized companies already run pen tests and hold the tools they need, because customers' security questionnaires asked for them, so some of these costs may already be in the budget.

    How much internal team time does SOC 2 take for a mid-sized company?

    Roughly 45 to 598 hours across the journey, excluding normal operation of controls during an observation period.

    StageInternal hours
    Planning4–12
    Readiness25–500
    Audit fieldwork15–80
    Reporting1–6
    Total45–598

    More people share the work, which adds coordination time. But a designated GRC owner can give compliance a larger share of their week than a startup founder can. That's why hours grow faster than weeks as companies scale.

    Who runs SOC 2 at a mid-sized company?

    Usually someone with designated GRC responsibility, rather than a founder fitting it in. How that looks depends on whether the company is regulated:

    • Regulated companies often have several people: a leader, supported by one or more junior team members.
    • Unregulated companies often bring in one mid-level person to own the function themselves.

    Either way, more stakeholders are involved than at a startup. Control owners sit across engineering, IT, people and operations, and decisions need more input before they're made.

    How is SOC 2 different for a mid-sized company than a startup?

    Two forces pull in opposite directions, and they roughly cancel out.

    The head start: much is already in place

    A mid-sized company serving a substantial customer base has usually built many controls already, because they make sense at that stage: onboarding and offboarding, insurance, and pen tests or vulnerability scans.

    Security questionnaires drive much of that maturity. Enterprise customers have already asked about business continuity plans, information security policies and more, so the company has put them in place. SOC 2 is more often about documenting and aligning what exists than building from scratch.

    The added complexity

    Mid-sized companies also navigate more customer requirements, and more regulatory drivers beyond general security compliance, such as GDPR, or APRA standards for companies serving Australian financial services. That adds coordination, and calls for more careful thought about control design. A control that suits today but conflicts with other obligations, or won't scale, creates problems later.

    The net effect

    The two offset each other, so a mid-sized company can move as fast as a startup. Larger organizations naturally move a little slower, though, so timelines lean slightly longer, and the high end of each range stretches further.

    Fast-scaling technology companies are the exception. Some mid-sized companies still operate with a startup's simplicity, and their SOC 2 journey looks much the same.

    How much of your existing security work carries over to SOC 2?

    Typically 80–90%, but it's worth being clear about what that means.

    Customer security questionnaires usually touch on 80% or more of the controls in a SOC 2 report: encryption settings, policies, risk management, and employee security such as background checks. Contracts often cover much of it too, turning some requirements into legal terms, such as background checks for everyone with access to the customer's environment or who supports their service.

    But being asked about a control isn't the same as having it ready for an audit:

    • A questionnaire may ask about a range of policies, and "no" can be an acceptable answer. SOC 2 expects them in place.
    • You may have a risk management process, but SOC 2 tests whether it's fully operating and covers all the relevant risks.
    • Some areas get less questionnaire attention because enterprises assess them directly: terms of service, service commitments and support processes.
    • Availability questions tend to focus on uptime commitments and history, not on how you configure auto-scaling or forecast capacity.

    So the coverage is substantive: nearly everything in SOC 2 has come up in some form. It just isn't always in the form SOC 2 expects.

    These percentages describe practitioner experience, not a guaranteed readiness score. Confirm coverage against your actual criteria and system scope.

    How do regulatory drivers like GDPR, HIPAA or CPS 230 affect SOC 2?

    They don't change SOC 2's scope unless you decide they should. SOC 2 is flexible about which controls meet its criteria, so there are several ways to bring regulatory requirements in:

    • Adapt the controls. Shape your controls so they meet the SOC 2 criteria and the expectations of customers who care about another framework, such as APRA's CPS 230 or a specific customer's control requirements.
    • Issue a combined report. A SOC 2+ report, such as SOC 2+ HIPAA or SOC 2+ GDPR, covers the additional requirements in the same report.
    • Use SOC 2 as the backbone. For GDPR, SOC 2 can cover the technical and organizational measures, with privacy controls kept separate or layered on top. Including the Privacy criteria covers the backbone of what GDPR requires.

    SOC 2, including its Privacy criteria, does not by itself demonstrate complete GDPR, HIPAA or CPS 230 compliance. Map the applicable obligations separately and agree any additional reporting scope with your auditor.

    Do multiple products need one SOC 2 report or several?

    It depends on two questions:

    1. Do the products serve the same customer audience? If so, those customers need largely the same content from the report.
    2. How much do the controls overlap? Shared infrastructure, configuration and policies point to one report. The more the controls differ, the stronger the case for separate reports, because combining them gets messy.

    For most mid-sized SaaS companies, one report is the better choice. Products serving the same customers usually share 80% or more of their controls, unless they're run as separate business units.

    Separately marketed products with different customer audiences or substantially different controls may justify separate reports. Confirm the boundaries and report design with your auditor.

    What changes at each stage for a mid-sized company?

    The stages are the same as for a startup. What changes is where the effort goes.

    • Planning. More stakeholders weigh in, and scope has to account for regulatory drivers and key customers' requirements, not just general security.
    • Readiness. Less building, more cataloguing and aligning. Much of the work is mapping existing controls, policies and questionnaire answers to SOC 2, and designing new controls so they fit other obligations and scale with the business.
    • Observation period. The same choice as at any size. A first Type 2 of 3 to 6 months is common, with six months the better minimum.
    • Audit fieldwork. Multiple products or system components, often added to serve enterprise customers, need working through to decide which are material and which the report directly covers.
    • Reporting. The report takes more care to fit the customer base: what customers expect to see, what can sensibly be left out, and why you can stand behind leaving it out when not every component applies to every customer.

    What's the fastest a mid-sized company can get SOC 2?

    The ingredients for speed are the same at any size: someone who knows compliance, SOC 2 as a top priority, the authority to act, and an auditor working at your pace. A mid-sized company often has the first, in a GRC owner, and much of the work already done.

    What holds it back is dependencies. More people need to give input and approval, and regulatory drivers or multiple products add decisions. With everything aligned, the realistic floor is about 5 weeks for a Type 1 and 18 weeks for a Type 2.

    What causes SOC 2 exceptions at a mid-sized company?

    The causes are the same at every size: missing documentation, informal processes, and gaps in access control and change control. At a mid-sized company, they tend to show up where processes grew team by team without being standardized or written down.

    What does year two look like for a mid-sized company?

    The audit fee usually holds steady. Audit firms put more work into year one expecting a renewal, and rarely reduce fees as their effort falls by about 20–30%.

    Your own effort drops by about 40–50%. Planning and readiness fall close to zero, leaving a tidy-up and a stock-take of controls, and fieldwork and reporting take about 30% less effort. Expect some readiness work again if you add products, system components or regulatory drivers to the scope.

    What changes when you switch auditors or platforms?

    Mostly the controls. Your audit firm and platform both influence how controls are written, and some firms work from a fixed template. A new firm's approach can also surface things the old one didn't cover, which can make the report clearer for your customers. Resetting your controls completely is rarely worth it: it creates work, and controls are usually similar enough. A good number of Throughline's clients have come from other audit firms. We use each client's own controls, either drafting them with our technology or building on the prior year's report, then add or refine a few through the audit.

    The audit process itself can feel quite different: how responsive the firm is, how it audits, what tools it uses, and whether one person leads or a large team works across it. The evidence auditors look for doesn't usually change much.

    Rigor can differ, though. A firm that has been box-ticking for years might never have checked for vulnerability scanning reports, leaving a repository full of vulnerabilities for the next auditor to find. That doesn't necessarily mean a problem for your report, and there are ways to work through it.

    How does a mid-sized company keep SOC 2 on track?

    • Name one accountable owner, even when several people contribute, so decisions don't stall between stakeholders.
    • Start from what you have. Your security questionnaire answers, policies and existing controls are the fastest route to readiness.
    • Settle scope early. Agree which products, system components and regulatory drivers the report covers before readiness starts.
    • Design controls for the next stage of growth, not just for the audit, so they don't need rebuilding as you scale.
    • Engage your auditor on report design, so the report reflects what your customers actually need to see.

    How can Throughline help with your SOC 2 audit?

    Our SOC 2 audit services are calibrated to your stage, system scope, service commitments and compliance goals. Readiness is included free with every audit, and a Type 1 is included at no extra cost with every Type 2 engagement. Management owns control decisions and implementation.

    The audit fee is the unavoidable external cost of obtaining an independent report. Platforms, consultants and outsourced internal audits are optional; operating suitable controls may still require spending based on your risks and commitments. Throughline includes Availability and Confidentiality by default. The related-cost tables describe market arrangements, not Throughline add-on charges.

    Read all four guides: cost and timeline benchmarks, SOC 2 for startups, SOC 2 for enterprises.

    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
    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.

    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.

    Last updated