That's what a technician texted back to a member last week. A tech he never hired. Last Thursday's EasyBench clinic went deep on the candidates already sitting in your Indeed account. The ones you passed on. The ones you meant to call. The ones you forgot about the day the bay filled up. I scrapped my scheduled demo for this one. Here's why. A client of ours thought Indeed applications arrive by email. They don't always. @Christi Warren got him on the phone and found a stack of resumes he had never opened. Techs who raised their hand months ago and heard nothing back. Here's what we covered: → Deploying your Bench Board. One click, one copy, and you have somewhere to put a name. Most owners skip this and try to hold the pipeline in their head. The head is where techs go to be forgotten. → The green light / yellow light / red light sort. You are not looking for perfect. Green light is obvious. Red light is the Domino's guy with zero shop experience. Yellow light is the man who did two years at a chain store. He stood shoulder to shoulder with someone good. That is worth a phone call. Most owners throw yellow lights away. → The Candidate Recovery Sprint in the Stealth Script Library. Copy-paste text and email scripts built for one job: waking up a tech who applied a year ago and got silence. The opening line is an honest admission, not a pitch. → Running the message through Jason Perkins. Ninety-five pages of technician avatar, trained into your Copilot. Paste your draft. Ask what would make it a 10 out of 10 for Jason. It will tell you which line sounds like a recruiter who just learned a trick. → The five words that carry the whole message. "Before I post anything publicly." That single phrase tells a tech he is being offered first access instead of a job ad. He is not one of two hundred applicants. He was chosen once already. → A member asked which number to text from. Personal cell, or the shop line through Tekmetric? We talked through best practice versus practical reality, and why a tech saving your number matters more than the platform you sent it from.

"I don't want to be in desperation." A shop owner told me that. Seven words. That's the whole game. Because most of us recruit the same way. We wait until someone quits. Then we panic. We rush an ad live. We settle on the next guy because the position can't sit empty. Or we go the other direction. We run "We're Hiring" all year long. Always be recruiting, right? Except technicians read that ad differently than you do. A good tech sees a shop that's always hiring and thinks one of two things. "That place must have brutal turnover." Or "They're only collecting resumes." Neither one builds trust. Both quietly cost you the people you want. So you're stuck picking between two bad options. Panic later, or look desperate now. The best techs are already working. They're not on job boards. One shop I know had a master tech in mind for a year. By the time a bay opened and they reached out, he'd already taken a job somewhere else. Another shop had been talking to him the whole time. They didn't lose that tech to a better ad. They lost him to a relationship someone else already had. The biggest recruiting mistake is waiting until you need a technician before you start meeting technicians. So what if we stopped recruiting? What if we started building relationships instead? That's the whole idea behind a Future Team Campaign. It isn't a hiring campaign. It's a relationship campaign. You're not filling a bay this week. You're becoming the shop a great tech already respects, long before he needs a new job. Same shop. Same budget. Opposite message. Opposite result. A hiring ad says "we need someone." A Future Team Campaign says "this is what it's like to work here, whenever you're ready." One smells like desperation. The other builds a bench. The best time to meet your next great technician isn't after someone quits. It's months before you need them. You can run one of these yourself. Starting this week. Pick three things that make your shop worth leaving another job for. Better bays. Real training. A boss who backs his people. Whatever is true.

