REVIEW DRAFTOverviewV1 · one pageV2 · part 1V2 · part 2V2 · part 3
THE BAY PLAYBOOK
DRAFT · COMPANY SECTION / PART 3 OF 3PARTNER GUIDE · FROM SPRINTO

Getting audit-ready, and what it costs

The five steps to audit-readiness, what the audit is like, the report you get, the timeline, the cost, and what comes after. (About 12 minutes)

PARTNER GUIDEWritten by Sprinto, our compliance partner, and shared with The Founder Folks. The words below are Sprinto’s.

Earlier: What to get. This part stands on its own if you’d rather start here.

The journey towards audit-readiness

You don’t need to have everything in place to start your journey, but it does involve homework. That means knowing where you stand, understanding what needs fixing, and collecting evidence as you go.

Start by taking an honest look at where you are today. Are you starting from scratch or do you already have policies and procedures in place? It’s important to be honest here, no matter how difficult it is. If you’re starting from scratch, you can use the Compliance Starter Kit to get started.

The flowchart below is what the audit-readiness journey typically looks like. It’s a good place to start for any framework you choose. But we’ll use SOC 2 as our example.

THE JOURNEY TOWARDS AUDIT READINESSTAP A STEP

Step 1: Define the audit scope

Now that you’ve done your homework, it’s time to decide which systems and processes to include for the audit. Typically, for a first-time audit, this list should include your production environment and any systems that handle customer data. For SOC 2, you’ll need to decide which Trust Services Criteria to include, whether you’re aiming for a Type 1 or a Type 2 report, and if you’re choosing a Type 2 report, how long your observation period is going to be.

Next, integrate your tools. It helps to have a compliance automation platform that consolidates evidence across your environment.

Step 2: Find and fix gaps

Understand what the framework expects. Since SOC 2 is interpretive, there’s no fixed checklist. Instead, you map your existing controls to the TSCs and spot where they fall short. This gives you a clear picture of what you have and what you need done.

The next step is to identify the gaps—overlooked vendor reviews, unencrypted devices, and missing policies are the most common. If you’ve taken a look at the Compliance Starter Kit, then any policy or control you don’t have in place from there becomes your to-do list. Bucket these by priority and fix high-priority items first.

Step 3: Consolidate status

Track the status of your controls. Keep an eye on which controls are passing, how many are failing, and which ones need immediate attention. An audit dashboard becomes your mission control—your single source of truth, ensuring things don’t slip through the cracks.

Collect evidence as you go. For a Type 2 report, auditors want proof that your controls worked throughout the observation period, not just on the day they checked. Manual screenshots capture only a single moment and quickly go stale. This is why having a compliance platform that collects evidence automatically goes a long way.

Step 4: Conduct a readiness assessment

Consider the readiness assessment a dry run before the audit. It gives you a lot of context on just how audit-ready you are. It allows you to review every control against its evidence as an auditor would, either through an external advisor or through a compliance platform. Anything that falls short goes back into your fix list. This way, you avoid any surprises when your auditor arrives.

Step 5: Undergo an independent audit

Once you have everything in place, it’s time to undergo the audit. Start by picking the right audit partner—either a licensed CPA firm for SOC 2 or an accredited certification body for ISO standards. Look for partners with experience auditing startups and who can integrate with your compliance platform (if you have one). If you’re going for a Type 2 report, your controls need to run for an observation period before the auditor reviews their performance.

Don’t be afraid to compare quotes on the same scope.

What to expect during the audit

An audit typically starts with a kickoff meeting where the auditor reviews the scope and timeline with you upfront. Once agreed, you will receive a document that lists the data and evidence you need to provide. Over the next few weeks, the auditor will conduct walkthroughs and interviews to assess how controls work in the live environment.

Auditors will also pick samples (typically for a Type 2 report) across the observation period, such as code changes or new hires, and check each one against controls.

They will often request additional evidence and review it, typically taking 7 to 10 days per review cycle. They may even come back with follow-up questions and clarifications—this is completely normal.

An auditor is an independent reviewer and not a consultant. It’s important to see the relationship as such and understand what an auditor will and won’t do. They will not build or write policies for you. And while they tell you what’s broken, do not expect them to tell you exactly how to fix it.

QUICK TIP
Assign a single point of contact for auditor communication and focus on answering questions clearly and completely.

What the results typically look like

At the end of an audit, you get a SOC 2 report with the auditor’s opinion on the front page. There are four possible opinions:

A CLEAN “UNQUALIFIED” OPINION

The smoothest landing—the best possible result. This indicates that your controls were presented fairly, are suitably designed, and operated effectively for the specified observation period.

A “QUALIFIED” OPINION

This indicates that the audit was largely successful, except for one or more areas that matter.

A “DISCLAIMER OF OPINION”

This indicates that the auditor was not able to gather sufficient evidence and therefore was not able to form an opinion.

