Why CRM isn't enough

Every services business I know runs on a CRM. Salesforce, HubSpot, Dynamics, something. And every one of them, at some point, runs into the same wall: the CRM tells you everything about the sale and almost nothing about whether you can keep the promise.

A CRM is a brilliant record of intent. It knows the pipeline, the stage, the close date, the value. What it doesn’t know is the question that actually decides whether a deal makes money: can we deliver what sales just sold?

The question a CRM can’t answer

Picture a deal moving to closed-won. Three hundred seats, German-speaking, live in September. The CRM is delighted. The forecast updates. Somebody rings a bell.

But the CRM has no idea whether recruitmentcan find three hundred German speakers by September. It doesn’t know whether operations can onboard them, or whether the platform integration the service depends on is finished. It doesn’t know whether, at the price sales agreed, finance would ever have signed it off.

The CRM recorded the promise. It has no way of knowing whether the promise is deliverable. And by the time anyone finds out, the deal is closed, the client is expecting a date, and the gap has become someone else’s emergency.

CRM was built for a different kind of business

This isn’t a criticism of the tools. CRMs were designed for businesses that sell a product: you close the deal, the thing ships, the transaction ends. For a business where the product is people delivering a service over months or years, the sale isn’t the finish line. It’s the starting gun.

In a people business the questions that matter all live after closed-won. Can we hire for it? Can we deliver it to the standard we promised? Are we actually making money doing it? A CRM was never built to answer those, because they belong to Hiring, Operations and Finance, three systems that, in most companies, have never once spoken to each other.

The gap between sold and delivered

This is where the money leaks. Salescommits to something in the CRM. Delivery inherits it weeks later. Nobody connected the sale to the capacity to deliver it, so the mismatch only surfaces once it’s already real: the role that can’t be filled on time, the margin that was never achievable, the service level written for a team that doesn’t exist yet.

I’ve written before about where the margin actually goes. A lot of it goes here, in the space between what the CRM recorded and what the business could actually do.

What “enough” would look like

A CRM isn’t wrong. It’s just not enough on its own. Enough would mean that the moment a deal is about to close, the same view that holds the sale can also tell you whether hiring can staff it, whether operations can deliver it, and whether finance would call it profitable, before the promise is made, not after.

That isn’t a better CRM. It’s a different idea: connecting the sale to the reality of delivering it, so “can we actually do this?” gets asked while the answer still matters. The CRM will always be where the deal starts. The question is whether anything in your business is set up to answer what happens next.