SKIP TO CONTENT
5SHIRY
START A PROJECT
  • LIVE
  • CLIENT / SELECTED WORK
  • CH24-01
  • HVAC · home services

Comfort Homes 24

HVAC service across Greater Sacramento. The website had to stop losing enquiries.

comforthomes24.comSTATIC CAPTURE
Comfort Homes 24 homepage as it renders on a desktop browser, captured from the live site
OPEN LIVE SITE ↗

Real desktop capture of comforthomes24.com, taken . Activate live preview to load the site itself.

ROLE
Strategy · Design · Build · Automation
OWNERSHIP
Client project
SYSTEM
Service site + estimate and dispatch flow
STATUS
Live
01 / OVERVIEW

Comfort Homes 24 provides heating and air conditioning service across Greater Sacramento — repair, installation, maintenance, diagnostics, indoor air quality, and emergency callouts.

A client project, not a business I own. The brief was commercial rather than cosmetic: the site needed to convert the people already searching, and stop losing the ones who called.

02 / PROBLEM

Home-services customers rarely know what they need. They know a symptom — the AC is not working, the heat is out, the bill is too high. A conventional service menu asks them to self-diagnose before they can act.

Meanwhile every enquiry that arrived by phone had to be written down, priced, scheduled, and remembered by a person. That is where the losses were, not in the design.

03 / SOLUTION

Lead with the symptom, not the service. A triage entry point in the customer’s own language routes them to the right service, and the booking and estimate flows capture everything the office used to write on a pad.

  • Symptom-based triage: “My AC isn’t working”, “I’m not sure”
  • Book Service and Get an Instant Estimate as parallel paths
  • Service, membership, tune-up, and service-area pages
  • Enquiry routing with SMS confirmation and follow-up
  • Local search structure for Greater Sacramento
04 / MY ROLE

A website was the smallest part of it.

The visible site is one layer. The routing and automation behind it did the commercial work.

DISCOVERY + STRATEGY

Mapped how enquiries actually arrived and where they died. The triage concept came out of that, not out of a design trend.

INFORMATION ARCHITECTURE

Services, membership, tune-ups, and service area organised so a first-time visitor lands in the right place in one click.

BRAND DIRECTION

Worked with the existing mark and built a clear, high-trust visual system around it. Legibility over fashion.

UI/UX

Two parallel primary actions — book, or get an estimate — plus a plain-language triage for everyone who cannot choose.

FRONTEND + BACKEND

The site, the forms, the estimate logic, and the routing layer that decides where an enquiry goes.

AUTOMATION

Confirmation, routing, and follow-up without office staff retyping anything.

LOCAL SEO

Service-area structure and page architecture aimed at the searches that actually convert.

05 / LEAD FLOW

Where the enquiries were going.

A service business does not lose customers on price. It loses them in the gap between someone deciding to call and someone answering. Every step below used to be a phone call or a sticky note.

01Symptom

Visitor picks what is wrong in their own words rather than choosing a service code.

AUTOMATED
02Route

Triage maps the symptom to the correct service and urgency.

AUTOMATED
03Capture

Booking or instant estimate collects property details in one pass.

AUTOMATED
04Confirm

SMS and email confirmation immediately, scheduling confirmed separately.

AUTOMATED
05Follow up

Responsive follow-up on quotes and completed work, on a timer.

AUTOMATED
06 / SYSTEM INSPECTION

For the technical reader.

STACKCH24-01
FRONTEND
Next.js · React · Tailwind
BACKEND
Node · Postgres · form and routing layer
INTEGRATIONS
Twilio SMS · Resend · Google Business Profile
INFRASTRUCTURE
Vercel · managed Postgres
SEO
Service-area page structure, schema markup, local landing pages
07 / PROCESS EVIDENCE

Only the parts worth showing.

Marked slots below — drop in real screens, admin captures, or diagrams and this section carries the case study on its own.

DROP: triage wireframes
P01Symptom triageThe one idea that changed the conversion rate: ask what is wrong, not which service.
DROP: estimate decision tree
P02Estimate logicWhat could be answered instantly versus what genuinely needs a visit.
DROP: routing diagram
P03Enquiry routingWhere each classified enquiry goes, and what happens when a channel fails.
DROP: mobile booking screens
P04Mobile bookingMost emergency enquiries arrive on a phone, often in a hot or cold house.
08 / OUTCOME

Enquiries arrive structured and acknowledged instantly, and nothing depends on someone remembering to write it down.

Published performance figures are being measured properly before they go on this page. When there are numbers worth defending they will appear here — sourced and dated.

OPERATIONAL STATUS
Deployment
Live
Enquiry acknowledgement
Automatic
Manual re-entry
Removed
Published metrics
Client-held
OPEN THE LIVE SITE ↗
09 / NEXT

Losing enquiries between the phone and the calendar?

This is the most common problem I fix, and it is rarely a design problem. Tell me how enquiries reach you today.

START A PROJECT ↗OPEN LIVE SITE

5SHIRY · CH24-01 · CLIENT / SELECTED WORK/work/comfort-homes-24