Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Buyers Are Building Internal Scorecards
Transcript
- Lucas: A few weeks ago I was talking to a procurement director at a Fortune 500 industrial firm, and she mentioned something that stopped me cold. She said her team now builds a vendor scorecard before they even talk to sales reps. Like, a formal, weighted, multi-criteria scorecard, and the reps have no idea it exists. Luna: Wait — they're grading you before you even pitch? That sounds like a teacher handing out a rubric before the essay is written. Lucas: Exactly. And it's becoming way more common than most founders realize. She walked me through their process for a recent CRM evaluation. They had eight vendors, eighteen criteria, and each criterion had a weight. Luna: What kind of criteria? I'm guessing the obvious ones — price, features, support. Lucas: Those were on there, but the weights were surprising. 'Data residency' was worth 15 percent. 'API rate limits and scalability' was another 12. 'Contract flexibility' — like month to month versus annual — that was 10. Price was only 8 percent. Luna: So price was lower weight than data residency? That's a shift. A few years ago price was probably the top criteria. Lucas: Right. And the scorecard was built by a cross-functional team — IT, legal, procurement, and the business unit. They met twice, debated weights, then locked it. No vendor input. Luna: So the rep is flying blind. They show up with a demo geared toward features, but the buyer is secretly checking boxes on a rubric the rep hasn't seen. Lucas: That's exactly the problem. And the rep who figures out what's on that scorecard has a massive advantage. The rep who doesn't — well, they're basically playing darts in the dark. Luna: How do you even find out about the scorecard? It's not like the buyer emails it over ahead of time. Lucas: No, they don't. But you can infer it. Smart reps now ask early in the process: 'How are you evaluating vendors? What are the top three criteria your team cares about most?' And they listen for the unspoken weight. Luna: But that only works if the buyer is willing to share. Some procurement teams treat the scorecard as confidential. Lucas: Which is why some reps are now doing the opposite — they build their own scorecard and share it with the buyer. As a tool to align expectations. 'Here's how we think you should evaluate us.' It's a power move. Luna: Interesting. So instead of waiting to be graded, you hand them the rubric. But doesn't that feel manipulative? Lucas: I asked that same question. The procurement director said she actually prefers it. It shows the rep understands the buying process and is trying to be transparent. As long as the criteria are fair, she said it speeds up the evaluation. Luna: So the winning move is to co-create the scorecard with the buyer. Lucas: Exactly. And this is where the really good reps separate themselves. They don't just ask about the scorecard — they help build it. They say, 'Based on what we've discussed, here are the criteria you might care about. Let's adjust the weights together.' Luna: That requires a lot of trust. And a lot of upfront work before the demo. Lucas: It does. But the alternative is showing up to a test you didn't know existed and wondering why you lost. Luna: You know, this reminds me of something I read. Gartner did a study last year — they found that B2B buyers spend only about 17 percent of their total buying time actually talking to sales reps. The rest is independent research, internal meetings, and, presumably, building scorecards. Lucas: Right. So the rep's window is tiny. And what they do in that window — including how they handle the scorecard dynamic — determines the outcome. Luna: I also wonder if this scorecard trend is a response to bad sales behavior. Like, buyers got burned by over-promising demos, so now they want a structured, quantitative way to compare. Lucas: That's definitely part of it. The procurement director I spoke to said they started using scorecards after a vendor promised a 99.99 percent uptime SLA and then delivered 99.9. The contract didn't specify the measurement methodology, and the vendor exploited it. The scorecard now includes a clause about uptime measurement. Luna: Ouch. So the scorecard becomes a shield against vendor spin. Lucas: Exactly. And it's not just large enterprises. I'm seeing mid-market firms adopt this too. Startups that sell to mid-market are suddenly facing RFPs with detailed scoring matrices. Luna: So what's the concrete takeaway for a founder listening right now? How do you prepare for a world where every buyer has a hidden scorecard? Lucas: First, assume there is one. Even if the buyer doesn't say it, they're comparing you on some unspoken criteria. Second, try to surface it early. Ask the question: 'How will the team make a decision?' If they say 'we'll evaluate based on value,' dig deeper — what does value mean to them? Luna: And third? I'd guess — align your messaging to the scorecard criteria you can influence. Lucas: Right. If security is weighted heavily, lead with your SOC 2 report and penetration testing results. Don't bury it in a data room. Put it front and center. Luna: Honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Helps us keep this ad-free. Lucas: Yeah, it's simple. If this kind of practical conversation helps you think about your sales process, that's all we ask. And it keeps us independent. Luna: Alright, back to the scorecard. One thing I'm curious about: when you co-create a scorecard with a buyer, do you risk alienating the other stakeholders who weren't in the room? Lucas: That's a real risk. The executive sponsor you're working with may not have full authority over the criteria. So the co-creation has to be inclusive. You don't want to build a scorecard that gets overruled in a room you're not in. Luna: So the rep needs to map the buying committee and understand who owns which criteria. Lucas: Exactly. IT might care about integration complexity. Legal cares about data processing terms. The business unit cares about time to value. The scorecard is just the aggregate of all those priorities. Luna: And if you can help them see that your product scores well across the board, you're golden. Lucas: Right. But you also have to be honest about weaknesses. If your product doesn't support a required data residency region, don't try to hide it. Better to acknowledge it and offer a roadmap commitment. Luna: Interesting. So the scorecard actually forces a level of honesty in the sales process. Lucas: Absolutely. And that's not a bad thing. The companies that win on scorecards are the ones that have actually built products that match what buyers value. It's a forcing function for product-market fit. Luna: I want to come back to that in a future episode — how scorecards are changing product roadmaps. But for now, final thought? Lucas: My final thought is: if you're selling enterprise software and you haven't asked a buyer how they're evaluating vendors, you're flying blind. Ask the question. Build the scorecard together. It's the single highest-leverage conversation you can have. Luna: And if you're a buyer listening, share your scorecard early. It'll save everyone time. Lucas: Good point. On that note — see you next time. Luna: See you.