CRM Platform: What Marketers Get Wrong Before They Buy

A CRM platform is software that centralises customer and prospect data, tracks interactions across the sales and marketing funnel, and gives teams a shared view of every relationship the business holds. Done well, it connects marketing activity to revenue. Done poorly, it becomes an expensive contact database that nobody trusts.

Most buying decisions go wrong before a single demo is booked. Teams define the wrong requirements, evaluate on features they will never use, and underestimate the integration work that determines whether the platform actually earns its licence fee. This article is about avoiding that.

I have bought, implemented, and inherited CRM platforms across multiple businesses. I have watched a well-resourced team at a mid-market agency spend six months on a Salesforce implementation only to revert to spreadsheets because nobody had defined what “a contact” actually meant in their business before they started. The platform was not the problem. The thinking before the platform was the problem.

What a CRM Platform Actually Does for Marketing

There is a version of this conversation that starts with pipeline management and sales velocity, and that is a legitimate framing. But marketers have a different set of questions. They want to know which campaigns drove which contacts, how those contacts moved through the funnel, where they dropped off, and what the revenue attribution looks like at the end of it.

A CRM platform answers those questions only if it is connected to the right inputs. Campaign data needs to flow in from your email tool, your ad platforms, your website analytics. Contact records need to be enriched over time, not just created once and left static. Activity needs to be logged consistently, whether that is a sales call, a form submission, or a content download.

This is where the marketing use case diverges from the sales use case. Sales teams want the CRM to show them what to do next. Marketing teams want it to show them what worked. Both are valid. Most CRM platforms serve one better than the other, and knowing which side of that line your primary use case sits on will save you a significant amount of evaluation time.

If you are working through how CRM fits into a broader marketing automation strategy, the Marketing Automation Systems Hub covers the full picture, from platform selection through to workflow design and measurement.

The Requirements Problem That Derails Most Evaluations

When I was running an agency and we were looking at upgrading our CRM, I made a deliberate decision to start the requirements process with the people who would use it daily, not the people who would approve the budget. That sounds obvious. In practice, most evaluations do the opposite. The senior team defines the requirements based on what they think the business needs, and the people who will actually log in every day are consulted late, if at all.

The result is a requirements document that is technically accurate and practically useless. It describes an ideal state that the team has no interest in maintaining because nobody asked them what would make their work easier.

Good requirements for a CRM platform evaluation look like this. You start with the data model: what objects do you need, what are the relationships between them, and what does your contact lifecycle actually look like from first touch to closed deal. Then you move to the workflows: what processes need to happen automatically, what needs human intervention, and where are the handoffs between marketing and sales. Then you look at the integrations: what does this platform need to talk to, and how does data flow in both directions.

Features come last. Not because they do not matter, but because features without a clear process context are just a list of things that might be useful someday. Vendors are very good at making features sound essential. They are less good at telling you which ones their customers actually use.

For a detailed breakdown of the platforms worth putting on your shortlist, the piece on CRM software: what to use and why covers the market with a clear commercial lens rather than a feature checklist.

Integration Is Where CRM Value Is Made or Lost

Early in my career, I taught myself to code because the business would not fund a website rebuild. That experience gave me a useful perspective on integration work: it is almost always harder than the vendor makes it sound, and the complexity compounds with every additional system you connect.

CRM integration is not a one-time project. It is an ongoing operational commitment. Data formats change. APIs get updated. A field that maps cleanly today may break when your email platform releases a new version. If you do not have someone in the business who owns this, you will feel the consequences within six months of going live.

The integrations that matter most for marketing teams are typically these. First, your email marketing or marketing automation platform, because without a clean bidirectional sync you lose the ability to attribute email engagement to contact records. Second, your website and analytics stack, because form submissions, page visits, and content downloads are some of the richest behavioural signals you have. Third, your ad platforms, because if you cannot tie campaign spend to contact acquisition and downstream revenue, you are flying blind on budget allocation.

