A practical CRM selection checklist for UK trades and small service firms: define needs, score features, check pricing and data protection, then trial properly.

Decorative CRM checklist title card illustration

The right CRM for a trade or service business is the one your team will still be using in six months. It needs to catch enquiries, turn them into quotes, book the work, get the invoice out and show you who has paid, without anyone retyping the same details. This checklist walks you through how to work that out: define what you need, score what you see, check the pricing small print, and test properly before you commit.

Pipelineapp
Keep Every Job Moving
Pipeline brings enquiries, quotes, bookings, job tasks, invoicing and payments together in one platform for UK trades and service businesses.
Get in touch

TL;DR

  • Map how a job moves from enquiry to payment first, then judge every CRM against that map, not against a feature list.
  • Score each shortlisted system on the same criteria: ease of use on a phone, quoting, scheduling, invoicing, integrations, reporting, security and total cost.
  • Count the real price: per-user fees, tier limits, text message charges and set-up time all change the bill.
  • Trial two or three tools with your own jobs and your own team in a normal working week.
  • Check how the supplier handles your customers’ data and whether you can export it if you leave.

Table of Contents

Start with how your work actually moves

Most CRM checklists start with software features. That is backwards. Start with your own business, because a tool that looks brilliant in a demo can still fight the way you work.

SME Software Help suggests three things before you look at any product: count your users, list the tools you use now, and sketch how work flows from enquiry through quote, winning the job and delivery. For a tradesperson, that sketch might look like this:

  1. An enquiry arrives by phone, text, web form or a recommendation.
  2. You log it, arrange a visit or ask for photos.
  3. You price it and send a quote.
  4. The customer accepts, and you book a date.
  5. The job is done, notes and photos are recorded.
  6. You invoice, chase and get paid.
  7. You follow up for reviews, repeat work or the annual service.

Draw it on a sheet of paper. Then mark every point where things currently go wrong: the enquiry that sat in a WhatsApp group, the quote nobody chased, the invoice you sent two weeks late because the job notes were in someone’s van. MMD Solutions recommends documenting where your current process causes duplication or delays, and that list becomes the most valuable part of your checklist. Every item on it is a requirement.

If you want a ready-made layout for mapping the whole journey from first enquiry to repeat business, this one-page capture plan template gives you a simple structure to adapt.

Count the people who need access

Write down everyone who will touch the system: you, an office admin, two or three engineers, perhaps a subcontractor or a bookkeeper. Note what each person needs to do. An engineer needs to see today’s jobs, add notes and photos, and maybe take a payment. The office needs the full picture. The bookkeeper needs invoices and payments. This list matters twice: it tells you which permissions you need, and it decides how much a per-user pricing model will cost you.

List the tools it will replace

Be honest about what you use today: a spreadsheet, a notes app, a paper diary, a separate invoicing package, a group chat. The aim is fewer places for information to live. If a CRM replaces three of those but you still keep two, you have added a tool, not removed one. Our piece on why “just check Dave’s phone” isn’t a customer database covers what goes wrong when customer details live in one person’s pocket.

Separate business tools converging into one customer record

The CRM requirements checklist

Use the table below as your master list. Mark each line as essential, useful or not needed for your business, before you see a single demo. Anything you mark essential is a pass or fail test.

Area What to check Why it matters for trades
Enquiries and leads Can you log leads from calls, web forms and messages in seconds? Is there a clear stage for each lead? Missed enquiries are lost work, and you rarely see them go.
Customer record One record with contact details, addresses, past jobs, quotes, invoices and notes You should never ask a returning customer for their postcode again.
Quoting Reusable templates, fast sending, a way to see accepted and ignored quotes Quotes are where most trades lose money, through slow follow-up.
Scheduling Visual calendar, drag and drop, multiple engineers, calendar sync Double bookings and forgotten visits cost goodwill.
Job tracking Job status, tasks, notes, photos, completion sign-off Tells you what is done, what is waiting and what is unpaid.
Invoicing and payments Invoices generated from the job, online payment, payment status visible Faster invoices mean faster cash.
Communication Automated email and text confirmations and reminders Fewer no-shows and fewer “where are you?” calls.
Mobile Full job workflow on a phone, usable on site If engineers will not use it, the data is never right.
Integrations Accounting, payments, calendar, text messaging, automation tools Stops double entry.
Reporting Leads won, quote conversion, revenue, outstanding invoices You need to see where the money is, not build a report.
Permissions Different access for owner, office, field staff Protects pricing and customer data.
Security and data Where data is held, how it is protected, export option You are responsible for your customers’ data.
Cost Monthly price, user fees, limits, add-ons, set-up time The advertised price is rarely the whole price.

A word on the last row. Kabooly advises looking past the headline monthly figure to user-based pricing, essentials locked into higher tiers, limits as you grow, data location, exportability and support. We cover that properly further down.

How to judge each criterion

A tick in a box tells you very little. “Mobile app: yes” can mean anything from a full job workflow to a stripped-down contact list. Here is how to judge the criteria that matter most, using tests you can run yourself.

1. Ease of use

