Our procurement team negotiated a solid contract with a major SaaS vendor last year. Good pricing, reasonable terms, standard enterprise SLA.

Six months later, we weren’t getting the support we needed. Tickets sat unresolved. Our account manager changed three times. Feature requests disappeared into a void.

The contract was fine. The relationship was broken. And procurement couldn’t fix it because they’d moved on to the next deal.

Procurement Optimizes for Contract Terms

That’s their job. They’re measured on cost savings, contract compliance, and risk mitigation. They’re excellent at negotiating pricing, payment terms, and legal protections.

What they can’t do is manage the ongoing relationship that determines whether you actually get value from the contract.

A vendor might commit to 99.9% uptime in the SLA. But when you have an outage, whether they mobilize their best engineers or stick you with tier-1 support depends on the relationship, not the contract.

IT Needs to Own the Strategic Vendor Relationships

For your critical vendors - the ones running core systems or enabling major initiatives - IT leadership needs direct relationships with vendor executives.

I’m talking about quarterly business reviews with their VP of Customer Success, direct access to their product team, relationships with their technical account managers.

This can’t be mediated through procurement. You need to be able to call someone at the vendor and say “this isn’t working” and have them actually care.

The Account Manager Churn Problem

Our CRM vendor has changed our account manager four times in two years. Each time, we lose institutional knowledge. The new person doesn’t know our environment, our history, or what promises the previous person made.

You can’t prevent turnover, but you can build relationships above the account manager level. When they change, the relationship with their director or VP continues.

That continuity is worth more than any contract clause procurement can negotiate.

Technical Escalations Don’t Follow Contracts

We had a production issue with our authentication provider at 2am on a Saturday. The SLA said we’d get a response within 4 hours for P1 tickets.

We got a response in 20 minutes because our platform architect had the mobile number of their senior solutions engineer and they’d worked together on our implementation.

No SLA in the world is better than actual relationships with people who can help.

Roadmap Influence Requires Relationship

If you want your feature requests to actually get built, you need more than a customer success manager filing tickets on your behalf.

You need the kind of relationship where you’re talking to their product team directly, participating in their customer advisory board, getting previews of upcoming features.

Some vendors brought in custom AI development specialists to help them build features we’d requested. That happened because we had strong enough relationships that they took our requirements seriously, not because our contract required it.

Procurement Can’t Save a Bad Relationship

I’ve seen IT teams try to fix vendor problems by involving procurement to “enforce the contract” or “renegotiate terms.”

Sometimes that works. Often it just makes the relationship more adversarial.

If your vendor isn’t performing, the first step isn’t threatening them with contract clauses. It’s understanding why the relationship broke down and whether it can be fixed.

Maybe they don’t understand your use case. Maybe they’re underwater with other customers. Maybe your account is too small to prioritize.

None of that gets fixed by procurement sending stern emails.

Build Relationships Before You Need Them

Don’t wait until you have a crisis to try establishing a relationship with vendor leadership.

When things are going well, that’s when you invest in the relationship. Provide case studies. Participate in their user conferences. Give constructive feedback on their product.

Build enough goodwill that when you need help, they’re motivated to provide it.

Some Vendors Don’t Want Deep Relationships

Not every vendor operates this way. Some have a pure self-service model where there’s deliberately no relationship to manage.

That’s fine for commoditized services. It doesn’t work for strategic systems where you need partnership, not just provisioning.

During vendor selection, evaluate their willingness to invest in customer relationships. Talk to their existing customers about whether the vendor is responsive when things go wrong.

Multi-Vendor Integrations Require Coordination

We use six different vendors for our customer data platform stack. When something breaks, it’s often at the integration boundary between two systems.

Both vendors will claim it’s the other’s responsibility. Your contract with each vendor doesn’t help because the issue is between them.

You need relationships strong enough to get both vendors on a call together to troubleshoot. I’ve had to facilitate these calls because neither vendor wanted to point fingers, but only because I had working relationships with both.

Procurement Should Focus on Risk and Compliance

I’m not saying procurement shouldn’t be involved. They should own:

• Contract renewals and negotiations
• Compliance with procurement policies
• Financial risk assessment
• Legal terms and liabilities

But the operational relationship - the “are we getting value from this vendor” question - has to sit with IT.

We have monthly check-ins with procurement about our strategic vendors. They flag contract milestones, we flag relationship issues. It works because everyone knows their role.

Vendor Relationships Are IT Assets

Your relationship with your major vendors is as much an asset as the software they provide.

When leadership asks why we’re staying with a vendor despite higher pricing, part of the answer is “we have strong relationships that give us preferential support and roadmap influence.”

That’s hard to quantify, but it’s real value. Procurement understands pricing. IT needs to help leadership understand relationship value.

Build those relationships deliberately. They’ll matter more than contract terms when you actually need help.