The 90-day probationary period isn’t protecting you. It’s giving you permission to avoid a conversation you should’ve had at week three. Think about your last bad hire. Interviewed well. Said the right things. Showed up on time that first week. Then week two happened. Late on Monday. Long lunch on Wednesday. Asked your lead tech the same question for the third time. Your advisor gave you that look. The one where she doesn’t say anything, but you both know. So you started negotiating with yourself. “Maybe he needs more time.” “Maybe it’s the learning curve.” “Maybe I’m being too critical.” Week four. Week six. Week ten. Nothing changed. You knew at week three. Your lead tech knew at week two. That’s not patience. That’s avoidance. Here’s what that avoidance actually costs you. In a three-tech shop, one underperformer doesn’t just drag. It compromises everything around it. Comebacks. Bottlenecks. Cars that should take three hours taking six. Your good techs notice. They don’t say anything to you. They say it to each other. And they start thinking about who else is hiring. Meanwhile, you’re not running your shop. You’re babysitting a problem you identified two months ago. One shop owner I talked with handles this differently. She tells every new hire on day one: “We will all know within 30 days if this is going to work or not.” Not a threat. A mutual agreement. She calls it a mutual audition. You’re evaluating them. They’re evaluating you. Both sides know the timeline. Here’s what her first 30 days look like: Days 1–2: No wrenches. Systems only. Learn the software. Learn the workflow. Learn the board. This does two things — gives them a fair start, and shows you immediately how they absorb information. Days 3–10: Supervised work. They’re looking at cars. Doing DVIs. Writing up what they find. Your lead tech is watching — not hovering, watching. Do they ask questions when they’re stuck? Do they help the tech next to them? Do they show up on time?

He read every 1-star review the shop had. Not the 5-stars. The 1-stars. This was before he applied. Before he walked through the door. Before he ever met the team. He went to Google. Pulled up the shop’s reviews. And started reading. But he wasn’t reading the complaints. He was reading the responses. He wanted to know one thing. What happens at this shop when a customer gets angry? Does the owner throw the tech under the bus? Or does the owner have the team’s back? He read every response. Then he applied. She asked him why. He could’ve gone to the dealerships up the road. They were hiring. Some paid more. His answer: “I only came to work for you because I can see that you protect your technicians against the outside world.” He didn’t pick the shop for the pay. Not the benefits. Not the sign-on bonus. He picked it because of how the owner responded to a 1-star review. Most shop owners think of Google reviews as a customer thing. They’re also a recruiting tool. The best technicians — the ones you actually want — are doing homework on you before they ever apply. They’re Googling your shop name. Scrolling your reviews. Reading how you handle conflict in public. These aren’t desperate candidates who blast their resume everywhere. These are employed techs with options. They’re choosy. And they’re looking for signals. Your 1-star reviews are one of those signals. Not the review itself. Your response to it. Here’s what a good tech sees when they read your review responses: Response #1: You throw your tech under the bus. “We sincerely apologize. The technician responsible has been spoken to and this will not happen again.” What a tech thinks reading that: If I make a mistake here, I’m getting publicly blamed. If a customer exaggerates, the owner sides with them automatically. Next. Response #2: You get combative. “Actually, you’re wrong. We did exactly what you asked for. Maybe if you maintained your vehicle properly this wouldn’t have happened.”

A member said that on last Thursday's EasyBench live implementation clinic. And it stopped me cold. Because that's the whole problem in one sentence. Not the technician shortage. Not bad job ads. Not Indeed. The problem is that most shop owners only think about hiring when someone quits. Only check the pipeline when a bay goes dark. Only pick up the phone when they're desperate. And desperate is the worst position to hire from. Here's what we covered: → The 7 Filters — every message you send a technician runs through a psychological gauntlet before they decide to reply. Identity. Angle. Value. Friction. Authenticity. We broke down each filter and diagnosed exactly where most shops get ghosted. If you've ever had a tech go silent after a great conversation, this is why. → Stealth Scripts: Training Invites — three new done-for-you messages for inviting bench techs to training events. NAPA classes, ADAS sessions, Vision , ShopHackers— whatever you're sending your team to. The play: grab an extra ticket, send a two-line text, let the tech say yes or no. No pitch. No pressure. Just value at every touchpoint. → The Callback Move — the single most powerful line in any follow-up message is a reference to something the tech told you in a previous conversation. It proves you were listening. It proves this isn't a mass text. We walked through how to use the Notes section in your Bench Board to capture these details so they're there when you need them. → Seeding Your Bench Board Fast — four ways to get names into your Bench Board this week: past Indeed applicants, phone contacts you've been saving, sticky notes scattered around the shop, and old applications in a filing cabinet somewhere. The goal isn't perfection. It's getting organized so you can start making contact. → A member shared how he customized his Bench Board with resume attachments, vibe scores, and a notes system his whole team uses. He walked us through it live. Every feature suggestion he made is getting built into the next version of the tool — because that's how EasyBench works. Members shape the system.

