Quick Summary
A good IT partner deliberately narrows its vendor list instead of representing every brand available, and that focus is what makes deep expertise and fast support possible.
Focused partners choose vendors through a defined process, often a cross-functional group weighing technology, support quality, and relationship strength, not one salesperson’s preference.
Comparable hardware from competing manufacturers tends to perform about the same. The real differences appear in price fairness, support speed, and how fast a partner can fix things when something breaks.
Ask any partner two questions before you sign: how do they handle their mistakes, and do they talk about your relationship as a partnership or a transaction?
By the time you’re finalizing a shortlist of IT partners, you’ve likely already done the obvious work: comparing pricing, checking technical fit line by line, confirming certifications. That’s the right first pass, and most buyers stop there because it feels thorough.
None of that tells you how any of these partners decided which manufacturers to represent in the first place. That decision, made long before you ever saw a proposal, shapes the price you’ll pay, the support you’ll get, and how fast problems get resolved once you’re a customer. Jeffrey Jansen, Vendor Relationship Officer for PC Corp put it plainly: “we really focus on our partners, and we’ve got great relationships with them because we tend not to be a treat of the week.” What follows is what that kind of deliberate selection actually looks like from the inside, and what to ask about it before you sign anything.
Why Focus Beats Breadth
If a partner isn’t chasing every vendor on the market, the obvious question is what are they doing instead. The answer, at a well-run partner, is a narrow, deliberately chosen list, built and maintained with purpose.
This starts with structure, not preference. Rather than one salesperson deciding who to sell, a defined group who understands our business and our target customers typically owns the decision: We focus on a certain small subset of vendor partners within PC Corp. We would have a matrix where we identify our partnerships for each different product category, whether it’s endpoints, printers, network, firewalls, servers, or storage. That matrix means every technology category has its own short list of vetted manufacturer options.
Who builds that list matters as much as the list itself. A cross-functional group, rather than a single technical individual, typically makes the call: we use our technology steering committee, comprised of people from sales, from technical, and from leadership, to gather information from all different areas and choose who our partners are going to be. That’s a standing structure built specifically to keep the vendor list narrow and deliberate. We go deeper on this in the difference between a local IT partner and a national reseller, since a wide network built on real relationships serves you differently than a broad one built on volume.
What the Committee Is Actually Weighing
A narrow list only helps you if the criteria behind it is right. Understanding what factors a steering committee weighs gives you a much sharper set of questions to bring to your own evaluation.
Technology on its own rarely settles the decision: “it’s not always based on just who has the best technology, but who’s got the best technology, who’s got the best support, and where do we have the closest ties?” Comparable hardware from competing manufacturers tends to perform similarly. A server from one major brand and a server from another will generally hold up comparatively under the same workloads.
If the underlying technology is roughly similar, the real differentiators are the ones a spec sheet doesn’t capture: whether the price reflects fair value, whether support actually shows up when you need it, and how close the relationship is between your partner and the manufacturer behind the product. This translates directly into what happens when something breaks. A tight relationship means faster escalation paths, more flexibility when a fix falls outside the standard playbook, and a partner who can pick up the phone and get a real answer instead of opening a generic support ticket and waiting.
The Payoff of Real Vendor Relationships: What Tight Ties Mean When Something Goes Wrong
Relationship depth sounds abstract until something goes wrong. A partner with real relationship depth can answer three questions on your behalf before you ever ask them:
- Where do we know we can get a fair price for the customer?
- Where do we know we can get the proper support for the customer in case something goes wrong?
- Where do we have those trusted relationships that if there’s one of those moments that everybody dreads, we can resolve it?
Price, support, and speed of resolution: that’s the concrete payoff of a deep vendor relationship, and none of it shows up in a product brochure or a spec comparison.
The scenario that matters most here is the one you hope never happens: a vendor discontinues a product line, gets acquired, or drops the ball on a critical issue. A partner with a shallow, transactional relationship to that vendor has less leverage to get you a fast answer. A partner with genuine relationship depth, the kind built through a deliberate matrix and a standing steering committee rather than a single person’s contact list, has somewhere to escalate and someone who’ll actually take the call.
What This Means for You as a Client Choosing an IT Partner
Everything above points to a single practical test you can run in your next partner conversation: ask how they choose the vendors they represent. If they can’t describe an actual process, a defined group of criteria, or some kind of standing structure, that’s a signal about how the rest of the relationship will probably run too.
If they can describe a real process, listen for two more things beyond the process itself. First, how do they talk about handling their own mistakes? With long-term relationships, the goal is always to do right by the client. If something goes wrong, a good partner is upfront about it. That honesty is what builds trust and turns the relationship into a collaboration instead of a sales pitch. A partner who volunteers this, unprompted, is telling you something real about how they’ll handle the moment your relationship gets tested.
Second, listen for whether they describe the relationship as a partnership or a transaction. According to Jeffrey, “that’s really the secret sauce: having an open, honest, transparent relationship with everybody involved, and trying as much as possible to see it as a partnership.” A partner who talks this way is telling you to expect an advocate inside the vendor relationship, not just a supplier on the other end of a purchase order. This kind of process is exactly the layer of diligence that most organizations miss when evaluating an IT partner, since pricing and technical fit are easy to compare, and vendor selection philosophy usually isn’t.
Structure alone doesn’t guarantee a perfect track record. Even a deliberate, well-run process runs into situations where things don’t go as planned. What separates a genuinely reliable partner from a merely well-organized one is what they do in those moments, which is exactly why “how do you handle mistakes” belongs on your question list right alongside “how do you choose vendors.”
Frequently Asked Questions
How do IT partners decide which vendors to work with?
A deliberate IT partner typically uses a defined, cross-functional process rather than one person’s preference. This is often a standing group with representation from sales, technical staff, and leadership, evaluating vendors category by category against specific criteria like technology, support quality, and relationship depth.
Does it matter how many vendors my IT partner represents?
Yes. Deep vendor relationships are difficult to maintain when a partner represents dozens of vendors across every category, and that limits the leverage available when you need fast support or an escalation. A partner working from a narrower, deliberately chosen list is more likely to have real influence with the manufacturers behind your technology.
What should I ask an IT partner about their vendors?
Ask how they decide which vendors to represent, and whether that decision comes from a defined process or an individual relationship. Talk to them about processes when a vendor drops the ball or a product gets discontinued. Have them describe a time they made a mistake with a client and how they handled it, since that answer tells you as much as anything about how the relationship will run.
Before You Sign, Ask This One Extra Question
Vendor selection isn’t a detail to be overlooked. It directly shapes the price you’ll pay, the support you’ll receive, and how fast a problem gets fixed, all of which matter more once you’re a customer than they did during the pitch.
A partner with a deliberate, criteria-based process for choosing vendors helps customers reduce risk, improve solution quality, and gain confidence that recommended technologies align with their business. That difference is invisible on a spec sheet and easy to miss if you stop your diligence at price and technical fit, which is exactly where most evaluations end.
If you’re evaluating an IT partner and want to know more about how they choose the vendors they represent, that’s a conversation to have before you sign anything. Connect With Us.
