What an HVAC Website Taught Me About Cutting Scope

The build for my HVAC client was fast, a few focused days with nothing exotic in it. What took longer was working out what mattered for a business that had never had a website before.

It wasn’t animations, and it wasn’t clever copy. It was a phone number that’s impossible to miss and service pages that match what people search for in their area.

What I left off the first draft

I didn’t overbuild the first version. There were no extra pages, no blog section nobody had asked for, and no dynamic service-area map that would have looked great and answered a question nobody was googling. After talking with the client about their needs, I thought through the four or five things a homeowner searching “AC repair near me” is trying to do. Call, check that they serve the area, see what they fix, and decide whether they look trustworthy. The site is built around those, and anything that didn’t help one of them stayed out.

That list is short on purpose. A homeowner with a broken air conditioner is not browsing. They’re hot, they want a person on the phone, and every extra thing on the page is one more thing between them and the number.

Who the shiny parts are for

There’s an instinct, especially when you build things for a living, to show off what you can do. I feel it too. But it’s worth asking who that’s for, the client or you. If your client isn’t technical, a pile of bells and whistles is more likely to overwhelm them than impress them, and a clean home page with a prominent phone number tends to do the impressing instead.

Most of what I’d call engineering on that project was restraint, not cleverness.

The technical stack was the same story. It didn’t need to be impressive. It needed to load fast, rank locally, and get out of the way, and every choice I made was measured against those three jobs. The parts of the project I’m proudest of are mostly things a visitor never notices because nothing slowed them down.

Cutting is harder than adding

Adding is easy, because every feature comes with a reason you can defend in a meeting. A blog is good for search. A map is good for showing coverage. Cutting is harder, because you have to defend the absence of something, and the only defense is knowing exactly who the page is for and what they came to do.

I’m not immune to the instinct either. The service-area map would have been the most fun thing to build on the whole project, and leaving it out was a small disappointment. I’d rather send a client a small, fast site that does four things well than a big one that does fourteen adequately, since they can always add later and can’t easily win back the attention a cluttered first version loses.

For the builders reading this: what’s a project where you learned more from cutting scope than from adding to it?