When Curative CEO Fred Turner announced his company had walked away from a $600,000 annual Salesforce contract after vibecoding a replacement CRM in two months, it landed as a provocation in go-to-market circles. But strip away the headline, and what you actually have is a sharper version of a conversation revenue teams have been having for years: does your CRM serve your go-to-market (GTM) motion, or have you built your GTM motion around your CRM?

That distinction matters more now than it ever has. AI-assisted development has lowered the cost of building custom tooling, compliance requirements are getting harder to meet with off-the-shelf configurations, and the commercial pressure on software budgets is real. The question is not whether Curative made the right call for every business – it almost certainly did not – but what the decision reveals about how GTM leaders should be evaluating their stack right now.

The Real Cost of a CRM Is Not the License Fee

The $600,000 figure gets the attention, but it is rarely the whole story. The true cost of any CRM platform includes implementation, ongoing administration, integration maintenance, training, and the opportunity cost of workarounds your team builds when the platform does not fit your process. Before a RevOps leader can make a credible build-vs-buy case to the CFO, they need to map all of those costs honestly.

That means auditing what your current platform actually does for your pipeline. Start with the basics: how many of your configured fields are actively used in reporting? How many automations are live versus deprecated? What percentage of your sales team logs activity without prompting? If the answers are unflattering, the problem may not be the platform – it may be that the platform was never properly aligned to your actual sales pipeline in the first place.

Audit active vs configured features – most enterprise CRM instances use less than 40% of available functionality
Map integration dependencies – custom-built tools often underestimate the cost of maintaining data connections
Quantify admin overhead – dedicated CRM admins are a real cost that rarely appears in license comparisons
Assess compliance exposure – especially for SMS and outbound communications, where gaps carry regulatory risk

SMS Compliance Is Becoming a GTM Risk, Not Just an IT Problem

TrueDialog’s launch this week of TrueConnect and TrueOptOut is a useful illustration of where CRM gaps create downstream GTM problems. TrueConnect surfaces every SMS conversation on every connected CRM record, while TrueOptOut uses AI-powered intent detection to catch opt-out requests that keyword matching alone misses. The second product exists precisely because standard CRM configurations are not reliably catching non-standard opt-out language – and that is a compliance liability, not a minor UX inconvenience.

For revenue teams building outbound sequences that include SMS, this is a sales cycle risk. A single compliance failure that results in a suppression list breach can damage sender reputation and reduce deliverability across the entire channel. GTM leaders need to treat SMS compliance infrastructure with the same rigour they apply to email cadence governance – and they need to confirm that their CRM either handles it natively or connects to a tool that does.

The broader point is that modern GTM execution involves a lot more than contact records and deal stages. When you evaluate your stack, the question is whether your CRM is the system of record for all revenue-relevant interactions, or just the ones that happen to be easy to log.

Vertical CRM and the ICP Alignment Test

The Leap CRM integration with RoofScope – which connects aerial measurement data directly into roofing contractor workflows – is a quieter but equally instructive story. Leap is not competing with Salesforce on breadth. It is competing on fit: the idea that a CRM built around the specific job-to-be-done of a roofing contractor will outperform a generic platform configured to approximate that workflow.

This is the same logic that drives the build-vs-buy conversation, applied at the vendor level. Vertical CRM platforms win when the Ideal Customer Profile (ICP) has highly specific workflow requirements that horizontal platforms cannot accommodate without significant customisation. The Leap-RoofScope integration – pulling measurement data directly into estimates, documentation, and job execution – eliminates manual data re-entry and reduces the gap between field data and CRM record. That is a genuine productivity gain, not a feature comparison point.

For GTM leaders evaluating platforms, the lesson is to apply an ICP lens to the evaluation itself. The right question is not “which CRM has the most features?” but “which CRM most closely matches how our revenue team actually works?” You can explore options across the CRM Tools Directory to compare platforms by use case rather than by brand recognition alone.

What GTM Leaders Should Actually Do with This

The Curative story will inspire some teams and mislead others. Vibecoding a CRM is not a strategy – it is an outcome that happened to work for a specific company at a specific stage with specific technical resources available. For most revenue organisations, the smarter path is a structured stack review rather than a rebuild.

Here is a practical framework for that review:

Start with outcomes, not features – define what your CRM needs to produce in terms of sales forecast accuracy, pipeline visibility, and rep adoption before evaluating any platform
Map your compliance surface – identify every channel where your CRM is the system of record and confirm that opt-out, consent, and logging requirements are actually met
Quantify total cost of ownership – license fees, admin time, integration costs, and the cost of workarounds all belong in the same model
Pilot before you port – if a vertical or lightweight alternative looks compelling, run a parallel pilot on a defined segment before migrating pipeline data
Measure churn rate on CRM adoption – if reps are abandoning the tool between training cycles, that is a signal worth taking seriously

Wall Street analysts have maintained coverage on Salesforce this week with no significant rating changes, which reflects the reality that enterprise CRM incumbents remain deeply embedded in large organisations. The Curative story does not change that calculus for most businesses. What it does is raise the legitimate question of whether every organisation is getting value proportional to what they are paying.

The GTM teams that will make the best decisions here are the ones that approach the build-vs-buy question as a disciplined operational exercise rather than a reaction to a headline. For more frameworks on structuring these decisions, the CRM Guides section covers stack evaluation in depth. And if you want to track how this conversation develops across the industry, the CRM Daily Newsletter covers it weekly.

Build vs Buy: What Curative’s CRM Move Tells GTM Teams

CRM Daily Digest

Get this kind of intelligence every morning.