Software for plumbers in San Diego

Plumbing looks like a single trade and behaves like two. One half is an emergency service where the decision is made in under a minute by whoever speaks first. The other half is planned work — repipes, water heaters, fixture replacements, remodels — that is considered for weeks and decided by whoever stayed in touch. The mistake is building software for one of them and assuming it serves the other.

The emergency half is a phone problem, entirely

There is no clever version of this. A homeowner standing over a spreading puddle is working down a list of numbers, and the list stops at the first person who answers. Search rankings, site design and reviews all contribute to being on that list. None of them help once the call is ringing.

For a small plumbing shop this is brutal arithmetic, because the person who would answer is under a sink. The options are a person whose job is the phone, or an answering system that picks up on the first ring, establishes the address and the nature of the problem, recognises urgency and escalates it immediately.

The failure mode worth naming: a system that tries to book an emergency into a calendar slot. Urgent calls should be triaged and handed to a human within minutes. Anything else is a worse voicemail.

The planned half is a memory problem

Here is the work that most plumbing shops leave on the table. Every service call produces observations — a heater near the end of its life, galvanised pipe that will need attention, a pressure regulator on borrowed time. The plumber mentions it, the homeowner says they will think about it, and the note dies in the van.

Those notes are a dated list of known future jobs at known addresses, with a known relationship already established. Nobody else in the market has that list. Keeping it and acting on it is the highest-return thing available to a plumbing business, and it requires a CRM (the framing shops page covers the mechanics) only in the loosest sense — a record with an address, an observation and a date to raise it again.

What the website is actually for

Two distinct jobs, and it is worth being clear about which is which.

For emergencies, the site exists to get you onto the list and to put a tappable number in front of someone in a hurry. It needs to load on poor signal, name the neighbourhoods you cover, and make the number the most prominent element on every page. Nothing else matters much.

For planned work, the site does the persuading. A homeowner choosing who repipes their house is doing research, and pages that explain what the work involves, how long it takes and what the disruption looks like are read carefully. This is where depth pays.

Reviews carry unusual weight here

Plumbing is chosen under stress and with little ability to judge quality in advance. A homeowner cannot assess a solder joint, so they use other people’s experiences as the proxy. That makes the review habit more valuable in this trade than almost any other.

The habit that works is undramatic: one link, sent to every finished customer, every time, without pleading. A steady accumulation over a year reads as a real business. A cluster of five arriving in one week reads as something else, and readers notice.

A sensible order

Cover the phone. Start keeping the observations. Then improve the site, and only then consider automation (the HVAC shops page covers the mechanics) for reminders and review asks.

Two businesses, one phone number

It is worth restating the split plainly, because it decides what to build.

The emergency side is won on speed and lost on a ring-out. It needs coverage and nothing clever. The planned side — repipes, heaters, remodels — is won on presence over weeks and lost on a note that died in a van. It needs a record and a date, not speed.

A shop that builds only for the first has no planned work pipeline. A shop that builds only for the second bleeds urgent calls to whoever answered. The HVAC hub describes a close cousin of the second problem, where the existing customer list outperforms new traffic for the first year.

The demos are running, the general contracting page covers the shared ground, and starting a project takes one sentence.

The five pieces

Every one of these is built separately and sold separately. Most shops need two of them, not five, and the order matters more than the count — a CRM with nothing feeding it is a very tidy empty room.

• Website — The site itself — pages, photos, forms, speed, and the search work that makes it findable. Page in progress.
• CRM — Where a lead lands, who owns it, and what happens on day two, day seven and day thirty. Page in progress.
• AI receptionist — Answers the calls nobody can pick up, asks the qualifying questions, books or hands off.
• Automation — The follow-ups, reminders, review asks and status updates that stop depending on memory. Page in progress.
• Estimator — A structured way to turn a job into a number, the same way twice, without a spreadsheet. Page in progress.

If you would rather see the software than read about it, the demos are real and seeded with sample data, and the process page covers how a build actually runs. When you are ready, start a project.