Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Prospects Are Asking for Reference Calls
Transcript
- Lucas: So you're in late-stage talks with a mid-market manufacturer. They've seen the demo, they've reviewed the security questionnaire, they've even signed a mutual action plan. Then the procurement lead says, 'We need three reference calls with companies in our industry that went live with your platform in the last eighteen months.' Luna: And they don't just want names and phone numbers. They want a structured conversation, specific questions, maybe even a shared agenda. Lucas: Exactly. That's the phenomenon we're seeing more of this year. The standard 'here are two logos and a testimonial' approach is getting pushed back. Buyers want to talk to peers who've actually done the implementation, not the hand-picked happy customers. So today we're going to look at how one mid-market CRM vendor I'll call FieldSync handled exactly this situation. Luna: FieldSync — is that a real company? Lucas: It's a composite, but based on a real scenario I heard from a sales leader at a company that does around fifty million in annual recurring revenue. They sell into manufacturing, logistics, and field services. Their typical deal is between fifty thousand and two hundred thousand dollars annually. And last quarter they had a prospect — let's call them Precision Parts — that was ready to sign, until procurement stepped in. Luna: And the procurement team asked for references that matched their industry and company size. Lucas: Not just matched. They wanted three specific companies: one that had gone live within the last six months, one that had been live for about a year, and one that had migrated from a legacy system. They also asked for contact information for the project sponsor, not just the executive champion. That's a level of detail that caught the FieldSync team off guard. Luna: So how did they respond? Did they just hand over names? Lucas: They almost did. The initial instinct was, 'Sure, we have happy customers, here you go.' But the sales engineer on the deal — smart person — said, 'Wait, let's prep our references first.' They didn't want to put a customer on the spot without knowing what questions would come. So they created a reference call brief: a one-pager with talking points, common objections, and the specific value metrics that mattered to Precision Parts. Luna: So they coached the references on what to say? Lucas: Not exactly. They didn't script them. They briefed them. They said, 'You're going to talk to a manufacturing company considering our platform. They'll likely ask about implementation timeline, integration complexity, and ROI. Here's what we've told them so far. You don't need to defend us — just tell your truth.' And then they scheduled a prep call with each reference individually. Luna: That's interesting because it shows respect for the reference's time and also protects the vendor from a bad call. But what if the reference has a negative experience to share? Lucas: That's the risk. And in this case, it happened. One of the three references — the one that had migrated from a legacy system — mentioned that their data migration took three weeks longer than planned, and that they had to hire a temporary consultant to fill the gap. That was a honest moment. Luna: And that could have killed the deal. How did FieldSync handle that? Lucas: They didn't try to spin it. The sales rep on the call acknowledged the delay and explained what they had learned from that project and what process changes they had made since. They had a documented improvement: they now assign a dedicated migration specialist for any deal over a certain size. The procurement team actually appreciated the transparency. The reference being honest made FieldSync more credible, not less. Luna: So the honest reference call actually became a trust builder. That's counterintuitive. Lucas: It is. But there's data backing this. A 2025 study from Gartner showed that enterprise software buyers who conduct structured reference calls are twenty-three percent more likely to sign, compared to those who only read case studies. But the key word is 'structured.' If the buyer just gets a name and a number, the call tends to be superficial. When both sides prepare an agenda, the signal is stronger. Luna: And what about the procurement team's role in this? Are they the ones driving the structured call? Lucas: Increasingly, yes. Procurement is getting more sophisticated. They have templates for reference calls now. I've seen procurement teams at large manufacturers send a list of ten questions in advance — things like 'What was the biggest challenge during implementation?' 'How long before you saw measurable ROI?' 'Would you choose this vendor again?' They treat it almost like a supplier audit. Luna: So vendors need to prepare their references to answer those questions honestly, not just give a testimonial. Lucas: Right. And the best vendors also ask their references for feedback after the call. What did the prospect ask? How did you feel about the conversation? That feedback loop helps them improve their reference program. FieldSync started doing that after the Precision Parts deal. Luna: And did Precision Parts end up signing? Lucas: They did. But it took another two weeks of negotiation on contract terms. The reference calls didn't close the deal, but they removed a major roadblock. The procurement lead told FieldSync afterward that the calls were the deciding factor in moving forward. Luna: So the real takeaway is that vendors should treat reference calls as a formal part of the sales process, not an afterthought. Prep the references, expect hard questions, and use the honesty to build trust. Lucas: Exactly. And if you're in enterprise software sales, you should also consider asking your own customers for permission to use them as references proactively. Don't wait for a prospect to ask. Build a reference pool that's diverse: different industries, different company sizes, different implementation timelines. That way you're ready when procurement comes knocking. Luna: It's a bit like building a bench of spokespeople for your product. They need to be trained, prepared, and willing to tell the real story. Lucas: Yeah. And speaking of willing — I want to mention something here. If you're finding these conversations useful for what you're building or running, listener support is what keeps this show ad-free and focused on practical topics like this. There's a page at buy me a coffee dot com slash fexingo where people can chip in if the content is adding value. Luna: Yeah, it's a small way to keep the lights on and the episodes coming. No pressure, just if it's helpful. Lucas: Alright. So back to reference calls. One thing I want to highlight is that not all references are created equal. FieldSync learned that references who were involved in the actual implementation carry more weight than references who only use the product day-to-day. Procurement teams want to talk to the person who dealt with the data migration, the integration, the change management. Luna: So the project manager or IT lead is more valuable than the VP of Sales who just loves the dashboard. Lucas: Exactly. And that means vendors need to cultivate relationships with those operational users. They're often the ones who can speak to the real effort and the real outcomes. FieldSync started a quarterly reference advisory board where they bring together implementation leads from different customers to share best practices. It builds a community and gives them a pool of ready references. Luna: That's a smart long-term play. It also makes the reference feel valued, not just used. Lucas: Right. And the other trend I'm watching is that some procurement teams are now asking for recorded reference calls. They want to listen to the conversation afterward, or share it with stakeholders who couldn't attend. That creates a new dynamic — the reference knows they're being recorded, so they might be more guarded. But it also means the call has to be even more structured and professional. Luna: Has FieldSync done any recorded calls? Lucas: Not yet, but they've had requests. Their legal team is working on a consent form. It's a delicate area. You don't want to put a customer in an awkward position. But if the buyer wants it, you have to figure out a way. Luna: It seems like the bar for enterprise software deals keeps rising. Between security reviews, value engineering, mutual action plans, and now structured reference calls, the sales cycle is getting longer but also more rigorous. Lucas: It is. But the upside is that when a deal closes after that kind of vetting, the implementation tends to go more smoothly. There are fewer surprises. The buyer knows what they're getting into. And the vendor knows the buyer has realistic expectations. That's good for retention. Luna: So the reference call isn't just a hurdle. It's an alignment tool. Lucas: Exactly. And that's the way to sell it internally. If your sales team is pushing back on reference calls because they slow down the deal, remind them that a well-run reference call reduces the risk of a post-sale churn. It's an investment in the relationship. Luna: Alright, Lucas. So for our listeners who want to improve their reference call process, what's one actionable step they can take this week? Lucas: Review your current reference list and categorize each reference by industry, company size, implementation role, and deal value. Then identify gaps. If you're selling into manufacturing but all your references are from retail, you have a problem. Start asking some of your manufacturing customers if they'd be willing to take a call. Offer them a small incentive — maybe a gift card or a feature preview. Build that bench before you need it. Luna: And for procurement teams listening — what's your advice? Lucas: Come with a structured agenda. Don't just ask 'Are you happy with the product?' Ask specific questions about implementation time, integration pain points, support responsiveness, and actual business outcomes. And if the vendor seems unprepared for the call, that's a red flag. A vendor that respects the reference call process is likely a vendor that respects the customer relationship. Luna: That's a good place to leave it. Thanks, Lucas. Lucas: Thanks, Luna. That's all for today's episode of B2B SaaS Talks.