Give a new person ten minutes and ask them to add a customer, create a quote and book a visit. If they need a manual, so will your engineers. Watch where they hesitate. Count the taps or clicks to log a new job. A system that takes two minutes to enter what takes ten seconds on paper will be abandoned by the second week.

2. Mobile access

MMD Solutions suggests testing the process on mobile during a normal working week. That is the right test. Try it in a van, on a roof, with patchy signal and dirty hands. Can an engineer open the job, see the address and notes, add photos, mark it complete and trigger the invoice? Can the office see that change straight away?

3. Integrations

List the tools you already depend on: your accounting package, card payments, your calendar, text messaging. Check each is supported directly, or through an automation connector, and ask what actually syncs. “Integrates with” can mean a full two-way sync of invoices and payments, or a basic export. Ask for a demonstration of your specific use.

Accounting deserves extra thought. HMRC says sole traders and landlords with qualifying income over £30,000 must use Making Tax Digital software from 6 April 2027, choosing from its list of recognised providers for digital records and quarterly updates. Your CRM does not need to be that software, but it should pass invoice and payment data cleanly to whatever you use, so your records are not retyped. If you invoice from your CRM, our guide to same-day invoices for UK small businesses shows what a good invoice should contain.

4. Reporting

Decide which five numbers you want to see every week. For most trade businesses these are: new enquiries, quotes sent, quotes accepted, jobs completed and money outstanding. If a CRM makes you export to a spreadsheet and build a chart to see these, it fails the test. Good reporting answers “where is the money stuck?” in one screen.

5. Scalability

Ask what happens when you go from two engineers to six. Does the price jump per person? Do features like multiple calendars or stronger permissions sit behind a higher tier? You do not need to plan for ten years, but you should know what the next step costs.

6. Customisation

You will want your own quote wording, job types, lead stages and message templates. You probably do not want to hire a consultant to set them up. The question is how much you can change yourself, and how long that takes. SME Software Help makes a point that is easy to miss: implementation time is a real cost, and a CRM that takes three months to set up properly can be expensive even if the software itself is cheap.

7. Security and permissions

Permissions are the practical side. Can you stop a new starter from seeing pricing or deleting customers? The legal side is covered in the data section below.

Build a simple scoring system

Without a scorecard, the shortlist ends up decided by whoever gave the smoothest demo. Keep it simple:

  1. List your essential and useful criteria from the table above.
  2. Give each a weight: 3 for essential, 2 for important, 1 for nice to have.
  3. Score each system from 0 to 5 on each criterion, after you have tested it, not after you have watched a demo.
  4. Multiply, add up, and compare.
  5. Ask the people who will use it daily to score the “ease of use” and “mobile” lines themselves.

Here is a worked example for a three-person heating business comparing two imaginary systems, A and B, on four criteria.

Criterion Weight System A score System A total System B score System B total
Mobile job workflow 3 4 12 2 6
Quoting templates 3 3 9 5 15
Accounting sync 2 4 8 4 8
Reporting 1 2 2 4 4
Total 31 33

System B wins narrowly, but look at what the scores say. It is much weaker on mobile, which the engineers will use every day. If your engineers are the bottleneck, you may decide mobile is a pass-or-fail line rather than a weighted one. The scorecard informs your judgement; it does not replace it.

Check the pricing before you fall for it

This is where checklists from general CRM sites fall short for trades. They talk about budget in broad terms. For a small team, the pricing model can change the answer entirely.

Per-user versus flat monthly pricing

Per-user pricing looks cheap when you are one person and gets expensive as you add engineers, office staff and part-timers. Flat monthly pricing charges a set amount for a plan, whoever and however many people use it within the plan’s terms. Our explainer on per-user, flat fee and everything in between lays out the models side by side, and the per-user pricing calculator lets you put your own headcount in and see what per-seat software really costs you over a year.

What to ask about a flat fee

Flat does not always mean everything is included. Ask each supplier:

  • Is there a cap on users, jobs, customers or storage within the plan?
  • Which features sit in a higher tier, and what do those tiers cost?
  • Are text messages included, or charged separately?
  • Are there set-up, training or onboarding fees?
  • What does an integration cost, if anything?
  • Is there a contract term, and what is the notice period?
  • What happens to prices at renewal?

Kabooly’s list of things to check includes growth limits and higher-tier essentials, and it is a good prompt for these questions. Write down the answers for every system so you compare like with like.

Work out the real annual cost

Build one figure per system: monthly price multiplied by twelve, plus any per-user fees at your current and planned headcount, plus message costs, plus add-ons, plus the time it takes to set up. That last one is the hidden cost. If setting up costs you two evenings a week for a month, that is time you could have spent quoting.

Data protection: what to check about your supplier

A CRM holds names, addresses, phone numbers, emails, job notes and sometimes photos of customers’ homes. That is personal data, and you are responsible for it under UK data protection law, even though the supplier stores it.

The ICO’s guidance says that when you use a processor, you must choose one that provides sufficient security guarantees, and your contract must require the security measures set out in Article 32 and information showing compliance, which can include audits and inspections. In practice, put these questions to every supplier:

  • Where is our data stored, and who can access it?
  • How is it protected, and how are access rights controlled?
  • What does your contract or terms say about security and about helping us meet our obligations?
  • Can we export all our customer data in a usable format if we leave?
  • What happens to our data when we cancel?

