A shop owner in our community had a tech ready to sign. Good tech. Right fit. Showed up on time, asked smart questions, liked the shop. Then they sat down to talk about pay. The owner walked him through the plan. Tiers, bonuses, how the hours break down, what happens when production picks up. The tech nodded along. But something wasn't clicking. He told me later: "It just scrambled his brain. He couldn't see that if I do this, this is going to yield this result." They never got that tech back on the phone. That tech didn't ghost because he got a better offer. He didn't ghost because he was flaky. He ghosted because he couldn't explain how he'd get paid. And here's what makes that so costly: A technician will never tell you he's confused. He'll tell you he'll think about it. Saying "I don't understand" costs him status in front of the guy he was hoping to impress. So he does the polite thing. He says he needs a couple days. Then he goes quiet. The owner files it under "flaky." Assumes a counter-offer. Changes nothing. And the next candidate goes quiet too. Most shop owners hear "ghosting" and think it's a loyalty problem. It's not. It's a clarity problem. A complicated pay plan is fine. This owner's plan is complicated. That's not the issue. The issue is whether it's explainable. Complicated means it takes a few minutes to walk through. Unexplainable means the tech leaves your office and can't repeat it back. Complicated attracts good techs who want to know exactly how to earn more. Unexplainable guarantees you never hear from them again. The plan is not the problem. The walkthrough is. Here's a test you can run this week. I call it the napkin test. After you walk a candidate through your pay plan, ask yourself one question: Could this tech explain how he gets paid to his wife tonight, from memory, with no paper in front of him? If not, you didn't lose him to money. You lost him to arithmetic. Here's what he needs to be able to say out loud before he walks out of your office:

A technician told me I don't exist. He'd commented on one of my posts. Said he can't get callbacks. So I messaged him. Offered a few ideas. Free. First, he asked if I was a bot. Then he asked which podcasts I'd been on. Then he told me he'd looked me up, and I "appeared nowhere." I Googled my name. A full page of podcast episodes. That's not the part that bugged me. He asked if I was a bot before he'd read a single one of my ideas. That's not a personality. That's a policy. Somebody taught it to him. Probably a lot of somebodies. Later he put it this way. He keeps a healthy skepticism for anyone online he doesn't know. He doesn't speculate. He calculates. Now read that as a shop owner. Anyone online he doesn't know. That's your job ad. You don't start at zero with a tech. You start at minus every shop that lied to him before you. Here's how your ad reads to him. "Competitive pay." He hears: they won't say the number. "Up to $45 an hour." He hears: nobody here makes $45. "Family atmosphere." He hears: pizza instead of raises. I am real. It didn't matter. Your shop can be the best in the county. It won't matter either. Being real and looking real are two different jobs. His skepticism didn't make him search harder. It made him stop sooner. One search. One bad read. Case closed. Your tech won't dig either. He'll look once and decide. Your proof has to be where he looks first. He looks in four places. At each one, he asks a different question. 1. The ad. Is any of this true? Cut every line any shop could write. Then add one a bad shop wouldn't dare put in writing. The real pay range. An open invitation to call one of your techs. Test every line: could he check it in under a minute? If not, prove it or cut it. 2. The look-up. Are they real? Google your shop on your phone like a stranger would. No photo of you or your crew? A Facebook page that went quiet in 2022? One tech watched a shop's Facebook for two years before he applied. Your page is the ad he actually reads.