The Vendor You Can’t Get on the Phone

You know the assessment. Three of their best people. The senior partner, the technical lead, somebody from operations. Sharp slides. Specific questions about your business. They named your competitors. They knew your industry. They had the case studies. You signed. You felt good about the signing.

And then, somewhere around month two, the relationship went quiet.

The senior partner you signed with stopped being on the calls. The technical lead from the assessment, you haven’t seen since. The person you actually got was a level-two tech who joined six weeks ago and is friendly enough but has never been on your sites and doesn’t know which of your three vendors is actually load-bearing for the quarterly close.

Then something broke. Real break. Field crew couldn’t log in on a Tuesday morning. You called. Voicemail. You emailed. Ticket generated. Two hours later you got a response, except the response was an explanation of why the issue probably wasn’t their problem - it might be a Microsoft thing, or it might be your network, or it might be something with how the application was configured originally, which was before they took over, so they’d need to investigate further, which would be billed.

That’s the moment. That’s the moment you knew you’d hired sharp pre-sale and ghost post-sale, and you were going to be paying for the difference for the next twenty-two months of the contract.

The 90-day fade is structural, not accidental

The reason this pattern repeats isn’t that the firm hired bad people. The people are usually fine. The pattern repeats because the firm is structured to sell hard and deliver soft.

The senior people are paid on revenue, not on delivery. They have an incentive to be in your assessment and a structural incentive to not be on your week-twelve operations call. The delivery team is a different team, a less expensive team, and a team that wasn’t in the room when the promises got made.

None of that is illegal. Plenty of firms run it that way. Just don’t mistake it for a bad-luck story. It’s the system working exactly the way it was built to work.

What “they don’t know your business” actually costs

The tax shows up in three places, and operators usually feel it before they can name it.

Every ticket starts at zero. The tech who picks up doesn’t know that your accounting close is the last week of every month and that you can’t take an ERP system down between the 25th and the 31st. They don’t know that the field office in Whitecourt is on a different connection than the office in Calgary. They don’t know which of your three contracted geologists has admin access to the GIS environment and which doesn’t. So the first hour of every call is them learning, and you’re paying for that hour every time.

Nothing gets ahead of you. Built-in IT looks at your environment between Tuesdays and notices the backup that failed silently, the certificate that’s about to expire, the user who’s about to lose access because their license assignment never got finalized. Bolted-on IT waits for you to call. By the time you’re calling, you already have a problem.

The vendor strategy drifts. Without somebody actually watching your stack, you accumulate. A second backup tool because the first one is unreliable and nobody wants to fix it. A third firewall because the second one is misconfigured and nobody wants to touch it. Six months later you’re paying for three things when one would do, and the MSP isn’t flagging it because the MSP doesn’t know what’s in your environment.

The opposite shape

What does accountability actually look like? Three things, and you can verify all three in a single call with any provider you’re evaluating.

The same senior tech is on your account for the life of the relationship. Not a partner who sold and disappeared. The actual technical lead who understands your environment, who’s been on your sites, who knows your three vendors and which one is load-bearing. If the answer to “who’s on the account” is “you’ll be assigned a technical account manager,” ask who, by name, and how long they’ve been on it.

The phone gets picked up. Not a ticket portal. A phone. With a name on the other end who already knows your business. That’s a structure choice - it costs more to operate that way, and the firms who do it are typically more expensive per seat than the white-label MSPs. If somebody’s competing on price alone, they’re competing on the structure that produced the vendor you couldn’t get on the phone last time.

Monthly walkthroughs that are real. Not a quarterly review that gets rescheduled three times. Monthly. With your senior tech, your account person, and somebody from your side. If nothing changed, the meeting is fifteen minutes. If something changed, you catch it that month, not at next year’s renewal.

Those three things are why we’ve gone eleven years without a security breach across our client base. It’s not magic. It’s the same senior people being in the room every month, learning the business in detail, and catching what slipped before it became a Tuesday-morning phone call.

What to do if you’re carrying one of these right now

If everything in this piece felt familiar, you already know which provider you’re paying. The harder question is what to do about it.

Three honest options. Each one has a real version and a fake version.

One: keep the provider, fix the structure. Real version: escalate, get the senior partner back on calls, put a monthly walkthrough in writing as a contract amendment. Fake version: complain at the next quarterly review and hope it changes.

Two: insource the parts that matter most. Real version: hire one senior IT person who owns the relationship, with the MSP behind them as a tier-two support layer. Fake version: ask your office manager to also handle IT escalations on top of their day job.

Three: change providers. Real version: run a structured evaluation, ask the three accountability questions above of every finalist, talk to two clients who are three or more years into the relationship. Fake version: pick whoever responds fastest to your RFP, sign in six weeks, hope it’s different.

The longer version of this argument - what a built-in IT relationship actually looks like, what the structures that produce accountability are, and how to evaluate a provider before you sign instead of after - lives in The Vencer Operating System. It’s free, and chapter three is specifically about the vendor-accountability question.

If you’d rather just have a twenty-minute conversation with no pitch attached - the kind where I tell you straight whether what you’re carrying needs fixing, and whether we’d be the right team or whether somebody else would - the calendar is on the contact page. If we’re not the right fit, I’ll tell you that too. Win-win or no deal. Including the conversation.