The handyman software shortlist, reviewed

What to take away

The nine products, and who each one suits

The nine below are a shortlist, not a ranking. They were picked to cover the shape of the market rather than to produce a winner: solo tools, small-crew tools, dispatcher-grade systems, and two built for adjacent trades. Crew size, pricing model and job type differ across the nine.

Jobber runs scheduling, quoting, invoicing and card payments in one app, and its mobile view is the one most technicians can use one-handed. Suits one to fifteen users, with a free trial. Published tiers are Core, Connect and Grow, and entry pricing typically runs $30 to $60 per user per month on annual billing as of 2026.

Housecall Pro adds a consumer-facing booking page and a strong payments layer. Tiers are Basic, Essentials and MAX, and Basic is capped at one user. Typical cost runs $60 to $200 per month by tier and billing cycle, as of 2026. Suits residential repair work where the customer books online.

ServiceTitan is the heavy end: dispatch boards, call booking, price books, and reporting deep enough for a multi-department contractor. Pricing is quote-based with no public rate card, and contracts usually run a year with implementation fees on top. Suits ten or more technicians with an office dispatcher.

FieldPulse covers scheduling, estimates, invoicing and maintenance agreements, and its custom-field builder is the reason it appears on handyman shortlists. Per-user monthly pricing typically runs $40 to $100 per user per month, less on annual billing. Suits three to twenty users.

Workiz handles dispatch, invoicing and payments with a phone system built in, which matters if the same person answers calls and runs jobs. Tiers are Lite, Standard and Ultimate, typically $65 to $225 per month by tier and user count. Suits one to ten users.

Service Fusion runs unlimited users on a flat monthly rate rather than a per-seat charge. Tiers are Starter, Plus and Pro, typically $200 to $500 per month as of 2026, with onboarding fees on annual contracts. Suits crews that grow and shrink with seasonal labor.

Kickserv is the lightest of the nine: scheduling, invoicing and estimates, with little else. Plans are Starter, Business and Premier, and a small crew typically pays under $200 per month, with user caps by tier. Suits a solo operator leaving a spreadsheet.

JobNimbus is strongest on the job as a tracked record with attachments and approvals, which suits insurance and hail work. Per-user monthly pricing typically runs $25 to $60 per user per month, with setup fees for larger teams. Suits roofers and exterior trades more than general repair.

Thryv bundles a customer record with marketing, listings management and review requests. Command Center tiers typically run $200 to $500 per month as of 2026, and contracts often run 12 months. Suits an owner who wants lead generation in the same tool as the invoice.

Those are typical market ranges rather than vendor quotes. Rates change without notice, so get the current figure in writing, including the cost of adding a second user.

QuickBooks and the export test

Two questions tell you more than any feature grid: where the invoice lands in your books, and what comes out of the system on the day you leave.

QuickBooks support splits into Desktop and Online, and the two are not interchangeable. Ask which version a vendor writes to. Treat "QuickBooks integration" without a version as an unanswered question, and get the answer in writing.

The same discipline applies to exports. Ask for a sample file from a live account during the trial, not after you sign.

Open the sample in a spreadsheet rather than a browser. If the photographs come back as a gallery you cannot download in bulk, what you have is a window, not an export.

What the title does not decide for you

A ranked list is wrong for most readers within a year, and wrong for some on the day it is written. Field service software is priced and shaped around team size. What suits a solo operator is close to useless at four routes, and a dispatcher-grade system will bury a one-person business in fields nobody fills in.

The deciding detail is often absent from any comparison table. Does property history exist independently of the customer record? Is a drive time field present and required? Can the technician use the view on a phone with cold hands? Those decide whether the system gets used at all.

The seven questions

Ask each vendor these, and ask for a demonstration rather than an answer.

The seventh gets deflected most often. Ask for a sample file rather than a description. Which measures are worth pulling out of the system is set out in the software and measurement overview.

The trial, on real jobs

Two weeks, on real jobs, with a deliberate mix. Book one job that changes scope on site. Book one callback to a job from the past month. Book one job for a customer you have never met. Book one long job that runs past the day you quoted.

Run it alongside whatever you use now rather than switching. Double entry for two weeks is cheaper than migrating twice.

Record three things per job: what took longer than it should have, what field got skipped, and what you worked around. A field skipped in a trial is skipped forever, and every report built on it lies quietly. How that expectation is set with a new hire is part of the hiring and training overview.

What a demo will not tell you

Three things surface in month three. How the app behaves with poor signal in a basement or a loft, and what happens to work recorded offline. What the cost becomes when a second user is added or the job count grows. Whether support answers at all.

Send a support question during the trial and time the response. That single test predicts more about your next two years than any feature list.

Security is part of the review

A system holding customer names, addresses, access notes and photographs of the inside of homes is holding something that has to be protected. Ask what multi-factor authentication is available, how access is removed when somebody leaves, and where backups live.

The NIST Small Business Quick-Start Guides are short and written for businesses this size, and CISA's resources for small and medium businesses cover the practical steps that prevent the most common incidents.

The records test

Whatever you choose has to produce records that satisfy the general obligation described in the IRS guidance on what kind of records to keep, with income and expenses shown clearly and supporting documents retained.

Two trade-specific checks. Job-level evidence, meaning the quote, the change approvals and the photographs, must be producible together for one job. And anything you refused and referred must be recorded, because work near a licensing boundary is exactly what you want a paper trail for, as covered in where the licensing line sits.

Worked example: scoring two candidates

Rank your requirements first, then score each product against that list rather than against each other.

Multiply weight by a score of 1 for yes, 0.5 for partial, 0 for no. Product A scores 10.5, Product B scores 8.5. The tie-breaker is which one the person on the road preferred, and which produced a complete export without a support ticket.

Deciding

Score the candidates against your ranked list. Then apply two tie-breakers: which one the person on the road preferred, and which one exported everything without a support ticket.

If nothing scores well, your business may sit between shapes, too big for a spreadsheet and too small for the tier that fits your requirements. Tighten the paper process and revisit in six months.

Running a system nobody fills in is worse than running none. The discipline it depends on is the same one behind the opening equipment checklist and how the van and kit are organized: a routine that works on a bad day.

Common questions

How much should this cost?

Ask instead what it saves. An hour a week of reconstruction, faster invoicing and fewer second visits are all measurable. A system that moves none of them is not paying for itself at any price.

Should I choose based on reviews from other trades?

Read them for the complaints rather than the praise. Complaints are specific and usually true, while praise in this category is often written during a honeymoon that ends at the first migration.

What about building something myself in a spreadsheet?

Viable for a solo operator, and it forces you to clarify your own data model. It stops working the moment two people need to write to it at once.

How do I migrate without losing history?

Export everything first and keep the file somewhere you control before touching the new system. Migrate customer and property records, and accept that some job history may arrive as attachments rather than structured data.