The Founder Who Can't Stop Being the Best Technician in the Room

The Job the Founder Won't Give Up

A ten-person electrical contracting firm gets a call for a commercial panel upgrade with an odd load configuration. The office manager books it, the crew lead reviews the drawings, and then, almost automatically, the founder decides to run the job personally. Not because anyone asked. Because it's the kind of job that used to define the business, and the founder is still, by a wide margin, the best person in the company to do it.

This happens constantly in solar installation, electrical contracting, HVAC, and other technical trades. The founder learned the craft first, built a reputation on doing it better than competitors, and started the company specifically because they were good with their hands and bad at watching someone else make mistakes on a customer's roof. Years later, with a full crew and a growing customer base, that same founder is still the one who gets called when a job is complex, a system is misbehaving, or a client is nervous. The company has grown around the founder's skill instead of past it.

The pattern is worth naming because it's rarely a failure of effort. It's usually the opposite: a founder who has worked harder and more skillfully than anyone else in the building, and who has never been given a clear reason to stop.

Why the Best Technician Keeps Doing the Work

There are a few reinforcing reasons this happens, and they compound.

The first is simple scarcity. Skilled labor in solar and electrical work is genuinely hard to find. The U.S. Bureau of Labor Statistics projects continued strong demand for solar photovoltaic installers and steady growth for electricians, which means founders competing for talent often can't hire their way out of the problem quickly. If the applicant pool for a given trade is thin to begin with, as we've covered in hiring field technicians when the applicant pool is too small, the founder's own hands become the most reliable resource on hand. It's rational, in the short term, to keep using the one tool you know works.

The second reason is quality control anxiety. A botched electrical job or a poorly commissioned solar array isn't a minor service failure. It can mean a fire hazard, a failed inspection, or a system that underperforms for years while the customer blames the company. Founders who've seen what a bad install actually costs, in callbacks, liability, and reputation, develop a justified wariness about handing off the highest-stakes work. That wariness rarely gets reexamined as the crew's skill improves.

The third is psychological, and it's the one founders like least to admit. Being the best technician in the room is often the identity that built the business in the first place. Stepping back from the tools can feel like stepping back from the thing that made the founder good at this. There's also a quieter incentive at play: doing the complex job yourself is often more satisfying, and more legible as "real work," than the slower, ambiguous work of building someone else's judgment. Harvard Business Review's well-known framing of delegation, the "who's got the monkey" problem, describes exactly this dynamic: a task migrates back to the person at the top not because it must, but because it's easier for everyone else to let it.

What It Costs the Business

The cost isn't visible on a single week's schedule. It shows up over quarters and years, in the shape of the business itself.

A founder who remains the top technician sets a hard ceiling on revenue: the company can only take on as many complex jobs as one person can personally run or personally supervise closely enough to trust. Growth becomes gated by the founder's calendar rather than by market demand or crew capacity. Sales teams, if they exist, learn to undersell complexity because they know what happens to the founder's schedule otherwise.

It also stalls the development of everyone below the founder. Technicians who are capable of growing into lead roles don't get the harder jobs, because the harder jobs go to the founder by default. Their judgment never gets tested on anything that matters, so it never develops, which then reinforces the founder's belief that no one else is ready. The bottleneck creates the evidence that justifies its own existence.

There's a financial cost too, one that's easy to miss. Founders who spend their time on tools are, by definition, not spending it on estimating, pricing, vendor negotiation, or the sales conversations that determine whether jobs are profitable in the first place. Some of the underpricing problems common in trades, discussed in why home service businesses underprice their first jobs, trace back to a founder who never had the bandwidth to build a proper estimating process because they were on a roof.

How Founders Actually Transfer Judgment

The founders who get past this don't do it by simply deciding to delegate more. They build specific mechanisms that make delegation survive contact with a nervous customer or a difficult job.

One is job classification. Rather than deciding case by case who runs a job, some founders build an explicit tiering system: routine installs go to any qualified technician, moderately complex jobs go to a named lead technician, and only a defined, narrow category (unusual code situations, high-liability commercial work, first-of-a-kind installs) still requires the founder. Naming the category shrinks it, because it forces the founder to justify each job's inclusion rather than defaulting to it.

Another is shadowing before handoff. Founders who successfully step back typically spend a period running jobs with a second technician present specifically to absorb judgment, not just process. That means narrating the decision, not just making it: why this panel gets a subpanel instead of a direct tap, why this roof pitch changes the mounting approach. Technical skill transfers through repetition; judgment transfers through explanation.

A third is deliberately letting some jobs go wrong at a small scale. A founder who intervenes at the first sign of trouble never finds out whether a technician can recover on their own. Founders who've successfully delegated complex work often describe consciously staying out of a job long enough for a lead technician to catch and fix a mistake themselves, with a debrief afterward instead of a takeover in the moment.

Finally, some founders formalize inspection and sign-off as a separate role from execution, so the founder's judgment gets applied as a check on finished work rather than as labor on the job itself. That's a meaningfully different use of the same expertise: reviewing ten jobs a week instead of personally running two.

The Question Worth Asking

A useful test for any founder still running the toughest jobs is to ask what happens to next month's pipeline if they get pulled onto a two-week project. If the honest answer is that new sales stall or promised timelines slip, the constraint isn't the market, the crew, or the season. It's a calendar that only has one person capable of handling what the business now regularly needs handled.