Gary Miller here, and sometimes I miss when you could just walk into someone’s office and draw on a whiteboard instead of sharing screens through three different security platforms.
So I’m on this Zoom call last month with a manufacturing company – $500K deal, enterprise software deployment, the kind that makes your quarterly numbers look respectable. The IT director, let’s call him Dave, starts the call with “We’re very interested in your platform, but we absolutely cannot put our data in the cloud.”
Fair enough. On-premise deployments aren’t dead, just more expensive and complicated. But then Dave continues: “However, we need our sales team to access this from mobile devices when they’re traveling, and our remote workers need full functionality from home.”
I’m thinking, okay, VPN setup, maybe some kind of secure gateway. I start explaining our on-premise mobile access options when Dave drops the real bomb: “Oh, and we want automatic updates and the same uptime guarantees as your SaaS customers.”
The silence on the Zoom call was deafening. My solution engineer, bless her heart, jumps in and starts explaining how on-premise means they’re responsible for their own infrastructure, maintenance, security patches – the whole nine yards. Dave’s response? “But your cloud customers don’t have to worry about that stuff.”
Exactly, Dave. That’s literally the point of the cloud.
We spent the next forty-five minutes in what I can only describe as a technical philosophy debate. Dave wanted cloud benefits – scalability, automatic updates, 99.9% uptime, mobile access, seamless integrations – but with on-premise deployment because “the cloud isn’t secure.” When our solution engineer mentioned that our cloud platform has SOC 2 compliance, enterprise-grade encryption, and better security than most on-premise setups, Dave said, “Yeah, but it’s still the cloud.”
The real kicker came when Dave asked about API integrations with their existing tech stack. Turns out, half their current platforms are cloud-based SaaS tools. Their CRM? Salesforce. Their communication? Slack and Teams. Their document storage? You guessed it – cloud-based. But our enterprise software? That had to stay on-premise for “security reasons.”
I tried one last approach: “Dave, what if we set up a hybrid deployment? Core data on-premise, but with cloud-based access layers for mobile and remote users?” His response was immediate: “That sounds complicated. Can’t you just make the on-premise version work like the cloud version?”
The deal died in committee three weeks later. The Slack thread with my team went quiet after we heard they went with a competitor who apparently promised them everything they wanted. I’m genuinely curious how that implementation is going.
You spend years learning about APIs, integrations, security protocols, and deployment models, but sometimes the real challenge is explaining why you can’t have your cake and eat it too. And that’s enterprise software sales in 2025 for you.
Leave a Reply