Choosing handyman software by the measures you need

What to take away

What a system has to do, in order of value

Rank these before comparing anything, because the order decides which compromises you can live with.

Capture the job accurately at booking, including the qualification answers, so the technician arrives with the right parts, and produce a written scope with exclusions before work starts. Record what happened, including drive time and mid-job purchases.

Invoice quickly and take payment at the door, and hold property history so the next visit starts informed. Report so the numbers you decided to watch come out without a reconstruction exercise.

Almost every small operator gets the fourth right and the third wrong, and the third is where the useful data lives.

The data model: three objects

The customer is who pays. The property is where the work is. The job is what happened.

Keeping the first two separate matters more than it sounds. A landlord with six properties is one customer and six histories. A property changes owner and keeps its history. A tenant who calls is not the customer at all, and the question of who may approve extra work depends on that distinction.

The job links the two and carries the fields that make everything else possible: the qualification answers, the scope and exclusions, any recorded change approval, drive time, mid-job purchases, and the service family tag. That tag is what lets you compare service families later, and adding it retrospectively is close to impossible.

If a system cannot hold a property history independently of a customer, know that before you commit, because it is the limitation you will hit first as landlord work grows.

Four shapes of system

Moving up a shape is triggered by a specific failure rather than by ambition. Jobs being double-booked. A technician arriving without parts because the qualification answers were in somebody's head. Invoices going out late because reconstructing what happened takes an evening. Any of those is the signal.

Examples to test include Jobber, Housecall Pro, Workiz, and FieldPulse. Treat them as candidates, not a ranking: check whether each can capture the fields you need and produce your measures before choosing.

Choose the measures first

Pick a small number of measures and check that a candidate system can produce each of them without manual work. Five or six is plenty, and they should span the whole business rather than clustering on money.

Track the metrics that change a decision.

Use these six measures as a starting set, and confirm that the system captures the fields needed to produce them:

Each of those depends on a field being captured at the time. That is the real test of a system: not what it reports, but whether the person on the route will actually fill in the field on a wet Thursday. A field that gets skipped produces a report that lies.

Booked work against break-even and contribution by service family are useful in pricing: compare job revenue with the direct time and costs recorded, then review pricing assumptions where contribution is weak. The pricing overview explains the broader framework. For marketing, use inquiry-to-booking conversion by source to see which channels deliver booked work; the marketing and growth overview covers the wider plan.

Security comes with the data

The moment you hold customer names, addresses, access notes, and photographs of the inside of their homes, you are holding something worth protecting. Access notes in particular: a system that records where the key is kept is a system that has to be secured properly.

Two federal sources publish guidance written for businesses this size rather than for enterprises. The NIST Small Business Quick-Start Guides set out the basics in short documents, and CISA maintains resources for small and medium businesses covering the practical steps that prevent the most common incidents.

A departing technician's access is the one owners forget, and it is the one that matters, because they have the customer list and the access notes in their pocket. Removing it belongs in the offboarding routine alongside the parts of the hiring and training overview that cover handover.

What the records have to satisfy

Whatever the system, it has to produce records that meet the general obligation described in the IRS guidance on what kind of records to keep: income and expenses shown clearly, with documents supporting purchases, sales, payroll, and assets.

Two additions that are specific to this trade. Job level evidence, meaning the quote, the recorded change approvals, and the photographs, because that is what settles a dispute. And a log of the safety checks, which is what turns the standing program OSHA describes in its recommended practices for a safety and health program from an intention into something demonstrable.

Where you work near a licensing or permit boundary, the record of what was refused and referred matters too, and the categories come from where the licensing line sits.

Plan the exit before the entry

Before committing to anything, ask one question: how do I get all of this out, in a form somebody else can read?

Ask for a sample export rather than a promise. Request CSV files for customer, property, and job records, plus the related photographs as downloadable image files or an archive. Check that the records retain identifiers that show which photos belong to which jobs. Confirm what happens to your data if you stop paying, and how long you have to retrieve it.

A history of every property you have worked on is valuable, and it is the thing most likely to be trapped. That value depends on consistent fields, which comes back to standards and to the kit that lets a technician complete a job properly.

See the van and kit setup and the measures in the service quality overview.

Common questions

Is paper acceptable for a solo operator?

For a while, and it is better than a system nobody fills in. What paper cannot do is answer questions across many jobs, so the moment you want to compare service families or track second visits, it has reached its limit.

Should the accounting and the job system be the same product?

Not necessarily, but they should exchange data without retyping. Manual re-entry is where errors and delays come from, and it is also what stops small businesses invoicing quickly.

How many measures should I track?

Few enough that you look at all of them monthly. A dashboard with twenty numbers is read as decoration. Five that you would act on is a management system.

What if the technicians will not use the system?

Then the system is wrong, or the fields are, and this is worth taking seriously rather than treating as a compliance problem. Ask which field is annoying and why. Usually one or two are badly designed and everything else follows once they are fixed.