Why your employee poaching defense keeps losing to a recruiter call

Two of your best people left last quarter, both to the shop across town, three weeks apart. You went back and reread the offer letter template your lawyer helped you put together last year, the one with the non-solicitation clause you paid to have redrafted. It never came up. Nobody threatened to sue anybody. Your ops lead and your top coordinator took a call, listened to a number, and said yes.

Your first instinct was to call the lawyer back. Tighten the clause. Add a longer cooldown.

Your second instinct, quieter and harder to shake, showed up around closing time. The contract didn’t keep them. The recruiter’s call did. Nobody stole them. They picked, and if you’re honest with yourself, you already know what they picked over.

Here’s the problem none of the poaching guides on page one of Google will say out loud. Employee poaching is a retention problem dressed up as a recruiting problem, and the contract layer can’t fix what pay transparency and a visible next role should. You don’t have an HR department to draft new clauses or a legal budget to fight this in court. What you have is two open shifts and a backfill you need filled this week, not next quarter. That’s the gap this post is about.

A non-solicitation clause didn’t keep them

It does real work, just not the work most owners assume. A non-solicitation clause restricts a departing employee, for a set period, from actively recruiting their former coworkers to follow them out the door. That’s useful. It is not a retention mechanism. It doesn’t stop your coordinator from accepting a competitor’s offer, and it doesn’t stop the competitor from making one. The clause only activates after someone has already decided to go.

Most small teams learn this the way you just did. Two or three people leave in a matter of weeks, the clause was sitting in every offer letter the whole time, and it never came up. That’s because the clause exists for a narrower problem: someone walking out with your client list or your pricing sheets on the way to a direct competitor. That happens, and it justifies a sensible non-solicit. It’s not the volume of loss most owners are quietly tracking when the same role reopens for the second time in a quarter.

What employee poaching actually is, and what’s illegal

Most poaching is legal. Agreements between competitors are not

In most US states, a competitor calling one of your employees with a job offer is ordinary, legal recruiting. It happens every day and there’s no clause that stops it. The illegal version is different: two or more employers agreeing among themselves not to recruit or hire each other’s people. Regulators call this a horizontal no-poach agreement, and since the DOJ Antitrust Division and the FTC published their joint Antitrust Guidance for Human Resource Professionals in October 2016, that kind of pact has been treated as a per se violation of Section 1 of the Sherman Act. Per se means prosecutors don’t have to prove the agreement hurt any specific worker. The agreement itself is the violation, and a corporation can be fined up to $100 million and an individual up to $1 million and ten years in prison for one.

The DOJ’s early attempts to prosecute this criminally didn’t go well. Juries acquitted defendants in the first wage-fixing and no-poach trials brought after the 2016 guidance. But the losing streak ended in April 2025, when a federal jury convicted a Nevada staffing executive of conspiring to fix wages for home health nurses, the DOJ’s first successful criminal trial conviction in this area. That November, a federal court sentenced him to 40 months in prison and $550,000 in fines, and the case is now on appeal at the Ninth Circuit. If an owner at a competing business ever floats “let’s just agree not to poach each other’s people,” that’s the moment to walk away. There’s no version of that conversation that ends well.

Non-solicitation clauses are narrow, and usually legal

This one sits between you and an employee, not between two employers. It restricts that employee, after they leave, from soliciting your clients or coworkers for a defined period. Courts weigh these on reasonableness of scope, duration, and geography, and most states enforce them if they’re reasonable. It’s a different legal animal from the horizontal no-poach pact above, and pages that blur the two together make the topic harder to reason about.

Non-competes lost their federal teeth in 2026

Non-compete clauses restrict an employee from working for a competitor at all, and here’s what changed. The FTC tried to ban them nationwide in 2024. A federal court set that rule aside, the FTC stopped fighting the ruling, and in February 2026 the agency formally struck the rule from the federal code. There’s no federal non-compete rule in effect right now. Enforcement is back to being an entirely state-by-state question, from a near-total ban in California to broad enforcement in states like Florida, and several states moved their own rules again this year, including a $70,000 minimum-pay threshold in Tennessee and a near-total ban on healthcare non-competes in Utah. None of this is legal advice, and the right move is a quick call with counsel in your state before you write or rely on one. For a hiring conversation, the point that matters is simpler: a strategy that leans on a non-compete is standing on ground that just shifted under it, twice.

Why “they got poached” is really a story about your pay bands

