Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Reps Are Now Selling to the COO
Transcript
- Lucas: So there’s this moment in an enterprise deal that a lot of reps dread—the procurement committee meeting where someone from operations shows up and starts asking about uptime SLAs, integration latency, and how the platform handles exception workflows. That person is often the COO. And increasingly, the COO isn't just attending the meeting—they're running it. Luna: That’s a big shift. For years, the COO was a stakeholder you briefed after the CIO had already signed off. Now they’re at the table from the start. Lucas: Exactly. And it’s not just a few progressive companies—we're seeing this across industries. I've been tracking deal commentary from a few large SaaS providers, and the pattern is clear: for platform deals—things like ERP, supply chain orchestration, work management—the COO is now the primary economic buyer in maybe one out of three deals, up from basically zero five years ago. Luna: What’s driving it? Is it just that software has become more operational, or is there something bigger going on? Lucas: Both. On the software side, platforms have gotten much better at handling real-time operational data—so the COO sees them as tools to run the business, not just IT systems. But on the organizational side, I think there’s a deeper trend: companies are flattening the it business divide. The COO is taking ownership of digital operations because they're the one accountable for throughput, cost per unit, and delivery speed. Luna: Right—the COO lives in those metrics. If a platform can demonstrably improve on-time delivery or reduce inventory carrying cost, that’s a direct line to their bonus. Lucas: Exactly. And that changes the sales conversation fundamentally. When you sell to a CIO, the pitch is often about security, compliance, integration with existing stack, and maybe total cost of ownership. When you sell to a COO, the pitch has to be about operational reliability, process standardization, and—this is the big one—a quantified business case tied to specific operational metrics. Luna: So the demo changes too. Lucas: Dramatically. A typical enterprise demo for a CIO might walk through architecture, admin console, API documentation. For a COO, you're showing how the platform handles a spike in order volume during peak season, how it routes exceptions, how it surfaces bottlenecks in real time. The COO wants to see edge cases—the stuff that keeps them up at night. Luna: I’ve heard reps say that COOs often ask very specific questions about the 'last mile' of a workflow—like, what happens when a supplier misses a delivery window? Does the system automatically reroute, or does it alert a human? Lucas: That’s exactly right. And if the answer is 'it alerts a human,' the COO wants to know how that human is chosen, what their SLA is, and what the escalation path looks like. These are not technical questions—they're operational design questions. And the rep needs to be able to answer them credibly. Luna: That implies the rep needs a different kind of preparation. Maybe even a different kind of rep. Lucas: I think the best organizations are starting to pair a sales rep with an operations consultant—someone who has run a supply chain or managed a warehouse. But that’s expensive. A more common approach is to train the existing sales team on operational fluency. Not just product features, but the language of throughput, cycle time, and cost to serve. Luna: Let me give a concrete example. I was talking to a logistics company—mid-sized, about $500 million revenue—and they recently replaced five point solutions with a single orchestration platform. The COO drove the entire evaluation. The CIO was involved only for security review and data migration planning. Lucas: That’s a perfect case. What was the COO’s main criterion? Luna: Reliability above all. They had a legacy system that crashed during peak hours twice in Q4 last year, causing shipping delays that cost them a major retail contract. The COO said, 'I don't care about AI features. I care about 99.99% uptime and sub-second response times under load.' Lucas: And that’s the thing—when you sell to the COO, the buying criteria are much more binary. Either the platform can handle the operational load, or it can't. There's less room for the kind of 'vision' sell that works with a CIO who is thinking about a three-year digital transformation roadmap. Luna: So the proof of value changes too. Instead of a sandbox environment where the prospect plays with features, you're running a load test against their actual production data from last peak season. Lucas: Exactly. And that’s a much higher bar for the vendor. It means you need to have done the work to ensure your platform can scale to their specific volume. It also means the sales cycle can be shorter—if you pass the test, the COO can make a decision quickly, because the pain is immediate. Luna: But what about the procurement process itself? COOs aren't typically steeped in software licensing or contract negotiation. Lucas: That’s an interesting point. In the logistics company case, the COO brought in procurement early, but they gave procurement very specific guardrails: the vendor had to meet these uptime SLAs, these response-time targets, and the contract had to include a clause for service credits if they failed. Procurement's job was to negotiate price and terms within those guardrails, not to question the technical decision. Luna: So the COO is effectively becoming the product manager for the procurement process. They define the requirements, and procurement executes. Lucas: That’s a great way to frame it. And for vendors, it means the business case document becomes more important than the feature checklist. The COO wants a one-pager that says: if you implement this platform, you will reduce order to ship time by X percent, reduce exception rate by Y percent, and deliver Z dollars in annual savings. And they will hold you to it. Luna: Which is why we’re seeing more outcome-based pricing in these deals. The vendor gets paid partly based on the operational improvement they deliver. Lucas: Right. We did a whole episode on outcome guarantees a few weeks ago, and this is exactly the context where they make sense. The COO has a measurable target, the vendor has a measurable impact—why not tie the economics to it? Luna: But not every vendor can do that. You need really good data and a mature implementation methodology. Lucas: Absolutely. And that’s the dividing line, I think. The vendors who invest in a proper business value assessment—the kind that actually models the prospect's operations—are the ones who will win the COO's trust. The ones who just bring a feature list will lose. Luna: So what’s the takeaway for a SaaS founder listening? If you’re building a tool that touches operations, should you start marketing to COOs directly? Lucas: I think you need to, but carefully. COOs don't read the same content as CIOs. They're not on Hacker News; they're at industry conferences, they read supply chain trade publications, they follow operational excellence thought leaders. Your content strategy has to meet them there. And your sales team has to speak their language. Luna: One thing that stood out to me in the logistics company story is that the COO actually asked for reference calls with other COOs who had implemented the platform. That's rare for enterprise software—usually references are with IT peers. Lucas: That’s a great sign that the buyer is the COO. They want to hear from someone who sat in their chair, made the decision, and saw the results. So vendors should be building a reference network of COO champions, not just IT directors. Luna: And that network takes time to build. You can't just ask your first COO customer to take five calls a month; you have to nurture that relationship. Lucas: For sure. But if you're early in your journey, even one strong COO reference can be a game-changer. It validates the entire thesis. Luna: This is the kind of practical, on-the-ground insight that makes these conversations useful for what you're building or running. If you're finding value in this show and want to help keep it ad-free and independent, you can support us at buy me a coffee dot com slash fexingo. No pressure, just a simple way to say this content matters to you. Lucas: Totally. And speaking of practical—let's talk about how the demo itself needs to change when the COO is in the room. I've seen a few really good examples of reps who restructured their entire demo flow around operational scenarios. Luna: Give me the best one. Lucas: There's a rep I know at a work orchestration platform—they sell to both IT and operations. When the COO is the primary, he starts the demo by saying, 'Let me show you how this platform handles a typical Tuesday morning in your business.' He pulls up a dashboard that shows order intake, inventory levels, and staffing. Then he introduces a disruption—a supplier delay—and shows how the platform automatically reassigns work, alerts the right people, and provides a new estimated completion time. It's narrative, not technical. Luna: That's smart. He's showing the COO the system's behavior under stress, not its architecture. Lucas: Exactly. And he follows up with a simple business case: how much does that disruption cost you today? How many manual calls and emails does it take to resolve? The platform reduces that by a certain percentage. The COO can immediately calculate the value. Luna: So the key is to map the software's capabilities directly to the COO's operational metrics. Cycle time, first-pass yield, cost per transaction, employee utilization. Lucas: Right. And to be honest about where the platform doesn't fit. If a COO asks about a specific workflow that your product doesn't handle well, the best reps acknowledge it and explain how they'd address it—maybe through a partner integration or a roadmap item. That builds credibility. Luna: It also sets realistic expectations. The last thing you want is a COO who bought based on a demo that didn't match reality. Lucas: And that’s the risk when you sell to an operational buyer. They are unforgiving if the software doesn't deliver. A CIO might tolerate some rough edges if the long-term vision is solid. A COO will not. If the platform crashes during go-live, you lose the account and your reputation in that industry. Luna: So the bar is higher. But the reward is also higher—coo led deals tend to be larger, faster to close, and stickier, because the software becomes embedded in daily operations. Lucas: Exactly. And that’s why I think this trend is only going to accelerate. As software eats more of the operational world, the COO will become the default buyer for a whole category of enterprise platforms. Smart reps are already adapting. Luna: It feels like the old divide between 'business' and 'IT' is finally collapsing. The COO is the proof. Lucas: Absolutely. And for anyone building or selling enterprise software, the question to ask yourself is: would your product survive a demo where the COO runs the agenda? If not, you've got work to do. Luna: Great place to leave it. Thanks, Lucas. Lucas: Thanks, Luna. Catch you next time.