What happened in the industry. What it means for your shop. What to do about it. 90 years. That's how long Grismer Tire & Auto Service has been family-owned in Ohio. Dayton. Columbus. Cincinnati. 28 locations. Three generations. Community roots so deep they practically hold up the sidewalks. Last week, Dallas-based private equity firm CenterOak Partners bought them. And that deal tells you more about where this industry is headed than anything else I've seen this year. But Grismer wasn't the only story. Sun Auto confirmed two separate acquisition clusters. A brand new PE firm announced it's entering the tire and auto space with $45 million and a single mission: build one platform from scratch. And the Driven Brands legal situation just got uglier. Here's what happened, what it means for your shop, and what to do about it this week. CENTEROAK BUYS GRISMER: THE DEATH OF "TOO LOCAL TO SELL" CenterOak Partners — a PE firm managing $2.5 billion in equity capital — completed a majority recapitalization of Grismer Tire & Auto Service on April 2nd. The family sold. The deal is done. Here's why this matters more than the average acquisition. Grismer wasn't some struggling chain looking for a lifeline. They were the gold standard. 90 years. 28 locations. An owner who was on the floor. The kind of shop that customers chose because they knew the people, not just the brand. And PE bought it anyway. CenterOak's track record tells you their playbook. They built FullSpeed Automotive to 600 locations and sold it. They grew CollisionRight six-fold and sold it. They built TruRoad into the second-largest auto glass platform in the country and sold it to Safelite. They didn't buy Grismer to keep it the way it is. They bought it to scale it. Expect tuck-in acquisitions in adjacent Ohio markets. Standardized service menus. Metrics-driven operations. And a corporate growth mandate that will inevitably change the feel of the place. Here's the part that matters to you: the "owner on the floor" culture that made Grismer special? That's now being traded for growth capital and a board of directors. And that means their most loyal "relationship-first" customers are going to start noticing.

A shop in Colorado Springs had been looking for a tech for over a year. The owner had done the usual. Asked his team in a meeting. "Hey guys, know anybody who might be looking?" Everyone shook their heads. Nope. Don't know anyone. So he moved on to Indeed, social media, the whole routine. A year later, still looking. We met and I said let's try something different. Let's create a referral postcard — something physical, tangible, with a $500 referral bonus printed on it — and hand it out in the next team meeting. He pushed back. "We already asked them. They don't know anybody." I said try it anyway. He handed out the cards. Within a few weeks, he hired two techs off of those postcards. Two. He went back to the next team meeting and said: "You guys have known for a year we've been looking for a tech. Why didn't you tell me?" The answer was simple and a little maddening: "I just didn't think about it. When I had the postcard in my hand, it was fresh in my mind. And then I knew you were going to pay me some money. And all of a sudden I jogged my memory and thought — yeah, I've worked with some guys in the past." That gap — between "I don't know anyone" and "actually, now that I'm holding this card and thinking about it, I know two people" — is the entire difference between asking for referrals and building a referral system. Every shop owner has done some version of "Hey, know anybody?" at a team meeting. That's not a referral system. That's a vaporware request. It's verbal — so it's forgotten before lunch. There's no incentive attached — so there's no urgency. And "know anybody?" is the vaguest question you can ask. It's easy to say no to, even when the real answer is yes. A referral system has three things most "asks" don't: something physical that stays in their hand or on their toolbox, something financial that makes it worth a phone call, and something consistent — it's not a one-time ask when you're desperate, it's a standing offer that runs all the time.