ScaleOps Best Practices

You Don't Need Most of Your CRM. Here's How to Find the 10% You Do

Written by Nelly Nechaev | Sep 5, 2026, 9:15:00 PM

Most companies use a fraction of the CRM they pay for, and that fraction is fine. The problem starts when nobody ever decided which fraction. What you get instead is a portal full of half-built things, and a team that quietly goes back to spreadsheets.

Deciding which parts of a platform belong to you, at your size, with your team, is a business decision. It doesn't come with the license. That's the whole argument of this piece, and everything below is the evidence for it.

The most honest thing said in the room

I sat in on a HubSpot for Startups webinar this August. Somewhere in the middle, a founder asked the question everyone in that session was probably thinking: why does this feel like a labyrinth?

The answer from HubSpot's side, more or less, was that he probably didn't need most of what he was looking at.

I've thought about that answer a lot since. It sounds like a criticism of the product. It isn't. It's the most useful sentence anyone said all hour, and it's the one thing no vendor is incentivized to say.

How much of a CRM actually gets used

The numbers back up the room. Research compiled across CRM vendors in 2026 found that 43% of businesses with a CRM use fewer than half of its available features, and Salesforce's own data shows only 34% of CRM users take advantage of advanced analytics and reporting. Adoption consultants put average daily active usage benchmarks at 40 to 60%, meaning that on a normal day, something close to half the licenses you're paying for aren't touched.

And then the one that should worry anyone about to start a project: 55% of CRM implementations still fail to meet their objectives, mostly because of data entry friction and poor user adoption. Not because of missing features. Because of friction.

So the gap isn't between companies that have a CRM and companies that don't. 91% of companies with ten or more employees already use one. The gap is between companies where somebody made deliberate decisions about scope, and companies where the platform's defaults made those decisions by accident.

Why "the same system as 300 unicorns" should worry you

You'll hear this as a selling point. It's meant to reassure. Proven at the highest level, therefore right for you.

For most companies it's a warning.

Tooling built for an organization with a dedicated RevOps function assumes a dedicated RevOps function exists to maintain it. Buy it without one and here's what actually happens, and I've walked into this exact situation more times than I can count: somebody configures about 60% of it, that person leaves or moves to another priority, and you're left with a system nobody fully understands and nobody wants to touch. Workflows run that no one can explain. Properties multiply. Reports contradict each other.

The tool didn't fail. The size did.

Your CFO's "let's wait" is usually right

When a smaller team asks to buy the serious tier and finance says wait, the standard reading is that finance is being short-sighted. Every vendor and most consultants will tell you exactly that.

I think finance is usually right, and right for a reason they often can't articulate. They've seen a company buy a system sized for an organization it wasn't, run it with no clear owner, and get nothing out of it. That's a real pattern they've correctly matched to. But "this platform is the wrong size for our stage" is a hard sentence to say in a budget meeting, so what comes out is "it's expensive" or "it's too early."

The productive response isn't to overrule them. It's to come back with something right-sized, with a named owner, and with a definition of what it has to do.

How to find your 10%

This isn't complicated, it's just rarely done.

Start from the decisions, not the features. What are the three questions you need answered every week? Where is each deal, who hasn't been followed up with, which channel is producing? Build only what answers those.

Name an owner before you name a tier. If nobody owns the portal, the tier doesn't matter. One person who understands why each thing exists is worth more than any feature set.

Write down why, next to what. The most expensive artifact in an established CRM isn't the license. It's the three years of undocumented decisions inside it. A one-line note on every workflow costs nothing and saves a project later.

Audit what's actually used, on a schedule. Not what's configured. What's used. Anything unused for a quarter is either a training gap or a deletion candidate, and you need to decide which.

Buy the tier your current process needs, not the one your five-year plan needs. You can upgrade. You can't easily un-build.

The other failure mode

I want to be fair here, because right-sizing gets misused as an excuse to under-invest.

The opposite mistake is real. Companies run for years on a system that genuinely can't support them, everyone knows it, and nobody wants to own the migration. That costs more than over-buying, because the loss is invisible. It shows up as deals that quietly don't happen.

So the principle isn't "buy less." It's "buy deliberately." Those aren't the same thing, and honestly the second one is harder, because it requires you to know what your process is before you shop for something to run it on.

Questions we get asked about this

How much of a CRM does a typical company actually use?
Less than half. Industry research from 2026 found 43% of companies with a CRM use fewer than half its available features, and only about a third use advanced reporting. Average daily active usage across organizations sits around 40 to 60%.

Is it bad to buy an enterprise CRM tier as a small team?
Not automatically, but it's a risk. Enterprise tooling assumes someone maintains it. Without a named owner, the usual outcome is a partially configured system nobody understands. Buy the tier your current process needs and upgrade when the process outgrows it.

Why do CRM implementations fail?
Rarely because of missing features. 2026 research puts the failure-to-meet-objectives rate at 55%, driven mainly by data entry friction and poor user adoption. In practice that means scope was never decided, nobody owned it, and the team went back to spreadsheets.

What's the first thing to do with an over-configured CRM?
Audit usage, not configuration. List what exists, mark what's actually been touched in the last quarter, and find out who owns each thing. Most companies discover a meaningful share of their portal has no owner at all.

 

 Curious what's hiding in your HubSpot? 

See what's broken in your HubSpot → We'll send you a full report — no strings, no pitch. Claim your audit. Claim your HubSpot Audit →