Last Thursday's EasyBench clinic went somewhere most owners assume is a dead end: finding the experienced techs already working in your area before they ever apply anywhere. The best techs aren't sitting on Indeed. They're in a bay they're 70% happy with. You can't wait for them to apply. You have to know they exist first. Here's what we covered: → The tech-finder prompt. Months of trial and error went into this. It pulls experienced, certified techs in your market by name. It cross-checks ASE lookups, LinkedIn, even local press releases. And it's built to skip the lube techs, the tire guys, and the IT guys who happen to have "technician" in their title. It surfaces people you'd actually hire. → The three-platform method. Run the same search through three different AI tools, then de-dupe into one list. Why three? Because every one of them will confidently make things up. One told me the average repair order in this country is fifty bucks and kept right on talking. Run a search once and you trust a hallucination. Run it three times and the truth is what survives in all three. → The org chart build. One member mapped his entire shop three years out in about four minutes. Where he is now. The GM he needs in 12 months. The seats that have to exist before he can retire. With the cost of waiting one more quarter built right into the output. → A member asked about adding checkboxes to his application to filter faster. We talked through why that backfires. Hand a tech a list of boxes and he checks all of them. The filter you think you built isn't filtering anything. → The gating continuum. The better the tech, the fewer hoops he'll tolerate before he'll even talk to you. A guy with 20 years and a dealer full of scan tools is not filling out a personality profile to find out what you pay. Front-load the friction and you screen out exactly the people you wanted. Service advisors are different. More of them apply, with less competition, so you can gate harder. Match the friction to the scarcity.

Three EasyBench clinics over the last few weeks ran a combined two hours and dropped enough tools to keep a shop busy for a month. Here's the recap of the stuff that actually moves the needle. The core idea: when a key person leaves, your instinct is to find another them. Replace the GM with someone who feels like the old GM. Replace the rebuild guy with someone who reminds you of him. Feels like wisdom. It's a trap. Because you're not recruiting against the future. You're recruiting against a memory. The old guy's personality got fused in your head with the job he did, and now you can't tell the two apart. So you screen for the wrong things and pass on the person who'd actually run your shop better. One line from a live demo said it better than I could: "The outgoing GM's personality is not the brief. The shop's operational requirements going forward are the brief. Those are rarely the same document." Read that twice. Then go look at every key seat in your shop. Here's what we covered: → The succession question you've been avoiding. We ran it live for a shop scenario with a GM slowing down with no replacement plan. You feed the role and your market in, and out comes the replacement profile. Not the best wrench. The informal leader. The 42-to-48 who already ran a $3M-to-$6M shop, with the title or without it. And the line that explains why experience beats years: "That pattern of survival and systemization is what you're actually buying." Someone who absorbed a staffing crisis, survived a toxic culture, navigated a cash-flow squeeze, and came out with better systems instead of better stories. That's the brief. You write it now, while everyone's still employed, not in a panic the week someone quits. → The mistake clock. Most shops, when a key person announces they're leaving, spend the first three months in denial and the last three in panic. They start recruiting with no time, no leverage, no clarity. That's the whole reason to build a bench before you need one. You're not building a pipeline because a seat is empty. You're building it so you never have to recruit in grief.

Are you staring at job boards while the techs you actually want are standing in your own shop? You've been asking your team the wrong referral question — and it's quietly costing you hires. In this post: - Why "do you know anyone looking?" gets you silence (and the question that doesn't) - The shop that hired two techs off a single team meeting - Why a referral is a thought, not a fact — and what that changes - The reason your best techs screen candidates harder than you do - How to make the ask feel like building the team, not poaching ~3 min read ____________ Your best tech knows three guys who'd be perfect for your shop. He's never going to tell you who they are. And it's your fault. Not because he's holding out on you. Because the only version of the question you've ever asked him is the one that makes a good tech go quiet. You've done it. I've done it. You walk through the bay and go, "Hey — you know anybody looking?" He says, "Nah. Not off the top of my head." So you write it off. Well's dry. You go back to the job boards, run the same ad, and tell yourself the puddle of techs in your area is just shallow. It's not shallow. You're fishing with the wrong question. "Do you know anyone looking?" and "Who's the best tech you've ever worked with?" feel like the same question. They're opposites. The first one asks a good tech to rat out a buddy who already has a job. The second one asks him to brag about someone he respects. One makes him a snitch. The other makes him a scout. Same goal. Opposite instinct. He went quiet on the first one because you accidentally asked him to be a problem for somebody else. Ask the second one and watch what happens. A shop I worked with had been looking for a tech for a year. Asked the team for referrals more than once. Every time, same answer: "Nobody knows anybody." We tried one thing. A physical referral card. Handed out in a team meeting. A real thank-you attached if it led to a hire. He hired two techs off it.