The Tech Who Wants a Raise: Decision Tree

Why this matters

A good tech walks into your office and asks for a raise. How you handle the next ten minutes shapes whether they stay engaged or start interviewing elsewhere. Say yes too fast and you train everyone to ambush you. Say no badly and you lose someone you cannot afford to lose. Most owners freeze here because they treat it as a yes-or-no, when it is really a diagnosis: who is asking, why now, and what is the raise actually worth against the cost of replacing them. Work the tree, do not react.

Start here: do not answer in the moment

The first move is to not give an answer on the spot. Reacting under pressure leads to a panic yes or a defensive no, and both are mistakes. Say something honest and calm: "I take this seriously and I want to give it real thought. Let me look at the numbers and let's talk in a couple of days." This buys you time to diagnose and signals you respect the request. Then run the branches below before you meet again.

Branch 1: Is this a keeper?

Be brutally honest about who is asking.

If this is an A-player - skilled, reliable, low callbacks, good with customers, someone whose departure would genuinely hurt - then the real question is not "do they deserve it" but "what does it cost me to lose them versus keep them." Replacing a strong tech costs months of lost productivity and ramp-up. Keeping a strong tech happy is almost always cheaper. Lean toward yes, and go to Branch 2 to get the structure right.

If this is a middle or weak performer, a raise is not automatically off the table, but it should be tied to a path, not granted for showing up. Go to Branch 3.

If this is someone you would not be sorry to lose, the request is information. Either they are worth more than you thought and you have been misjudging them, or they are overvaluing themselves. Be honest with yourself about which.

Branch 2: For your keeper, what is the right structure?

A keeper deserves a real answer, but how you give the raise matters.

• Tie it to value, not just tenure. "You've earned this" lands better when it names what they earned it with: the skills gained, the jobs they now run solo, the customers who ask for them. This frames future raises around growth, not the calendar.
• Consider the whole package. Sometimes the answer is a raise. Sometimes it is a raise plus a path to lead tech, or better benefits, or a performance bonus structure that lets them earn more by producing more. Money is one lever among several.
• Get ahead of the next one. Lay out what the path up looks like so they are not back in six months. "Here's where you are, here's what the next level pays, here's what it takes to get there."

Branch 3: For a developing tech, anchor it to a plan

If the tech is solid but not yet at the next level, do not just say no. Say "here's how you get there." Pull out the competency checklist for the next rung and walk it together. "You're close. Master these three things and the raise that comes with that level is yours." This converts a raise demand into a development conversation and gives them a concrete reason to grow instead of a reason to leave.

If the tech is underperforming, be direct and kind. Name the gaps, name the standard, and be clear that pay follows performance here. "I can't move your pay right now, and here's exactly what would change that." A vague no breeds resentment. A specific no with a path is a challenge they can rise to.

Branch 4: When you have to say no or not-yet

Sometimes the honest answer is no, or not now: the business cannot support it, the timing is wrong, or the request outruns the contribution. If so, say it straight and explain the why. People can handle a no they understand far better than a maybe that drags out. Never make a promise you cannot keep just to end the conversation, because an unkept pay promise is how you lose a good tech and your credibility at once.

If money is genuinely tight, look for what you can offer instead: a clear timeline for revisiting, more of the work they want, schedule flexibility, a development path. Honesty about constraints keeps trust intact even when the answer is not what they hoped.

Avoid the traps

• The counteroffer trap. If a tech only got a raise by threatening to leave, you have trained the whole crew to threaten. Worse, a tech who took a counteroffer often leaves anyway. Address pay before it becomes an ultimatum.
• The fairness ripple. A raise for one ripples through the crew. Make sure any raise holds up if the rest of the team learned about it, because they will.
• The legal floor. Pay decisions touch minimum wage, overtime, and equal-pay rules that vary by state. Keep your practices consistent and confirm the specifics with an attorney or your state labor office.

References

• U.S. Department of Labor, Wage and Hour Division, pay and overtime requirements
• Society for Human Resource Management (SHRM), compensation and pay-equity guidance
• See related: Paying for Performance Without Gaming It
• See related: The Stay Interview: Keeping Them Before They Leave