Technician Bonus Cap: How an Epoxy Flooring Company Capped Crew Bonuses at $400 Per Job After 3 Techs Passed It

9

min read

24.10.26

A technician bonus cap of $400 per job kept three techs from outrunning a 45% gross profit gate at one epoxy flooring company. Here is how it works.

A technician bonus cap sounds like the opposite of motivation. At one small epoxy flooring company it turned out to be the part of the plan that made everything else safe to run. After three technicians each earned more than $400 on a single job, company leadership and the ShareWillow team agreed on a hard limit: no technician earns more than $400 from one job, no matter what the formula says.

This is a story about what a bonus is supposed to buy, what happens when it does not buy it, and why a ceiling is one of the cheapest fixes available. The results are early, so this is not a victory lap. It is a look at how a company with real money on the table decided to keep its plan and put a limit on it.

The Problem: A Bonus That Was Not Buying What the Company Wanted

The company installs epoxy floors with a small crew, and its leadership had a clear idea of what the bonus program was for. They wanted fewer callbacks. They wanted less time spent managing the field, checking job quality, and worrying about whether a floor would come back with a complaint. The bonus was supposed to make technicians act like owners of the job.

It was not doing that yet. On a recent review call, the company's lead decision-maker said plainly that they were not seeing the benefit they expected from the program. Callbacks were still a concern, and the field-management burden had not gone away.

Then came the math that many owners eventually do. If the company was going to spend this much on bonuses and still feel like it needed more management, was the money better spent on a person? The bonus spend could cover a production manager, someone who would oversee job schedules, field crews, job checks, and quality control, for nearly half of what the bonuses were costing.

That is a fair question, and it is worth asking about your own plan. A bonus is not free labor motivation. It is a cost, and it has to earn its place against every other way you could spend the same dollars.

The Plan Rules Before the Cap

Before the cap, the company already had two safeguards built into its technician bonus. Payouts were calculated under a 45% gross profit threshold, meaning a job had to clear that margin before a bonus was on the table, and a 5% maximum on the payout rate. Once the numbers were reviewed, the payout went to the company's accountant to run through payroll.

On paper, those two rules protect margin. A job that comes in thin pays nothing. A job that does well pays a limited share. What the rules did not do was limit the dollars one technician could earn on one job. On large jobs, a small percentage is still a large check.

Three gates before a bonus pays: 45% gross profit, 5% maximum rate, and a $400 cap per tech per job

That is exactly what showed up in the data. Three technicians had earned more than $400 on a single job. Nobody had broken a rule. The formula did what it was built to do. The problem was that the formula had no ceiling, and a bonus without a ceiling is hard to budget and hard to explain.

Essential KPI Guide [Free Download]: We put together a guide + template of the top 20 essential KPIs used by thousands of successful businesses to boost efficiency and increase profits. Get the guide now →  

Technician Bonus Cap: The Third Gate

The fix was simple, and it was agreed on the same call. Each technician's payout is limited to $400 per job. The 45% gross profit gate still decides whether a job pays at all. The 5% maximum still limits the rate. The new cap sits on top and limits the check.

Think of the three rules as three questions asked in order:

  1. Did the job make enough money? If gross profit is under 45%, there is no bonus.
  2. How much of that money can be shared? No more than the 5% maximum.
  3. Is any one technician taking too much from this one job? If the answer is yes, the payout stops at $400.

Here is a simple illustration of how the cap behaves. These numbers are examples, not figures from the company. If the formula produced $180 for one technician, the technician is paid $180. If it produced $400, the technician is paid $400. If it produced $520, the technician is paid $400 and the extra $120 stays with the company. The cap only touches the outliers, which is the whole point.

Why Leadership Worried About Changing the Number

The most interesting part of the call was not the cap itself. It was the hesitation. Technicians had already seen some of their bonus amounts in the platform, and the company's decision-maker was concerned that lowering a number they had already looked at would feel like taking something away.

That is a real risk with any change to a live plan, and it is the reason caps are best introduced before the first large payout, not after. In this case the team noted that callbacks could already trigger adjustments to a bonus, which meant the numbers technicians saw were never completely final. With that in mind, the company approved the $400 limit, and the ShareWillow team agreed to send the updated payout details to the two people running the plan.

If you are about to cap a plan that is already running, two habits help. Tell technicians what is changing before they see it on a pay stub, and explain that the cap applies to every technician the same way. A rule that treats everyone alike is much easier to defend than a one-time correction.

Putting the Money in Context

The production manager comparison deserves another look, because it frames the whole decision. A cap does not just protect a single payout. It protects the total.

Bar comparison of annual bonus spend against a production manager costing nearly half as much

When bonus spend is predictable, owners can compare it honestly with other options. A company that knows the most any technician can earn from a job, and the margin every job has to clear first, can ask a sharper question: is this plan buying quality, or is it just buying output? If the answer is quality, the program is worth keeping. If it is only output, a manager or a different structure may do more for the money.

