The wage that screens out everyone worth hiring

TL;DR — Average pay is a fence, not a starting line. You can want the top 10% of talent, or you can pay the market average. You can't post both.

In this post:

Why "competitive pay" is quietly the reason your best applicants never apply
The number that actually pulls an A-tech (it isn't the average)
How a careful salary survey still hands you the wrong number
The back-of-the-table mistake that loses techs even when the money is right
The one question that exposes your real number in ten seconds

4 min read. Short on time? Catch the video on the go.

___________________________________________________

An owner described the tech he wanted in one line.

The guy who chases the fault nobody else can find. The hardest seat in any shop to fill.

Then I asked what he'd pay.

He didn't have a number.

That's not a knock on him. Almost nobody has the number ready. But the gap between I want the best diagnostic tech in my market and I'm not sure what I'd pay is where most hiring falls apart.

The owner finds the market average. A salary survey, what his buddy down the road pays, a gut number. He lands on something "competitive." He posts it.

Then he goes fishing for a tech who is, by definition, nowhere near average.

You wrote a number built from the middle and went hunting for someone who lives at the top.

The best diagnostic tech in your area already knows what he's worth. He's not guessing. He's getting pinged. Your "competitive average" sits below his number — far enough below that he doesn't even reach out. The ad doesn't offend him. It doesn't register. He scrolls past it the way you'd scroll past a job paying half what you make now.

Average pay isn't a floor you negotiate up from.

It's a fence that keeps the good ones on the other side.

A REAL SURVEY, READ BACKWARDS

I ran a full salary survey for a shop in the Charlotte market not long ago. Thirty-one usable comps — dealerships, European specialists, recon operations, independents. Real ads, real ranges.

The average high end across all thirty-one came out to about $103,000.

Stop there and you anchor at $103K. It feels safe. Nobody can call you cheap at the survey average.

But this shop wasn't hiring an average tech. They needed a lead diagnostic tech who could protect their acquisition decisions and keep cars from coming back. Filter the same survey down to that tier — the master and diagnostic and European comps — and the real market sat at $120,000 to $150,000.

The average and the target were forty grand apart.

That forty grand is the fence.

Sit with this part. The survey was rigorous. Thirty-one comps, pulled from live postings. And it still hands you the wrong number the second you anchor to the middle. The error isn't sloppiness. It's a reading habit — owners pull the average because the average feels responsible, when the tech they want is sitting at the top of that same chart.

There's a number that cuts through all of it, and it needs no survey:

What does your best tech actually take home in a great week?

Not his base. Not his hourly. What he clears when production and efficiency are clicking. That number is provable. It's already happening in your building. Post that, and you've raised a flag the right tech can see — and it's true, which is the whole game on the other side of the table.

THE MISTAKE ON THE OTHER SIDE OF THE TABLE

Say you fix the number. You aim high. The right tech finally walks in.

You sit him down and walk him through the pay plan. He nods. He leaves. He never calls back.

You assume it was the money.

It wasn't.

He didn't leave because the number was too low. He left because he couldn't understand how to reach it. Base, plus tiered percentage of the ticket, plus a quarterly bonus, plus a guaranteed minimum for the first ninety days — every piece of that can be smart, and strong shops win passive candidates with packages built exactly that way.

But a pay plan you can't draw on a napkin is, to the tech across the desk, just fog.

Complexity in a pay plan reads as risk to the person being paid.

He's employed right now. You're asking him to trade a paycheck he understands for one he doesn't. The number on your ad got him in the door. The fog walked him back out of it.

So here's the filter:

If you can't explain how a tech builds his own paycheck in under two minutes, your pay plan is costing you hires no matter how generous it is.

"Here's how you build a $120K year here — base covers you to here, production takes you to here, hit these numbers and you're at the top." That's not a sales pitch. It's a gift. It's the most attractive thing you can say to a tech risking a stable seat. And it's the thing most owners can't deliver cleanly, because they've never had to say it out loud.

THE WHOLE THING IN ONE LINE

The number that fills the bay isn't a digit you pick.

It's a number aimed high enough that the right tech sees it — and explained clearly enough that he believes he can reach it.

Most owners miss on one end.

The owners with empty bays miss on both.

Now I'm curious how the room actually does this.

When you set the pay number for your next A-tech, what do you anchor to? The survey average? What your current top guy makes? What you wish you could pay and hope production covers it? Something else entirely?

And be honest — could you explain your own pay plan to a stranger in two minutes? Most of us think we can. Fewer of us have tried.

Drop your method in the comments. I want to see how owners are really setting this number right now — and I'd bet there are three or four approaches in here worth stealing.

6:55

4 comments