Do you need RevOps, or just a better CRM? How to decide before you change tools

Do you need RevOps, or just a better CRM?

Almost every B2B company needs a CRM, more or less sophisticated. The useful question isn't whether you need one, but whether you're ready to get value from it.

And a CRM's value isn't in the data. It's in what you do with it. A record nobody uses to decide is a cost, not an asset.

That's why technology comes after three things: people, process and culture. If your team isn't used to recording things and deciding with data, no tool will build that habit on its own. If it is, choosing a tool becomes a sensible technical decision: size, volume, integrations and how it grows with you.

RevOps is the discipline that designs that process: which stages your sale goes through, what it takes to move from one to the next, who owns each piece of data and which decisions it informs. What is Revenue Operations? →

What does a tool fix, and what does a process fix?

A tool stores a process; it doesn't design one.

How do you know the problem isn't your CRM?

In the first few minutes of a conversation, some signals point to an organisational problem rather than a technical one:

• Data plays no part in how decisions are made. Sales meetings run on impressions, not on what the system says.
• The fields exist, but they're empty. Lead source or loss reason is missing from most records.
• Pipeline stages have no entry or exit criteria: they reflect each salesperson's gut feel.
• Deals are won from any stage, which means the funnel doesn't describe how you actually sell.
• There are several pipelines, duplicate records and deals nobody has touched for months.
• The forecast lives in someone's personal spreadsheet, outside the CRM.
• What the team believes about where customers come from doesn't match what the customer base shows.
• Marketing and sales don't share a definition of a qualified lead.

If you recognise three or more, changing tools will move the problem to another screen. What's needed is to sort out how departments work together, the process between marketing and sales, and each team's role.

And when is it the CRM?

Sometimes changing tools is the right call. It's almost always a question of fit:

• The tool is too big for you. A platform built for large teams can work in a small company, but the licence cost and the complexity aren't justified, and it ends up unused.
• The tool is too small for you. A home-grown tool holds while there are only a few of you. When you grow and need more integrations, automation or support, it becomes the bottleneck.
• The cost doesn't scale with you. Some plans get more expensive with every active contact or user. Projecting the bill two or three years out can change the decision.

For small companies there's a third route: a bespoke CRM built with no-code or low-code tools, such as a well-designed database in Notion. If the process is clear, it can be enough, and it costs less than any off-the-shelf platform.

What should you decide before choosing or setting up a CRM?

Everything around the configuration of a tool, without counting the tool itself, is worth as much as the tool, or more. These are the five decisions to have taken:

1. The stages, and who does what at each one. Which stages a contact goes through to become a lead, and a lead to become an opportunity. Not just as a concept: what each team has to do at each stage to move it forward.
2. The reports and KPIs you decide with. Which reports the leadership team looks at today, which indicators it uses to decide, and where each figure comes from.
3. The qualification criteria. What separates a marketing lead from one sales accepts (MQL and SQL, if you use those terms), written down and shared.
4. When a proposal goes cold. How long it can go without a reply before you count it as lost, and what marks a proposal as accepted or rejected.
5. Why you lose. A mandatory loss reason from a closed list, and the habit of reviewing important losses instead of forgetting them.

And one condition before all five: who looks after the data. Someone has to own the hygiene of the CRM, because whatever the CRM doesn't know doesn't exist.

What happens when you migrate CRM without deciding the process?

Several things tend to happen at once:

• The team goes back to its old ways. If the decision was taken without the people who use the tool every day, resistance to change wins. As we say in Spain, the goat always heads back to the hills.
• Fields get lost on the way. Nobody checked that every field in the old system had an equivalent in the new one, or how much customisation it had.
• Automations stop doing what they did, or do it differently without anyone noticing.
• Nobody can fix it when it breaks. Support varies from one platform to another, and the person who maintained the old CRM isn't always still around.
• The decision came from the top for the wrong reason. A good salesperson from the platform persuaded someone with authority, on cost savings or on fashion, and the team that works with the tool every day found out afterwards.

What never appears in the quote for a new CRM?

The licence is in the quote. What almost never is:

• training the team;
• support when something breaks;
• implementation consultancy;
• the time each department spends defining its use cases.

