Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Reps Sell Through the Procurement Scorecard
Transcript
- Lucas: So you've spent months building a champion inside the prospect company. You've done the demo, the proof of concept, the security questionnaire. Then procurement sends you a scorecard — and your product scores a 62 out of 100. You lose. Luna: The dreaded internal scorecard. I've heard reps call it the 'black box' of enterprise sales. Lucas: Exactly. And most reps treat it as a black box — they see the score and give up. But here's the thing: scorecards are actually predictable if you know how procurement builds them. And if you know the categories before they hit you, you can shape your proposal to score higher. Luna: So you're saying reps should ask for the scorecard before they submit a proposal? Lucas: Ideally, yes. But in practice, procurement doesn't share it until the final stage. So you have to reverse-engineer it. Let me give you a concrete example. I talked to a rep at a workforce planning SaaS company — let's call them ShiftPlan — who was chasing a $2.3 million annual deal with a large retailer. Luna: That's a big number. What happened? Lucas: The rep had done everything right. He had the VP of HR as his champion. The demo went great. They passed the security review. Then the retailer's procurement team sent over a scoring sheet with seven categories. ShiftPlan scored well on functionality and security, but got a zero on 'implementation timeline' and 'data migration support.' Luna: Zero? That seems harsh. Lucas: It was harsh — but it was also a clue. The rep realised those two categories hadn't been discussed at all. The champion had assumed the implementation would take three months, but ShiftPlan's standard timeline was six months. And the rep hadn't even mentioned data migration because the product had a built-in import tool. Luna: So the scorecard revealed gaps the rep didn't know existed. Lucas: Right. And that's the key insight: a scorecard isn't just a verdict — it's a map of what the buyer cares about. Once the rep saw those zeros, he went back to his champion and asked for the actual criteria behind each category. Turns out, the retailer had a mandate that any new software had to be live within 90 days, and they had a legacy HR system with messy data. Luna: 90 days is tight. Did ShiftPlan adjust? Lucas: They did. The rep worked with his professional services team to craft an accelerated implementation plan — 75 days — with a dedicated data migration specialist. He resubmitted the proposal with those specifics highlighted. His new score was 88 out of 100. They won the deal. Luna: That's a great comeback. But it sounds like the rep got lucky — he had a champion who shared the criteria. Lucas: True. But the smarter play is to preempt the scorecard. Before you even submit a proposal, ask your champion three questions. First: what categories will procurement use to evaluate vendors? Second: what weighting does each category have? Third: what does a top score look like for each one? Luna: And if the champion doesn't know? Lucas: Then they're not a real champion. A true internal advocate should know the procurement process. If they can't answer those questions, you need to invest more time bringing them up to speed — or find a different sponsor. Luna: Let me push back. Some procurement teams treat the scorecard as confidential. They don't want vendors gaming the system. Lucas: That's fair. And some are genuinely proprietary. But in my experience, the categories are usually standard: functionality, cost, implementation, support, security, compliance, and sometimes innovation or strategic fit. The weighting varies. So even if you can't get the exact sheet, you can approximate it. Luna: So you're saying build a generic scorecard and fill in the blanks? Lucas: Exactly. I know a few top-performing reps who keep a template with 10 common categories. Before every deal, they rank their own product against the likely competition in each category. If they see a weakness — like slow implementation — they either fix it or find a way to minimise its importance. Luna: That feels like playing chess while the other side plays checkers. Lucas: It is. And the best part is, once you understand the scorecard, you can even influence the criteria. I've seen reps who, during the discovery phase, subtly educate the buyer on why a certain category matters more than they think. Luna: Give me an example. Lucas: Sure. Say you're selling a cybersecurity tool. You know procurement will weight cost heavily. So you start talking about breach recovery costs, which are often 10 times the annual subscription. You reframe the conversation from 'cheapest tool' to 'lowest total cost of ownership.' Suddenly, cost becomes less important than security coverage. Luna: So you're basically shaping the scorecard before it's written. Lucas: That's the goal. And if you do it early enough, procurement's template might even include a category your product excels at — like 'threat detection speed' — because you've convinced the business team it's critical. Luna: I want to go back to the ShiftPlan case. What about the competition? Did the rep know what scores the other vendors got? Lucas: He didn't, and that's another lesson. Procurement usually shares only your score. But if you have a strong champion, they might leak relative rankings. In this case, the rep learned that the top vendor scored 92 — but their implementation timeline was 120 days. So ShiftPlan's 75-day timeline became a differentiator. Luna: So speed trumped experience. Lucas: For that buyer, yes. And that's why you need to understand not just your own scorecard but the competitive landscape. If you know the competitor's weakness, you can highlight it in a way that changes how procurement weights the categories. Luna: This is making me wonder: how many deals are lost because of scorecard mismanagement? Lucas: I've heard estimates that 30 percent of enterprise SaaS deals that reach final procurement fail on the scorecard — even when the product is superior. It's not about the best product; it's about the product that scores highest on the buyer's specific grid. Luna: That's a sobering number. And it means a lot of reps are leaving money on the table. Lucas: Completely. And if this kind of practical insight helps you close a deal or improve your approach, honestly, if it was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. We keep the show ad-free, and listener support makes that possible. Luna: Yeah, it's a small gesture that goes a long way for us. And we really appreciate it. Lucas: So back to the scorecard — there's one more thing I want to flag. After you win the deal, don't throw the scorecard away. It's a goldmine for future sales. You can use it to refine your pitch for similar prospects. Luna: What do you mean by refine? Lucas: Well, the ShiftPlan rep now knows that retailers in that vertical care about implementation speed and data migration. So before he even meets with the next retailer, he prepares a slide deck that highlights a 75-day implementation and dedicated migration support. He's effectively pre-scoring himself. Luna: So the scorecard becomes a sales tool, not just an evaluation. Lucas: Exactly. And if you collect enough of them from different deals, you can build a playbook for each vertical. That's how you move from reactive selling to proactive selling. Luna: I love that. So the next time a rep gets a scorecard with a low score, they shouldn't panic — they should see it as feedback. Lucas: Exactly. And better yet, don't wait for the scorecard. Go find out what's on it before they hand it to you. Luna: Alright, that's a solid takeaway. Thanks Lucas. Lucas: Thanks Luna. See you next time.