A recruiter calling your best coordinator on a Tuesday isn’t what makes her leave. That decision was already half made. The call is just the moment it becomes visible. People who know they’re paid fairly, can see what the next role looks like, and have had a real conversation about their pay in the last year take the call and say no thanks. People who haven’t had that conversation in fourteen months take the call and listen. Small teams that worry most about poaching are usually the ones running the second pattern.

What an honest exit interview tells you

If you actually run an exit interview instead of skipping it because you already know why someone’s leaving, the honest answers cluster around three sentences. “I hadn’t had a real pay conversation in a long time.” “I didn’t know what my next role looked like here.” “Everyone else’s pay had moved and mine hadn’t.” The third is the most common and the easiest to fix. Small businesses adjust pay quietly, often without telling the people it applies to. The competitor’s recruiter quotes the new number, and your coordinator has nothing to compare it to except her own paycheck, which hasn’t changed.

The pattern shows up across the owner-operators we talk to: someone’s best hire leaves for a 15 to 25 percent pay bump the owner could have approved internally, if anyone had actually asked.

What losing them actually costs you

This is worth fixing before it happens, because the math is bad after. Gallup estimates that replacing one employee costs somewhere between half and two times their annual salary, once you count the vacancy, the ramp time, and the disruption. On a team of ten or fifteen, losing two people in a month isn’t a staffing hiccup. It’s a chunk of a year’s payroll walking out the door, plus the shifts nobody’s covering while you backfill, and a hiring velocity problem you didn’t choose.

The pool you’re hiring from is also thinner than it feels some months. The most recent federal jobs data puts the national quits rate at 1.9 percent, about 3.1 million people leaving jobs voluntarily in a single month. Every one of those people is a candidate somebody else is trying to hire too. When a competitor pulls from your team, you’re not just backfilling a role. You’re competing for a pool that’s already moving.

The two levers that beat a Tuesday phone call

There are two structural levers worth pulling here. Recognition programs, team lunches, and a nicer break room are tactics on top of these two. They don’t substitute for either.

Pay transparency

It comes down to three specific things. People know what they currently make relative to the range for their role. They know what the next level pays and roughly what gets them there. And they know if the ranges themselves moved this year, because you told them, not because a recruiter did.

Together, those three remove the surprise that makes a recruiter’s number land like a gut punch. When an outside offer shows up, your coordinator already knows whether it’s genuinely above what you pay or just about the same, and whether the right conversation is “I’m out” or “can we talk about my pay.” A short pay review every six months, where you actually have the conversation instead of skipping it, does most of the rest of the work. You don’t need a system for this. You need it on the calendar.

A visible next role

This means someone three months in can answer two questions without guessing. What does the next role up look like, and roughly what does it pay? And what specific things, over what timeframe, get them there?

Both are answerable for almost any role, even a small one. Most owners don’t answer them, partly because writing it down feels like a promise, and partly because the next role was never actually defined. The cost is the phone call your best person takes because the recruiter has an answer and you don’t. “You’d be running the front desk within a year at this range, here’s what that takes” beats any mission statement on your careers page. The two are doing the same job, one for people you haven’t hired yet and one for people you already have.

”I can’t match what they’re offering”

This objection deserves to be taken seriously. It also gives cover to owners who’d rather not do the harder, structural work.

Where it’s actually true

Sometimes it is. A specialist in a thin local market, someone with a rare license or a decade of niche experience, can command a premium a small business genuinely can’t match. Those cases exist. They’re not most of your departures.

Where it stops being true

Everywhere else, it usually turns out to be a 15 to 20 percent gap you assumed was unfundable and never actually checked. That gap is rarely unfundable. It’s unexamined, because nobody weighed the cost of losing someone against the cost of a raise. Two people leaving is often a bigger number than a modest, team-wide pay adjustment. And what people actually resent isn’t being paid a little below market. It’s not being told, while everyone around them quietly gets a bump they didn’t.

What a quarter without a poaching problem looks like

Back to those two open roles. Same size team, same competitor down the street, but picture it six months later, after you’ve made two changes.

The structural work

You wrote down pay ranges for every role in January, three tiers for your front-of-house roles, two for back office. People know roughly where they sit. You wrote the next role for each current one right after, with the specific things that move someone up a tier. None of it is binding the way a contract is. All of it is visible the way a contract isn’t. Pay conversations happen twice a year now, on the calendar before anyone’s annual review, so the money conversation isn’t an afterthought tacked onto a performance talk.

The hiring side of the same picture

