Planned Maintenance for HVAC Firms: The Contracts That End Feast and Famine

There are two kinds of month in a reactive-only HVAC firm, and neither is any good for sleeping. In the hot months the phone will not stop, you turn away work you would kill for in March, and every job runs at a sprint. In the mild months the vans sit, the overdraft creeps, and you quote thin because you are hungry. Planned maintenance is how HVAC firms get off that curve. This post is about the money: why HVAC planned maintenance contracts smooth revenue and lock in commercial clients, how to structure a simple PPM offer without guessing at numbers, and the unglamorous operational failure that quietly kills these contracts after you have won them. It pairs with our HVAC software page, which covers the tooling side of the same work.

The feast and famine curve

Reactive work arrives with the weather, not with your capacity. A heatwave stacks up AC failures faster than you can book them. A cold snap does the same for heat pumps and heating. In between sits the quiet, and the quiet does the real damage.

Fixed costs do not pause for it. Wages, van finance, insurance and the unit rent roll on through a slow April exactly as they do through a frantic July. So you quote thin in the quiet months because the diary is empty, and those thin quotes quietly set your market price for the rest of the year. Hiring gets harder too: you cannot promise steady hours, so you either do not hire and burn out the team every peak, or you hire and sweat the payroll every trough.

A reactive-only firm is not really running a schedule. It is renting itself to the weather.

What a planned maintenance contract actually buys you

Planned preventative maintenance, PPM in the trade's shorthand, inverts that shape. A commercial client pays an agreed amount across the year for scheduled visits to kit you both know. Four things change, and all four are money.

• Revenue arrives on a schedule you set, priced in advance, whether the weather cooperates or not.
• The contract client calls you first when something breaks. A PPM agreement is, in practice, right of first refusal on every breakdown on that site.
• The kit is known. Your engineer walks into a plant room they have seen before, with history, instead of diagnosing a stranger's installation at emergency pace.
• A book of maintenance contracts is an asset. A buyer can value it, a bank can lend against the story it tells. A phone that rings in heatwaves is not an asset. It is a weather report.

None of this needs a glossy brochure. It needs an offer you can deliver and a schedule you can keep. The second half of that sentence is where most firms fall down, and we will get to it.

Structuring a simple PPM offer

Three decisions: how often you visit, what a visit covers, and what it costs. Take them in order.

Visit frequency, by equipment type. Resist the urge to invent a number. Three anchors already exist. First, the manufacturer's service schedule, which is often a condition of the warranty your client wants to keep alive. Second, the law: for systems above the F-Gas charge thresholds, mandatory leak checks already recur at fixed intervals set by charge size, so for larger kit part of your visit calendar is written by regulation before you sell anything. Third, duty cycle: a condenser over a kitchen extract lives a harder life than a split unit in a quiet office, and its visits should come round sooner. Frequency by equipment type and duty, anchored to warranty and law, is defensible in front of any client. A number picked to win the deal is not.

What a visit covers. Write a checklist per equipment type and do the same work every time: filters, coils, condensate drains, electrical connections, controls and setpoints, refrigerant checks and records where the system size requires them, and a short written report after every visit. The report is the product. The client cannot see a clean coil from their desk, but they can file a dated report that says their kit was looked after by someone competent. Clients renew on the reports.

The pricing thinking. We will not hand you a benchmark number, because any number we printed here would be a guess about your patch, your kit mix and your drive times, and guessed benchmarks are how firms talk themselves into bad contracts. Build it from your own costs instead: realistic hours per visit including travel, consumables, a fair share of overhead, multiplied by visits per year, plus a margin you would defend to the client's face, divided into a monthly figure. Then make one more decision explicitly: what happens when the kit breaks between visits. Discounted labour rate, priority response, an included allowance, whatever you choose, write it into the agreement. Ambiguity about call-outs eats PPM margin from month one. And resist underpricing to win the logo: an underpriced contract becomes an obligation you resent, the service quality sags with your enthusiasm, and the client notices sag long before renewal.

How these contracts actually die

