Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Deals Now Require a Vendor Risk Tiering System
Transcript
- Lucas: So you've got a fifty-person SaaS startup, solid product, a couple of logos in the mid-market, and you finally land a meeting with a Fortune 500 bank. The procurement team sends over a pre-demo questionnaire — and buried in it is a new question they haven't seen before: 'Please self-classify your organization into one of the following vendor risk tiers.' Luna: I've seen this. It's vendor risk tiering — and it's becoming a standard gate in enterprise procurement. The tier determines how much due diligence they do, how often they audit you, even what contract terms they offer. Lucas: Exactly. And the categories are usually something like Critical, High, Medium, and Low. But here's the thing — the vendor doesn't get to just pick Low and move on. The procurement team validates your classification against their own criteria. Data sensitivity, system criticality, regulatory overlap, subcontractor chain, even your cyber insurance limits. Luna: Right. So if you're a vendor that handles payment data or PII, you're probably getting flagged as High or Critical automatically, regardless of your actual security posture. It's like being put in a box before you even open your mouth. Lucas: And that box has real consequences. A Critical tier vendor at a bank like JPMorgan might require a full on-site audit, quarterly business continuity reviews, and a dedicated relationship manager from their third-party risk office. A Low tier vendor might just need an annual SOC 2 report and a signed data processing addendum. The difference in cost of sale is enormous. Luna: I've heard from sales reps who say tiering is now the first thing procurement asks about — before pricing, before functionality. It's a filter. If you're classified High or Critical, the sales cycle can stretch by months because legal and compliance have to sign off. Lucas: And that's for a reason. Regulators are pushing for this. After the SolarWinds breach, the SEC started asking about how public companies oversee their software supply chain. Then the DORA framework in Europe came in. Now a lot of US financial institutions are voluntarily adopting tiering frameworks from the Shared Assessments Program or the Vendor Risk Management Maturity Model. Luna: So this isn't just one bank being picky. It's becoming a procurement standard. And I think the interesting question is: does tiering actually reduce risk, or does it just shift the burden onto smaller vendors who can't afford the compliance overhead? Lucas: That's the tension. A fifty-person startup might have better security practices than a legacy vendor with a thousand employees, but the legacy vendor has a dedicated compliance team to fill out the tiering questionnaire. The startup founder is doing it themselves at 11 p.m. after the kids go to bed. Luna: And the questionnaire itself — it's not short. A typical tiering request from a large enterprise can run forty to sixty fields. Things like: Do you encrypt data at rest and in transit? What encryption standard? AES-256? Do you have a data retention and deletion policy? Do you share data with any sub-processors? Have you had a breach in the last three years? Lucas: Yeah. And the thing that catches a lot of vendors is the 'sub-processor' question. If you use AWS or Azure to host, you have to list them. If you use a third-party logging tool, you list that too. Suddenly your supply chain is exposed, and the enterprise starts asking about their sub-processors' sub-processors. Luna: It cascades. And there's no standard format. One bank uses a spreadsheet, another uses a dedicated portal like OneTrust or Archer. Vendors have to adapt every time. Lucas: So let's get concrete. What should a vendor rep have ready before they even receive that tiering questionnaire? First, a complete data map — what data touches your system, where it's stored, how it flows. Second, your compliance certifications upfront: SOC 2 Type II, ISO 27001, maybe FedRAMP if you're going after government. Third, a clear articulation of your sub-processor chain. Luna: And a documented incident response plan. I've seen tiering questionnaires that ask for your average time to detect and contain a breach. If you don't have that number, you're already starting from a weaker position. Lucas: Right. The best-prepared vendors now have a 'tiering packet' — a pre-built set of answers to the most common questions. They keep it updated quarterly. And they don't wait for procurement to ask. They proactively offer it during the early discovery call. Luna: Which changes the dynamic. Instead of being reactive, you're showing that you understand their risk framework. That builds trust. And sometimes it can even influence the tier you get classified into, because you're demonstrating maturity. Lucas: I've seen exactly that. A vendor in the healthcare space was initially pegged as High risk because they handled protected health information. But they proactively shared their recent HIPAA audit results, their breach history — zero incidents — and their cyber insurance coverage of ten million dollars. The enterprise moved them to Medium, which shortened the legal review from three months to six weeks. Luna: That's real leverage. And it shows that tiering isn't just a barrier — it's also an opportunity to differentiate. If you can prove you're low risk, you can compress the sales cycle. Lucas: But here's where I get a little skeptical. The tiering systems are still very binary. A vendor that handles financial data but has stellar security is still classified Critical because of the data type. And a vendor that handles no PII but has sloppy security practices might get Medium. The system doesn't capture nuance well. Luna: So there's a gap between the risk tier and the actual risk. Which means vendors have to do double duty: meet the formal criteria, and then also educate the procurement team about their real security posture through conversations and demos. Lucas: And that's where the sales rep's role shifts. They used to just sell the product. Now they have to sell the vendor's security readiness. They need to know the difference between SOC 2 Type I and Type II, understand what a data retention schedule looks like, and be able to explain why they use AWS over GCP. Luna: That's a lot to ask of someone whose primary job is quota attainment. Some companies are now creating a 'security sales engineer' role — someone who sits between sales and compliance and handles the tiering questionnaires. Lucas: It's becoming a necessary function. And it's not just for the big vendors. If you're a ten-person startup targeting enterprise, you need someone who can speak the language of vendor risk management. Otherwise you'll get stuck in procurement purgatory. Luna: Which brings up a broader point. This tiering trend is ultimately about procurement trying to standardize something that's historically been very ad hoc. Every enterprise had its own spreadsheet, its own set of questions. Now they're trying to create consistent tiers so they can compare vendors apples to apples. Lucas: And that's a good thing in theory. But in practice, it can lock out newer, more innovative vendors that don't have the compliance infrastructure yet. There's a risk that tiering becomes a barrier to entry rather than a genuine risk management tool. Luna: Yeah. And I think the next evolution will be tiering that adapts — maybe using continuous monitoring instead of a static annual questionnaire. Some of the larger cybersecurity firms are already offering that as a service. Lucas: Speaking of services that help vendors get ready — and this is a bit of a tangent, but it connects — if you're a founder or a sales leader trying to navigate this landscape, conversations like this are exactly why we keep the show ad-free. We want these insights to be accessible without a paywall. If you find the episodes useful for what you're building or running, and you'd like to support that mission, you can buy us a coffee at buy me a coffee dot com slash fexingo. It's a small way to keep the show going and growing. Luna: Yeah, it helps us keep bringing on practitioners and digging into the details that actually matter for your day-to-day. Appreciate anyone who chips in. Lucas: So back to tiering — I think the key takeaway for vendors is: don't treat the tiering questionnaire as a hurdle. Treat it as a sales document. The way you fill it out communicates how seriously you take risk. And in enterprise sales, that's as important as your product demo. Luna: Exactly. And if you can't fill it out confidently, that's a signal that you need to invest in your compliance posture before you go after the big logos. Lucas: Because the tiering isn't going away. If anything, it's going to get more granular. I've seen early versions of frameworks that include a 'tier zero' for vendors that have direct integration into critical systems. That's a new category with even more scrutiny. Luna: Interesting. So the bar keeps rising. The question is: will procurement teams standardize around one framework, or will we end up with dozens of incompatible tiering systems that vendors have to juggle? Lucas: That's the million-dollar question. If the industry converges on something like the Shared Assessments SIG questionnaire, you could see a world where a vendor fills out one comprehensive tiering form and it's accepted by multiple buyers. That would be a game-changer for efficiency. Luna: But we're not there yet. For now, vendors have to be ready to pivot for each enterprise. Which is why having a dedicated tiering packet is such a practical first step. Lucas: Absolutely. And that's where we'll leave it. Next time, I want to talk about how some vendors are starting to push back on tiering — arguing for a more collaborative risk assessment rather than a one-size-fits-all classification. Luna: That sounds like a good one. See you then.