Your vendor rep just left. 
​Everything they knew about you went with them.

You finally got your telecom environment documented. The rep who set it up knew your architecture, your quirks, your pain points. Then you get an email: "I wanted to let you know I've moved into a new role..."

Meet your new rep. They have your account number and a copy of your last invoice. That's it.

The real challenge

Most businesses treat this as a minor annoyance. It isn't. When a vendor rep turns over, you don't just lose a contact. You lose the accumulated context of every conversation, every workaround, every escalation that ever got resolved. The new rep starts at zero. You pay for the catch-up in time, repeated explanations, and stalled projects. Call it the continuity tax.

The vendor's org chart changed. Your multi-year contract did not.

That's not a singular instance of assistance. That's what continuity actually looks like.

What you can do about it

• Map your own environment before the next rep arrives. Keep a living document of your architecture, contract provisions, escalation contacts, and any open issues. Don't rely on the vendor to hold this.
• Ask your new rep to confirm what they know before the first call ends. If they can't describe your setup accurately, you're starting over. Set that expectation early.
• Treat every renewal as a reset moment. Rep turnover tends to cluster around contract cycles. A renewal negotiated by someone who doesn't know your environment is a negotiation you'll lose.
• Build one relationship that doesn't turn over. The structural fix is having a permanent point of contact on your side of the table, someone who carries your tribal knowledge regardless of what happens inside any vendor's org. That person remembers the wiring issue from 2019, the escalation that took three weeks, and the clause you negotiated into the last contract.

Vendor reps get promoted, reassigned, and poached. That's the nature of the business. Your environment doesn't change when they depart. Your advocate shouldn't either.

Why this compounds

Over a typical five-year infrastructure lifecycle, a mid-sized business will cycle through multiple reps at each carrier or platform vendor. Every handoff costs time. Some cost more. The businesses that manage this best aren't the ones with the best vendors. They're the ones with the best memory.

After 15 years of sitting on the client's side of the table, this is one of the most consistent sources of friction I see. It's quiet, it's recurring, and it's almost entirely preventable.

If you've never taken stock of how much context lives inside a vendor relationship you don't control, that's worth 15 minutes.

Ask for your IT Procurement Readiness review

What's your current system for documenting vendor relationships and architecture? Curious what's working out there.