Growth Systems · Framework

The CRM is not the problem. The workflow around it is.

Most CRM problems are workflow problems. A framework for fixing the sales motion before blaming the tool.

John Soriano John Soriano / / 2 min read

I have seen the same conversation play out in startups, consultancies, service firms, and distributed B2B teams.

Pipeline visibility is poor. Follow-ups fall through. Forecasts feel unreliable. Someone says the CRM is not working. Someone else suggests moving to a different one.

Most of the time, the CRM is not the real problem. The workflow around it is.

A new CRM will not fix a team that has not agreed when to create a contact, what counts as a qualified lead, what each deal stage means, or who owns the account after the first call. It just gives the business a cleaner place to repeat the same confusion.

Where the workflow breaks

The gaps that kill CRM adoption usually cluster in three places.

First, the entry point. If it is not clear when something should enter the CRM, people make different decisions. One person logs every inbound form. Another waits until a call is booked. Another keeps early conversations in email until they feel “real.” The CRM becomes incomplete before the pipeline even starts.

Second, the update motion. Logging a deal once is easy. Keeping it current is the hard part. If stages do not match how the team actually sells, or if updating a record takes more effort than the value it returns, people stop doing it. The CRM drifts from reality. Once it drifts, people stop trusting it.

Third, the handoff. SDR to AE, sales to delivery, sales to customer success, account manager to finance: each handoff creates a moment where context can disappear. That is not a software problem. It is a process problem that needs a clear checklist and a shared definition of done.

Fix the motion first

Before recommending a different CRM, I ask teams to document their actual current workflow. Not the official one. The one people really follow.

What triggers a new record? What does each stage mean? What information is required before a handoff? Who owns the next action? Which report does leadership actually use? What data is safe and necessary to store?

Usually, this exercise reveals the real issue. Often the answer is not a new platform. It is a one-page operating agreement that clarifies how the team uses the tool they already have.

Then evaluate the tool

Once the workflow is clear, evaluating the CRM becomes much easier.

Does it support the team’s actual sales motion? Does it make the next action obvious? Does it reduce manual reporting? Does it protect the data that should be protected? Does it integrate cleanly with the tools where leads and customer conversations already happen?

Those are useful questions. But they only become answerable after the business knows what the motion is supposed to be.

Switching tools without fixing the motion is how teams end up doing the same CRM audit again in eighteen months with a different logo on the login screen.


John Soriano, founder of XataTech
John Soriano
Developer · AI Builder · Systems Thinker

I help founders and companies design and implement AI, software, and operational systems that create real business value. Founder of XataTech.

Let's talk

Looking at AI for your business?

Tell me the workflow that quietly costs you the most. I'll help you figure out whether AI actually belongs there — and what it would take to make it stick.