If you are unsure what your own obligations are, speak to the ICO’s guidance for small organisations or a qualified data protection adviser. Do not rely on a supplier’s marketing page alone: ask for the terms in writing.

Shortlist, then trial with real work

SME Software Help recommends shortlisting two or three tools based on simplicity and integrations, then trialling them with your team using your own data and your actual process. More than three and you will never finish the evaluation.

A two-week trial plan

  1. Day 1: Import or enter around twenty real customers and five live jobs.
  2. Days 2 to 3: Set up your quote templates, lead stages and a couple of automated messages.
  3. Days 4 to 10: Run real enquiries through it. Send real quotes. Book real visits. Have engineers use the mobile app on site.
  4. Days 11 to 12: Raise at least one real invoice and take or record a payment. Check it reaches your accounting software.
  5. Day 13: Pull the reports you decided you needed.
  6. Day 14: Everyone scores the system independently, then you compare notes.

MMD Solutions makes the same point: use real or sample data and let the team run its actual process through the system. A trial on made-up jobs tells you nothing about how it copes with a Tuesday when two engineers are off and a boiler fails.

Red flags during a trial

  • Engineers keep reverting to text messages or paper.
  • You need support to do something routine.
  • The same information has to be entered in two places.
  • You cannot find out who has not paid.
  • The supplier goes quiet or vague when you ask about export or pricing.

Where we stand: a view from the Pipeline team

We built Pipeline for UK trades and service businesses, and we have seen the same pattern repeatedly. Enquiries come in through five channels, quotes sit in someone’s inbox, job details live in a group chat and the invoice goes out late. Nothing is catastrophic on its own, but together it is money walking out the door.

Our view is that a CRM for a trade business should be judged on the whole journey, not on the lead screen alone. If it captures the enquiry but cannot schedule the job, send the invoice and show you who has paid, you are back to spreadsheets within a month. That is why we put leads, jobs, appointments, quotes, invoices and payments in one place, with one customer record.

Where we stand: a view from the Pipeline team — overview diagram

We also believe pricing should be easy to predict. A trade business with a growing team should not be penalised for adding an engineer. That is why our pricing is a flat monthly fee with no per-user charges. Whatever system you choose, run the numbers at your planned headcount, not just today’s.

And finally: test it on a phone, on site, with the person who likes paperwork least. If they will use it, everyone will.

— Chris

Where Pipeline fits

If you want to test a system built around this checklist, Pipeline covers leads, quotes, scheduling, job tracking, invoicing and payments in one platform for UK trades and service businesses, with a mobile app for field teams and integrations with Xero, QuickBooks, Stripe, Google Calendar, Twilio SMS and Zapier. Pricing is flat and monthly, with no per-user fees: Solo is £12 per month, Starter is £38 per month and Professional is £63 per month, and there is an Enterprise plan for larger needs. Text messages are listed as a separate line on the pricing page, so check how they apply to you. See the full details on the Pipeline pricing page.

Pipelineapp

If you work in a specific trade, our pages for HVAC businesses and builders show how the workflow looks in practice, and our guide to plumbing business software features breaks down what you actually need versus what you can skip. Heating engineers weighing up whether they need software at all may find our piece on job management software for heating engineers useful.

Make the decision

At the end of the trial, you should have three things on the table: your scorecard totals, the real annual cost of each system and the team’s honest feedback. If one system leads on all three, the decision is easy. If they split, trust the team feedback over the scorecard, because a slightly less capable tool that everyone uses beats a better one nobody opens.

Before you sign, confirm in writing:

  • The exact monthly price and what it includes, at your planned headcount.
  • Contract length, notice period and renewal pricing.
  • How you export your data.
  • Who to call when something goes wrong, and how quickly they respond.
  • A plan for the first month: who imports data, who trains whom and by when.

Then move everything over in one go. Running two systems side by side for months is how “the old way” survives.

FAQ

How do I choose a CRM for a small trade business?

Start by mapping your work from enquiry to payment, and note where it breaks down. Turn that into a checklist of essentials, shortlist two or three systems and trial them with real jobs on your team’s phones. Score them on the same criteria and compare the true annual cost.

What should be on a CRM requirements checklist?

At minimum: lead capture, a single customer record, quoting, scheduling, job tracking, invoicing and payments, automated messages, mobile use, accounting and payment integrations, reporting, permissions, data security and total cost. Mark each as essential, useful or not needed before you look at products.

Is a flat fee CRM better than per-user pricing?

It depends on your headcount. A flat monthly fee is easier to budget as your team grows, while per-user pricing can be cheaper for a one-person business. Work out the annual cost at your planned team size, and check for limits, higher-tier features and message charges either way.

How long should I trial a CRM?

Two weeks of normal work is a sensible minimum, so the trial covers enquiries, quotes, bookings, a completed job and an invoice. Use your own data and have the people who will use it daily try it, especially on mobile.

Sources

Recommended