Section 1
Hour 0 to 24: control the information and the accounts
The damage from a poach is rarely the one departure. It is the contagion and the account loss that follow. Move on both today. • Do not counter with money in the first conversation. Say you value him, you want to understand the offer, and you will talk properly tomorrow. This buys a day and stops you from panic-matching a number you will regret. A rushed counteroffer signals that your pay was never fair, which tells every other tech to go get an offer too. • Secure the customer relationships he touches. Quietly make sure the accounts and service agreements he manages are documented, that a second face has been introduced where possible, and that no customer relationship lives only in his phone. The platform is not just buying a technician. It is buying the customers who ask for him by name. • Talk to your other key people first, before rumor does. The crew will hear about the offer within a day. Get to your other two or three people you cannot lose and reassure them directly, before the story becomes "the platform is picking us off and the owner is scrambling."
Section 2
Hour 24 to 48: make the real counter, which is not the bonus
Now you respond to the technician. The counter is not a matching check. It is a version of the thing capital cannot easily wire: a career he can see, that costs him money to walk away from. • Counter with a stream, not a lump. A signing bonus is a one-time payment for showing up. Counter with something that grows the longer he stays: a defined raise tied to a visible skill rung, a retention amount that vests over the next few years, a share of the profit on the work he leads. He should be weighing a check that clears once against a stream that keeps getting bigger. • Name the path. The platform's pitch is "join something bigger." Your counter is "here is the next rung, here is what it pays, here is what unlocks it, and here is the ownership or lead role waiting at the top." A staircase he can see the top of competes with a step sideways off it. • Be honest about what you will and will not do. If your base pay is genuinely below the market median, close that gap and say so, because no vesting stream retains a tech who is underpaid today. If your pay is fair and the platform is simply buying headcount with a fund's capital, say that too. A tech can tell the difference between an employer investing in his decade and a bidder filling a seat.
Section 3
Hour 48 to 72: decide, and either way protect the base
Some techs will stay for the path. Some have already decided, or need the cash this month more than a career in three years, and no counter reaches them. Either way, your job by hour 72 is the same: the base is protected. If he stays, put the counter in writing so it is real, and use the episode to publish pay bands and a retention ladder for the whole crew, so the next recruiter's call meets a system instead of a negotiation. If he goes, let him go cleanly, keep the relationship warm, hold the accounts you documented on day one, and make sure the rest of the crew sees an owner who responded with a plan rather than a panic. A clean exit that keeps the customers and steadies the crew is a better outcome than an expensive save that teaches everyone to threaten leaving.
Section 4
The fitness test
You are ready to handle a poach well if, on the day it happens, you can avoid matching cash in the first conversation, document and secure the accounts the tech touches within 24 hours, and come back inside two days with a counter built on a rising stream and a named career path rather than a lump sum. Under those conditions a single poach costs you at most one person, and often not even that, while your crew and your customers stay put. You are exposed, and this episode will not be the last, if your only available response is to match the bonus, because that means your pay is an unpublished negotiation and your customer relationships live in one technician's phone. The fix is not a bigger checkbook. It is a retention ladder and account documentation built before the next call comes, so the platform's capital meets a switching cost it cannot easily buy out. Handle these 72 hours with a plan, then spend the next 90 days making sure the plan exists in writing for everyone else.