Marketing Technology
How to choose a CRM without being sold to
November 2025 · Written by AI, sense checked by Zuni
CRM selections have a well-documented failure mode: organisations get excited by a product demonstration, align internally around that product, and then reverse-engineer their requirements to match what they've already decided to buy. Vendors are very good at producing compelling demos. They show you the best version of their platform, solving a simplified version of your problem, with an expert at the wheel. It's persuasive. It's also not a useful basis for a decision that will affect your organisation for the next five to ten years.
Why CRM selections go wrong
The most common reasons a CRM selection fails are: requirements weren't defined before the market was assessed; the wrong stakeholders were involved (usually just the marketing team, without input from IT, sales, customer service, or operations); the evaluation weighted features over fit; and total cost of ownership was calculated without accounting for implementation, training, and ongoing support.
Vendor lock-in is also underestimated. Some platforms are designed to make migration expensive – proprietary data formats, complex integrations, and long contract terms all contribute. By the time organisations realise the platform isn't right, leaving is painful.
Start with requirements, not product demos
A vendor-neutral selection process starts well before you talk to any vendor. The first step is mapping the business requirements – what does the CRM need to do, for whom, connected to which systems, and supporting which customer journeys? These requirements should come from a structured process: stakeholder workshops, current state analysis, and a clear view of where the gaps are between what you have now and what you need.
Requirements should be categorised by priority – must-have, should-have, and nice-to-have – and should include functional requirements (what the system does), technical requirements (how it connects to your existing architecture), and operational requirements (how it will be managed and by whom). Only once requirements are documented should you begin assessing the market.
Build a fair evaluation framework
An evaluation framework translates your requirements into a structured scorecard. Each vendor is assessed against the same criteria, weighted by importance. This prevents the loudest voice in the room – or the slickest demo – from dominating the decision. It also creates a defensible audit trail, which matters when you're presenting a recommendation to a board or executive team.
Include implementation partners in the assessment, not just the software. The quality of your implementation will determine whether your CRM investment actually delivers value. A mediocre platform well-implemented often outperforms a best-in-class platform poorly deployed.
The case for independent advice
There's an obvious conflict of interest in seeking advice about CRM from people who are paid to implement CRM platforms. Independent advisers – who are not aligned to any vendor and have no commercial interest in which platform you choose – are better placed to help you define requirements, assess the market fairly, and make a decision based on your needs rather than their partnerships.
The cost of independent advice is modest relative to the cost of choosing the wrong platform. More importantly, a good selection process de-risks what is often a multi-year, organisation-wide commitment.
Want to talk about how this applies to your organisation?
Get in touch with Zuni →More insights
View all articles →