Pay for the Work You Actually Want

Your payroll is giving instructions

Pay people for speed alone and don’t act shocked when they rush. Pay for sales alone and watch discounts, lousy-fit customers, and impossible promises multiply.

Every pay structure tells employees what matters. Sometimes it tells them something completely different from what you say at the morning meeting.

A productive pay structure has two parts. Base pay buys dependable, competent work. A bonus rewards a clearly defined result above the normal expectation.

The trick isn’t making employees hungry enough. It’s making the right behavior worth repeating without paying them to wreck something else.

For an established service business, that usually means balancing completed work, profitability, and quality. Not inventing seventeen metrics and calling the spreadsheet leadership.

Base pay buys competence, not miracles

Base pay is the predictable hourly wage or salary someone receives for doing their role properly. It should reflect skill, responsibility, and what replacing that person actually costs in your local market.

Build pay bands around demonstrated capability. Here’s an illustrative hourly structure for a service shop, not a market-rate recommendation:

• $23–$26: Performs defined tasks with supervision.
• $27–$31: Completes standard jobs independently and documents the work.
• $32–$36: Handles difficult jobs, trains others, and carries lead responsibility.

Write down what moves someone between bands. Certifications where relevant. Proven diagnostic ability. Consistent workmanship. Training competence. Not “seems ready” or “threatened to quit on Friday.”

At $28 an hour for 40 hours, weekly base wages are $1,120. If employer payroll taxes, insurance, and benefits add an illustrative 20%, the business spends $1,344 before overtime or bonuses.

That loaded cost belongs in your pricing and labor percentage calculations. The employee’s wage is not your full expense.

A bonus should be upside, not rent money held hostage. A weak base with a lottery attached creates turnover, not loyalty.

Fund the bonus before you promise it

A bonus pool is money set aside for employees when an agreed result is achieved. Start with the economics, then pick the payout. Not the other way around.

For a crew that shares jobs, a team pool can work better than individual commissions. It rewards finishing profitable work together instead of fighting over the easiest assignments.

Consider this illustrative monthly plan:

• Completed-job revenue: $100,000.
• Materials, subcontractors, and loaded direct labor: $60,000.
• Gross profit before the proposed bonus: $40,000.
• Predetermined gross profit threshold: $32,000.
• Amount above threshold: $8,000.
• Employee bonus pool: 15% of $8,000, or $1,200.

Gross profit is revenue minus the direct costs of delivering the work. Gross margin expresses that amount as a percentage of revenue: here, 40% before the bonus.

Suppose bonus-related employer costs add another $180. The total expense becomes $1,380, leaving $6,620 of the amount above threshold in the business.

That remaining money is not automatically net profit. It still helps cover rent, office payroll, vehicles, and other overhead.

The $32,000 threshold and 15% payout are examples, not universal benchmarks. Set yours using comparable operating periods, your overhead requirements, and a realistic budget. If normal work doesn’t cover the business, a clever bonus won’t rescue it.

Make the scoreboard fair and boring

Employees should be able to explain how they earn the bonus without you opening six tabs.

For that team pool, you might divide payouts by eligible hours worked during the period. An employee with 160 of the team’s 800 eligible hours receives 20% of the $1,200 pool: $240.

Define eligible hours, leave treatment, new starters, and departures in writing. Show the numbers weekly. Don’t move the threshold halfway through the month because the payout looks bigger than expected.

Only attach incentives to results people can meaningfully influence. Technicians shouldn’t lose a bonus because your quoting mistake demolished job profitability. Reception staff shouldn’t be measured on total sales when they don’t control capacity or pricing.

Use documented quality checks and completed-job records. Include genuine rework costs in job costing, but investigate their cause rather than automatically blaming whoever touched the job last.

If collections affect payout timing, explain that upfront. Cash flow matters, but office billing delays shouldn’t quietly become a field employee’s penalty.

Have payroll and a qualified local employment adviser review the plan. In the U.S., many promised performance bonuses affect overtime calculations for nonexempt employees. Budget for that before announcing a number.

Stop paying people to make expensive mistakes

These incentives look sensible until someone follows them exactly:

• Revenue-only commission: Encourages discounting and overselling. Tie rewards to profitable, properly scoped work instead.
• Jobs-per-day bonuses: Encourage cherry-picking easy jobs and rushing difficult ones. Account for job complexity and verify completion quality.
• Average ticket targets alone: Can reward unnecessary add-ons. Require legitimate customer need, clear authorization, and sound workmanship.
• Zero-reported-incident bonuses: Can encourage hiding injuries and near misses. Reward safety participation and following procedures, never silence.
• Manager-discretion bonuses: Turn compensation into a popularity contest. Publish the formula and any exceptions before the earning period starts.

Reviews can flag service problems, but one angry customer shouldn’t control someone’s paycheck. Neither should a bonus encourage begging for five stars.

Use SOPs to define acceptable work. The bonus rewards results within those standards. It doesn’t buy permission to skip them.

Fix the definition of winning first

Monday morning, pick one role or crew. Write down three things: what base pay buys, what earns extra, and what unacceptable behavior the incentive might accidentally reward.

Run the proposed formula against eight to twelve weeks of actual jobs. Include callbacks, overtime, and employer costs.

Then show employees a sample calculation and run a clearly labeled shadow period before launching it.

If you can’t explain the payout in two minutes, simplify it. Confusing pay is expensive bullshit.