SOC 2 Without a Compliance Platform — how the no-software route works
A SOC 2 without compliance software is not a workaround — it is the original route. SOC 2 is an attestation, not a certification: a licensed CPA firm examines your controls and signs an opinion, and that is the entire mechanism. Before the platform category existed, every attestation worked the same way it can work for you today: a consultant runs readiness, evidence lives in organized shared storage on a calendar cadence, and the CPA firm examines and signs. Nothing in the standard asks for software. This guide walks the route end to end — including what it honestly demands of you, and the situations where a platform really is the better call.
Five things to know before choosing this route
- The standard never mentions software. SOC 2 is defined by the AICPA’s Trust Services Criteria and examined under AT-C attestation standards. The auditor tests controls and evidence — the container the evidence arrives in is not part of the opinion.
- The route predates the category. Consultant-run readiness, organized evidence, licensed CPA examination — attestations worked this way before platforms existed and still do. You are choosing a proven route, not improvising one.
- Every platform function has a plain equivalent. Evidence store: a structured drive plus your ticket system. Monitoring: the cloud tooling you already run, plus quarterly consultant check-ins. Dashboard: the auditor’s request list, worked as a checklist.
- The real price is discipline. Nothing nags you. The evidence calendar needs a named owner and a working cadence — that is the honest demand, and the honest reason some teams should buy software instead.
- Cost and time do not suffer. Consultant-led, India-delivered: indicatively $2,500–$10,000 all-in, attestation included. With TCSA: Type I in 6-8 weeks end to end, Type II in 14-16 weeks end to end, including the 12-week minimum observation window.
Five stages, no subscription anywhere in them
The no-platform route has the same skeleton as every SOC 2 engagement — preparation, then examination. What changes is who does the preparation: a readiness consultant instead of software guiding your own team. Here is the whole route, in order.
- 1. Gap assessment. The consultant maps your current practices against the Trust Services Criteria in scope and produces a gap list with owners. This is diagnosis, not remediation — our guide to the SOC 2 readiness assessment explains what a real one covers.
- 2. Control design. Each gap becomes a control fitted to how you actually operate — your cloud, your ticketing, your team size — rather than a generic template. Small teams get controls a small team can actually run.
- 3. Policies. The consultant drafts the policy set to match the controls as designed, and your leadership reviews and adopts them. Policies describe what you do. Auditors test whether you do it.
- 4. The evidence calendar. Every control gets a cadence — monthly, quarterly, or per-event — and a named owner. Evidence lands in a structured shared drive as it is produced, dated inside the period. This calendar is the engine of the whole route. SOC 2 evidence collection covers what each artifact looks like.
- 5. CPA examination. An independent, US-licensed CPA firm — readiness consultant and auditor must be independent of each other — examines the controls and evidence and issues the report. Who can perform a SOC 2 audit covers how to verify the signing firm.
For a Type II, stage four is most of the elapsed time: the controls simply operate across a 3-12 month observation window while evidence accumulates. No route — platform or not — compresses that window, because it runs in real time.
What replaces each platform function
A compliance platform is a bundle of conveniences, and each one has a plain equivalent built from things you already run. Our sibling guide to what SOC 2 automation actually automates takes the bundle apart in detail. This table is the working substitution map.
| Platform function | No-platform equivalent | What makes it work |
|---|---|---|
| Evidence store | A structured shared drive — one folder per control, a naming convention with dates — plus your existing ticket system for approvals, access reviews, and change records | Naming discipline: the folder structure mirrors the auditor’s request list |
| Automated evidence collection | Calendar-driven exports from systems you already run: IAM reports, logging and alert screenshots, MDM device lists, backup job records | A recurring calendar with a named owner per artifact |
| Continuous monitoring | The monitoring your cloud provider already gives you — native logging, alerting, and configuration checks — plus quarterly consultant check-ins to catch control drift | Alerts routed to a channel someone actually reads |
| Policy templates | Consultant-drafted policies fitted to your actual practices, version-controlled like code | Policies that describe what you really do, so testing confirms rather than surprises |
| Task dashboard and reminders | The auditor’s evidence request list worked as a checklist, with the consultant chasing open items | One accountable owner on your side, and the consultant as the external nag |
| Auditor marketplace | The consultant coordinates an independent, US-licensed CPA firm | Verify licensure and AICPA peer-review status yourself — at any price, on any route |
Notice what is absent from the right-hand column: anything you would need to buy. The substitutions are organizational, not technical — which is exactly why the honest cost of this route is measured in discipline, not dollars. Whether that trade suits your team is the real question, and our guide to whether you need SOC 2 software works through it.
What this route asks of you: discipline on the calendar
Here is the part a sales page would soften. The no-platform route works only if the evidence calendar actually runs — because auditors accept only evidence dated inside the period under review. A quarterly access review skipped in March cannot be recreated in November. It is simply an exception in your report.
- One named owner. Not a committee, not “the team”. One person owns the calendar, closes each item, and files the artifact. In small companies this is typically a founder or the engineering lead, at a few hours a month once the rhythm settles.
- A cadence that survives busy quarters. The calendar does not pause for a product launch. Evidence produced late is evidence dated late — and the observation window does not negotiate.
- An external check. Quarterly consultant check-ins exist precisely because internal discipline drifts. The consultant reviews the drive against the calendar and flags gaps while they are still fixable inside the window.
And the plain version of the counter-case, because it deserves plain words: if your evidence calendar keeps slipping and nobody owns it, buy the platform. Software discipline beats human discipline, and a tool that nags reliably is worth its subscription for a team that has proven it will not nag itself. That is not a failure of the route — it is an honest reading of your own operating culture, and cheaper than discovering it during fieldwork.
What it costs and how long it takes — same standard, fewer invoices
The examination sets the calendar on every route, so going platform-free does not slow you down — it removes a line item. Sprinto’s published claim that manual preparation takes 3-6 months versus weeks with automation compares software against an unassisted internal team. A consultant who has run readiness hundreds of times compresses the same phase without a subscription.
| Stage | Type I route | Type II route |
|---|---|---|
| Gap assessment and control design | Weeks 1–4 | Weeks 1–4 |
| Policies and evidence calendar stood up | Weeks 4–8 | Weeks 4–8 |
| Observation window | None — design examined at a point in time | 3-12 months, your choice, and evidence accumulates on the calendar |
| CPA examination and report | Final weeks | Fieldwork after the window closes |
| End to end | 2-4 months, or 6-8 weeks with TCSA | Commonly 6-12 months, or 14-16 weeks with TCSA at the 12-week minimum window |
| Indicative all-in cost (consultant-led, India-delivered) | From about $2,500 | $3,000–$10,000 |
For scale: Sprinto’s published 2026 cost guide prices platform subscriptions at $4,000–$30,000 per year by headcount, with platform-plus-partner-network audit totals of roughly $6,000–$60,000 under 500 employees — the audit is always billed on top of the subscription. Why the same report spans such different numbers is a structural story we tell in full in why SOC 2 quotes vary so much, and the SOC 2 cost guide breaks down the India-delivered engagement line by line. For the platform routes’ full multi-year arithmetic, see SOC 2 total cost of ownership.
Where the route strains — and when a platform wins
The no-platform route is strongest in year one, when a consultant is driving and the observation window is short. Three situations genuinely test it, and pretending otherwise would make this guide a sales page.
Year two, without a retainer
Renewal windows typically widen to a full 12 months, and every month needs evidence dated inside it. Teams that end the consulting relationship after the first report often drift until a scramble before fieldwork. Keep a light quarterly retainer, or accept that you are choosing the harder version of the route — year two and renewal covers the shift.
Many frameworks at once
Running SOC 2 alongside ISO 27001, HIPAA, and GDPR obligations multiplies the evidence calendar. One system of record starts to earn its fee when the same artifact serves four frameworks — a genuine platform strength, weighed against its cost in platform vs consultant.
Fast headcount growth
Access reviews scale with people. At small headcounts a quarterly review is an hour with an IAM export. Past a few hundred employees, automation stops being a convenience and starts being the only sane way to run the control.
The pattern across all three is the same: the route strains where volume outgrows a human calendar. If you can see that point coming — a funding round that doubles the team, a second framework already committed to a customer — factor it into the decision now rather than migrating mid-window.
This route, delivered: what we charge
This is the engagement we run: gap assessment, control design, policies, the evidence calendar, quarterly check-ins, and the attestation coordinated through independent, US-licensed CPA firms — no platform licence anywhere in the stack, working with the tooling you already have. Indicatively $2,500–$5,000 for a Type 1 and $3,000–$10,000 for a Type 2, all-in, fixed before we start. The full framework picture lives at our SOC 2 service page.
Serving clients across India, USA, UK, Australia & UAE. Final pricing depends on your Trust Services Criteria, stack, and entity structure — the scoping call is where indicative becomes exact.
The no-platform route — questions buyers actually ask
Can you get a SOC 2 report without compliance software?
What replaces the platform if we go without one?
How long does a platform-free SOC 2 take?
How much does SOC 2 cost without a platform?
Will the auditor accept folders and screenshots instead of platform exports?
When is a compliance platform the better choice?
Doesn’t manual preparation take much longer than automation?
What happens in year two without a platform?
Related Reading.
Why SOC 2 Quotes Vary
Two bills, three audit routes, and what every quote hides.
Read morePlatform vs Consultant
Who actually does the work, stage by stage.
Read moreDo You Need SOC 2 Software?
An honest decision guide — worth it, optional, or overhead.
Read moreSOC 2 for Startups
Under 50 people the equation flips. Here is the maths.
Read moreWhat Automation Actually Automates
Evidence, yes. Scoping, risk, and judgement, no.
Read moreThree-Year Cost of Ownership
Year one is the smallest number you will pay.
Read moreMandated vs Vendor-Added
What the AICPA actually requires — and what it does not.
Read more