Picture two controls contractors in the same region. Similar top-line revenue, similar headcount, both well regarded by the engineers and facility teams they work with. On paper, they look like the same business. (They're a composite, drawn from patterns we see in conversations with owners and buyers, not any one company.)
Put both in front of the same buyer, and the reactions are very different. One gets a polite review. The other gets real interest, sharper questions, and a stronger offer. The difference isn't how much revenue each one brings in. It's what kind.
Quick take
- Buyers weigh your revenue mix early, often before they dig into the financials
- Service agreements and embedded systems work are easier to underwrite than project wins that must be re-won every year
- Your technical team is part of what's being bought, and dependence on any one person discounts it
Revenue Mix Comes Before the Financials
The first contractor grows mostly through projects: new installs, retrofits, and bid work won one job at a time. It's real revenue, often at good margins. But nearly all of it has to be won again next year. A buyer looking at that profile sees a capable sales engine and immediately asks how much of it depends on who is doing the selling.
The second contractor does similar project work, but a meaningful share of its revenue comes from service agreements, preventive maintenance, and ongoing support on systems it already installed. Much of that work renews without a new bid.
Buyers tend to read this mix early, sometimes before they open the financials at all. Recurring revenue under agreement is easier to underwrite because a buyer can see where next year's work is coming from instead of having to assume it.
Project-Heavy Profile
Most revenue comes from installs and bid work that has to be re-won each year. Service happens informally, usually when a customer calls. Relationships run through whoever sold the job. Next year's revenue depends largely on this year's sales effort.
Recurring-Revenue Profile
A meaningful share of revenue comes from service agreements and ongoing support. Customers are under contract, with defined scopes and renewal terms. Relationships run through the technicians who know the systems. A buyer can see much of next year's revenue before it's earned.
The part of your business you call maintenance is often the part a buyer calls valuable.
Why Embedded Systems Get Attention
You already know how this plays out. Once a BMS is running in a building, the contractor who programmed it and understands its quirks tends to stay involved. Facility teams call the people who know the system, and switching means time, risk, and a learning curve most building owners would rather avoid.
To a buyer, that stickiness matters. It doesn't guarantee a customer stays forever, and experienced buyers don't treat it that way. But it does make the relationship harder for a competitor to displace, and durability is exactly what they're trying to price.
The Team Is Part of the Deal
Experienced controls technicians and programmers are hard to find. A buyer looking at a controls business is often acquiring a team as much as a book of business, and they know how long it would take to build that team from scratch.
That's also where value can leak. As we covered last week, when critical knowledge lives with one person, whether that's the owner or a single senior programmer, a buyer sees risk where you see capability. A team whose know-how is shared and documented is worth more than one built around a single indispensable person.
What You Can Do Now
None of this requires changing the kind of company you run. It starts with seeing your own business the way a buyer will.
Know your split. How much of your revenue is project work, and how much is recurring? Track it the same way every year so the trend is visible, not reconstructed after the fact.
Know what's actually under agreement. Many contractors have loyal customers who call them for everything without anything in writing. To you, those customers feel locked in. To a buyer, a signed service agreement and a long-standing habit are two very different things.
Get the technical work out of people's heads. Programming standards, system records, and service procedures should exist on paper, not just in memory. Diligence will test whether the business can explain itself, and documentation is how it does.
Where CB Energy Fits
This is the kind of positioning work our two programs address. REV (Raise Your Enterprise Value) is built for owners with an 18-month to five-year horizon, with time to expand recurring revenue, build out a service division, and reduce key-person dependency. AR (Acquisition Readiness) is for owners considering a transition within the next 18 months, focused on clean financials, addressing concentration risk, and entering any process prepared rather than reactive.
The recurring, technical side of your business may already be your strongest asset. The goal is to make sure a buyer can see it as clearly as you do.