Video is increasingly part of this picture too. Platforms like Vidyard have built direct integrations with Salesforce and Pardot, which means video engagement data, who watched what, for how long, and how many times, can flow directly into contact records. That kind of behavioural signal is genuinely useful for lead scoring and sales prioritisation. It is the sort of integration that sounds like a nice-to-have until you see it working.

The question to ask every vendor during evaluation is not “do you integrate with X?” but “show me what the data looks like in the contact record after the integration runs.” The first question gets you a yes. The second question gets you the truth.

Mobile CRM: Not Optional Anymore

There was a period when mobile CRM was a feature that appeared in vendor presentations and then got quietly ignored by everyone actually using the platform. That period is over. Field sales teams, account managers, and anyone who spends time in client meetings rather than at a desk now expects to log activity, pull up contact history, and update deal stages from their phone.

The case for mobile CRM solutions is straightforward: data entered immediately after a meeting is more accurate than data entered at the end of the day from memory. The longer the gap between the interaction and the log, the worse the data quality. And data quality is the foundation everything else in your CRM is built on.

When evaluating mobile capability, look beyond the existence of an app. Test the actual workflows your team will use most frequently. Can they log a call in three taps? Can they pull up a contact record with full interaction history before walking into a meeting? Can they create a follow-up task without switching to a laptop? If the answer to any of those is no, or “yes, but it takes eight steps,” the mobile experience will not get used consistently, and inconsistent usage is the beginning of data quality problems.

HubSpot, Salesforce, and the Platform Decision Most Teams Overthink

Most CRM platform decisions eventually come down to a comparison between HubSpot and Salesforce, with Microsoft Dynamics appearing in enterprise contexts and a range of lighter tools competing for the SME segment. The choice between them is less about which platform is better in the abstract and more about which one fits the maturity, size, and technical capability of your business.

HubSpot has invested heavily in its platform over the past few years. The HubSpot product evolution has moved it from a primarily marketing-focused tool to a more complete CRM suite, which makes it a more credible option for businesses that previously would have defaulted to Salesforce. It is worth understanding what has changed before you assume you know where the capability gaps are.

Salesforce remains the dominant enterprise choice, and for good reason. The customisation depth, the ecosystem of third-party apps, and the reporting flexibility are genuinely superior at scale. But that power comes with implementation complexity and a total cost of ownership that catches many businesses off guard. The licence fee is often the smallest part of the Salesforce bill once you factor in implementation, customisation, and ongoing administration.

For smaller businesses, the calculus is different. If you are running a lean team and you need something that works out of the box with minimal configuration, the enterprise platforms will slow you down more than they help you. The best CRM for small business is almost never the most feature-rich option. It is the one your team will actually use.

I have seen this play out repeatedly. A business convinces itself it needs enterprise-grade CRM because it is planning to grow into it. Two years later, it is paying for a platform it is using at 15% of capacity, and the team has developed workarounds that sit outside the system entirely. The platform did not fail. The ambition in the buying decision was not matched by the operational reality.

Workflow Automation Inside the CRM

One of the most significant shifts in CRM platforms over the past five years is the expansion of native workflow automation. What used to require a separate marketing automation tool or a custom integration can now often be handled inside the CRM itself. Lead assignment rules, follow-up sequences, lifecycle stage transitions, task creation based on contact behaviour: these are standard features in most mid-tier platforms now.

The risk is that teams automate before they have documented the process they are automating. I have walked into businesses where the CRM automation was running correctly, in the sense that it was doing exactly what someone had configured it to do, but what it had been configured to do was a process that nobody actually followed anymore. The automation had locked in a workflow that the team had moved on from, and nobody had gone back to update it.

If you are starting to think about how automation should work across your marketing stack, not just inside the CRM, the piece on workflow automation: where to start is worth reading before you configure anything. Getting the sequencing right before you build saves a significant amount of rework.

The practical principle here is straightforward. Document the process on paper first. Walk through it with the people who will be affected by it. Identify the edge cases. Then automate. In that order. Automating an undocumented process does not make it better. It makes it harder to fix.

