Key takeaways
- A notebook hides your pipeline. A CRM shows every live lead, open quote and scheduled job in one glance, so nothing escapes. This single change pays the rent.
- A trades CRM follows a job lifecycle — lead, quote, job, done, follow-up — not a sales funnel that ends the moment a deal closes. The finish line for you is the start of the relationship.
- Eight features matter most, and everything else is noise until a specific job is lost without it. Hunt for the eight, not the brochure.
- Off-the-shelf job-management software gets you going fast and cheap, but per-seat fees and data lock-in stack up over years. A custom CRM earns its keep when your pricing rules, branches, mobile workflows or ownership goals do not fit a template.
- Roll out in four phases, one crew and one habit at a time: capture, shift off paper, automate a single reminder, then adopt reporting. Instant, perfect adoption does not exist.
- Measure response time, quote win rate, rebook rate and revenue per repeat client. What you cannot see, you cannot improve.
The real cost of the notebook era
Almost every trades business I talk to starts the same way: a spiral notebook on the dashboard, an envelope of job sheets behind the driver seat, sticky notes on the monitor, and one person who seems to hold the whole operation in their head. This is not laziness. It is how the business grew — eight jobs a week, then fifteen, and the notebook stayed one page ahead. Then the phone started ringing twice as often, three crews were running, and the notebook quietly fell three pages behind.
The real cost of the notebook era is not the paper. It is the three silent leaks that paper cannot show you: missed follow-ups, forgotten quotes and a total lack of data. Start with follow-ups, because that is the leak with the biggest hole in it. In most service trades, the first quote does not win the job — the follow-up does. A customer will talk to three plumbers, two roofers or two towing dispatchers, and the one who rings back or sends a polite reminder the next day gets the work. When your follow-ups live on a sticky note that got stuck to your sleeve and lost, the job goes to whoever is organised enough to chase. Every week, a handful of quotes quietly die without you ever knowing they had a pulse.
The arithmetic on one lost job is worth doing slowly, because it is the whole argument for a CRM in a few numbers. Take a mid-range ticket for a trades job — call it around $600 for the sake of the example, which for most plumbing, HVAC, locksmith, towing or handyman work sits somewhere in the ordinary range. Now imagine you lose just one such job per week to a missed follow-up. Fifty-two weeks at roughly $600 is around $31,000 a year in revenue that walked away not because you could not do the work, but because nobody picked up the phone. Try the arithmetic with your own average ticket and your own guesstimate of lost jobs and it rarely looks comfortable. Some months it looks like the entire profit margin for a crew.
One missed follow-up a week at an ordinary trades ticket is roughly $30,000 a year of revenue you already earned and then dropped.
Then there are the forgotten quotes themselves. Quotes that never got sent because the notebook page was too full. Quotes sent a week late, after the customer already gave the job to someone else. Prices quoted to the friendliest round number from memory instead of the real numbers from the last job, so the invoice arrives with a surprise and the customer goes elsewhere next time. Forgetting a quote costs you the quote, and forgetting the follow-up to a good quote costs you the win. Both are storage problems, and both are solved the same way: put the quote in a place you will see it again.
Finally, the leak that is hardest to see from inside the notebook: the total absence of data. With paper, you cannot answer the simplest business questions. What is your actual quote win rate? Which lead source — the review site, the referral, the van branding — actually produces paying jobs? Which jobs turn a profit after materials, diesel and rework? Who are your best twenty clients, and when did you last serve each of them? A notebook stores yesterday but never adds it up. That matters more than it sounds, because the businesses that improve are the ones that can see the score. The notebook era is a big reason tradespeople often feel busy for twelve hours a day and still surprised at the end of the month.
And one more layer, because service work is compounding in a way sales work is not. One happy customer is not one job. It is repeat visits, annual service, referrals to neighbours, and the occasional emergency call at two in the morning. When a customer is lost to a forgotten follow-up, you are not losing one job — you are losing the whole rebooking loop for that address for years. The notebook era made that loop invisible. The whole point of a trades CRM is to make it visible enough to run.
None of this is dramatic, and that is exactly why it survives. No single day the notebook costs you a catastrophic contract; instead it costs a small job here, a forgotten annual service there, and a referral you never heard about, which quietly went to whoever followed up. Paper leaks are death by a thousand small cuts, and the reason they stay hidden is that they never announce themselves. You notice only when you finally add up the year and realise the work was there but the money was not.
Why a trades CRM is not a sales CRM
Here is the first confusion that sinks most buying decisions: when people hear the letters CRM, they picture the sales software used by sales teams — Salesforce and its cousins, with deal stages, opportunity amounts and a pipeline that ends when a deal closes. That model was built for businesses that sell and then hand off to someone else. A sales CRM asks: how many deals are in the funnel, and which ones will close this month? It is a fine tool, and completely the wrong shape for a service business, because your deal does not end when it closes. It barely starts.
For a trades business the right shape is a job lifecycle, and it loops. Lead comes in — a call, a web form, a review-site message, a street referral. That lead becomes a quote, with real numbers and a real follow-up date. The accepted quote becomes a scheduled job, on a calendar, attached to a specific day and a specific crew or van. The job runs — it has statuses: scheduled, in progress, waiting on parts, done. When it is done, the invoice lands in the customer's hand and the follow-up loop begins again: a happy-call check, a review request, and a six-month or annual reminder for the next service. Lead, quote, job, done, follow-up. The funnel is a funnel only until the win; the service loop never ends, and that is a feature, not a design accident.
The difference shows up in a handful of field service concepts that a sales CRM simply has no slot for. Scheduling, for one: a sales tool tracks an expected close date; a trades CRM must put the job on an actual day with a real crew and a real duration, and then handle the double-booking the moment the phone rings. Dispatching, for another: the job does not just exist, it needs a van assigned, a tech assigned, the address, the equipment and the call notes, all visible from the field. Job statuses matter in a way deal stages never did, because three jobs are in flight at the same moment and every update needs to be reflected in a scheduling view the office and the van share. And mobile job sheets — the tech in the van needs the full picture on the phone: the quote the customer saw, the notes from the call, room for on-site notes and photos, and an e-signature capture at the end. A sales pipeline would not know what to do with any of that.
So when you evaluate any software, stop asking whether it can track opportunities. Ask whether a finished job automatically lands back in your calendar as a follow-up a few months later, whether the scheduler knows the job is not done until the status says done, and whether the tech on site can see the whole history on their phone. That loop is the entire difference between software built for sales teams and software built for service work. You will live inside this tool every day for years; it is worth insisting it mirrors how your jobs actually move.
Walk one real week through both models and the difference becomes obvious. A window-cleaning quote arrives on Monday; in a sales CRM the deal sits in a stage called proposal warm and the reporting asks when it will close. In a trades CRM that same quote already has a date range, a crew, a note about materials, and a follow-up scheduled for Friday morning. What matters is not whether it closes; it is that Friday's call actually happens, and that when it does, the crew and the van are ready to move. Sales software tracks whether the deal is alive. Service software decides whether the work really happens. For the trades business owner reading this, only the second question ever put money in the account.
The eight features your trades CRM must have
Here is the honest version of a feature list: most CRM brochures are noise, and most features you will never touch. Focus on eight capabilities that directly stop jobs from escaping, in the order of the damage they prevent.
- Contact records with full job history. Every call, quote, job, note and invoice lives on the customer in one card. You remember who the client is before you walk through the door, and rebooking a good client takes thirty seconds instead of a painful memory search.
- A visual quote and job pipeline. Every open quote and active job, its stage and its likely date, visible in one screen. When you can answer where the work is in two seconds, nothing hides between the quote and the schedule.
- A calendar and jobs board. Drag jobs onto days, block out holiday weeks, see crew capacity and spot double-booking before it happens. This is your real dispatch centre, and moving a job should take seconds, not phone calls.
- Reminders and follow-up automations. The software nags on your behalf: a polite quote follow-up after three days, a happy-call after each job, and an annual service reminder six or twelve months out. Automating one reminder pays for the whole tool on its own.
- Invoicing and hand-off. A done job turns into an invoice in one click, and payment attaches to the job record. The gap between finishing the work and getting paid shrinks, and at the end of the month you can see exactly which money is still out.
- Reporting that answers real questions. Win rate, jobs per week per crew, money in versus money out, top customers by revenue. If the software cannot answer these, it is a glorified filing cabinet, and businesses that keep score simply improve faster than neighbours who guess.
- Mobile access for the crew. The job sheet, notes, photos and signature live on the phone in the van. Paper stops travelling between the van and the office, and the tech becomes part of the system instead of the reason it breaks.
- Integrations with what you already use. Google Business Profile for reviews, your accounting package, and payment links. The CRM should talk to the tools around it, so chasing reviews, bookkeeping and invoices never become a second job you do at night.
Notice what is not on the list. Fancy dashboards, marketing automations, territory planning, live chat — none of it stops a job escaping the way these eight do. If a demo is glittering everywhere except the pipeline, the calendar and the follow-up, politely steer it back to the boring stuff, because the boring stuff is where the money lives. Those eight features are the load-bearing wall of a trades CRM; everything else is decorating, and you can add decorating later without regret.
Feature checklist: what to ask for
When a vendor walks you through a demo, work through this checklist rather than the demo script. The must column is the nucleus that stops jobs escaping; the nice column is genuinely optional and often worth skipping at first.
| Feature | What it does for you | Must / Nice |
|---|---|---|
| Contact records with job history | Every client, job and note remembered automatically | Must |
| Quote to job pipeline | Shows every open quote and job in one view | Must |
| Calendar and jobs board | Places work on days, shows crew capacity | Must |
| Follow-up reminders | Chases quotes and rebooks clients on your behalf | Must |
| Quote templates with your branding | Sends professional, consistent quotes in minutes | Must |
| Job statuses and change tracking | Keeps everyone on the same state, office and van | Must |
| Mobile job sheets | Lets techs log work, photos and signatures on site | Must |
| Invoicing linked to jobs | Moves finished jobs straight into billing | Must |
| Basic reports | Answers win rate and revenue questions weekly | Must |
| Online payment links | Gets money in faster with less chasing | Nice |
| Accounting software integration | Syncs invoices and expense records automatically | Nice |
| Team roles and permissions | Controls who sees what, per user and per crew | Nice |
Off-the-shelf options, honestly
Let me be straightforward with you, because it saves everyone time: for most trades businesses, most of the time, off-the-shelf job-management software is the right start. It is up in days, it comes with a tested mobile app, the crews can be trained on it with a two-minute video, and there is usually a real support team behind it. If your processes are the ordinary shape — take a quote, do the job, send the invoice — a solid off-the-shelf product will beat a custom build on speed and price in year one almost every time. Start there, and only move when you have a concrete reason.
The honesty part is about what happens after year one. The pricing model of most job-management SaaS is per user, per month, with add-ons stacked on top: payment processing, SMS follow-ups, extra reports, more branches. A one-person shop sees a modest monthly bill. A three- or five-tech team multiplies the per-seat fee, adds the crew apps and the plugin fees, and before long the monthly subscription feels less like a tool and more like rent on software you will never fully own. To put it in your own terms: on rough typical pricing, a multi-crew team can reach a point where the monthly bill is the equivalent of a profitable job or two every single month, forever.
A few practical notes if you do go off the shelf, because the choice deserves a real test rather than a guess. Take the trial seriously and put three genuine jobs through it before you pay for anything — a demo full of tidy sample data tells you nothing about whether your crews will open it on a bad Tuesday in the rain. Ask how data leaves the system and check it yourself, because export is the difference between renting your history and owning it. And keep one fact above all others in mind: a bright interface is not a workflow, and the only test that matters is whether your own quote-to-follow-up loop survives contact with the software. The good options will let you find that out for a month or two at modest cost, and that is exactly how a decision like this should be made.
Then come the limitations, and these are the quiet ones. You live inside their workflow: their job sheet is their job sheet, and you can only push it so far before the shaping fights back. If your pricing has distance zones, emergency loadings or trade-specific rules, most off-the-shelf tools express that badly or not at all, and you end up pricing in a spreadsheet and typing results into the software — which is how the notebook sneaks back into a different coat. Customisation is limited, reports are generic, and your data sits in their system. Most of them let you export, so it is rarely a prison, but it is a landlord: good while it works, awkward when you want to leave.
So here is the decision in one table, and I mean both columns of it.
| Option | Cost | Flexibility | Time to start | Risk |
|---|---|---|---|---|
| Off-the-shelf SaaS | Low monthly fee per user plus add-ons | Limited — you work their way | Days | Low at first; fees and lock-in climb over years |
| Tailored off-the-shelf | Setup fee plus a higher monthly fee | Medium — adaptations sit on top of their core | Weeks | Upgrades can overwrite your customisations |
| Custom CRM | One-time build, optional support | Full — the software follows your rules | Weeks to months | Needs a clear spec and up-front investment |
Read that table the way it is written, not the way a salesman would. The custom row is the most flexible and the least risky once built, but it carries the development risk of getting the spec wrong and the cash-flow question of paying once instead of monthly. The off-the-shelf row gets you moving this week, but slow rent and an eventual ceiling are priced into every monthly invoice. A custom build is only worth it when the subscription row is costing you more in fees, workarounds or lost data than the build.
When a custom CRM makes sense
Custom sounds glamorous and is mostly not; it is practical in a specific handful of situations. If any of these sound like you, off-the-shelf will frustrate you daily, and a custom build starts to look like the cheap option.
Your pricing rules do not fit a template
Distance-based pricing, emergency loadings, trip charges, material markups, bulk discounts, call-out fees on weekends. If today your pricing lives in a spreadsheet and gets transcribed into your jobs, then off-the-shelf software is adding a step, not removing one. A custom CRM can carry your pricing rules natively, so the quote is calculated by the system, and the figure the customer sees is the figure you intended. This is the most common trigger, and it is a good one.
You run multiple branches or multiple crews
Dispatching across regions, per-crew availability, jobs that transfer between vans, and reporting per branch. Off-the-shelf tools treat extra branches as an add-on fee and a simplification. When your business has real geography, a custom build can put the whole map and every crew in one view, with rules per region instead of a compromise shape.
Your field workflow is the product
Trades businesses differ most on site, not in the office. Inspection checklists, safety sign-off, photo evidence, custom job sheets per trade, e-signatures, time-on-site capture. If your crews carry paper or their own apps because the generic job sheet is too thin, that is your field service software telling you the truth. A custom mobile job sheet built around your actual day can pull the field into the system properly.
You already have systems it must join
An established accounting package, a quoting engine, a booking portal, a fleet or asset list, or a Google and Microsoft stack your whole office runs on. A custom CRM plugs into what exists rather than replacing it, which means your estimates, invoices and job history can share one spine instead of duplicating entry. If your existing system is doing part of the job well, the answer is to connect, not to restart.
You want ownership and to end the per-seat rent
This one is about where the business is going. Pay once, own the code, add users and crews without the price climbing, and keep your data in a place you control. For a business that plans to go from a few techs to a fleet, the seats are a multiplier, and custom removes that ladder entirely. Combined with the other triggers above, ownership is usually the final nudge that makes the build decision easy — and we build exactly these kinds of custom CRM and web desktops apps as a core part of what KorTechX does.
If you are still weighing the practicalities of starting small, the companion piece on a smaller first CRM setup is the right next read. The short version of when custom wins: when the rules, the geography, the field workflow or the growth plan outgrow the template, and when the monthly rent and the workarounds cost more than building your own.
One honest caveat so this does not read like a sales pitch: a custom CRM is the wrong answer for a business that is not yet sure how it works. If your pricing rules still change every month, if you have never tracked a win rate, or if you doubt you will stick with any system for a year, the subscription product is a cheap way to discover the answers. Custom is a decision made from knowing what hurts for a while, not from a vague itch. Put the trigger plainly: when you can write on a page the specific rules and workflows an off-the-shelf tool cannot carry, and the monthly rent plus the workarounds have already cost more than the build — that is the day to build. Before that day, you are paying a different kind of tuition and that is fine too.
Data and migration: what to export now
Whatever you choose, the single most valuable thing you can do this weekend costs nothing but coffee: start exporting your business from the notebook while you can still read it. Do this before you pick software at all, because the data drives the decision.
Make a list of every customer, even the ones you have not seen in two years — they are the rebooking pool. For each: name, phone, email, address, the last job date, the last quote amount, and a notes line for the details that matter, like the boiler you installed and the washroom you re-tiled. Then add the past quotes with their amounts and dates, because that is win-rate evidence. Add the recurring and annual jobs, the payment history, and the customer notes that make you look brilliant in the forty seconds before a job. Yes, it is an afternoon of typing. No, it does not get easier next month, when the notebook is another forty pages colder.
Then clean it once before it moves anywhere. Drop the duplicates that the notebook creates — the one client with three spellings of their name. Mark which customers are still active, which moved, and which stopped answering. Put everything in a plain table with the same column order throughout, because a tidy export turns migration from a hero project into an import that just works.
When the new system arrives, migrate rather than cut. Run the tool and the notebook side by side for the first month, import the history you cleaned, and let the two disagree visibly until they agree. Set a cut-off date on the calendar — the day the notebook officially retires, framed, like a trophy — and after that, nothing new lands on paper. The empty notebook is not a loss. It is the whole point.
A migration also deserves one person who owns it. Nominate the person who already knows where everything lives, give them a couple of deliberate afternoons, and let them treat the export as a project rather than a spare-time chore. You will find the truth of your operation in that spreadsheet — which customers are real, which jobs actually repeat, and which lines of the notebook were optimism instead of fact. Then keep the first import deliberately small, your top fifty customers and the current month of jobs, so that success on day one is achievable and the team tastes a win instead of a data-entry marathon.
Rolling out a CRM in a working business
Here is the most useful thing I can tell you about rollout, and it goes against every demo video ever made: do not switch everything on at once. A trades business is a machine that is running while you fix it; the crews are on the road, jobs are in flight, and nobody has spare hours for a software ceremony. Roll out in four phases, each one a habit that has visibly made their day easier before the next phase arrives.
Phase one: capture. The only rule is that every new lead goes into the CRM before anything else. Calls, web forms, review-site messages, referrals — each one becomes a contact with a note of what they need. This phase is small and instantly rewarding, because the team stops losing numbers in one week. If first responses to those leads are eating your day, that is a separate problem with its own lever — we have a separate piece on AI agents for local service businesses that covers exactly that.
Phase two: shift from paper. Move the quote and job sheets into the system, one crew or one trade at a time. Give the end of the day a fixed ritual: everything you did today is in the software before the keys leave your hand. This is the phase where the notebook starts to look silly, and that is the feeling you want.
Phase three: automate one reminder. Pick the single highest-value follow-up in your business — usually the quote follow-up, sometimes the annual service reminder — and switch it on. Watch what happens to open quotes in the next three weeks. This is the cheapest marketing you will ever buy, and it is the phase where the software officially pays for itself.
Phase four: adopt reporting. Put a fifteen-minute review on the calendar every week. Win rate, open work, rebooking, money out against money in. Let the numbers show where the leaks are; in the notebook era you could not see them, which is why they kept leaking. A weekly scorecard turns a vague business feeling into a list of boring, fixable problems.
And a warm note on the human part, because rollout is a people project even when the software is perfect. Praise the first week of zero missed entries out loud. Find the person who already runs the notebook and make them the champion, not the victim. Give it six to eight honest weeks before you judge results. Adoption beats features every single time — a simple tool with a loved team will beat a powerful tool nobody opens.
Wherever you meet resistance in these phases, almost always there is one specific objection worth listening to, because it is usually true. The tech has a point that the app loads slowly in a network dead zone. The office has a point that the form carries two fields too many. Each objection names an actual friction point; fix those, one at a time, and the rest of the resistance dissolves on its own. Treat the rollout exactly the way you treat a job site: smooth the path, remove the obstacles blocking the crew, and the work gets done.
How to measure it
A CRM for a trades business is finished work only when it produces numbers you act on. Four KPIs cover most of the value, and each one is a leak you can plug in sequence.
Response time. Hours from a lead arriving to you replying. This is the fastest KPI to move and the one with the biggest early wins, because the job often goes to whoever answers first. If your average response drifts from hours to a day-plus, you are handing out quotes to the competition. Watch this one every single week.
Quote win rate. Jobs won against quotes sent. Low here usually means a follow-up problem rather than a pricing problem — the quotes are moving but nobody is chasing them, which is precisely the leak a trades CRM is built to close. Once the follow-up reminder is automated, the win rate is your proof it is working.
Rebook rate. The share of your jobs that come from customers you have served before. In a notebook era this is invisible luck; tracked in a CRM it becomes a number you deliberately grow, because repeat work is the cheapest, least stressful revenue you have. If rebooking is low, add the happy-call and the annual reminder to the follow-up automation.
Revenue per repeat client. What a single relationship is worth across a year — the number that justifies pushing annual service plans and maintenance retainers. One homeowner served twice a year for a decade is worth more than two dozen one-off crisis jobs, and the CRM is the only place that fact becomes visible.
Start by logging a month of honest baselines — if the first month is ugly, that is the data telling you the truth, not a reason to hide. Then set one modest improvement per quarter: respond within an hour, win two more quotes a month, book five annual services. The software is not the improvement; the measurement is, and the software is what makes the measurement possible. What you cannot see, you cannot improve.
Resist the pull of vanity numbers along the way — how many contacts the system holds, how many notes were logged — because they measure typing, not money. The four KPIs above are the ones that move the bank account. Set a monthly ritual where you and, if you have one, a trusted partner read the four numbers together for fifteen minutes and agree on a single change to make for the month ahead. That small ritual is the whole return on the software, and it is worth more than any hundred dashboard features you will never open.
Pitfalls that sink most rollouts
You get one warning shot at avoiding the mistakes everyone makes, so here they are plainly. The first is over-engineering from day one. Somewhere between signing up and going live, teams configure forty custom fields, every status colour in the rainbow and an approvals chain. That is software archaeology — you are building a museum for future features nobody has asked for. Ship the minimum truthful version and let painful needs, not imaginings, add the rest.
The second is the twenty-field form. In trades, the golden rule of data entry is that the person capturing it is under a sink or standing at a gate in rain, not sitting at a desk. Name, phone, what they need, when they need it, one note line. Five fields, tops. Every extra field you add is a field somebody will skip or fabricate, and ten skipped fields make the whole form feel disposable.
The third is expecting instant adoption. You will see three types of week one: the champion who embraces it, the sceptic who tolerates it, and the pattern in the data showing that some jobs still live on paper. Judge in eight weeks, not eight days. Praise small wins loudly, give the champion the road, and make the sceptic prove the paper is faster out loud — usually they can not.
The fourth is choosing on price alone. The cheapest pile of features normally costs the most in workarounds, missing data and the quiet return of the notebook. The real price of a CRM is not the subscription line; it is whether the crew opens it daily. A tool that costs a bit more but gets used is the cheap one. A free tool that nobody opens is the most expensive thing you can buy.
And a fifth, sneakier pitfall to round out the list: the parallel notebook. Somewhere in month two, half the crew is digital and one person still keeps a personal list because they trust it more. That hybrid is the worst of both worlds — the data is split, the reports lie, and the digital half quietly stops being trusted. Retire the last piece of paper the moment you spot it. A single source of truth is the entire point, and a tool with everyone in it is worth more than a perfect tool with one person still outside.
The bottom line
A CRM for a trades or service business is not an expense. It is how you stop losing jobs to a notebook, and losing them with the polite silence of never knowing they existed. It tracks the lead, the quote, the job, the invoice and the follow-up in one place, it remembers what paper forgets, and it turns a busy business from a blur of sticky notes into a pipeline you can actually see and steer.
Start simple and start this week: export your notebook into a clean table, put every new lead in one place, and automate a single follow-up. Buy off-the-shelf first unless your pricing rules, your branches, your field workflow or your growth plan clearly outgrow a template. And when the template is the problem — when the per-seat rent, the inflexible job sheets and the data you do not fully own are costing more than building your own — a custom build is the honest answer, and it is the kind of work we do every day here at KorTechX. We build custom CRMs and job-management web apps for trades and service businesses that have outgrown the template, wired around how your work actually runs. If you are reading this while half your quotes sit in a notebook, that is exactly the conversation worth having — get in touch and we will talk it through.
One firm promise to finish on: none of this requires a six-figure project. This week it is a clean export and a rule about where leads land. Next month it is an automated follow-up and a fifteen-minute weekly scorecard. And if the template starts to pinch after that, the custom conversation is a short one. Every stage of this journey is cheaper than the notebook era it is replacing, and every stage moves you further from the day a good job walks out the door because nobody remembered to call back.