You’re filling the two backfills the same way you fill any role now. Applications land on one Position Link, and Truffle screens every resume against the criteria you set when you posted the role, so the obvious mismatches fall away before you open a single one. For roles pulling a real flood of applicants, candidates record a short one-way interview instead of you chasing phone screens between shifts. AI Match shows how closely each response lines up with what you asked for, and Candidate Shorts compress the most relevant moments into about thirty seconds. AI surfaces the evidence. You still make every call. You watch a handful of Shorts over coffee and you’ve got three people worth talking to before lunch, on top of a job that already had you covering a shift that morning.

The backfill loop and the retention loop feed the same file. The intake questions that calibrated the screening also calibrated the pay range for the role and the path out of it, so the next person you hire knows what the next step looks like before they say yes. That’s exactly what was missing when the last two walked.

You haven’t touched a contract. You’ve changed what it feels like to work there, and made sure that if someone does leave, you’re not the one drowning for three weeks while you dig through resumes by hand.

What real poaching defense looks like

Horizontal no-poach pacts between competitors are still per se illegal, carry felony exposure, and you should never propose one, no matter how casually it comes up. Non-solicitation clauses do narrow, useful work. Non-competes are now a state-by-state question with no federal backstop. Get each one right with a lawyer who knows your state.

What the wrong response gets you

Treat poaching as a contract problem and the response is more contract: a longer cooldown, a non-compete in a state where it might still hold. None of it touches the math your coordinator runs on a Tuesday afternoon when her phone buzzes. The recruiter has a number. You don’t. Someone else leaves next quarter, for the same reason, because the actual conditions never changed.

What the right response gets you

Treat it as a retention problem and the response is structural. Ranges published. The next role written down. Pay conversations on the calendar instead of skipped.

The recruiter still calls on Tuesday. Your coordinator still takes it. The call just ends differently, because she can tell the recruiter she’s already in range, she knows what’s next, and there’s no 25 percent gap sitting there to negotiate. The recruiter moves on to a less prepared business next.

If you’re already three roles into backfilling this quarter, the fastest thing you can fix today isn’t the contract. It’s how long it takes you to turn a reopened role back into a hire. Truffle’s plans start at $49 a month, with a 7-day free trial and 30 credits to try it on the exact roles you’re refilling right now, no card required. The pay ranges and the growth paths are the longer project. Getting the next backfill off your desk by Friday is the one you can start today.

Frequently asked questions about employee poaching

Is employee poaching illegal?

In most US states, no. A business reaching out to a competitor’s employee with a job offer is ordinary, legal recruiting. What’s illegal is two or more competitors agreeing among themselves not to recruit, hire, or solicit each other’s employees. The DOJ and FTC have treated those horizontal no-poach pacts as per se violations of the Sherman Act since their joint 2016 guidance for HR professionals. DOJ won its first criminal trial conviction tied to this kind of conduct in April 2025, and that November a federal court sentenced the executive involved to 40 months in prison and $550,000 in fines. This isn’t legal advice. Talk to a lawyer licensed in your state.

What’s a no-poach agreement?

A no-poach agreement is an arrangement between two or more employers, usually competitors, not to hire or actively recruit each other’s employees. It’s different from a non-solicitation clause, which sits between an employer and an employee. The version between employers is the one antitrust regulators have flagged as per se illegal under federal law, with criminal fines up to $100 million for a company and $1 million for an individual.

What’s a non-solicitation agreement?

A non-solicitation agreement is a clause in an employment contract restricting a departing employee, for a defined period, from actively recruiting former coworkers or soliciting clients. It’s enforceable in many states if the scope, duration, and geography are reasonable. It doesn’t stop a former employee from accepting an outside offer, and it doesn’t stop a competitor from making one.

Are non-compete clauses still enforceable in 2026?

It depends entirely on your state. The FTC tried to ban non-competes nationwide in 2024, a federal court struck that rule down, and the FTC formally removed it from the federal code in February 2026. There’s no federal rule in effect. Some states, like California, void most non-competes by statute. Others enforce them if they’re reasonable in scope and duration, and several states tightened their own rules again in 2026. Check your state’s current rule with a lawyer before you write or rely on one.

How do you prevent employee poaching at a small business?

The durable fix is pay transparency and a visible next role, not a tighter contract. Write down pay ranges for each role. Run a real pay conversation twice a year, and an honest exit interview when someone leaves so you know if the same reason is about to repeat. Define what the next role looks like and what specific work gets someone there. People who have that information take a recruiter’s call and say no thanks. People who don’t take the call and listen.

Can a company sue another company for poaching its employees?

In narrow cases involving trade secret theft, a specific non-solicitation clause being broken, or tortious interference with a contract, yes. The bar is high and the facts matter a lot. Most ordinary recruiting activity is legal and isn’t grounds for a lawsuit.