Data Quality: The Problem That Compounds

I spent time in a previous role managing a CRM that had been live for four years without a data quality programme. The contact database had 180,000 records. Roughly a third of them were duplicates, another third had incomplete data, and a meaningful portion of the email addresses were either invalid or belonged to people who had left the companies they were associated with. The platform was technically functioning. The data inside it was largely useless.

Data quality in a CRM degrades naturally over time. People change jobs. Companies merge or close. Contact details become outdated. This is not a failure of the platform. It is the nature of business data. What matters is whether you have a process for managing it.

The basics of a data quality programme are not complicated. You need a duplicate detection and merge process that runs regularly, not just at implementation. You need field validation rules that prevent garbage data from entering the system in the first place. You need a regular audit of your most important segments to check that the records in them are still accurate. And you need someone who is accountable for data quality as an ongoing responsibility, not as a project that gets done once and forgotten.

The compounding effect runs in both directions. Good data compounds in value: better segmentation, more accurate attribution, higher deliverability, cleaner reporting. Poor data compounds in cost: wasted campaign spend, missed follow-ups, incorrect reporting that leads to bad decisions. The gap between a business with a data quality discipline and one without it widens every year.

CRM for Specific Sectors: Why Context Changes Everything

Generic CRM advice tends to assume a B2B SaaS or professional services context. The reality is that CRM requirements vary significantly by sector, and some of the most interesting implementation challenges come from industries where the standard playbook does not apply cleanly.

Legal services is a good example. Law firms have specific requirements around client confidentiality, conflict checking, matter management, and the regulatory constraints that govern how they can communicate with prospects. A CRM that works well for a technology company will not necessarily work for a law firm without significant customisation. The piece on marketing automation for law firms covers what actually works in that context, which is worth reading if you are evaluating CRM for a professional services business with similar constraints.

Government and public sector contexts present a different set of challenges, primarily around data sovereignty, procurement rules, and the need for specific compliance certifications. HubSpot has documented some of the CRM software options relevant to government agencies, which illustrates how differently the evaluation criteria look when procurement and compliance requirements are primary constraints rather than secondary considerations.

The principle that applies across sectors is this: the further your business is from the archetypal B2B sales model that most CRM platforms are designed around, the more carefully you need to evaluate whether a platform’s standard configuration will work for you, or whether you are buying a platform and then paying again to make it fit your actual business.

The Knowledge Base Question Nobody Asks at Demo Stage

Here is something that gets overlooked in almost every CRM evaluation: what happens when your team needs help? Not during the sales process, when the vendor is attentive and responsive, but six months after go-live when you have a specific configuration question and the person who set up the system has left the business.

The quality of a vendor’s documentation and self-service support is a legitimate evaluation criterion. A platform with a comprehensive, well-maintained knowledge base will cost you less in ongoing support than a platform where every question requires a support ticket or a paid professional services engagement.

This connects to a broader question about how your team will build and maintain internal knowledge around the platform. If you are thinking about how to document your CRM configuration, your custom fields, your workflow logic, and your integration architecture in a way that survives staff turnover, the piece on best knowledge base software in 2026 covers the options for building that internal documentation layer properly.

I have seen businesses lose months of productivity because a key CRM administrator left and the institutional knowledge about how the system was configured left with them. The fix is not complicated. It requires treating your CRM configuration as something that needs to be documented as carefully as any other business process. Most teams do not do this until they have experienced the consequences of not doing it.

Attribution: What Your CRM Can and Cannot Tell You

When I was at lastminute.com, I ran a paid search campaign for a music festival that generated six figures of revenue within roughly a day. The attribution was clean because the transaction happened online and the tracking was in place. That kind of closed-loop clarity is what every marketer wants from their CRM. It is also, in most B2B contexts, significantly harder to achieve than it looks.