AN “ADVERSE” OPINION

A rare scenario in which an auditor is of the opinion that your controls do not meet the required criteria. This happens when an organization undergoes an audit before it is ready.

Exceptions are specific instances in which an auditor found a control that didn’t work as intended, such as the one employee who promises to “complete security training right after this sprint.” They are very common, even for clean reports. What’s important here is that you acknowledge and address them.

Buyers will often look for a short management response, explaining what you did to resolve these exceptions.

When it comes to ISO, nonconformities are equivalent to exceptions. Nonconformities are classified as major (severe failures that critically impact the capabilities of an ISMS) and minor (minor lapses that do not critically impact the capability of an ISMS). Major nonconformities need to be resolved before you’re certified, whereas minor nonconformities require a corrective action plan.

The complete SOC 2 timeline

FROM SCOPING TO REPORTFIVE ACTIVITIES
2 WEEKS
Scoping
  • Understand where you are
  • Decide which systems fall within scope
  • Integrate tools with a compliance platform
6 TO 8 WEEKS
Fixing gaps
  • Implement policies
  • Identify gaps
  • Bucket gaps, fix by priority
SET UP AFTER SCOPING, THEN ONGOING
Consolidating status
  • Implement an audit dashboard
  • Monitor control status
  • Collect evidence as you go
1 TO 2 WEEKS
Readiness assessment
  • Conduct a readiness assessment
  • Fix gaps
1 WEEK TO CHOOSE AN AUDIT PARTNER, 3 TO 6 MONTHS AS FIRST OBSERVATION PERIOD (FOR SOC 2 TYPE 2)
Audit
  • Choose an audit partner
  • Observation period
  • Undergo an audit

A breakdown of costs

Alright. Let’s talk money. For most early-stage companies, the first SOC 2 report costs around $14k to $18k in year one if you pick a compliance automation platform or $19.5k to $28.5k if you go the manual route, for the Security criterion alone. This estimate includes tooling, testing, auditor fees, and an approximation to account for team bandwidth and resources (if done manually).

Treat these as ballpark figures, not an exact quote.

YEAR-ONE COST, SOC 2 SECURITY CRITERIONSWITCH THE ROUTE
COMPONENTTYPICAL RANGEWHAT IT DEPENDS ON
Compliance automation platform$4,500Frameworks, team size, and integrations
Auditor fees$3k - $6k for 3 TSCs
$2.5k for additional TSCs
TSCs, observation period, scoped systems, audit firm chosen
Penetration testing$1.5k - $2.5kSize and complexity of apps and infrastructure
Supporting tools$5kDevice management tool, password manager, background checker, logging tool
Cost of manpower and misc. expenses*$10k - $15kHow ready you are and how much you automate
TOTAL, FIRST YEAR
–

*Cost of manpower is the value of the time your team spends on compliance work a platform would otherwise handle, like collecting evidence by hand, tracking controls in spreadsheets and chasing screenshots. It doesn’t appear on any invoice, but it adds up.

The totals above add up the rows in Sprinto’s table. The platform total leaves out the manpower row, and the manual total leaves out the platform row.

What to do next

An audit isn’t the finish line. Once your report lands, it’s tempting to file it away and get back to building your product. But your controls need to keep running because your next observation period begins as soon as the previous one ends.

The good news is that year two is far easier than the first one, as long as you keep the good habits going. Here’s how you close the loop:

CLOSING THE LOOP5 ITEMS · TICK AS YOU GO
AFTER THE REPORT LANDS
Remediate findings
Fix every exception or nonconformity and record when and how you did so.
Monitor controls
Controls drift quietly. Actively monitor controls and carry out remediations as and when you notice things slip.
Plan your renewals
SOC 2 must be renewed every year. And ISO 27001 requires yearly surveillance audits (yearly check-in audits). Add these dates to your calendar and work backward.
Revisit scope
As your company grows and adds new tech, the scope you’ve chosen becomes obsolete. Update your scope and add new frameworks as your business evolves.
Leverage your SOC 2 report to build trust
SOC 2 reports are usually shared under NDA. Many startups set up a simple trust page that prospects can access on request.
0 of 5 in place

Cleared for takeoff

If you’ve made it this far, give yourself a pat on the back. You’ve just sat through an entire chapter on compliance and lived to tell the tale.

A little while ago, SOC 2 was something you nodded along to in meetings while quietly googling it under the table. Now you know what it is, when you need it, and how to get started. And that’s more than many founders moving to the US can say.

Yes, it’s work—there are policies to write, evidence to chase down, and at least one moment you’ll find yourself documenting the fact that you documented something. But compliance is far more predictable than it looks. Do it properly, and it pays you back long after your auditor has gone home.

Compliance is huge, but you only need to explore the corner of the galaxy your customers live in. And now you have a map.