The agency's headcount at the time the routing rule was put in place.
Sales could no longer contact the specialist directly, at all.
Every request routed through a single point of contact, evaluated against criteria the specialist wrote himself.
From the rule going in to the specialist running his own initiatives, uninterrupted.
Every growing business has one person everyone needs. Here, it was a senior technical specialist — the only one who could build the client-reporting dashboard the whole team depended on, and everyone knew where to find him.
That was the problem. By November 2023, sales was pulling him into calls, account managers were pinging him mid-build, and his actual project kept losing weeks to work that wasn't his to do.
Nobody decided to overload this specialist; it happened the way these things usually do — one urgent client question here, one "can you just hop on this call" there, and his actual project, the one only he could finish, kept sliding.
Two people on the leadership team named exactly what that was doing to him, in the same meeting where the rule got announced. "I don't think he's looking for a job, but I think he's burned out and stressed," the VP of Operations said. The President went further, tying it back to something the company claimed to stand for: "That's going against our core value of work-life balance and prioritizing our own well-being."
No single interruption was the real problem. Nothing in the day-to-day made an interruption cost anything — the real damage was the distance between the value on the wall and what was really happening to their best specialist.
A gatekeeper routing rule removes one person's ability to be reached directly by everyone who wants something from them. Instead of every request going straight to the specialist, it goes to one named person first — the gatekeeper — who checks it against criteria the specialist already agreed to. Clear the bar, and the request gets through. Miss it, and it waits, or gets handled another way. The rule doesn't make someone less available; it makes someone else responsible for deciding when they're needed, so the specialist isn't the one saying no to coworkers all day.
No training session. No reminder email. The VP of Client Experience installed a rule with teeth instead, and told the leadership team about it plainly: "I've met with the sales team to set hard boundaries on how they use his time."
The rule itself was just as direct — sales couldn't contact the specialist at all; every request had to go through the gatekeeper, who would evaluate it and decide whether the specialist needed to be involved.
There was no side channel left open, either — the rule named the exact workarounds it was closing off:
"Do not chat him and ask him to join a meeting. Do not email him to ask if he can join a call."
— VP of Client Experience
Every request had to clear that one named gatekeeper, checked against a list the specialist had written himself. Whoever knew what needed him was the one deciding, not whoever asked loudest.
| Before the routing rule | After the routing rule |
|---|---|
| Anyone in sales or account management could reach him directly, any time. | Every request routes through one named gatekeeper first. |
| No standard for what counted as urgent — whoever asked loudest got him. | Requests are checked against criteria the specialist wrote himself. |
| The client-reporting dashboard lost weeks to interruptions (November 2023). | The specialist ran his own initiatives without interruption (March 2024). |
| Pulling him into a call cost nothing for whoever did it. | Sales is barred from chatting, emailing, or messaging him directly. |
Swap "sales team" for "dispatch." Swap the specialist for the one foreman who runs a particular piece of equipment, or the office manager who's the only one who remembers how payroll gets processed (the person nobody ever wrote a backup plan for). Home service businesses run into the identical version: the lead installer pulled off a job because a salesperson oversold a same-day slot, or the one estimator everyone routes every odd job through because nobody trusts anyone else to price it. Neither business looks anything like the other on an org chart — the capacity leak looks identical in both, and the mechanism that fixes it travels just as cleanly. A named gatekeeper. Written criteria for when the interruption is worth it. One rule specific enough that "just this once" stops being an option.
A rule announced in one meeting doesn't rewire five weeks of habit on its own, and this one didn't.
By December 19, the President was reporting the opposite of a clean win: the specialist had been on PTO a lot and pulled into sales and other client issues, so his own project — the one the rule existed to protect — had barely moved. "That's delayed us significantly," he said. One rule existed on paper. Nothing was leaning on it yet.
What changed between that setback and the specialist showing up in February and March consistently owning his own work wasn't a second announcement — it was the gatekeeper holding the line, request after request, until routing around the specialist simply stopped happening. By February 20, the VP of Client Experience said he was now responsible for the software deployment, driving it himself. By March 5, she reported "good signs and good attitudes" and handed him something forward-looking instead of reactive — leading a developer-mentorship program instead of firefighting someone else's client call. March 12: he was still driving the project, with a defined team around him. Four months passed between the rule going in and it holding for real.
Most versions of this story skip that stretch; keeping it in matters, because a rule that survives its first bad month is the one that was ever real.
Build the exception into the criteria, don't leave it to habit. This agency's rule didn't say "never" — it said every request gets evaluated against criteria the specialist wrote himself, by a single gatekeeper, before it reaches him. Real urgency still got through; what stopped was everyone deciding for themselves that their own request counted as urgent. That distinction matters because urgency judged by the person asking is almost always inflated — a routing rule works precisely because it hands that judgment to someone with nothing to gain from calling everything urgent.
Because "please respect his time" isn't enforceable, and a routing rule is. December's setback happened even with the rule on the books — a rule nobody is actively holding turns into a suggestion. A gatekeeper is what makes a boundary a mechanism instead of a request.
Longer than one meeting. In this case, it took roughly four months from the rule being announced to the specialist consistently running his own work without interruption, including a real setback about five weeks in where the old pattern came back. Expecting an immediate, permanent result is what makes businesses give up on a good rule too early.
No. This mechanism is the same in a five-person crew as it is in a 100+-person agency. What matters is that one specific person becomes the decision-maker for "does this need to interrupt them" — and that person isn't the specialist, since they're the one least able to say no in the moment. Five-person shops don't need a VP title to run this; they need one person, even the owner, who agrees to say no on someone else's behalf. Whatever title sits on the gatekeeper's business card matters less than whether requests have to go through them before they reach the specialist.
For this agency, a delayed internal project and a specialist headed toward burnout on the company's own stated values. In a home service business, the same pattern shows up as missed installs, a foreman who quits, or an estimator who stops catching pricing mistakes because they're never given an uninterrupted hour to look at a job.
Same discipline, opposite direction. That piece protects time from clients calling after hours. This one protects time from other departments during business hours. Both come down to the same principle: a specific, named rule decides when an interruption earns its place. That judgment never falls to whoever's asking.
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.
A remodeling contractor's client texted him at 1 a.m. over a set of freshly refinished floors, the latest in a pattern of boundary violations his business had no system to prevent. Building a documented client policy, alongside a fixture-by-fixture pricing calculator, showed him where his responsibility ended and where his margin had been quietly leaking.
