Mechanical contractor valuation: service base vs construction backlog

How do buyers value a mechanical contractor?#

Buyers usually value a mechanical contractor on adjusted EBITDA multiplied by a market multiple, and the multiple they choose depends heavily on revenue mix. A company whose earnings come from planned maintenance agreements and repeat service customers looks very different from one whose earnings depend on winning the next hard-bid job.

This article does not quote multiples, because they move with the market, the buyer and the size of the company. What stays constant is the reasoning: buyers pay for earnings they believe will repeat, and they discount earnings that depend on bidding, bonding and the owner's estimating judgment.

Many buyers of commercial HVAC businesses say they are most interested in service work. For a seller, that puts the burden on you to show which part of the business behaves like a service base and which part behaves like a project contractor, with records rather than labels.

Service base vs construction backlog at a glance#

The service base and the construction backlog differ in how revenue arrives, where margin risk sits and what ties up cash. Buyers work through each line of this comparison when they form a view of earnings quality.

What counts as a recurring service base?#

A recurring service base is revenue that returns without a new bid: planned maintenance agreements, scheduled PM visits, controls and building automation support contracts, and the repair and replacement work those visits generate. Buyers also look at time-and-materials service from customers who call year after year, though they credit it less than contracted work.

Service agreement value depends on terms as much as volume. Buyers read the coverage level, price escalation language, term and renewal mechanics, cancellation rights and any clause that limits assignment to a new owner. A roster of agreements that renew automatically and can be assigned earns more confidence than the same roster on handshake renewals.

Be careful with what you label recurring. Warranty work, one-off equipment rentals and a tenant improvement customer who happens to buy service do not belong in the service base, and buyers will reclassify them during diligence if you do not.

The records that prove service revenue recurs#

The records that prove service revenue recurs connect an agreement to the visits it produced and the revenue that followed. A summary slide is not enough; buyers ask for exports from the field service system and match them to the general ledger.

If service history sits in a field service platform such as ServiceTitan, BuildOps or FieldEdge while projects sit in construction accounting software, build the link between them before a buyer asks. The same customer often appears in both under different names.

Renewal history is easier to defend when every cancellation carries a reason code: building sold, moved to a competitor, equipment replaced under a construction contract, or price. Buyers treat a cancellation caused by a building sale very differently from one lost to a competitor.

• 1Agreement roster by year with start date, renewal date, cancellation date and reason, so renewal history can be measured.
• 2PM visit records per agreement, showing scheduled versus completed visits and the technician who performed them.
• 3Deficiency findings from PM visits linked to quotes and approved repairs, which shows pull-through.
• 4Revenue by customer by year, so buyers can see customer cohorts and concentration.
• 5Technician hours split between service work and construction work.
• 6Equipment lists by site with make, model and age, from the service system or controls platform.

How buyers diligence the construction backlog#

Buyers diligence the construction backlog by testing whether past bids turned into the margins you expected. A large backlog raises interest, but the real question is whether it will finish at the margin shown on the work-in-progress schedule.

Margin fade on closed jobs is the record buyers weigh most. If your estimators consistently hit their numbers, show it job by job rather than as a blended average.

Bring the change order log into the same conversation. A contractor that recovers scope changes through signed change orders shows commercial discipline; one that routinely absorbs them shows a margin leak that buyers will extrapolate into the backlog.

Illustrative: separating two businesses inside one contractor#

Illustrative: a fictional commercial mechanical contractor runs a design-assist construction group and a service department that grew out of warranty calls. Its financial statements show one company, and the owner still estimates every large bid.

Ahead of a planned sale, the CFO splits the income statement into service and construction, tags every agreement in the field service system with its renewal history, and links PM deficiency findings to repair quotes. The construction group builds a closed-job margin report covering every bid since the current chief estimator was hired.

When buyers arrive, they see two businesses with their own evidence. The service base is underwritten on renewal and pull-through records, and the backlog is discussed against a clear record of bid-to-actual performance instead of a single blended margin.

How SourceX looks at service and project records#

SourceX looks at the same records from a different angle: whether PM findings, service calls, equipment histories and project change records can be licensed to AI developers once customer and personal details are removed. Records that connect a finding to a decision and an outcome rate well on several drivers in the SourceX Enterprise Data Value Framework, including domain expertise, human-generated signal and AI utility.

A license does not transfer ownership, and it is separate from valuing the company. If you license records before a sale, the license terms, exclusivity and permitted use will appear in diligence, so plan them with your advisors. The initial SourceX fit check collects only metadata about systems and record types, not files.