What is a CRM and what does it do for B2B

CRM stands for customer relationship management. People use the term for two things. The system, the software that holds your customers, contacts and sales opportunities. And the way of working that comes with it: agreements about what you record, when, and who follows up on what.

That second part is often forgotten. A CRM is not a ledger that balances itself. It is only as good as what your team puts in. So whoever introduces a CRM is not just choosing a package, they are also making agreements. What counts as a lead? When does it become a deal? Who calls a new request within a day? What must be on a deal before it can move to Proposal?

Why bother? Because in most companies without a CRM, customer knowledge is scattered. Part of it sits in the account manager's inbox. Part in a spreadsheet one colleague maintains. Part in the head of someone who goes on leave next month. When that person leaves, the knowledge leaves too.

A CRM puts that knowledge in one place, with the company instead of the person. Whoever opens a customer sees who works there, what was discussed in recent months, which quotes are out and when the next meeting is. That is the whole idea. Everything else, such as automations, reports and AI, builds on it and only works when that foundation is right.

In B2B this matters even more, because you sell to organizations, not to individuals. An order rarely comes from one person. There is a user, a budget holder, someone from procurement and sometimes a director who has the final say. A B2B CRM has to show that whole group, with each person's role.

In the literature you often see three kinds of CRM. They are worth knowing, because vendors talk about them this way.

• Operational CRM. The daily work: leads, deals, activities, email and quotes. This is what most people mean when they say CRM.
• Analytical CRM. Reporting on what happens: conversion per stage, deal cycle time, revenue per segment, a weighted forecast.
• Collaborative CRM. Sharing information across teams: sales, service and marketing look at the same customer. An open ticket is visible to the account manager.

In practice the three overlap, and that is fine. A modern B2B CRM does all three, but not every package goes equally far. Some are mainly a sales CRM with a pipeline. Others also put support, marketing and customer success in the same system.

Which one you need depends on where it pinches. If deals slip away because nobody follows up, start operational. If leadership does not know what will close next quarter, you need the analytical part, but that only works once the operational part is in order. And if sales and support work past each other, the collaborative part is where the gain is. Read how to choose a CRM to turn that into requirements.

The most important design decision in a B2B CRM is that organizations and people are separate records linked to each other. It sounds technical, but it decides how useful your CRM still is two years from now.

Take a spreadsheet with a row per contact and a Company column. With three contacts at the same company, the company name appears three times, probably spelled three ways. When the address changes, you change it three times. If you want to know your revenue with that company, you add it up by hand.

In a CRM the company exists once. People hang off it, as do deals, activities and email. Change something about the company and it changes everywhere. Revenue per customer is a sum the system makes for you.

Three situations where this makes the difference in B2B:

• Someone changes jobs. Your best contact at a customer moves to another company. In a good CRM you link the person to the new organization and the history stays with the old one. Often that is your next customer.
• Groups and holdings. A customer with five branches that each order separately. With a parent organization you see them as a group and per branch.
• A buying committee. A deal decided by four people. You link them all to the deal as participants, so you see who you have and have not spoken to.

Two things go wrong most often in practice. Duplicate organizations, because someone creates both Baker Ltd and Baker Limited. And people without an organization, because it was quicker. Both make your reports unreliable. Read data quality on how to prevent that.

For most teams the pipeline is the screen they choose a CRM for. But a pipeline only works when everyone means the same thing by each stage. So you give every stage an exit criterion: what must be true before a deal can move on. Below is a template for a B2B service company or wholesaler with a sales cycle of a few weeks to a few months. Copy it and adjust it.

• Intro scheduled. There is a meeting in the calendar with someone who owns the topic. Exit: the meeting took place. Starting win probability 10 percent.
• Need confirmed. You know what problem the customer wants to solve, by when and who else decides. Exit: the customer confirmed they want a proposal. Win probability 25 percent.
• Proposal in progress. You are working on the quote. Exit: the quote is sent and a follow-up is booked. Win probability 40 percent.
• Quote sent. The customer has the quote. Exit: the customer replied with questions, a counter offer or a yes. Win probability 50 percent.
• Negotiation. You discuss price, scope or terms. Exit: a verbal yes or a definite no. Win probability 75 percent.
• Won or lost. When lost, always record a lost reason. Without it you learn nothing from your pipeline.

The win probabilities above are a starting point, not the truth. After a few months you look at your own data to see how many deals are really won from each stage, and you adjust. Also give each stage a maximum time. If a deal sits in Quote sent longer than, say, twenty days, you want to see it. More in B2B pipeline stages and setting up a sales pipeline.

One of the first things a CRM gives you is an honest view of what is in the pipeline. Not the sum of all deals, which is always too optimistic, but the weighted value. An example with made up numbers.

Say you have twelve open deals averaging 10,000 euros. Together 120,000 euros. That sounds good, but they sit in different stages.

• Four deals in Need confirmed, 40,000 euros, times 25 percent is 10,000 euros.
• Five deals in Quote sent, 50,000 euros, times 50 percent is 25,000 euros.
• Three deals in Negotiation, 30,000 euros, times 75 percent is 22,500 euros.

So the weighted pipeline is 57,500 euros, not 120,000. That is the number you plan a quarter with. And if your target is 80,000 euros, you know now that you need more new opportunities, not at the end of the quarter.

The same sum also shows where it leaks. If many deals drop out between Quote sent and Negotiation, the problem is in your quotes or your follow-up, not your lead generation. Without a CRM that is a feeling. With one, it is a number per stage. Read more in forecasting for B2B.

A second sum is about time. Suppose eight reps each spend half an hour a day looking for information: which email had that price, who spoke to that customer last. That is four hours a day, twenty hours a week. Whether that holds for you, you only know once you measure it. But it shows where the time goes.

A CRM does not sell for you. It makes visible what happens and what gets left behind. If nobody records the next step, the CRM sees nothing, and then it is an expensive spreadsheet.

At Sales Surge we have done more than 150 CRM implementations. These are the pitfalls we run into most:

• Too many fields on day one. A deal with thirty required fields does not get updated. Start with what you actually use in your sales meeting. The rest comes later.
• Stages without exit criteria. Then a deal sits in Negotiation because the rep has a good feeling about it. Your pipeline becomes a wish list.
• The CRM as a control tool. If reps mainly see the CRM as a way for the manager to check on them, they fill in the minimum. Make sure it gives them something too, such as an overview of what to do today.
• Importing dirty data. Whoever imports everything during a switch also imports every duplicate and outdated contact. Clean up first.
• No owner. A CRM without someone looking after it gets polluted within a year. Appoint an owner, even if it is a few hours a week.
• Everything at once. Rolling out sales, marketing and service together is a lot. Start where it pinches most and expand after. Read a CRM rollout in phases.

The biggest pitfall is treating a CRM as an IT project. It is a change in how your team works. That takes explanation, training and a few weeks of adjusting. More on that in CRM adoption.

A CRM holds personal data: names, email addresses, phone numbers and what you discussed with someone. So GDPR applies. That need not be a hurdle, but it helps to sort out a few things up front.

For ordinary business contact with a customer or prospect you usually have a legal basis in performing a contract or a legitimate interest. For marketing email to large groups it is stricter: in many cases you need consent, and you must be able to show it. A good CRM records that consent on the person, with its source and timing.

You also need to handle requests. Someone asks what data you hold on them, or asks to be erased. In a spreadsheet and five inboxes that means searching. In a CRM you want an export per person and a way to erase someone completely. Agree on retention periods too: how long do you keep data on a prospect who never became a customer? This is not legal advice, check the details with your own adviser. Read more in email and GDPR.