Choosing a CRM: the decision grid, beyond features

Here is an observation vendors do not like: in most CRM projects that fail, the tool chosen could have been suitable. The CRM benchmark had been filled in carefully, the demos had impressed, the boxes were ticked. And the project still went off the rails, because the decision had been made on features and not on what actually makes a CRM succeed or fail: fit with the revenue process, adoption by the teams and data quality.

The real first question is therefore not “which CRM has the most features?” but “which CRM will my teams still be using in 18 months, with reliable data to manage revenue?”. Everything else follows from that.

Why the feature list is the worst starting criterion

On the functional foundation (contacts, pipeline, tasks, basic reporting), the serious CRMs on the market are equivalent. HubSpot, Salesforce, Microsoft Dynamics or Pipedrive all manage a pipeline correctly. Comparing 200 lines of features is like comparing cars on whether they have a steering wheel.

What really differs between platforms, and between projects: how easy it is to get the tool adopted, how data is structured and governed, the full cost over three years, and the ability to evolve (integrations, AI). None of these topics fits in a spreadsheet cell.

There is a second, more uncomfortable reason: the feature list is the vendors' playing field. It is the comparison they prepare for you. Taking back control of the decision means moving the evaluation to your own criteria: your revenue model, your teams, your information system, your full budget. This is exactly the purpose of the grid below.

Criterion 1: fit with your revenue model

The decisive criterion, and the one most often skimmed over. A CRM structures processes: if this structure does not match the way you generate revenue, teams will work around the tool from the second week.

What to evaluate

Start from your processes, not from the tool. Map your actual sales cycle: how many stages, how many people involved on the customer side, what average length, what turning points. Then test each shortlisted CRM against this specific process, in a demo, on your own cases.

Concrete points to watch:

• Can the pipeline structure be adapted to your cycle (several pipelines, conditional stages, multi-line deals) without heavy development?
• Does the CRM handle your real business objects (subscriptions, projects, sites, cases) or does everything have to be forced into “deals”?
• Are marketing-sales scenarios (lead handoff, scoring, nurturing) native or do they depend on third-party tools?
• Warning sign: if the vendor's demo only shows its standard scenario and never yours, you have not evaluated anything yet.
  
  

At Markentive

Our projects start with scoping, not with a demo. Workshops come prepared: draft data models, documented use cases, demonstrations built directly in HubSpot on scenarios close to the client's context. The specification is built jointly from the existing setup, the objectives and the data assets, which makes it possible to test the tool against the revenue process before any commitment.

Criterion 2: predictable adoption by your teams

A CRM that sales reps do not fill in is worthless, however powerful it is. It is blunt, but it is the experience of every project: adoption multiplies everything else.

What to evaluate

Real day-to-day usability, not the demo's: how many clicks to log a call, create a deal, find an account's history. Have the tool tested by your most reluctant users, not your most enthusiastic ones. Their verdict is the right predictor.

Also evaluate the support setup: does the vendor or integrator offer training by user profile (sales, marketing, manager)? Who provides hands-on support after go-live, and for how long? A deployment without hypercare in the first weeks lets bad habits set in, and they can no longer be corrected.

A last, often ignored signal: the mobile version. If your sales reps are in the field and the mobile app is poor, adoption will be decided there.

At Markentive

We treat adoption as a project in its own right, not as an end-of-project step. Training is tailored for each user group, with customized content, manuals and follow-up questionnaires. Go-live is followed by a hypercare phase, then agile support if needed. Our HubSpot CRM and sales enablement training illustrates this setup.

Criterion 3: data governance and reporting reliability

A CRM is first and foremost a database. If the data is wrong, everything built on it (reporting, forecasts, automation, AI) is wrong too.

What to evaluate

• Data quality rules: deduplication, required fields, formats, validation at entry. Native or requiring extra tools?
• Granularity of permissions: who sees what, who edits what, at what level of detail?
• Compliance: data hosting, GDPR, reversibility (can you cleanly retrieve your data if you leave?).
• Reporting: can the dashboards your management needs be built without a weekly Excel export?

A position we stand by: reporting that requires reworking data in a spreadsheet every week is not reporting, it is a symptom.

At Markentive

Data governance structures our deployment protocol: mapping of data assets in the specification, then a four-stage migration (basic configuration, migration and cleaning, advanced configuration and imports, verification before go-live). Our consultants receive ongoing training on data, security and GDPR, and the agency is ISO 27001:2022 certified. The logic behind everything: precise configuration produces accurate reporting, which builds team trust, which drives adoption.

