Skip to content
GuideEvergreen guide

The vendor you can't lose is already costing you

Your best supplier, contractor or software guy is also your biggest single point of failure. Here's how to keep them happy and stay in control.

By Ray Okonkwo · Money & Business6 min read
The vendor you can't lose is already costing you

Quick answer: Don't fire the indispensable vendor and don't squeeze them. Make sure you own your accounts, your data and your documentation, put a backup in place on a small job, and tell them what you're doing. Dependence is fine. Dependence you can't survive losing isn't.

Picture a forty-person HVAC outfit. The scheduling system was built by one contractor six years ago. He's fast, fair on price and picks up on the second ring. Dispatch, invoicing and the technicians' phone app all run through what he built. Nobody else has ever seen the code. The hosting account is in his name.

That business is doing fine. It's also one car accident, one retirement or one "I got a full-time offer" away from a very bad month.

You probably have one of these. A bookkeeper who keeps the books in a way only she understands. A machine shop that's the only one in three counties that holds your tolerance. A freight broker who knows which drivers actually show up. They're good, which is why you leaned on them, and the leaning is the problem.

How it happens

Nobody decides to depend on a vendor. It happens one convenience at a time.

They fixed something at 9 p.m. once. You stopped writing things down because they remembered. You stopped getting quotes because they were fair. Three years later they hold your passwords, your process and your history, and you've never signed anything that says so.

The fix isn't suspicion. It's a habit of asking the question before something breaks.

The Tuesday test

Pick your top five vendors by how much would stop without them, not by spend. For each one, answer this:

  • If they vanished Tuesday morning, what stops that day?
  • How long until it's running again, and who does that?
  • What do they hold that you can't get without them? Logins, files, customer data, a key, a formula, a relationship.

The third question is where the surprises are. A vendor who's hard to replace is an inconvenience. A vendor who holds your data hostage, even by accident, is a liability.

Write the answers down. If the honest answer to "how long" is "I have no idea," that's your first finding.

Own the keys

This part is non-negotiable, and it's cheap. Do it this month.

  • Accounts in your name. Domain, hosting, ad accounts, software licenses, payment processors, the business listing. If the vendor set it up, you should be the owner and they should be an added user. Transfer it if it's backwards.
  • Billing on your card or your account. Not theirs, not reimbursed through them.
  • A current copy of your data. Customer lists, job history, files, configurations. Exported and stored somewhere you control, on a schedule.
  • Admin credentials in a place two people in your company can reach. Not in one person's head, and not only in the vendor's.

You'll hear "that's a hassle" from some vendors. A good one says "about time." A vendor who pushes back hard on you owning your own accounts has just told you something important.

Make them write it down

Knowledge is the other thing they hold. Ask for a plain-English document of how your piece of the operation works: what runs when, what depends on what, what to do when it breaks, who else knows how to fix it.

Pay for it. A few hours of their time is a real line item, and it shows you respect their work. For a contractor, make it a deliverable on the next invoice. For a shop, it's the drawing, the process sheet and the supplier list for the material.

A running joke in ops is that the documentation is always "almost done." Put a date on it.

Look at the contract

Most small-business vendor agreements, when they exist at all, say nothing about leaving. Fix that at the next renewal or the next big job. Things worth asking for:

  • A notice period long enough to replace them, often 60 to 90 days.
  • Help with handoff if either side ends the relationship, at an agreed rate.
  • Your data returned in a usable format on request.
  • A cap on price increases, or a notice requirement before one.
  • For custom software, a clear statement of who owns the work you paid for.

The details depend on your state and your deal, so have a lawyer who handles business contracts read it before you sign. An hour of that's cheap next to a rebuild.

Build a second option, quietly

You don't need a full backup vendor. You need a warm one.

Give a second supplier a small, real slice of work. A low-risk job, a minor product line, a side project. Enough that they know your systems, you know their quality and the first invoice has already cleared. Cold-calling a backup in the middle of a crisis is how you end up paying double and getting second-rate work.

Yes, it costs something. The second vendor will be a little slower and a little pricier at small volume, and you'll spend some of your own time on it. Think of it as an insurance premium. If the number feels too high, you can find where the money's going in your profit and loss and decide what it's worth.

Tell them what you're doing

This is where owners get it wrong in both directions. Some do all of the above in secret and treat the vendor like a suspect. Others never do it because it feels disloyal.

Neither is right. Say it straight: "You've been great for us, and that's exactly why I need to make sure we're covered if something happens to either of us. I'm moving the accounts into our name, and I'd like to get the process written up. I'm also trying a second shop on a small job. Nothing's changing about how we work with you."

A good vendor hears that as respect. They have their own risk, namely one customer who might disappear, and a client who plans ahead is a safer client.

And hold up your end. Pay on time, every time. Plenty of vendor trouble starts when the invoice goes late and the relationship starts to sour, and most late invoices are a process problem, not a people problem. Fix yours before you ask more of them.

When dependence is fine

Some indispensable vendors should stay that way. A specialist who's far better than anyone else you could find is worth the concentration risk. Three mediocre suppliers don't beat one excellent one.

So don't chase redundancy for its own sake. Accept the dependence where the quality justifies it, and cover the exposure: keys in your hands, the process on paper, a warm backup you hope never to use. Pay them well and say thank you.

The same logic applies to the person on your own payroll who holds all the knowledge. If the day does come when you have to part ways with someone you've leaned on, do it the right way, and be glad the handoff was already written down.

Own the keys. Pay the invoice. Then the best vendor you've got can retire, move or get a better offer, and you'll wish them well and mean it.

Ray Okonkwo

Money & Business

Former commercial banker turned small-business owner. Covers salary, credit, margins and the arithmetic nobody does before signing.

Watch

Watch how it's done

Picked for this article.

From channels we rate. Plays on YouTube.

The.Shawn.Peterson

High-Value Business, Part 6: Reduce Customer and Vendor Dependency