I used to tell early-stage founders that most of their customers won't ask for SOC 2 yet, so they can wait. That's all done now.
Just a few years ago, that was decent advice. A startup showed an enterprise buyer it was legit by sharing its policies, going through an audit, and answering security questionnaires. Corporate IT was one of the steps in the sale, every IT team had its own custom questionnaire, and the whole thing was long and tedious (I had plenty of those conversations back then).
At SupplyShift, before we had the report, we had very long and involved conversations with customers' IT departments, walking through basically every practice that SOC 2 Type II certifies. We did all of them. We just didn't have the paper. For a while you could get away with saying "we're compliant with SOC 2 Type II practices, we just don't have the piece of paper yet," and once we did have it, those conversations got a lot shorter: here's the report, bye.
What changed
IT departments have changed, and now I'm seeing even smaller deals with startups requiring SOC 2. A lot of companies now have internal policies that say certain software contracts require SOC 2 Type II, and the people who enforce those policies don't make exceptions for a promising startup.
I was just on a call with a client that I would have never suspected would need SOC 2 (type of customer, area, etc.) who said they were asked about it. Their customers are small businesses, often a few people in the shop, and I was frankly floored.
Another one of my clients has a contract that's capped in size until their SOC 2 is done, and once it is, that contract gets a lot bigger. The buyer wants to do more with them, and their own internal rules won't let them until the paper shows up. So my answer has changed: SOC 2 is becoming, unfortunately, the price of doing business.
The question shows up late
The SOC 2 question usually comes from whoever reviews the contract when it lands, often after the person you've been selling to has already said yes. It can even show up after you think the deal is done.
By the way, if your sales team doesn't know what the customer's IT approval process looks like, the deal timeline might be in for a big surprise.
This is also why when you start matters. If you've already kicked off the process, you have a real answer when it comes up: "We're in the process of getting our SOC 2 Type II, and our anticipated date is February." That answer keeps a lot of deals moving. It's a when, not an if, so you want this stuff rolling sooner rather than later.
What's actually in it
Most of SOC 2 Type II is about policies and procedures for data security, and very little of it lives in your code. The questions look like this:
Is there a person who can shut down someone's laptop if they get let go? Is there a process for it?
Is there software that keeps people from installing whatever they want on their machines?
Is every single person trained on preventing cyberattacks?
There's also a penetration test, and it will find something (that's fine, you fix it).
This is mostly COO work. If you don't have policies yet, the platforms have templates, so you review what they've got and commit to it. Everyone who works anywhere near this stuff should plan on a day or so of reading policies, agreeing and signing. It's mind-numbingly boring, I hate the process, and it just needs to happen. Your CEO and CTO end up doing a lot of extra work, so warn them now.
By the way, letting customers sign in with their Google or Microsoft accounts helps here. They get to use their own hardened accounts, with two-factor and whatever their internal security policies are, and those two cover the vast majority of enterprise users. It's a small lift for your engineers.
(If you sell into Europe, expect ISO 27001 to come up more than SOC 2. There's a lot of overlap between the two.)
What it'll cost you
If you're a seed-stage B2B founder selling to enterprise, plan for it in your sales cycle, and your budget cycle. The most painful part is spending time on policies, honestly. You can write your own policies, and there are also platforms out there (I've looked at several) that help you do it for a reasonable amount of money.
The audit takes about 4-6 months and repeats every year. All in, between the platforms that maintain policies, audits, certs, etc., you're probably looking at 10-15K and, at least initially, a week's worth of your time dealing with policy development and approval. Maybe a bit more. I'd weigh platform vs doing it yourself carefully.
Happy to help think through it if you don't have someone on your team who's done it before.