Does a Small Contractor Really Need a CRM?

Honestly? If you're a one-truck operation doing 30 jobs a month and nothing is falling through, no. A whiteboard and a phone work, and a CRM will cost you money and evenings to achieve the same result. The answer changes — sharply — the moment more than one person needs to know what's happening, and it changes for reasons that have very little to do with software.

The five signals you've outgrown the spreadsheet

Not one of these on its own is decisive. Three of them together usually is.

• You've lost a job you can't account for. Someone called, someone promised to call back, nobody did, and there's no record of any of it. This is the most expensive signal and the easiest to miss, because a job you never knew you lost doesn't show up anywhere.
• Two people need the same information and get it from each other. The moment your answer to "did we quote the Hendersons?" is "ask Dave," you have a system whose uptime is Dave.
• Quotes go out and nothing chases them. Most shops' single biggest recoverable revenue line is quotes that were never followed up. A spreadsheet does not chase.
• You can't answer basic questions about your own business. What's your average job value? Which lead source actually books? How many quotes converted last quarter? If those take an afternoon to work out, you're flying on feel.
• The same data gets typed three times. Once into the phone notes, once into the quote, once into the invoice. That's not a productivity problem, it's an error-rate problem — the addresses drift.

If none of that describes you, close this tab and go do the work. We'd rather tell you that than sell you a build.

What a contractor CRM has to do that a generic one doesn't

Most CRM software is designed for salespeople chasing deals over weeks. Contracting doesn't work that way — the "deal" is often a two-day cycle that ends with a van at an address. A system for the trades needs:

• Scheduling and dispatch, not just a calendar. Who is where, with which van, and what happens when the 10am overruns.
• Quote to invoice in one thread, so the approved quote becomes the job becomes the invoice without retyping.
• Job history against an address, not just a person. Homeowners move; the boiler doesn't.
• Recurring and maintenance work, which is the difference between a business with a pipeline and one that starts every January at zero.
• Something a tech can use on a phone with cold hands. The most beautifully configured system in the world fails here first.

The options, honestly compared

Four realistic paths, with real published pricing where it exists.

Jobber and Housecall Pro prices from their own pricing pages, checked 3 September 2026 (monthly billing; both discount for annual). Zoho CRM in USD: free for up to 3 users, then roughly $14–$52 per user per month depending on edition — Zoho's site serves prices in local currency, so check your region. ServiceTitan does not publish pricing; the range shown is third-party estimate, not a quote.

Two honest notes on that table, since we build the last row.

ServiceTitan is genuinely better than the alternatives above a certain size. The reporting, the dispatch board and the call-centre tooling are built for operations running dozens of techs, and shops that size do not regret it. What gets people hurt is buying it at eight techs: third-party estimates put implementation at $5,000–$15,000 for a small team with a six-to-twelve-month rollout and a twelve-month minimum contract. That is a serious commitment for a business that might change shape twice in that window.

Jobber and Housecall Pro are the right answer more often than we'd like. If your process is a normal residential service process, an off-the-shelf product that works on Monday beats a configured platform that works in six weeks. Jobber's top tier now bundles an AI receptionist of its own. We'd rather you knew that than found out after signing with us.

Where Zoho actually makes sense

Three situations, specifically:

• Your process is genuinely not standard. Multiple trades under one roof, a commercial arm with different paperwork, subcontractors with their own workflow. Off-the-shelf field-service tools are opinionated by design, and fighting those opinions costs more over three years than configuring something to fit.
• You want one system, not five subscriptions. CRM, invoicing, forms, email, documents and reporting inside one suite, priced per user rather than per tool, with the pieces already talking to each other.
• You care about owning it. The configuration, the data, the automations, the accounts — yours, portable, no lock-in. If you fire your implementer (us included), the system keeps running.

And where it doesn't: if you need it live next week, if nobody internally will own it, or if a $79 product does the job. Zoho's licence is the cheap part; the build is where the money and the time go.

The cost nobody quotes you

Licence price is the smallest of the three real costs.

• Licence. $0 to a few hundred a month depending on seats and tier. Predictable, and the number every vendor leads with.
• Implementation. Data migration, configuration, integrations, training. A few thousand for a straightforward Zoho build; five figures and half a year for enterprise field-service software. This is where budgets actually go.
• Adoption. The one nobody prices. A system your techs won't use has a total cost equal to everything you spent plus the work you lost while they went back to texting you.

The third one kills more implementations than the first two combined. The predictor is boring: whether one person inside the business genuinely owns the system, and whether the techs' daily path through it is shorter than the thing they were doing before. If entering a job takes longer than texting the office, they will text the office.

What actually breaks in a migration

• Duplicate customers. Same household, three spellings, two phone formats. Dedupe on phone number before you import, not after.
• Historical jobs with no structure. Ten years of invoices with the work described in free text. Decide early what you genuinely need queryable and accept the rest as an archive.
• Recurring maintenance schedules. Almost always the hardest thing to move, and the most valuable. Rebuild these by hand and check them twice.
• The accounting join. Whatever your books run on, the handoff is where reconciliation quietly goes wrong for a quarter.
• Your own head. The rules that live only in the owner's judgement — which customers get priority, when you waive a fee — have to be written down before they can be configured. This is usually the slowest part and it is not a software problem.

How to decide this week

1. Count the leaks. How many quotes are outstanding with no follow-up? How many calls last month have no record? Put a dollar figure on it using your average job value.
2. If that number is under a few thousand a year, do nothing. Seriously. Revisit in six months.
3. If it's material and your process is standard, trial Jobber and Housecall Pro. Both are cheap enough to test properly and you'll know inside two weeks.
4. If it's material and your process isn't standard — or you want one owned system — scope a configured build and get the scope fixed in writing before anyone starts.
5. Whatever you pick, fix the front door first. A CRM records what happened to leads you captured. It does nothing about the ones that went to voicemail, which for most shops is the bigger number.

If a configured system is where you land, that is what our Zoho system build is — scoped for a fixed price, built to your process, and yours to keep. And once it exists, the list inside it becomes an asset you can actually work: see reactivating past customers.