Most of it isn't an external invoice but hours from your own team, and those hours cost money too. Add to that how the licence grows as the business grows: by active contacts, by users or by features.

Three cases where it looked like the CRM and was the process

Cases from RevOps Studio diagnostics, anonymised.

A marketing services company. The team was thinking about switching tools. Not a single opportunity had its source or loss reason recorded, and what was lost over two years came to almost three times what was won. The diagnostic concluded their CRM was good enough: the problem was what had been defined and who looked after it. A new CRM doesn't fix fields nobody is required to fill in. The recommendation, doable in days: mandatory lead source and loss reason from a closed list, stages redefined as verifiable milestones, the forecast kept separate from opportunities, and one person responsible for the data. It all fitted in a one-page specification.

A creative studio. The CRM was reasonably clean. The fault was that the funnel didn't describe how the firm really sold: projects were won from any stage, the value of each opportunity didn't match what was invoiced by milestone, and the hand-off to invoicing was manual. The process needed redesigning for its two ways of selling, with clear definitions of contracted, invoiced and recognised revenue. Hygiene, not a rebuild.

A digital services agency with no CRM. It had no CRM by choice. Three or four proposals in every ten were lost with no record of why, and the owner credited LinkedIn with 10% of new business when it had brought in 5 of his 12 accounts. The recommendation wasn't to buy a CRM. It was a spreadsheet with five validated fields: source, stage, date, value and loss reason. That was enough to start learning from its own customer base.

What if you don't have a CRM yet?

Before you choose one, answer four questions: why you haven't had one until now, where your sales data lives today, who keeps it up to date, and how departments pass information to each other.

The answers will tell you what you need. Sometimes what you need is to start smaller: a well-designed spreadsheet with source, stage, date, value and loss reason, and one person responsible for it. When it falls short, you'll know exactly what to ask of a CRM.

HubSpot, Salesforce, Pipedrive or Zoho: which should you choose?

Don't start by comparing them with each other. They're all solid, established platforms with a community behind them. The earlier question is different:

• Does it fit your size today?
• Can it grow with you?
• Is that growth sustainable in cost?

Before you decide, project the bill against your expected contacts, users and features. A "best CRM" ranking doesn't know your process. How to choose a CRM by process requirements →

Why don't we recommend a platform?

Whoever sells licences or partners with a platform ends up recommending that platform: because of the commercial agreement, and because it's what their team knows how to implement. The recommendation is biased from birth, even when it's made in good faith.

RevOps Studio is not a HubSpot, Salesforce or Pipedrive partner and takes no platform commissions. So we can recommend the tool that fits your process, or no off-the-shelf tool at all if a bespoke CRM serves you better. The interest is in your objectives, not in the technology.

Three questions to ask yourself before you decide

If you're about to change CRM, ask yourself three questions:

1. Are my processes solid enough for a CRM to get value from them? Stages, criteria and owners.
2. Do I have a data culture? Not just in people: where the data lives, how good it is, who looks after it and how much weight it carries in decisions.
3. Do I understand the full economic impact? The licence, how it scales with the business, and the less visible cost: hours of dedication, teams and perhaps a hire.

If any answer is "I don't know", the first step isn't a CRM demo. It's finding out where the process breaks.

Frequently asked questions

How much does it cost to implement a CRM? It depends on the licence, the number of users and contacts and, above all, on what the quote leaves out: training, support, implementation and your team's hours. Before you ask for prices, estimate those hours and project how the licence will grow with your business.

Can I use Notion or a spreadsheet as a CRM? Yes, if the process is clear and the volume allows it. A well-designed base with five mandatory fields and one person responsible can serve you better than a platform nobody updates.

Who should look after the CRM? A named person, with time set aside for it and the authority to insist the fields get filled in. Without that owner, whatever the CRM doesn't know doesn't exist.

What is RevOps, in one sentence? The discipline that designs and maintains how a company generates, qualifies and closes business: processes, criteria, roles, tools and data.

What if I don't know which process I need? Start by finding out where it breaks. The Revenue Diagnostic walks your sales chain with your own data and tells you which stage fails, what it costs and what to attack first, before you choose any tool.