A director of sales at a growth-stage SaaS company lost the biggest opportunity of his year on a single sentence.
He'd been working the deal for months. Enterprise prospect, the kind of logo that would have reshaped the company's pipeline for the next two quarters. The product fit was strong. The technical evaluation was clean. He was deep into final-stage conversations when the prospect's procurement team came back with one requirement: a current SOC 2.
The company didn't have one. Not in progress. Not in draft. They were building toward it — but “building toward” is not a thing you can hand to a procurement officer. The deal didn't die that day. It just went quiet, in that specific way enterprise deals go quiet when they're never coming back.
The director of sales did everything you would expect a strong sales leader to do. He explained the controls in detail. He offered a call with engineering. He proposed a contractual commitment to deliver the report on a defined timeline.
“Call us back when you have a SOC 2 in hand to provide.” |
Procurement was polite and unmovable. Their vendor risk policy required a third-party attestation. There was no path that didn't start with a report in hand. They wished him well.
The competitor that won wasn't better. They were provable.
Here's the part worth sitting with.
The director of sales had no power to fix the actual problem. He could escalate, he could sell harder, he could bring in the CEO — none of which changed the fact that the document didn't exist and wasn't going to exist for many months. The decision that would have prevented this loss had been made — or rather, not made — somewhere upstream of him, by people who were not aware that was a common request in the sales process.
That's the structural failure. Sales leaders feel this first. Engineering teams feel it second, when they get pulled into a frantic compliance sprint after a deal is already lost. Operating partners feel it last, if they feel it at all — usually as a vague pipeline miss that gets explained as “competitive” or “timing” in the next sales pipeline update.
The actual cause — the controls were there, the proof wasn't, and a prospects procurement doesn't accept “trust us” — almost never makes it into a written document the operating partner ever sees.
This is the quiet pattern killing portfolio enterprise growth right now. Not breaches. Not attacks. Not anything that shows up in a threat report. Just deals that go quiet because the paperwork doesn't exist, and the people who could have funded the fix six months earlier never find out it was the reason.
Every enterprise deal your portcos lose to “competitive dynamics,” “pricing,” or “timing” deserves one more question: what did procurement ask for that we couldn't produce? That answer is almost never the one that reaches you. It's almost always the one that matters.
Next Wednesday: why every portco in your fund handles cyber risk differently — even though you've systematized every other operational function. The portfolio paradox, and what to do about it.