How to choose a CRM for a B2B sales team
Most CRM comparisons list features. In practice a B2B CRM fails for three reasons: reps do not fill it in, the forecast does not match reality, and quotes still happen in Excel because the system knows neither stock nor contract pricing.
This guide starts from those three risks and turns them into criteria you can verify in a 45-minute demo.
Who it is for
- Sales directors leading between 5 and 200 people
- Founders moving past the stage where selling depended on them
- Companies with an existing ERP that want a CRM on top of it, not instead of it
The 7 criteria, in the order that matters
1Time to log one visit
Time it in the demo: customer, conversation, next step, order. If it takes more than 90 seconds on mobile, reps will fill it in on Friday from memory and your pipeline data becomes fiction.
2Working without signal
Field reps lose signal in warehouses, basements and rural areas. Ask for an explicit offline scenario: entering an order with no connection, syncing on reconnect, and what happens on a data conflict.
3Forecast from behaviour, not rep optimism
Ask how opportunity probability is computed. If it is a percentage the rep types in, the forecast will always be inflated. You need weighting by stage, time in stage and actual activity.
4Stock and contract price at quoting time
In distribution and manufacturing, a quote without real stock and the customer's negotiated price is a risky promise. Check that the CRM shows availability and the customer's price list inside the quoting screen.
5What happens when a rep leaves
Ask to see a portfolio handover: contacts, conversation history, open quotes, commitments made. If the history lives in the rep's personal phone, you do not have a CRM - you have an address book.
6The order's path after the signature
Selling does not end at yes. Follow the order through to delivery and invoicing in the demo. A CRM that stops at the opportunity leaves back-office on email.
7True cost over 24 months
Add licences, implementation, data import, ERP integration and internal hours. Compare it with the current cost of chaos: forgotten opportunities, uncontrolled discounting, admin time. The ROI calculator gives you both numbers.
Red flags in a demo
- The demo only runs on prepared data, never on an import of your own files
- You are shown the desktop screen but never the mobile one
- The answer on ERP integration is "that can be done, we will scope it in the project"
- There is no clear answer to "who owns the data and how do I export it"
How to decide
Decide on two numbers: how many minutes a day the system asks of a rep, and how close the 30-day forecast lands to actual results. Everything else can be learned; these two decide whether the team still uses the system in six months.
Aktualisiert:
Häufige Fragen
Isn't a generalist international CRM enough?+
It is enough for selling services or software. For distribution, manufacturing and retail with portfolio selling, it lacks live stock, contract price lists and the ERP link - and adding those through custom development costs more than the licences.
How long is a realistic implementation?+
For a team under 50 people, 3-6 weeks to daily use, provided customer data is clean. Cleaning the customer base is usually what delays projects, not configuration.
Do I have to drop my current ERP?+
No. The CRM takes over the customer relationship and selling; the ERP stays the source of truth for stock, invoicing and accounting. The two exchange data both ways.
How do I know the team actually uses it?+
Measure the share of opportunities updated in the last 7 days and the number of orders entered from the field. Below 70%, adoption is formal, not real.
Passende Glossarbegriffe
Wo CRMconnect passt
Verwandte Ratgeber
CRM implementation in 30 days: the week-by-week plan
A realistic four-week CRM rollout: cleaning the customer base, configuring the pipeline, onboarding reps and producing the first forecast report.
CRMHow to measure CRM ROI: the formula and the numbers to track
A ROI formula for a B2B CRM, with the four measurable sources of gain and a method for setting the baseline before implementation.