What a CRM Actually Is
A CRM, customer relationship management software, is the system a sales team uses to track customers and deals. Reps log their accounts, calls and opportunities into it, and management forecasts off whatever is in there. It is built on one assumption: revenue moves through a funnel. A lead becomes an opportunity, the opportunity moves through stages, and the forecast is a sum of those stages. For a software company that is an accurate picture of how money is made.
In reality, the companies operating in the industries we serve do not sell that way. The customer has been there for decades, the order comes in by phone or email, and most of the day is RFQs, spec questions and quotes that are answered and forgotten by lunch. The order book runs as a system. The account rarely does.
What we've seen specifically is that most of these companies have bought a CRM at some point, and in most cases the record never got filled in. Every time, the reps got blamed. Actually, it was never a discipline problem. The tool was built for a business shaped differently from theirs.
Rich Liu has built the sales organizations behind some of the fastest-growing companies in software, scaling five multi-billion-dollar companies through two IPOs and an acquisition. As Chief Revenue Officer at Navan, the leading business travel and expense platform, he grew the company 25x in three years. Before that he was Vice President of Global Sales at MuleSoft, leading corporate sales through the company's acquisition by Salesforce, the largest CRM company in the world. Rich is direct about it:
"The CRM is the right system for the business it was designed for. Every deal is new, it moves through stages, and the whole company organizes around that pipeline. The companies Emanate works with were never that business. The account is twenty years old and the order comes in by phone."
Why It Was Never Going to Fit
It assumes a foundation that was never built. A CRM only works on top of clean adoption, a linear pipeline and a revenue operations team maintaining it every day. Most of these companies have none of that. The record lives in the transaction systems, the inboxes and the phone calls, where the CRM cannot reach it.
It is built for the wrong work. Meeting prep, deal health, pipeline review. Revenue here runs on RFQ resolution, spec matching, configured quoting and netback, none of which exist in a CRM data model.
It is installed, not deployed. An administrator connects it once and the sellers are expected to use it. Nobody forward-deploys into a distributor or a manufacturer to map twenty years of account history across five systems.
It charges for seats and records. The business model needs every rep in the tool and every deal typed in. On these sales floors the reps are on the phone, which is exactly where they should be.
The newest move from the traditional CRM vendors is to put AI agents on top of the record. It confirms where enterprise software is going, and it changes nothing here. An agent reasoning over the record still needs the record, and for most of these companies the record is the thing that was never built.
Rich has seen this from both sides:
"Every revenue leader learns the same lesson. The CRM is only as good as what your people put into it, and keeping it clean is a cost you have to be able to pay. In software you hire for it. In these industries the only people who could do it are the ones customers actually want on the phone, and nobody should pull them off it to type."
In Practice
A CRM is a system of record. It holds whatever someone entered. Emanate is a system of action. It does the commercial work, and the record is a consequence.
Every action writes the record. Every inquiry answered, quote drafted, follow-up sent and account signal detected lands back in the systems of record automatically, with no one maintaining anything.
It is built for how these companies sell. RFQ resolution, spec matching, configured quoting and netback are the work, so that is what it does.
It is deployed, not installed. Emanate's team sits inside the company and maps the account history across the transaction systems, the inboxes and the people who hold it. That is what adoption actually takes here.
Where there is a CRM, it stops going stale. Emanate connects to it and keeps it current as a byproduct of acting. The reps never have to open it, and the record is right anyway.
It is not tied to one model. Emanate routes across every major model provider, so each task gets the best model for it.
Plugins Versus the Real Work
For the first time, a commercial operation can run as a system of action, not just a system of record. The record no longer depends on a rep typing after the fact. It is created by the work, and it is complete because nobody had to complete it.
What we've seen with companies operating in these industries is that they did not fail to adopt the CRM. The CRM failed to fit them. Where there is one, it should stay current without anyone maintaining it. Where there never was one, the record still has to come from somewhere. A plugin to a system built for someone else does neither. The power is in doing the work.