CRM Software: What CRM Tools Do, and How to Choose One by Capability
Customer relationship management is a set of business capabilities before it is a product category. Organizations that choose CRM software the other way around often buy a sales tool and call it a customer strategy.
By Capstera Business Architecture Staff · Updated
14 min read
CRM stands for customer relationship management. CRM software is the category of applications that record an organization's interactions with customers and prospects and support the work of acquiring, serving and keeping them: managing leads and sales opportunities, running marketing campaigns, and handling service cases, around one shared record of each customer.
A customer calls to complain about a late order. The service agent cannot see that the same customer is in the middle of a large renewal negotiation with sales, or that marketing sent them a cheerful "thank you for your loyalty" email that morning. Three teams, three systems, three versions of the customer, and the one person who sees all of it at once is the customer. The promise of CRM software is a single view of every customer that every team works from. Whether it delivers depends on decisions that have little to do with the software: which customer-facing capabilities the organization needs, how they connect, and who owns the customer data.
Key Takeaways
- CRM is a set of business capabilities, across sales, marketing and service. CRM software supports them; it does not define them.
- The core of any CRM system is a shared data model: accounts, contacts, leads, opportunities, cases and activities.
- CRM software is commonly described as operational, analytical or collaborative, and most products combine all three.
- CRM, ERP and customer data platforms overlap but serve different jobs. Most organizations need CRM to integrate with ERP rather than replace it.
- Choose CRM by capability: decide which customer-facing capabilities the organization needs most, and test vendors on those.
- Most CRM disappointments are about adoption and data quality, not features.
What Is CRM?
The term is used for two things: the business discipline of managing customer relationships, and the software that supports it.
As a discipline, customer relationship management covers how an organization finds prospective customers, wins their business, serves them and keeps them. That work is spread across three functions that rarely share a reporting line: sales, marketing and customer service. As a software category, CRM covers the applications that support that work, usually around a shared record of each customer and every interaction with them.
The distinction matters because the software is far easier to buy than the discipline is to build. A CRM system can be configured in months; agreeing who owns a customer record, how a lead passes from marketing to sales, and when service can see the sales pipeline takes longer and matters more. Business architecture starts with the capabilities and treats the software as the means.
| Function | Typical CRM features | Business capabilities supported |
|---|---|---|
| Sales | Lead and opportunity management, pipeline, forecasting, quotes, account plans | Lead Follow-Up and Qualification, Opportunity Management, Pipeline Management, Sales Forecasting, Account Planning |
| Marketing | Campaigns, email, segmentation, lead scoring, landing pages | Campaign Management, Email and Messaging Marketing, Segmentation and Targeting, Lead Management |
| Customer service | Case management, knowledge base, service levels, self-service portals | Case Intake and Classification, Case Investigation and Resolution, Service Level Management, Knowledge Delivery and Use |
| Across all three | Shared customer record, activity history, reporting, workflow | Customer Interaction Record Management, Customer Service Data Management, Sales Data and Systems Management |
How CRM Software Works: The Data Model at the Center
Every CRM product is built on a small set of shared business objects. Understanding them explains most of what a CRM can and cannot do.
An account is an organization the business deals with; a contact is a person, usually linked to an account. A lead is a prospective customer not yet qualified. An opportunity is a potential sale with a value, a stage and an expected close date. A case is a service request or complaint. Activities, such as calls, meetings and emails, attach to any of these. Campaigns, quotes and products complete the typical core.
The value of a CRM system comes from these objects being shared. When sales, marketing and service all work on the same account and contact records, a service agent can see an open opportunity, and a salesperson can see an open complaint. When each function keeps its own records, or when the CRM is fed from several systems that disagree, the single view of the customer becomes another copy to reconcile.
That is why customer data deserves architecture attention before CRM configuration. Which system is the master for a customer's legal name, billing address or consent preferences? How are duplicates prevented? A business data model that answers those questions once saves a CRM program from answering them inconsistently, field by field.
Types of CRM Software
Three labels describe what CRM software does. Most products today combine all three.
Operational CRM supports day-to-day customer work: entering leads, progressing opportunities, running campaigns and handling cases. It is what most people mean by CRM. Analytical CRM turns the data into insight: pipeline analysis, customer segmentation, churn indicators and campaign performance. Collaborative CRM shares customer information across teams and, sometimes, with partners and customers themselves, through portals and shared records.
A more practical distinction today is scope. Broad suites cover sales, marketing and service on one platform. Specialized products go deep in one area, such as a service desk or a marketing automation tool, and integrate with the rest. Industry editions add data models and processes for sectors such as financial services or healthcare.
Well-known products include Salesforce, Microsoft Dynamics 365 (Microsoft's former Dynamics CRM, which it brought into the Dynamics 365 family in 2016), HubSpot, Zoho CRM, Oracle's and SAP's customer experience suites, and many specialized tools. Products, editions and pricing change frequently, so evaluate current offerings against your own capability needs rather than relying on reputation.
CRM vs. ERP vs. Customer Data Platform
Three kinds of system hold customer data. Confusing them leads to buying the wrong one, or two that fight over the same records.
CRM manages the relationship: interactions, opportunities, campaigns and cases. ERP runs the transactions that follow: orders, fulfillment, invoices and payments. A customer data platform (CDP) gathers customer data from many sources, often including website and app behavior, to build unified profiles, mainly for marketing.
The common pattern is integration, not replacement. An opportunity won in the CRM becomes an order in the ERP system; invoice and payment status flows back so salespeople and service agents can see it. A CDP may feed audiences and profiles into the CRM's marketing tools. The architecture decision is which system is the master for which data, and how changes flow between them.
| CRM | ERP | Customer data platform | |
|---|---|---|---|
| Main job | Manage relationships and interactions | Run orders, fulfillment and finance | Unify customer data from many sources |
| Core records | Accounts, contacts, leads, opportunities, cases | Customers, orders, invoices, payments | Unified customer profiles and events |
| Main users | Sales, marketing, service | Operations, finance | Marketing, analytics |
| Typical question it answers | Where is this deal, and what did we last say to this customer? | Has this order shipped, and has it been paid? | Who is this customer across every channel? |
How to Choose CRM Software by Capability
Feature lists for CRM products run to hundreds of lines, and the leading products tick most of them. Capability priorities are what separate a good choice from a merely adequate one.
Start with the customer-facing capabilities. Capstera's reference models for the three functions CRM serves are detailed: the Sales model has 36 Level 2 capabilities, and the Marketing and the Customer Service and Experience models have 53 each. No organization needs all of them supported equally by one product. The question is which ones matter most to the strategy and perform worst today.
Rate those capabilities for strategic importance and current performance. A business that wins on relationship depth with a small number of large accounts will prioritize account planning, opportunity management and strategic account management. A high-volume consumer business will prioritize campaign management, personalization and case handling at scale. These two organizations should not run the same evaluation, even if they shortlist the same vendors.
Then test vendors on scenarios built from the priority capabilities, run end to end with your own data: a lead from a campaign through qualification, opportunity and quote to the handoff into ERP; a complaint from intake to resolution with the sales team notified. Score adoption risk as seriously as features. A CRM that salespeople avoid updating produces a pipeline nobody trusts.
- List the customer-facing capabilities in scope across sales, marketing and service.
- Rate each for strategic importance and current performance; agree the priorities.
- Decide which system will be the master for each customer data object.
- Write end-to-end scenarios for the priority capabilities and the handoffs between functions.
- Run vendor demonstrations on those scenarios, with your data, not scripted demos.
- Assess adoption: how much effort each role must put in, and what it gets back.
- Build the business case on the priority capabilities and the measures that should move.
Why CRM Programs Disappoint
CRM software is mature. When programs fall short, the causes are usually organizational.
- Low adoption. If entering data costs salespeople time and returns nothing they value, the system fills with stale records and the pipeline report becomes fiction.
- Poor data quality. Duplicates, missing fields and conflicting sources undermine the single customer view the program was meant to create.
- A sales tool called a customer strategy. Deploying only sales features leaves marketing and service on separate systems, and the customer still sees three companies.
- Undefined handoffs. Without an agreed definition of a qualified lead, or of when service sees a sales opportunity, the integration has nothing to integrate.
- Over-customization. Recreating every legacy screen and exception makes upgrades expensive and leaves the organization behind the product.
- No measures. Without a baseline for the capabilities the program targets, such as lead conversion or first contact resolution, nobody can tell whether it worked.
A Worked Example: Choosing a CRM for a Specialty Insurer
An illustrative example. The insurer and its decisions are invented to show capability-based selection.
A specialty insurer sells through brokers and services policyholders directly. Its broker managers use spreadsheets; its service team uses an old case system; marketing sends broker newsletters from a separate tool. The proposal on the table is a well-known CRM suite, chosen because a competitor uses it.
The business architecture team starts from capabilities. Across sales, marketing and service, two capabilities stand out as both important and weak. Partner opportunity management matters because brokers bring nearly all new business, and the insurer has no shared view of which brokers are bringing which opportunities. Complaint handling matters because complaints are slow to resolve and nobody sees them in sales conversations with the same brokers.
Those two capabilities reshape the evaluation. Vendor demonstrations must show a broker submitting a risk, the underwriter's quote, and a broker manager's view of every opportunity from that broker; and a complaint raised by a policyholder appearing on the broker's account record. One shortlisted product handles the broker scenario far better than the competitor's choice. The selection changes, and the business case is built on broker submission volume and complaint resolution time rather than on "a single customer view."
CRM and Business Architecture
Business architecture keeps a CRM program anchored to what the customer-facing organization needs to be able to do.
The capability map defines scope in terms the business recognizes and shows which capabilities the CRM will support, which stay with specialist tools, and which are not changing. Value streams such as lead-to-order and issue-to-resolution show the handoffs between sales, marketing and service that a CRM must make seamless, and the measures that tell whether it has. The business data model settles which system owns each customer object.
Together they also protect the program from scope drift. When a new request arrives, the question becomes which capability it serves and whether that capability is a priority, rather than whether the product can do it.
Go further
- Business architecture-led CRM transformation — Running a CRM program from the capability map rather than the feature list.
- ERP system — Where CRM hands over: orders, fulfillment and invoicing.
- KPI meaning — Defining lead conversion, retention and resolution measures that teams trust.
- Business case — Building the CRM case on the capabilities it improves.
Frequently Asked Questions
What is CRM software?
CRM software is the category of applications that record an organization's interactions with customers and prospects and support sales, marketing and customer service work, such as managing leads and opportunities, running campaigns and handling service cases, around a shared record of each customer.
What does CRM stand for?
Customer relationship management. It refers both to the business discipline of acquiring, serving and retaining customers and to the software that supports it.
What are examples of CRM tools?
Widely used examples include Salesforce, Microsoft Dynamics 365, HubSpot, Zoho CRM, and the customer experience suites from Oracle and SAP, along with many specialized tools for service desks or marketing automation.
What happened to Microsoft Dynamics CRM?
Microsoft brought Dynamics CRM into its Dynamics 365 family in 2016. Its sales, customer service and marketing capabilities are now offered as Dynamics 365 applications.
What are the three types of CRM?
Operational CRM supports day-to-day sales, marketing and service work; analytical CRM turns customer data into insight; and collaborative CRM shares customer information across teams and with partners or customers. Most products combine all three.
What is the difference between CRM and ERP?
CRM manages customer relationships and interactions: leads, opportunities, campaigns and cases. ERP runs the transactions that follow: orders, fulfillment, invoicing and payments. Most organizations integrate the two so a won opportunity becomes an order.
How do you choose CRM software?
Identify the customer-facing capabilities that matter most to the strategy and perform worst today, decide which system will own each customer data object, then test vendors on end-to-end scenarios for those capabilities using your own data, and weigh adoption as heavily as features.
Why do CRM implementations fail?
Mostly because of low adoption, poor data quality, undefined handoffs between sales, marketing and service, over-customization, and the absence of measures showing whether the targeted capabilities improved.
Pro Tips
- Give every role something back for the data it enters: a salesperson who updates an opportunity should get a better forecast or less admin, not just a request for more fields.
- Agree the definition of a qualified lead, in writing, before configuring lead scoring.
- Decide the master system for each customer object before the first integration is built.
- Pilot with the team whose capability is the top priority, and measure the capability, not logins.
- Retire the spreadsheets and side tools on a set date; parallel systems are where adoption goes to die.