UBC

Business journal

How to choose a CRM for a small business

What a CRM is really for, signs you need one, must-haves vs nice-to-haves, questions to ask before buying, a cost example and a two-week trial plan.

Author: UBC editorial team · Published · Updated

6 min read

Choose a CRM around the customer requests your team handles every day. Test follow-ups, handovers, permissions and exports using realistic fictional records before importing personal data. Compare the full cost and daily effort, rather than buying the longest list of features.

Headset with microphone for customer conversations
Workflow illustration; not a photograph of UBC premises or equipment. Plantronics headset.jpg — Petey21; Hohum / Wikimedia Commons — CC0 1.0. Resized and converted to WebP.

What a CRM is actually for

A CRM (customer relationship management system) does three jobs in a small business:

  • One history per customer. Every order, call, email, quote and complaint in one place, so anyone on the team can pick up a conversation without asking “who spoke to them last?”.
  • Follow-ups that do not get forgotten. Each next step has a date and a person responsible: call back on Thursday, send the quote, check in after delivery.
  • A pipeline. A simple view of open opportunities and the stage each one is at (new enquiry, quote sent, negotiating, won, lost), so you can see what is likely to come in next month.

If a tool does these three things well and your team uses it, it is doing its job.

Signs you need one

  • Customer details live in several places: your inbox, a phone, a spreadsheet, a notebook at the counter.
  • You have lost a sale because nobody followed up on a quote.
  • When someone is off sick or leaves, their customer knowledge leaves with them.
  • You cannot answer simple questions such as “how many quotes did we send last month and how many did we win?”.

If two or more of these sound familiar, a CRM will probably pay off. If you have a handful of customers and one person handles all of them, a well-kept spreadsheet may be enough for now.

Must-have vs nice-to-have

Function Must-have or nice-to-have Why
Customer record with full history Must-have It is the reason the tool exists
Tasks and reminders with dates and owners Must-have Stops follow-ups slipping
Simple pipeline with stages Must-have if you send quotes Shows what is coming in
Import and full export (e.g. CSV) Must-have You must be able to leave
User roles and permissions Must-have with 2+ people Not everyone needs to see or delete everything
Main communication channel Must-have if used daily Test your actual WhatsApp, email or other channel
Link to your shop, sales or stock Must-have if you sell products Orders belong in the customer history
Mobile access Nice-to-have (must-have for field sales) Depends on how you work
Marketing automation and campaigns Nice-to-have Useful later, often costly
Advanced reports and forecasting Nice-to-have Simple counts are enough at first
AI features Nice-to-have Check what they do with your data
Laptop keyboard for working with records and orders
Workflow illustration; not a photograph of UBC premises or equipment. ThinkPad T430 (keyboard).jpg — Vitaly Zdanevich / Wikimedia Commons — CC0 1.0. Resized and converted to WebP.

Questions to ask before buying

Can I get all my data out?

Ask how to export customers, contacts, notes, tasks and history, in what format and whether there is a charge. Try it during the trial. A tool you cannot leave becomes more expensive every year.

Where is the data stored and how is personal data handled?

Before importing personal data, ask the provider where it is hosted, what processing terms apply, how access is logged, and how correction, retention and deletion requests are handled. Ask your data protection adviser which requirements and exceptions apply to your situation. Test the functions with fictional records first.

Can I control who sees what?

With more than one user, check that you can limit who exports data, deletes records or sees sensitive fields.

Does it connect to what I already use?

List the tools that hold customer information today: email, web shop, invoicing, inventory. A CRM that does not see orders gives you half the picture. If you sell products, the customer history should show what they bought and whether it was in stock; our guide to keeping stock records explains why one shared record matters.

What will it really cost?

Many CRMs charge per user per month, with extra charges for add-ons. Compare the total for the team you will have in a year, not today.

Worked example: total cost over one year

Illustrative figures, not real vendor prices. You have 3 people today and expect 5 within a year.

Option A Option B
Pricing model €20 per user per month €70 flat per month up to 10 users
Email integration Included +€15 per month
One-off setup €0 €200
Cost with 3 users, 12 months 3 × €20 × 12 = €720 (€70 + €15) × 12 + €200 = €1,220
Cost with 5 users, 12 months 5 × €20 × 12 = €1,200 €1,220 (unchanged)

Option A looks cheaper today; at 5 users the difference almost disappears, and at 6 users (€1,440) Option B becomes cheaper. Do the sum with your own numbers and add the setup hours. Compare the result with the margin on the extra sales you expect; the margin calculator helps with that.

A two-week trial plan

Create realistic fictional or anonymised records that represent your own workflow.

Days 1–2: set up. Import 30–50 fictional customer records. Use real customer data only after checking permissions and the conditions for its use. Define your pipeline stages (no more than five or six). Create user accounts with the roles you would actually use.

Days 3–7: daily use. Log every call, email and quote for those customers. Create a follow-up task for every open conversation. Connect your email and, if possible, your shop or invoicing.

Days 8–12: test the hard parts. Hand a customer over to a colleague: can they continue without asking you? Run a full export and open the file. Delete a test contact and check it is really gone. Look at the pipeline: does it match reality?

Days 13–14: decide. Ask each user three questions: did it save you time, what did you avoid entering, and would you keep using it? If people quietly stopped using it, that is your answer.

Common mistakes

  • Buying for the features in the demo instead of the three jobs you need done.
  • Importing a messy spreadsheet as-is. Remove duplicates and old contacts first.
  • Too many fields and stages. Every extra required field is a reason not to log something.
  • No owner. Someone has to decide how the team uses it and keep it up to date.
  • Keeping the old spreadsheet “just in case”. Two records mean neither is trusted. The same applies to stock; see spreadsheet comparison.

If you are considering AI features, read AI for shops.

Customers, sales and stock together

For a business that sells products, a CRM is most useful when customer history, orders and stock are linked.

How UBC handles this See UBC capabilities →

← All articles