Companies that have wrestled with this tradeoff usually end up tying the bonus to something the field can actually influence. One coatings company, for example, moved from hourly pay to a team bonus tied to forecast hours, which we cover in production pay vs hourly pay for crews. Another contractor funds its pool only on jobs above a 45% gross margin, the same gate used here, as described in the electrical installer bonus plan story.

Profit sharing

made simple.

Give your team a stake in the company’s success. ShareWillow helps you create and manage profit-sharing programs that motivate employees and drive business results.

Get a demo

Making the Plan Visible to Technicians

The second half of the call was about engagement. Technicians use ShareWillow to check their bonus figures, and at least one had already asked about his number. That is a good sign. A technician who asks about the number is a technician who cares about it.

Still, leadership wanted more. The company agreed to set up a walkthrough so the crew can see how to read their progress and their projected monthly earnings. The ShareWillow team also took on a follow-up item: look at ways to improve how technicians track their own progress during the month, so the bonus is something they work toward every day and not a surprise on payday.

The company also flagged a small account-status mismatch for one technician who was clearly using the app, and the team sent it to engineering to investigate. It is a minor detail, but it shows why a rollout benefits from a regular check-in. Small mismatches, left alone, turn into doubts about whether the numbers are right.

What a Cap Does Not Fix

A cap is a budget tool. It will not, on its own, reduce callbacks or free up a leader's schedule. The original goals, fewer callbacks and less field-management stress, still depend on the plan rewarding the right behavior. Callbacks already trigger bonus adjustments at this company, which is a step in the right direction, and the next conversation is about whether that signal is strong enough.

It is also too early for results. The company has agreed on the cap, the payout is being updated, and a follow-up meeting is on the calendar. What can be said today is narrower and still useful: three technicians crossed $400 on one job, the company set a limit, and leadership now has a predictable ceiling to weigh against the cost of hiring a production manager.

How to Set a Technician Bonus Cap

If you want to copy the approach, here is a practical sequence:

  1. Look at your largest payouts first. Sort recent bonuses by technician and by job. The right cap is usually just above what a strong technician earns on a normal job.
  2. Keep the margin gate. A cap protects the payout. A gross profit threshold protects the job. You need both.
  3. Cap per technician, per job. A per-job limit keeps one large project from distorting a month. It also keeps the rule easy to explain.
  4. Announce it before it bites. Tell the crew what is changing and apply it to everyone the same way.
  5. Review it against alternatives. If the bonus is not changing behavior, compare its cost with other options, as this company did with a production manager.

For more ways to structure payouts, our guide to bonus structure examples walks through common formulas, and the ShareWillow product features page shows how gates, caps, and tiers are calculated from your job data. Another company that protected margin while still paying real bonuses is covered in how a painting company protected margin while paying real bonuses.

The takeaway is not that $400 is the right number. It is that every bonus needs a ceiling, a floor, and a team that can explain both in one sentence. This company now can.

What is a technician bonus cap?

A technician bonus cap is a maximum amount a technician can earn from a bonus, usually per job or per pay period. This company limits each technician to $400 per job, on top of a 45% gross profit threshold and a 5% maximum rate.

Should you cap technician bonuses per job or per month?

A per-job cap keeps one large project from swinging payroll and is the easier rule to explain. A monthly cap can work too, but it hides which jobs are driving the payout. Many companies start with a per-job limit and add a monthly one only if they need it.

Does a bonus cap hurt technician morale?

It can if technicians first see a larger number and then watch it shrink. Introduce the cap before large payouts, apply it to everyone, and let technicians track their own numbers so nothing comes as a surprise.

Related reading

Conclusion

Cap the bonus per tech per job, keep the gross profit gate, and let technicians see their own numbers before payday.

Create incentives
that
drive results

You shouldn't need complex equity plans to align your team. ShareWillow makes it simple to create transparent profit-sharing programs that motivate employees and grow your business.

See the product

Incentive plans to help
small businesses thrive.

"I was able to leverage the knowledge of the ShareWillow team to learn how other companies were designing their bonus plans. The template was extremely helpful."

Brian Tustin
Owner, First Rate Movers

Download for Free

Related Articles

Diagram showing a $50 callback charge flowing back to the original HVAC install job

HVAC Commission Chargeback: How an HVAC Company Charges a Fixed $50 Callback Back to the Original Install Crew

HVAC commission chargeback explained: a fixed $50 callback charge follows the original install crew, and commission waits until the job is paid in full.

Continue reading

October 24, 2026

Motivate employees to act like owners, without complicated equity

Book a performance pay audit today, and let us show you how ShareWillow can help your business increase efficiency, reduce callbacks, and grow profits.