What plumbing contractor software should measure for first-year owners

What to take away

Start from the questions, not the categories

Write down the questions you cannot currently answer without guessing. Typical ones in a small plumbing firm:

Each question implies a piece of data that has to be captured by somebody, in the field, on a busy day. That capture problem is the real project. The software is the easier half.

The functions a plumbing firm actually needs

Two rules save money. Buy the smallest number of systems that cover these, because every integration is a place where data goes missing. And do not buy for a function you have not yet needed; the cost is not the subscription, it is the half-used system nobody maintains.

One category is easy to overlook. Safety training records, hazard assessments, and incident reports have to live somewhere findable. The Occupational Safety and Health Administration's Recommended Practices for Safety and Health Programs describes a program that depends on those records existing rather than being reconstructed. Decide which system holds them before you need one.

The five numbers

Pick five and hold them steady for a year. More than five and none get acted on.

First visit resolution rate. Jobs resolved on the first visit, over jobs attended. The most informative single number in service plumbing, because it moves with diagnosis, stocking, scheduling, and skill.

Callback rate. Calculate this as jobs with a return visit for the same issue within your written callback window divided by jobs attended in that measurement cohort, reported as a percentage. Apply the window consistently; there is no universal period or target. Exclude, for example, a documented return for an unrelated new issue or separately authorized added work, but count a return for the same unresolved issue.

Unbilled completed work. Work finished and not yet invoiced, in value and in days. The most common cash leak in a young trade business, and invisible unless you look.

Days to collect. From invoice to payment received, by customer type. Residential and commercial behave differently and should be tracked separately.

Booked contribution by channel. What each acquisition source actually contributes after direct costs, not what it grosses. This is what stops a channel producing small distant jobs from looking successful.

Write the formula, the data source, and the owner for each one before the first measurement. Most arguments about numbers turn out to be arguments about definitions.

Data quality, which is a field problem

A reporting system is only as good as what a technician enters at the end of a long day.

Four practices carry most of the weight.

The financial half of this has a standard to meet. The Internal Revenue Service describes a recordkeeping system that clearly shows income and expenses, with supporting documents behind each entry. IRS Publication 583, Starting a Business and Keeping Records, discusses this approach; supporting documents can include invoices, receipts, deposit slips, canceled checks, and bank statements. Meeting it is a reasonable baseline for the operational records too.

Security, because of what you now hold

A plumbing firm's systems hold customer addresses, photographs of the inside of their homes, notes on when they are away, and payment information. That is a serious set of data to be responsible for, and small firms are targeted precisely because they assume nobody would bother.

The National Institute of Standards and Technology's Cybersecurity Framework provides a cybersecurity risk-management baseline. The Cybersecurity and Infrastructure Security Agency's Cyber Essentials is guidance aimed at small businesses. Both cover practical fundamentals such as controlling access, keeping software updated, backing up records, and preparing to respond to incidents.

Five items are worth doing regardless of size.

The last one matters because field staff will do what is convenient unless told otherwise, and a photograph of a card in a phone gallery is a genuine liability.

What technology cannot fix

Software makes a good process faster and a bad process faster too.

A dispatch system will not fix an unclear service menu. It will make the confusion visible to more people at once.

An estimating tool will not fix prices that were never derived. That belongs in the pricing and profit guide. A quality dashboard will not fix an undefined defect, the subject of the service quality guide for owners.

Fix the process, then buy the tool that supports it. The reverse order is how firms end up paying monthly for a record of their own confusion.

Choosing without being sold to

Run every candidate through the same short evaluation.

Does it work in the field, on a phone, with gloves on? Can you export your data in a usable format without asking permission? What happens to your records if you stop paying?

How does it handle trade work: multiple visits to one job, change orders, partial payments? What does support look like on a Saturday?

Trial it on real jobs rather than in a demonstration. Two weeks of genuine use tells you more than any comparison table.

Rolling it out without losing a month

Introduce one system at a time, and start with job records rather than with reporting. The field habit is the hard part, and it has to exist before any number means anything.

Train it properly, which means writing down how your firm uses the system rather than pointing at the vendor's documentation. That belongs alongside the other operational training described in the hiring and training guide.

Two more things to check before committing. Whether the system's records satisfy the documentation your jurisdiction expects, which sits with the obligations mapped in the licensing and compliance guide. And whether it can produce the channel data you need to manage acquisition, described in the marketing and growth guide.

The monthly review

One hour, same day each month, same five numbers, same definitions.

Look at the trend rather than the level, and pick one thing to change. A review that produces five actions produces none.

Where a number moves, ask whether the business changed or the recording changed. A sudden improvement in first visit resolution usually means someone stopped recording the second visits. That is a data question before it is a performance question.

Hardware, which is part of this

The systems only work if the field devices do. Phones or tablets that survive a job site, mounts, charging in the vehicle, and a plan for connectivity where there is none. Treat these as equipment with the same replacement discipline as everything else, which is covered in the equipment and setup guide.

Offline capability deserves specific attention in this trade, because a great deal of plumbing work happens in basements and crawl spaces where a signal does not reach.

Common questions

What software does a small plumbing business need?

Job records, quoting and invoicing, payments, and bookkeeping. Everything else is an addition once a specific need exists. Which product depends on how you work, and no honest list can decide it for you.

How many numbers should I track?

Five, with written definitions, for a year. Adding a sixth is usually a way of avoiding acting on the first five.

Is a spreadsheet good enough?

For a solo operation, often yes, provided it is backed up and someone maintains it. The point at which it stops working is usually the second technician, when two people need the same record at the same time.

What is the most common mistake?

Buying a system to impose a process that does not exist yet. The software does not create the discipline; it records whether you have it.