CRM features checklist for buying decisions

A CRM product page lists dozens of features, but only a few change your daily work. This checklist groups them by area. Tick only what you will use in the first twelve months, and compare vendors against that list, not against theirs.

Sales

• Contacts and companies, with several people per company.
• A pipeline with stages you can change yourself, without asking the vendor.
• Deals with a value, an expected close date and an owner.
• Tasks and reminders linked to the contact.
• Quotes with reusable templates.

Marketing

• Segments based on purchases, source or tags.
• Email campaigns with a visible unsubscribe link in every send.
• Automations with triggers (form, order, date or inactivity) and waits between steps.
• A/B tests on emails or flows.
• SMS or WhatsApp, only if you will actually use them.

Service and store

• A shared inbox for email (Gmail, Outlook or IMAP, depending on the vendor).
• A full history per contact: emails, calls and orders.
• Bookings or appointments, if customers book time with you.
• Web forms that create the contact in the CRM.
• A connection to your store (WooCommerce, Shopify or WordPress), with orders and products synced.

Admin

• Roles and per-module permissions: who can view and who can edit each area.
• Invoicing, or a connection to the invoicing software you already use.
• Data export to Excel or CSV.
• Tools for GDPR compliance: handling unsubscribes and access or erasure requests.
• An API or webhooks, if you need to connect other systems.
• An analytics dashboard with the numbers you check each week.

How to use the list

1. Tick only what you will use in year one. Features you will not use should not influence the decision.
2. Make one column per vendor and note "yes", "no" or "via integration". A third-party integration is not the same as a native feature: it is another system to maintain.
3. Ask for a trial with your own data. Import a small list of real contacts and create a test order or deal.
4. Check which plan each feature sits in. Some only appear on higher plans, which changes the cost.

Things that often go unused in a small business: detailed reports nobody opens, accounting modules when an accountant already handles the books, and connections to tools you do not use.

What the checklist does not cover

Price, support and ease of use matter as much as features, but you check them differently. Ask for the price in writing with your team size, and ask how long support takes to answer a specific question.

For a starting point, the CRM for small business guide explains which profiles need which tools, and the all-in-one CRM page describes what Flowgration includes. To see the most-compared options, read the best CRM for small business roundup. The guide on how to choose a CRM for a small business covers the full process.

Frequently asked questions

How many features should a small-business CRM have?

There is no set number. Count the ones you will use in the first year. For a small team, a dozen well-chosen features is usually enough.

What matters more: the pipeline or automation?

It depends on how you sell. If follow-ups slip through, start with the pipeline and reminders. If you send the same emails every day, look at automation.

What is the difference between a native feature and an integration?

A native feature comes inside the same product. An integration depends on another tool or a connector. It can work well, but it adds a point of failure and often another cost.

Should I ask for a demo before I choose?

Yes, and make it about your own use cases: import your contacts, create a test order and send a test email.

How do I compare features without ending up with the longest list?

Score only the features you marked as necessary. Anything you do not need should not add points to any vendor.