When an account cancels, the reason that gets written down is almost always price, a competitor, or a change of management at the customer’s end. Those reasons are easy to record and impossible to argue with.

They are also, in a large share of cases, not what happened.

The loss does not look like a training problem

Account losses arrive one at a time, months apart, each with its own explanation. Nobody lines them up against the question of who was servicing those accounts and how that person was prepared. So the pattern stays invisible, and the response is a sales response: more quoting, more prospecting, a push on pricing.

You can replace lost accounts that way. You cannot stop losing them that way.

What a spring hire actually gets for onboarding

Here is the sequence almost every operator runs, not because they decided to but because of when the hiring happens.

You hire a technician in spring, which is exactly when you are at capacity. There is no spare week. So onboarding becomes riding along with whoever has room in the truck, for a week, maybe two.

What the new person learns on those ride-alongs is not your standard. It is one experienced technician’s shortcuts, including the ones that exist because that technician is good enough to get away with them. Shortcuts transfer faster than standards do, because shortcuts are what the day actually looks like.

Then the new person gets a route, because the route needed covering, which is why you hired in spring.

The newest technician is the only person from your company the customer sees

Think about what you just did. The person with the least preparation is now the only representative of your business that a set of customers will ever meet. The owner does not visit. The office is a phone number. The service is the technician.

That person answers the questions, sets the expectations, decides what gets reported and what gets quietly left out, and determines whether the customer believes the problem is being handled. They do all of that on two weeks of informal exposure.

This is the most customer-facing role in the company and in most operations it is also the least deliberately trained.

Nobody checks what the new person actually retained

The ride-along gets logged. A date, a trainer, a route. What does not happen is anybody confirming, a month later, that the new technician can identify what they are looking at, knows why the inspection runs in that order, and can explain a finding to a manager without reading from a form.

Without that check you do not know what you have. You find out from the account, later, when a customer has already decided the service is not working.

What happened to retention when we changed this

In an operation I was responsible for, client retention sat in the mid sixties. We moved it into the mid nineties and it held there.

Nothing exotic did that. No new software, no incentive scheme, no rebrand. We changed one assumption: we stopped treating the technician as the person who performs the service and started treating them as the person who protects the relationship, then equipped them to do that job.

Three parts. Train them properly before they carry accounts alone. Confirm they retained it rather than assuming the ride-along worked. Support them in the field while they are still learning, instead of reviewing their failures afterward.

Train them, then confirm it

Confirmation is the step that gets skipped, and it is the cheap one. A short structured check at thirty days and ninety days, on the material that matters for the accounts they hold, tells you whether your onboarding worked on this person.

If it did not, you find out while it is still fixable and while the accounts are still yours. If it did, you have a documented reason to give them more responsibility, which is the thing good technicians leave for the absence of.

Support in the field costs less than blame afterward

A supervisor in the vehicle for half a day in month two is a small cost. A cancelled commercial account is not, and neither is the replacement of a technician who concluded at month seven that nobody was going to help them.

Most operators have the second two costs in the budget and will not spend the first one, because the first one is visible and the other two are absorbed.

Price is the reason given, not the reason

Customers rarely tell you the real reason they left, partly out of politeness and partly because they have rationalized it themselves. Price is the acceptable answer. It is also the one that puts the responsibility entirely on you and requires no further conversation.

Your strongest accounts, the ones with real contracts and real scrutiny, are not usually lost on cost. They are lost when the person showing up stops inspiring confidence. That confidence is a function of competence, and competence is a function of how that person was trained.

Two questions to ask this week

The first: how was your best technician trained? Write down what actually happened, not what the manual says.

The second: how was your most recent hire trained? Write that down too.

If the two answers are different, you already know where next year’s account losses are coming from. If the two answers are the same and both are informal, then your best technician is good in spite of your onboarding, not because of it, and you cannot repeat them.

Where to start

Pick the three accounts you would most hate to lose. Find out who services them, how that person was trained, and when anybody last confirmed what they know.

That exercise takes an afternoon and it is uncomfortable, because the three accounts you would most hate to lose are frequently serviced by the person with the most room in their schedule rather than the most preparation.

Fix that order and you have addressed more of your retention than any pricing change will.