Criterion 4: integration with your information system

An important criterion, but deliberately placed here and not at the top of the grid: a project led by technical considerations often chooses the wrong tool for good architectural reasons.

What to evaluate

List what needs to be connected (ERP, billing, telephony, business tools) and qualify each data flow: criticality, volume, frequency, direction of synchronization. Then evaluate for each CRM the availability of native connectors, the maturity of the API and the cost of custom development.

The structuring point: a CRM is not an ERP, and should not try to become one. A sound architecture entrusts business complexity to the ERP (production, billing, inventory) and relationship agility to the CRM. The right question is not “how do we connect everything” but “what does the CRM replace, and what really needs to be connected”.

Be wary of off-the-shelf middleware presented as a universal answer: on custom objects, high volumes or critical flows such as billing, it quickly reaches its limits.

At Markentive

We systematically favor the simplest architecture: first identify what HubSpot replaces, then what needs to be connected. Depending on the case: a native connector when it covers the need (e.g. HubSpot/Salesforce), tools such as Make or n8n reserved for simple non-critical flows, a dedicated connector (API, UI Extensions, custom code) as soon as volume or criticality requires it. Our SalesOps & Data offer covers these architectures, and the client remains the owner of all deliverables (code repository and documentation handed over at the end of the project).

Criterion 5: total cost of ownership, not the license price

Two CRMs with equivalent licenses can have full costs that differ by a factor of two over three years. This is the criterion where vendor comparisons are the least reliable, by design.

What to evaluate

The full budget includes five items: licenses (watch out for contact tiers, modules billed separately and forced upgrades), integration and deployment, training, change management, and recurring operations (administration, changes, support). Ask each candidate for a three-year projection on these five items, based on your actual volumes.

Also ask about the integrator's engagement model: time and materials or fixed price, what happens in case of overruns, who bears the risk of drift.

At Markentive

We work at a fixed price for a fixed scope: the budget is known before starting and the alignment of interests is structural (a workload overrun is our problem, not yours). The RACI is provided at the scoping stage and the expected involvement on the client side is made explicit (about 0.5 to 1 day per week during the project).

Criterion 6: scalability and AI readiness

The CRM you choose today will support your uses in 2029. And things are moving fast: automatic enrichment, prospecting agents, generated meeting notes, conversational qualification.

What to evaluate

• Is the vendor's AI roadmap native (built into the platform and its data) or cosmetic (a chatbot added on top of the existing product)?
• Do the AI features use your actual CRM data, and with what confidentiality guarantees?
• The ecosystem: app marketplace, partner community, release frequency.
• Will your data be clean enough to feed these uses? An AI agent on a dirty database reproduces errors at scale.

At Markentive

HubSpot builds AI into the core of the platform with Breeze: enrichment, agents, assistants connected to CRM data. Our conviction as an integrator: the order of the work is fixed: data governance first, enrichment second, agents last. This is what we audit before any AI deployment for our clients.

The grid of questions to ask in a tender

Fit with revenue - Can you run the demo on our sales cycle, with our business objects? - How does the tool handle your specific needs: multiple pipelines, subscriptions, buying committees?

Adoption - How many clicks to log a call and create a deal? - What training setup by profile, and what support in the first 8 weeks?

Data and reporting - Which data quality rules are native (deduplication, validation)? - How do we retrieve all of our data if we leave?

IS integration - For our critical flows: native connector, middleware or custom development, and who maintains it? - What does the tool replace in our current stack?

Cost and engagement - What full-cost projection over 3 years for our volumes (licenses, integration, training, run)? - Fixed price or time and materials? Who bears the risk of overruns?

Scalability and AI - Which AI features are available today, on which data, with what guarantees? - What does the product roadmap for the next 18 months look like?

How Markentive meets these 6 criteria

We prefer to be evaluated on the criteria of this grid rather than on promises:

Where do you stand, even before choosing?

The grid above assumes you know yourself well: processes, data, teams, information system. This is the best investment before any demo. Our teams can discuss it with you based on your context.

Learn more

• Our CRM integration offer: scoping, deployment and IS integration by a senior team.
• A website connected to the CRM with HubSpot CMS: when the website and the CRM share the same database.