CRM attribution works well when the buying experience is short, the number of touchpoints is manageable, and the conversion happens in a channel you control. It gets complicated when deals take months to close, involve multiple stakeholders, and include touchpoints that are not tracked, such as word of mouth, events, or conversations that happen outside any digital channel.

The honest answer is that CRM attribution gives you a useful approximation, not a precise measurement. It will tell you which campaigns generated the most pipeline, which channels are producing the highest quality contacts, and where in the funnel you are losing deals. That is genuinely valuable. It will not give you a perfect model of every influence on every buying decision. Expecting it to do so leads to over-engineering the attribution model and under-investing in the marketing activity that is hard to measure but often highly effective.

The practical approach is to use CRM attribution data to inform decisions rather than determine them. Treat it as one signal among several, not as the definitive answer to which marketing activity is working. The businesses I have seen get the most value from their CRM data are the ones that combine it with qualitative insight from sales conversations and customer interviews, rather than treating the platform’s reporting as a complete picture of reality.

Content strategy is part of this picture too. If your content marketing is generating contacts that convert well, that should be visible in your CRM data. If you are thinking about how to structure a content platform that feeds cleanly into your CRM pipeline, Optimizely’s buyer’s guide to content marketing platforms is a useful reference for understanding how the content and CRM layers interact.

Implementation: The Phase That Determines Everything

CRM implementation is where most of the value is created or destroyed. The platform decision matters. The implementation matters more. A well-implemented mid-tier platform will outperform a poorly implemented enterprise platform every time, because the quality of the data, the consistency of the processes, and the adoption rate of the team are all determined during implementation, not during the sales process.

There are a few principles that consistently separate successful implementations from failed ones.

Start with a clearly defined data model before you configure anything. Agree on what a contact is, what a company is, what a deal is, and what the relationships between them look like in your business. This sounds like a simple step. It often takes longer than teams expect, because it surfaces disagreements about business processes that have never been explicitly resolved.

Run a pilot with a small group before you roll out to the full team. The pilot will surface configuration problems, workflow gaps, and usability issues that you will not find in a demo environment. Fix them before they become problems at scale.

Define what good looks like before you go live. What does a complete contact record look like? What fields are mandatory? What does the sales team need to see when they open a contact? What does the marketing team need to see when they are building a segment? These questions need answers before go-live, not after.

Plan for adoption as seriously as you plan for configuration. Training is necessary but not sufficient. The team needs to understand why the CRM is being used, not just how. If the benefit of logging activity is not visible to the person doing the logging, they will stop doing it. Make the value of good data visible to the people creating it.

When to Reassess Your Current Platform

There is a version of the CRM conversation that assumes you are starting from scratch. Most businesses are not. They have an existing platform, an existing data set, and an existing set of integrations. The question is not “which CRM should we buy?” but “is our current CRM still the right fit, and if not, what does migration actually cost?”

The signals that suggest it is time to reassess are usually operational rather than technical. The team is maintaining data outside the CRM because the CRM is too difficult to use. Reporting requires manual extraction and manipulation because the native reporting cannot answer the questions the business is asking. Integration with a new tool the business has adopted is technically possible but practically painful. The platform has grown beyond what the current CRM can handle without significant customisation that was not budgeted for.

Migration is expensive in ways that are not always visible upfront. The data migration itself, the re-implementation of workflows and automations, the retraining of the team, and the productivity dip during transition all have real costs. Before committing to a migration, it is worth asking whether the problems you are experiencing are platform problems or process problems. Migrating to a new platform does not fix a process problem. It just creates a new environment in which the same process problem plays out.

If the problems are genuinely platform-related, then migration is the right call. But go in with clear eyes about what it involves, build a realistic timeline, and do not underestimate the data quality work that needs to happen before you migrate. Moving bad data from one platform to another does not improve it.

CRM sits at the centre of a broader marketing technology ecosystem. If you want to understand how it connects to the rest of your automation infrastructure, the Marketing Automation Systems Hub covers that full picture, from platform selection through to measurement and optimisation.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions