Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How Asking for a Success Metric Turned a Skeptic into a Buyer
Transcript
- Lucas: So we've all been there — a deal that feels done, the champion is on board, and then it hits procurement and just… sits. Today I want to talk about a rep who pulled it out of the ditch by asking for something most of us would never think to ask for: the buyer's definition of success. Luna: Like, a success metric? Not a discount, not a meeting, not a no for now? Lucas: Exactly that. And before we get into the weeds — if this conversation has moved your work forward in any small way, the reason it stays free and ad-free is listener support. If that's been useful to you, the way to keep that going is to buy me a coffee dot com slash fexingo. It costs less than a latte, and it genuinely keeps the lights on here. Luna: And honestly, if this episode gives you one line to use in the next quarter, that's the cost of a coffee well spent. Lucas: So here's the deal. It was a mid-market software company, about four hundred employees. The rep had been chasing them for six months. The product fit, the budget was there, but the deal kept stalling in the final procurement review. The champion on the inside kept saying 'almost there,' but nothing moved. Luna: That's the classic stall. What changed? Lucas: The rep stopped pushing the ROI spreadsheet and asked a different question. Instead of 'what's your budget' or 'what's the timeline,' she asked the head of operations directly: 'What does success look like for you ninety days after we go live?' Luna: And that got them talking? Lucas: It got them talking, but not the way you'd expect. The ops head didn't give the answer she wanted. He said, 'Honestly, I don't think this is going to work. My team is already stretched thin, and I don't see how this integrates without breaking our monthly close.' That was the first time anyone had said that out loud. Luna: So by asking for the success metric, she surfaced the real objection. The hidden skeptic. Lucas: Exactly. And that's the move. So many reps are afraid to ask anything that might open a can of worms, so they never learn what the actual blocker is. But this rep leaned in. She asked him to be specific about what success would look like — what number, what process, what change. Luna: Did he give her a number? Lucas: He did. He said, 'If we could reduce the time it takes to close our monthly books from twelve days to eight, that would be a win. But I don't think your software does that.' And that was the gift. Because now she had a concrete target and a specific doubt. Luna: And she could address the doubt directly. Lucas: Right. She brought in their implementation lead, ran a small proof of concept with the ops team, and they showed how the integration would actually shave those four days by automating the reconciliation step. Not a generic 'we'll help you be more efficient' — a specific 'here's how we get you from twelve to eight.' Luna: So the success metric became the north star for the whole sales process. Lucas: It did. And it changed the conversation from price and features to a shared goal. The procurement team could see that the software was tied to a measurable outcome they cared about. The champion could justify it internally because he had a metric, not just a gut feeling. Luna: And the deal closed. Lucas: Closed in about three weeks. But the real lesson isn't that asking for a success metric is a magic bullet. It's that it forces the buyer to be specific about what they actually need, which either surfaces a real objection you can address or reveals that they don't have a clear definition of success. Luna: And if they can't define success, is that a red flag? Lucas: I'd say it's a yellow flag. It could mean they're not the real decision-maker, or that the project isn't a priority. But it's also an opportunity to help them define it — which positions you as a partner, not just a vendor. You can say, 'Let's think through what success would look like together.' Luna: But isn't there a risk they give you some vague, unmeasurable thing like 'improve customer satisfaction'? Lucas: Then you ask for the metric behind it. 'What would satisfaction look like in numbers — a Net Promoter Score shift? A retention rate? A response time?' You keep drilling until you get to something that can be measured, because if it can't be measured, you can't sell it. Luna: So the question is really a discovery tool disguised as a closing technique. Lucas: That's a great way to put it. And it works in the later stages, too. I've seen reps use it in the final proposal review, when the legal team is nitpicking. One rep asked the CFO: 'What's the one thing that would make this deal a clear win for you?' And the CFO said, 'Honestly, I need to see that our service costs drop by fifteen percent by Q4.' That reframed the negotiation from price per seat to a target the rep could actually commit to. Luna: And then they could structure the contract around that outcome, maybe with a performance clause. Lucas: Exactly. That's when you move from being a vendor to being a strategic partner. And it also helps you know when to walk away. If the buyer defines success as something your product can't deliver, you need to know that before you sink another three months into the deal. Luna: So what's the exact wording? 'What does success look like in ninety days?' Lucas: That's a good one. But I'd vary it based on the stage. Early on, you might ask 'What problem are you hoping this solves, and how would you know it's solved?' Later, 'What's the one metric that, if it moved, would make this a no-brainer?' And in the final stage, 'If we could guarantee this one outcome, would you be ready to move?' Luna: But doesn't that come across as pushy if you ask for a commitment too early? Lucas: You don't ask for the commitment in the same breath. You ask for the metric first, listen, and then later you can say, 'You told me success looks like reducing your close time to eight days. If we can show that in a pilot, is there anything else standing in the way?' That's a powerful check-in because it's based on their own words. Luna: And it makes the buyer feel heard, which never hurts. Lucas: Never. But there's a trap I want to flag: don't ask for the success metric and then ignore it. If they say 'reduce churn by ten percent' and you come back with a proposal that doesn't mention churn, you've broken trust. You have to tie everything back to that metric. Luna: So the whole sales process becomes a project around one shared goal. Lucas: That's exactly what separates the good reps from the great ones. The great ones use the success metric to build a narrative. They can say, 'Here's where you are today, here's where you want to be, and here's the bridge we're building together.' That's a much more compelling story than 'Our software does X, Y, and Z.' Luna: And it's harder for a competitor to replicate, because it's tied to their specific situation. Lucas: Right. Anyone can copy a feature list. But if you've co-defined success with the buyer, you've created a relationship that's not easily replaced. And that's really the goal of any sales conversation — to make yourself indispensable. Luna: So what's the one takeaway you'd leave our listeners with? Lucas: Next time you're in a deal that's stuck, don't ask for a discount or a meeting. Ask for the metric. Ask the buyer to define what success looks like in a measurable way. It might be the most uncomfortable question you ask — but it's also the one that could unstick the whole thing. Luna: That's a good line to leave with. I'm going to try that one in my next negotiation. Lucas: Let me know how it goes. And if you want to share your own success-metric story, we'd love to hear from you. For now, that's the close for today.