Evaluating a New Service Line Before You Commit
Why this matters
Most new service lines are added on a hunch: a tech says "I could do that," a customer asks twice, and suddenly it is in the catalog. Then margins sag and nobody can say whether the line is helping. Evaluating before you commit is the cheap insurance. The point is not a perfect forecast, it is forcing every soft assumption into the open where you can see which ones are actually load-bearing. A line that cannot survive honest questions on paper will not survive contact with the schedule.
Know what "commit" costs before you weigh it
You cannot judge whether a line is worth it until you are honest about the whole bill, most of which is not equipment. Committing costs you:
- Cash for tools, stock, training, and any licensing.
- Crew attention and owner attention, the scarcest resource in a small shop.
- Focus: every hour on the new thing is an hour not spent deepening the core.
- Exit cost: once staffed and marketed, a line is hard to unwind without cutting people.
The last two are the ones owners forget, and they are usually larger than the first two.
Demand: evidence, not enthusiasm
The single most common failure is launching into demand that was never there. Grade your evidence honestly:
- Strong: you already turn away or refer out this exact work, repeatedly, to customers you have. That is proven demand at near-zero cost to reach.
- Moderate: customers ask about it, competitors offer it and seem to be growing, real searches for it exist in your area. Worth a cheap test (see related: testing a new service before you go all in).
- Weak: you think people would want it, or one big customer asked once. That is a hypothesis, not demand. Test it before you spend.
Economics: compare the shape, not just the size
Compare the line's shape to your core rather than guessing at figures you do not have yet:
- Gross margin per job relative to the core. A line that runs at a materially thinner margin than your core has to clear a high bar to justify the attention.
- Utilization: how many billable hours a week can it realistically hold? A high-margin line that only fills a few hours is a hobby.
- Ramp: how long until a tech is efficient at it? Competency in a new trade skill is a long investment, not a weekend.
- Cannibalization: is it net-new revenue, or just moving work you already had? A line that eats your core is not growth.
Fit: how far from what you already do
The cost of a line is mostly the gap between what you own and know and what the line demands. The closer the fit, the cheaper and faster the ramp.
- Same trucks, same certifications, same customers, same sales motion is a true add-on.
- New licensing, new equipment, a different buyer, a different way of selling is a near-startup wearing your logo. Judge it as one (see related: the adjacent services that fit your trade naturally).
Attention and ownership: who feeds it
A new line with no clear owner starves. Before committing, name the person accountable for it hitting its targets, and be honest about whether they have the bandwidth or you are asking someone already full to do more. Protect the core: the plan cannot quietly assume your best tech now does two jobs.
The go/no-go scorecard
Score the candidate before you decide. Several weak answers is a no or a not-yet, not a maybe.
| Question | Green | Red |
|---|---|---|
| Demand | You already refer this work out | You assume people want it |
| Fit | Same crew, tools, buyer | New license, new market |
| Margin | At or above the core | Materially below the core |
| Utilization | Fills real weekly hours | A few jobs a month |
| Cannibalization | Net-new revenue | Moves existing revenue |
| Owner | A named, un-maxed champion | Nobody, or someone already full |
Green across the board is a launch. Mostly green with one red is a fixable gap to close first. Multiple reds is a line to test cheaply or leave on the shelf.
References
- U.S. Small Business Administration (SBA), market validation and growth planning
- Trade-standard practice on service-line ramp and margin analysis
- See related: Testing a New Service Before You Go All In; The Make-or-Buy Decision for a New Service; Add a New Service Line or Go Deeper in Your Core