We’re a Small Customer—Why Does It Feel Like Nobody Cares? The Slow Death of Trust in Enterprise Support

# “We’re a Small Customer—Why Does It Feel Like Nobody Cares?” The Slow Death of Trust in Enterprise Support ## When Silence Becomes the Loudest Answer There’s a specific kind of frustration that builds when you’re not being told “no”—you’re just not being told anything at all. That’s where this situation lives. A small non-profit, trying to do the right thing, planning ahead for a renewal, asking a simple question: what’s it going to cost to move from socket licensing to VUL? Weeks pass. Then months. Questions get asked, answers get sent back, and then… nothing. No quote. No clarity. No timeline. Just silence stretching longer than the renewal window itself. At some point, the problem stops being pricing. It becomes something much worse: a complete breakdown in trust. ## The Memory of “Better Days” What makes this hit harder is that it didn’t always feel like this. There’s a recurring tone in the conversation—almost nostalgic. “Support used to be really good,” the user says, not angrily, but with a kind of tired disappointment. That contrast matters. Because when expectations are built on past reliability, any drop in responsiveness feels sharper. It’s not just that support is slow—it’s that it used to be fast. It’s not just that communication is broken—it’s that it once worked. And that gap between past and present? That’s where frustration turns into doubt. ## The Small Customer Problem Nobody Wants to Admit Then comes the uncomfortable layer underneath everything: size. “I understand we are small compared to enterprises,” the user admits. And that one line explains more than any technical detail ever could. Because once you say that out loud, the implication is clear—you’re not the priority. No one from the company says it directly. No policy spells it out. But the experience speaks for itself. Bigger customers get faster answers. Smaller ones wait. Some replies try to soften that reality. “Find a reseller,” people suggest, almost like a workaround rather than a solution. Others even offer to escalate internally, asking for company details to push things along. But that raises a bigger question: why should escalation be necessary just to get a quote? ## The Pricing Black Box What’s striking is how simple the original request actually is. This isn’t a complex deployment issue or a deep technical failure. It’s pricing. A number. A quote. And yet, it’s treated like something opaque, almost inaccessible. One user jokes about it feeling “magical” because no one can produce it after two months of trying. Meanwhile, fragments of real numbers start appearing from others. One person casually drops: “$1800 = 10 instances.” That’s the kind of clarity the original user has been chasing—and it didn’t even come from official channels. This disconnect is where confidence starts to crack. If pricing feels like a mystery, what else is hidden behind the curtain? ## The Workarounds That Shouldn’t Be Necessary As the thread unfolds, a pattern emerges. People aren’t solving the problem—they’re routing around it. “Find a reseller.” “Try a different contact.” “Maybe something went wrong internally.” These aren’t solutions. They’re detours. And while they might eventually lead to an answer, they don’t fix the underlying issue: the system isn’t working the way it should. Even when someone from inside offers help, it feels reactive rather than proactive. A fix for one case, not a sign of a system that consistently delivers. ## The Financial Reality Nobody Can Ignore There’s also a quieter pressure running through this entire situation: money. This isn’t a large enterprise with flexible budgets. It’s a small organization trying to plan ahead, trying to understand whether the next step is affordable. “Budgets are tight,” the user says plainly. And without a clear quote, there’s no way to make a decision. Do you renew? Do you migrate? Do you leave entirely? That uncertainty isn’t just inconvenient—it’s paralyzing. Because every day without an answer is a day closer to a deadline you can’t prepare for. ## The Breaking Point Isn’t Technical—It’s Emotional What’s interesting is that none of this is about the product itself. There’s no mention of backups failing or features missing. The frustration isn’t technical—it’s relational. It’s about feeling ignored. About chasing answers that should be straightforward. About wondering if your business matters enough to get a response. And that’s where things start to break. Not in the infrastructure, but in the relationship between customer and vendor. ## So What Happens Next? This is the part nobody says out loud, but everyone understands. When support feels unresponsive, when pricing feels unclear, when communication feels one-sided—people start looking elsewhere. Not because they want to, but because they feel like they have to. Some will go through resellers and eventually get what they need. Others will wait it out and renew anyway, hoping things improve. And a growing number will take this as a signal to start evaluating alternatives entirely. Because in the end, it’s not just about cost or features. It’s about confidence. And once that’s gone, even the best product star