Not in a dramatic cancellation. Quietly.

The schedule lives in one person's head, or on a wall chart in the unit. Reactive work always shouts louder than planned work, so the spring visits slip into summer. Then comes the fatal moment: the client notices before you do. The facilities manager sends the email that says "I think we were due a visit in May?" and the entire value of the contract inverts, because the thing they were paying for was not the filter change. It was not having to think about the filter change. You have turned their peace of mind back into their chore. At renewal they say "we are getting a couple of other quotes", and nobody ever says why.

There is a second, slower leak: paperwork drift. The visit happened, but the report went unsent and the invoice went out three weeks later, which strangles the smooth cash flow the contract existed to create. We wrote about that half of the disease in how to get invoices paid on time.

Read both failure modes again and notice neither is a competence problem. The engineering was fine. The memory failed.

The record book answer

The fix is a record book with dates that surface. Every unit of kit on file, per client and per site: model, refrigerant, charge, service history. Every unit carrying its next-service date. And the week's planned visits landing in the diary alongside the reactive work, booked like real jobs, so planned work stops being the thing that gets bumped when the phone rings. That is the whole mechanism. There is no cleverness in it, only the discipline of writing things down where they will resurface on their own.

This is where OptiTech Automation fits. Equipment records are held per customer and site, next-service dates sit on file, and planned visits are scheduled across the year so they land on the calendar without anyone keeping a wall chart, each visit carrying the site history so the engineer walks in knowing the kit. Record keeping is on every plan; automatic reminder sends to customers are part of the Growth plan. Standard is £599 a month plus a one-off £249 Onboarding Investment for up to 15 people on the tools, and Growth is £1,749 a month for up to 30. That is a band, not a flat price whatever your size, and we would rather say so here than have you discover it on a call. Both bands, and the smaller tier below them, are set out on the pricing page.

The honest line: if you hold two or three contracts and run one van, you do not need software to keep them alive, and we are the wrong purchase this year. A spreadsheet, a wall calendar and the discipline to look at them will carry that book fine. The tool earns its keep at the point where the contracts outgrow the head that has been holding them.

What steady money changes

One last thing PPM revenue buys you, and it may be the biggest: it changes the shape of your growth decisions. With contracted visits on the calendar for the next twelve months, taking on another engineer stops being a leap of faith about next summer's weather and becomes arithmetic against work you have already sold. We walked through that exact calculation in the second van decision. Feast-and-famine firms grow by gambling. Contract firms grow by counting.

If the maintenance side of your week is the part that keeps slipping, the servicing, booking and dispatch tooling is on the HVAC software page. And if you want the broader picture of how online booking works for UK trades before you talk to any vendor, ours included, the plain-English guide covers it with no demo call required.

Common questions about HVAC planned maintenance

How often should a planned maintenance visit come round?
Take the frequency from three places rather than picking a number: the manufacturer's service schedule, which is often a warranty condition, the mandatory F-Gas leak-check intervals for systems above the charge thresholds, and the duty cycle of the kit itself. A condenser over a kitchen extract earns visits sooner than a split unit in a quiet office.

What should a PPM contract cost?
We will not print a benchmark, because any figure would be a guess about your patch, your kit mix and your drive times. Build it from realistic hours per visit including travel, consumables, a share of overhead, multiplied by visits per year, plus a margin you would defend to the client's face, then divide into a monthly figure.

What happens when the kit breaks between scheduled visits?
Decide that before you sign, and write it into the agreement. A discounted labour rate, a priority response window, an included allowance of hours, any of them can work. What kills margin is leaving it unsaid, because every emergency call then becomes a negotiation you are having while the client is already annoyed.

Why do maintenance contracts get cancelled?
Rarely over a dramatic failure. The usual death is a visit that slips because reactive work shouted louder, and the client noticing before you do. The moment a facilities manager has to ask whether a visit was due, you have handed their peace of mind back to them as a chore, and that is what they were paying to avoid.

Planned visits only hold if they land in the same diary as the reactive work, and the live demo shows a week where both sit together.