When a production manager's criticism gets personal, sales reps adapt the way most people do: they avoid the trigger instead of confronting it. They quietly stop selling whatever job type sets him off. Nobody chooses to lose that work. It just stops showing up in the pipeline.
Nora (not her real name) runs a foundation and crawl space moisture-control company. Her production manager had made a quiet, well-intentioned decision about his own pay. It was now steering which jobs her sales team would sell.
When a production manager's criticism gets personal, sales reps adapt the way most people do: they avoid the trigger instead of confronting it. They quietly stop selling whatever job type sets him off. Nobody chooses to lose that work. It just stops showing up in the pipeline.
Nora (not her real name) runs a foundation and crawl space moisture-control company. Her production manager had made a quiet, well-intentioned decision about his own pay. It was now steering which jobs her sales team would sell.
Her production manager had been training a crew member and wanted to reward it. He gave up part of his own bonus without telling ownership:
"I understand why he did it, and I commend him for making the choice to try to encourage him. But I can feel he's feeling the stress because he's not making what everybody else is making in bonuses. It's kind of a weird thing to navigate, because it's of his own thinking." — Nora.
The math was simple. Smaller bonus share, same job, same hours. Within weeks, the strain showed up somewhere else entirely: not as a request for a raise, but as scrutiny. "Last week there was a bit of an issue with the one project, and now all of a sudden he's nitpicking every project," Nora said. One real mistake on one job turned into heavy criticism of every job on the board.
The criticism wasn't abstract, and it didn't stay contained to the one job that started it. He began pushing back hard on how jobs were designed, scoped, and priced, heavily enough that Nora's sales reps started quietly avoiding the job category he complained about most, just to skip the argument. "He'll criticize very heavily how the jobs are designed, scoped, priced, et cetera, to the point where our salesmen will shy away from selling that type of job to avoid conflict," Nora said. This wasn't the first time. "We've had it happen with two or three salesmen in the past," she said, and now she was watching it start again with her most consistent rep. That rep had just closed a $30,000 foundation job the week before the foreman's scrutiny ramped up, the exact kind of job at risk of quietly disappearing from the pipeline if the pattern held.
Stuart Trier, CEO of Clear Results, named the missing structure directly:
"That's the container that needs to be held for whoever brings production and sales together. Otherwise it becomes you versus me." — Stuart Trier.
Without a real process connecting the two departments, every disagreement turns into a contest over who wins instead of what the job needs, and the same contest repeats itself on the next disputed job too.
A pay band is a defined range for a role: foreman, trainee, technician, set in advance and applied the same way every time someone qualifies for it. Discretionary pay works the other way. In the moment, a manager decides what someone earns, based on personal judgment instead of a fixed rule.
Discretionary decisions aren't automatically wrong. A generous one, like sharing a bonus with a trainee who's stepping up, can be exactly the right call in isolation. What happens next is where it breaks down: nobody agreed to it in advance, nobody can point to a rule that explains it, and the person who made the call has no path to reverse it except living with the financial hit. A pay band closes that trap. The trainee's progress still gets rewarded, but through a defined level change everyone already understands, and the manager who trained him keeps his own paycheck intact.
Most home service business coaching programs stop at telling an owner to "set clear expectations" and leave the actual mechanics there. An operating-system advisor goes further: building the pay bands, the change-order gate, and the meeting structure that make the expectation enforceable instead of aspirational.
| Signal | Personal feedback loop (no container) | Structured alignment container |
|---|---|---|
| Who raises a scoping concern | Whoever is frustrated that week, informally | A scheduled review, every time, regardless of mood |
| What a mistake becomes | A pattern of criticism on every future job | A single logged issue, reviewed once, closed |
| Who absorbs the tension | Sales reps, by quietly avoiding a job type | The process, through a defined change-order step |
| Compensation changes | A manager's individual call, made unilaterally | A defined pay band, applied the same way to everyone |
None of this closes the underlying speed difference on its own. His crew really is slower than the company's other crew, a real efficiency gap that a structured meeting format doesn't fix. What the meeting format does is stop that gap from being litigated job by job, in public, at sales reps' expense. Nora is already training a third crew for spring. Closing the speed difference itself is still a separate, unfinished project, one that a better conversation alone won't touch.
The pattern isn't specific to foundation work. A commercial flooring subcontractor's field superintendent gives 40% of his own completion bonus to a trainee he's mentoring, without telling the company. His own pay drops. Within a month he's complaining that estimators are pricing jobs too thin, the same complaint, the same root cause, a different trade. It shows up on the sales side too: a custom pool builder's excavation foreman hates the tight shoring tolerances that infinity-edge pools require, and criticizes any rep who sells one. Reps stop pitching infinity-edge designs and steer customers toward flat, low-margin fiberglass shells instead. That profitable, premium category quietly disappears from the pipeline for the same reason every time. Nobody built a structure for the disagreement, so the disagreement won by default.
Separate the feedback from the person delivering it. Route every scoping or pricing disagreement through a scheduled review instead of letting it surface as informal criticism on the next unrelated job. Log a one-time issue and it gets solved once; leave a complaint pattern unstructured and it trains reps to avoid the category entirely. This calls for a procedural change, and not a personality conversation with the manager.
Address the decision and the underlying gap separately. Acknowledge the intent if it was a generous one, but don't let it stand as an informal precedent. Replace it with a defined pay band that would reward the same behavior without leaving the original decision-maker financially worse off. Skipping this step means the same workaround resurfaces the next time someone wants to reward a trainee.
Not quite: a typical home service business coach hands an owner general guidance and checks in periodically, while an operating-system advisor goes further, building the specific mechanism itself (a pay band, a change-order gate, a meeting structure) live, with the owner, using what happened in the business that specific week.
Install a recurring meeting where sales and production review the prior week's jobs together, comparing actual costs and time against what was quoted. Treat every disagreement as a single item to resolve in that meeting, and don't let either side carry a standing grievance into the next job. The goal is a shared record both departments trust, well ahead of scoring a winner.
Check where the complaint lands. A direct request for more money is a straightforward pay dispute. Criticism of unrelated work, tighter scrutiny of other people's jobs, or scope arguments that only started after a pay change point somewhere else: the money triggered it, but the missing piece is a process for airing the actual complaint directly instead of sideways.
Yes, and it's common. Two crews doing the same work rarely run at the same pace, for reasons that have nothing to do with effort. Training history, team composition, and side responsibilities all affect speed. The actual mistake is leaving that gap undocumented. It then gets settled through informal blame instead of a scorecard everyone could just look at together.
This piece is based on a real Clear Results advisory conversation. Some details have been adjusted to protect client confidentiality.
Stuart Trier is the Founder and CEO of Clear Results. Over the past 20 years, Stuart has built, bought, and sold 11 companies across the home service, healthcare, and marketing industries. He built his first company from startup to $8M in revenue in 3 years before a successful exit, then built a chain of 28 healthcare clinics and sold the business to a publicly traded company. Following that acquisition, Stuart spent 3 years working alongside the CEO, helping lead the organization through a take-private transaction before participating in a nine-figure exit to a Fortune 10 company. Today, he's the lead investor behind an electrical services platform operating across 3 U.S. states, and has worked directly with owners through 1,800+ strategic advisory sessions.
