Quick Summary
If your organization has a fixed IT standard, whether a vendor supports it is a plain yes or no, not a negotiation.
Standards handed down from a parent company or head office are common, and organizations benefit from communicating their non-negotiable ones to a prospective partner up front.
If you don’t have a set standard yet, that’s not a gap. It’s the point where a real advisory conversation should start.
A good partner will tell you plainly where they fit, even when the answer is that they don’t.
If your organization already has a fixed IT standard, like a required firewall vendor, a specific backup platform, or an approved hardware list, someone likely handed it to you, and it wasn’t necessarily your call. Either way, you’re not shopping around so much as checking a box: can this partner work inside the lines you’ve already got, or not? As Peter Somoya, an Enterprise Solutions Consultant at PC Corp, says, “Some customers have standards and they want to know if you can support that standard. That’s an easy answer. We either do or we don’t, yes or no.”
If you don’t have a standard, you’re dealing with a different kind of question. You know you need something, maybe networking, maybe a security upgrade, but you’re not sure exactly what to ask for or who else should be part of the conversation.
Whether you are in the first situation or the second, you’re asking the same thing: how do I figure out if a prospective procurement partner be honest with me about what they can and can’t do? This article outlines the way forward for both.
Why “Can You Support Our Standard?” Is a Yes-or-No Question
When your organization has a fixed standard, there’s no room for a sales conversation, and that’s not a problem to work around.
Maybe your cyber insurance policy names a specific endpoint detection platform, a compliance framework requires a particular logging and monitoring tool, or a franchise agreement locks every location into the same point-of-sale system.
A partner who tells you plainly that they can’t support what you need isn’t failing you. They’re giving you an honest answer that saves you time: this isn’t a fit, and that’s fine.
Contracts, certifications, and internal policy sometimes make that outcome the only one available and hearing it early on is preferable to a partner who tries to talk you out of a requirement you never had the authority to change in the first place.
A Real Standard Doesn’t Leave Room to Be Talked Out of It
When your business has a standard, it’s more than just a matter of preference, and trying to introduce an alternative is a wasted conversation for both sides. Usually your team is already trained and certified on whatever the standard is, your support relationships are built around it, and your renewal cycles assume it. Swapping vendors at that point means retraining staff and rebuilding support relationships from the ground up, which is exactly why some organizations don’t leave room to negotiate. If that’s your situation, a partner offering you three alternatives you can’t actually use isn’t being thorough. It’s a detour neither of you needed.
That same instinct, pushing you through a process instead of just answering the question, is also what separates a local partner against a national reseller. A national reseller’s account management is often standardized for consistency across regions, which is good for predictable, high-volume procurement, but it’s built to keep a deal moving through a process, not to close it out with a fast no. A local partner isn’t running that same process, so there’s less standing between you and a straight answer.
There’s a reason a real standard doesn’t need the same evaluation process other IT decisions do. Even government-facing supply chain guidance, like the framework CISA built for small and mid-sized businesses vetting IT vendors, builds in room for answers that land somewhere between yes and no. A real standard is the rare case where that gray area doesn’t exist: you don’t need a scoring matrix, or a “partial” column, to answer a question that only has two possible answers.
How a Standard Set Above You Can Cascade All the Way Down
Sometimes the standard isn’t even yours. It was set two or three layers above you, at a parent company or a head office where you don’t have a seat at the table, and it lands on your desk as something to enforce, not something you were ever asked to weigh in on. This happens more often in mid-market and multi-layered corporate structures than most people expect. A regional branch of an insurance company might be required to run the same policy management platform as every other branch nationwide, a decision made at a level the branch office never touches. A multi-location healthcare group runs into the same thing with electronic health records: every clinic uses whatever system the parent health system standardized on, whether or not the clinic’s own IT lead had any say in choosing it.
When that’s the situation, a partner offering perfectly reasonable alternatives can still end the conversation on the spot, simply because you’re not authorized to consider them. You end up saying some version of “you clearly don’t understand our requirement,” and the conversation is over before it started. That’s the real cost: time spent on alternatives your team was never in a position to accept, over a standard that was never up for debate in the first place.
If your standard came from somewhere above your own team, whether that’s a corporate parent, an acquisition that changed your compliance requirements, or a policy set by someone who left the organization years ago, that’s worth saying out loud early to a prospective partner. It changes the entire conversation, and a partner who understands that will ask about it before they ever make a recommendation.
To be clear, a partner telling you they can’t meet a standard like this isn’t a bad partner. It just means there’s no fit for this particular need, and that’s a legitimate outcome (sometimes even a contractually or legally required one), not a failure on either side.
When There’s No IT Standard, That’s Where Real Guidance Matters
Not having a fixed standard isn’t a sign you’re behind or unprepared. It’s simply a different starting point, and it calls for a different kind of conversation: one where a partner’s real value and guidance shows up instead of getting sidelined by a spec sheet.
If You Ask for Help Directly
Sometimes you know you need to buy, but you don’t know exactly what. Peter described a version of this conversation that comes up often: a customer used to buying one specific thing, like a switch, suddenly needs a whole security system with cameras attached. They know networking, but cameras are a different category entirely, and they’re not sure who else needs to be in that conversation. So they just ask outright: could you help me figure this out?
That question is what separates a vendor from an advisor. One sells you the switch you asked for. The other tells you the cameras and the network aren’t separate purchases, and makes sure both get handled by people who are actually talking to each other.
If a Partner Raises It Before You Do
Sometimes you haven’t brought up standards at all, and a good partner raises the question anyway. That’s not overreaching. It’s part of the job.
Take a request that starts small. You come in asking for a server, and by the time the conversation is done, you’re talking about the payroll system you’re deploying on top of it, the software it needs, and who’s handling the integration and training. What looked like a straightforward purchase turns into a bigger picture you hadn’t planned to lay out yet.
That’s exactly the moment worth pausing on. If a partner is going to widen the conversation like that, it’s fair to ask why their read on the whole picture should carry any weight. Peter treats that pushback as a good sign, not an inconvenience. It’s the question he says a prospective partner should always be ready to answer without flinching:
“What are you thinking, or what is it that you represent, or why should I buy it from you? What is it that you do that the other guy doesn’t do?”
That’s what separates real advisory value from a sales pitch wearing an advisor’s badge. Whether or not you’ve raised standards, or anything else, a good partner should be ready for that question before you even ask it.
And just like a fixed standard is a legitimate starting point, not having one yet is too. Neither reader is behind. You’re both just further along or earlier on the same road, and the right partner meets you wherever you actually are.
Get a Straight Answer Before You Commit to Anything
Whichever camp you’re in, a fixed standard you need a straight answer about, or no standard at all and a need for real guidance, you now know what the right answer looks like. In one case, it’s a clean yes or no. In the other, it’s a partner asking the right questions instead of pushing recommendations.
A partner who can’t be honest about a standard they can’t support wastes your time before the relationship even starts. And a partner who treats a no-standard situation as just another sale, instead of a chance to genuinely help, isn’t giving you the guidance you actually need.
Talk to PC Corp
Whether you’re locked into a standard or still deciding what’s right for your environment, we’re happy to have that conversation, the quick yes-or-no or the bigger one. Talk to PC Corp about what you’re working with, and we’ll tell you plainly where we fit.
Frequently Asked Questions
Can an IT company support our existing requirements?
It depends entirely on the specific standard and the vendor, but the answer should always be a direct yes or no. A partner who can’t support your requirement should tell you that upfront rather than trying to steer you toward something else. If they can support it, that’s a clean fit; if they can’t, that’s useful information you needed before signing anything, not after.
What happens if my IT provider can’t support our standard?
If your standard is truly fixed, especially one inherited from a parent company or head office, a partner who can’t meet it simply isn’t the right fit for that particular need. That’s not a failure on either side, and it’s often a contractually required outcome rather than a preference issue. The better outcome is finding that out in the first conversation, before either side has invested time in a relationship that was never going to work.
How do IT vendors handle companies without a set technology standard?
Without a fixed standard, the conversation should shift from selling toward advising: asking what you’re trying to accomplish before recommending anything specific. A good partner treats this as an opportunity to understand your situation properly, not as a chance to push whatever they happen to sell. If a partner skips straight to a recommendation without asking what you need first, that’s a red flag.
