Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Procurement Now Requires a Technical Buyer
Transcript
- Lucas: You know that moment in an enterprise software deal where procurement hands the contract over to legal and everyone just waits? That's the classic dead zone. But there's a newer, less obvious friction point that's emerging — and it's happening earlier in the process. Luna: The technical buyer. Not just the CFO or the VP of Sales, but the CTO, the head of engineering, the person who actually has to make the software work. Lucas: Exactly. And this person is no longer a passive stakeholder who gets a demo and nods. They're increasingly the one who kills a deal or saves it. I think the shift really accelerated during the 2020 to 2023 SaaS boom, when companies were buying tools to grow at any cost. Luna: Right. Back then, if a sales rep could get a VP of Marketing to sign, procurement basically rubber-stamped it. Technical due diligence was an afterthought. Lucas: Now, with every software vendor under pressure to show efficiency, the question has become: 'What is the total cost of ownership, not just the license fee? How many engineering hours will this require to integrate? Will it create data silos?' Those are technical questions, and procurement can't answer them. Luna: So the technical buyer becomes the gatekeeper. I've heard from several mid-market SaaS vendors that their sales cycles have actually gotten shorter when they identify the technical buyer early — even though adding another stakeholder would seem to slow things down. Lucas: There's a concrete example I want to walk through. A friend of mine is VP of Sales at a company that sells a data pipeline tool — think ETL, but with a modern twist. Their typical buyer used to be a director of analytics, and procurement would handle the negotiation. Average deal cycle: nine months. Luna: Oof. Nine months in SaaS is almost a lifetime. Lucas: Right. So they started analyzing lost deals and found that the biggest single reason deals fell through was technical — the buyer's engineering team would raise objections after the contract was signed. Integration complexity, security concerns, data residency. Things that procurement never flagged. Luna: So they retrained their sales team to engage the VP of Engineering from day one. Lucas: Exactly. They stopped treating the demo as a feature walkthrough and started treating it as a technical architecture review. They built a sandbox environment where the prospect's engineers could actually test integrations with their existing stack. And they shifted their pricing from per-seat to consumption-based, because engineers hate paying for licenses they don't use. Luna: And the result? Lucas: Within six months, their average sales cycle dropped from nine months to four. And their win rate on deals where the VP of Engineering was involved from the start went up by about 30 percent. Luna: That's a dramatic shift. But I wonder — does this mean procurement is becoming less relevant? Or is their role just changing? Lucas: Their role is definitely changing. In the old model, procurement was the final gatekeeper on price and terms. Now, the technical buyer gates the deal before procurement even sees it. If the technical buyer says no, procurement never gets to negotiate. Luna: And if the technical buyer says yes, procurement's job becomes more about structuring the contract around technical requirements — data security, SLAs, exit provisions — rather than just squeezing the license fee. Lucas: Exactly. This is a really interesting trend because it forces software vendors to think about their product's integrability as a sales asset, not just an engineering concern. Luna: I want to bring this back to something you mentioned earlier — the idea that the technical buyer can actually shorten the sales cycle. That seems counterintuitive. Adding more people to the process usually makes it longer. Lucas: It does, but only if they're added serially. The vendors that win are the ones that get the technical buyer involved in parallel with the economic buyer. They basically create a dual-track process: the procurement track handles commercial terms, and the engineering track handles technical validation. Both happen at the same time. Luna: So instead of handoffs, you get parallel processing. Lucas: Exactly. And this is where the really successful vendors differentiate themselves. They don't just pitch to the technical buyer; they give them a real, usable demo environment and a clear integration playbook. They treat the engineer's time as the scarce resource it is. Luna: It makes me think about the rise of 'product-led sales' in enterprise. Companies like Slack and Zoom basically forced enterprise adoption by making the product so easy to try that the technical buyer could start using it without procurement's permission. Lucas: That's a great point. And now we're seeing that same dynamic in more complex categories — data infrastructure, security tools, developer platforms. The technical buyer is essentially the new champion, replacing the old 'executive sponsor' model. Luna: If today was worth a coffee to you, honestly, that's the link — buy me a coffee dot com slash fexingo. Keeps the show ad-free and lets us keep digging into these shifts. Lucas: Yeah, it genuinely helps. And it's the smallest ask we can make. So back to the technical buyer — what happens when the technical buyer and procurement disagree? Because that's happening more often now. Luna: I've seen cases where procurement wants a three-year lock-in for a discount, but the engineering team wants a one-year commitment because they're planning to migrate to a different cloud provider in eighteen months. Who wins? Lucas: In the deals I've seen, the technical buyer usually wins — but at a cost. The vendor often has to offer a more flexible contract, which means lower upfront revenue. But the trade-off is a faster close and a happier customer. And in the long run, that's better for retention. Luna: So the vendor's sales team needs to be able to facilitate that internal negotiation between procurement and engineering, rather than just selling to one side. Lucas: Absolutely. And that requires a much higher level of sales skill. It's not enough to be a relationship builder anymore. You need to understand the technical architecture well enough to answer questions about data residency, latency, API versioning. And you need to understand procurement well enough to structure creative commercial terms. Luna: That's a much harder hire. Most sales reps are either 'hunters' who are great at cold outreach, or 'farmers' who are great at account management. This demands both, plus technical fluency. Lucas: And that's exactly why we're seeing more vendors create a hybrid role — sometimes called a 'solutions consultant' or 'sales engineer' — who is paired with the rep from the first meeting. The rep handles the relationship and the commercial track; the solutions consultant handles the technical track. Together, they navigate both procurement and engineering. Luna: So the technical buyer trend is really driving org design changes inside the vendor, not just sales process changes. Lucas: Right. And I think it's going to accelerate. As enterprise software becomes more deeply embedded in core business processes — not just CRM and ERP, but AI pipelines, data infrastructure, cybersecurity — the technical buyer's role will only grow. Luna: One question I have: does this trend favor large incumbent vendors with established integration ecosystems, or does it level the playing field for smaller, more agile startups? Lucas: That's a great question. On one hand, incumbents have a huge advantage because they already have integrations with the major platforms. A Salesforce rep can say, 'We connect to everything.' A startup can't always say that. Luna: But on the other hand, technical buyers tend to prefer modern, api first architectures. They hate legacy bloat. A startup with a clean API and a developer-friendly experience can win over the engineering team even if the company is tiny. Lucas: Exactly. I've seen startup vendors beat Oracle and SAP in competitive evaluations simply because their integration documentation was better and their sandbox was easier to set up. The technical buyer cares about time to value, not brand reputation. Luna: So the playbook for a startup selling to enterprise is: obsess over the developer experience. Make your API documentation the best in the category. Hire a solutions consultant who used to be a senior engineer. And price in a way that makes the technical buyer look good to their CFO. Lucas: I think that's exactly right. And the vendors that do this well are going to compress their sales cycles dramatically. The ones that don't are going to find themselves losing deals they thought they had won, because the technical buyer vetoed them after procurement had already agreed on price. Luna: It reminds me of something I heard from a procurement leader at a Fortune 500 company. She said, 'I used to be the one who killed deals. Now I'm just the one who signs them. The engineering team kills them long before I see them.' Lucas: That's the new reality. And it means that if you're a software vendor, your sales process has to be built around the technical buyer from the very first touchpoint. Not as an afterthought, not as a demo at the end of the cycle, but as a core stakeholder whose needs shape the entire deal. Luna: I think that's a good place to leave it. Next episode, I'd love to dig into how this changes the way vendors think about pricing and packaging — because if the technical buyer is the gatekeeper, the pricing model has to make sense to them first. Lucas: That's a great idea. We'll do that. For now, if this resonated, you know where to find us. Thanks for listening.