The Gap Between Your ERP and Your Group Chat
Most surgical sales operations run on two systems.
One is the ERP. NetSuite, SAP, Dynamics, QAD — pick your flavor. It tracks what got purchased, what got invoiced, what’s on the books, and what got written off. It is the financial truth.
The other is the group chat. Or the spreadsheet. Or the notes app. Or the dispatcher’s whiteboard. Or the regional manager’s inbox. It tracks who’s covering tomorrow’s case, where the loaner kit actually is, what the surgeon switched to last Tuesday, and which rep is on vacation next week. It is the field truth.
Both are real systems. Neither is wrong. They just don’t connect to each other — and the most important work in your business happens in the gap between them.
This isn’t a discipline problem. It’s a missing layer. And until you’ve named it, you can’t fix it.
What actually lives in the gap
I’ve worked both ends of this gap. As a full-line ortho rep, I had answers about the field the home office couldn’t see — and the home office had answers about the books I couldn’t see. Neither side was hiding anything. The information was just spread across systems that didn’t talk, and bridging them fell to whoever asked first.
If you sat down and wrote out everything the ERP doesn’t know, the list would be longer than you’d guess.
- Which rep is covering Thursday’s hip revision at 7am.
- Whether the right kit is actually in SPD or still in transit.
- That the surgeon updated her preference card last month and the new version isn’t in the binder.
- That the loaner from last week’s case never made it back to the warehouse — it’s in someone’s trunk.
- That tomorrow’s add-on at the surgery center has no rep assigned because two of them thought the other one had it.
- That the kit count at one of your hospitals is off by one because the last cycle count missed an expired tray someone pulled.
None of that is on the books. None of it is wrong, exactly — it’s just not anywhere a system can see it. It’s in a text thread. A notes app. A memory.
The ERP knows what got billed. The group chat knows what happened. Reconciling the two is a job no one was hired to do — but somebody on your ops team is doing it, every day, full time, at the cost of every other thing they could be doing.
Why your team doesn’t have a CRM in the middle (and doesn’t need one)
Here’s something the broader software industry doesn’t say out loud: most mid-market device companies don’t run a real CRM.
Some have a spreadsheet they call a CRM. Some have a Salesforce instance they bought, configured, and quietly abandoned. Some have nothing — because the last time they tried to roll out a CRM, the reps refused to use it and the data became unreliable inside a quarter.
That isn’t a failure of leadership. It’s a CRM problem.
CRMs were built for opportunity pipelines — businesses where the unit of work is a deal that closes once. Surgical sales doesn’t work that way. The unit of work is a case, and a single surgeon will run hundreds of them over the years you own the relationship. There’s nothing to “close.” There’s only the next case.
A CRM doesn’t model that. Not because Salesforce is bad — but because Salesforce was built for the wrong shape of business. So reps reject it, ops reject it, and the spreadsheet wins by default.
The takeaway: you don’t need a CRM in the middle. You need a system that fits the actual shape of the work — case, kit, rep, surgeon — and connects to the financial system you already have.
That’s the gap.
What “filling the gap” actually means
The work that lives in the gap splits cleanly into three things:
Case coordination. A surgical calendar that knows the surgeon, the procedure, the OR, the assigned rep, the required kits, and the preference card snapshot at the time of the case. That moves a case through a real lifecycle — scheduled, confirmed, in progress, completed — instead of a chain of texts.
Inventory and chain of custody. Real-time location and status of every kit, tray, and consigned implant. Not a quarterly snapshot. Not “Tony has it” from a text three weeks ago. Every transfer, check-in, check-out, and use event captured at the moment it happens.
Field execution. The reps and ops actually doing the work. Their territories, their coverage, their communication tied to the case record so nothing important ends up in a thread no one can find six weeks later.
Notice what isn’t on that list: GL accounting, accounts payable, financial close, vendor master maintenance, audit reporting. That’s the ERP’s job. We’re not coming for your ERP — we’re feeding it cleaner data and getting out of its way.
Notice what else isn’t on that list: opportunity pipelines, lead scoring, marketing automation. That’s a CRM’s job, if you have one. If you don’t, you don’t suddenly need one.
What’s in the gap is the gap. Nothing more, nothing less.
What changes when the gap closes
When the ops team stops spending its day reconciling the ERP against the group chat, a few things shift at once.
The ops team stops being a reconciliation engine. They stop chasing kits, manually merging spreadsheets, and updating the same case status in three places. They start doing the work they were actually hired for: making sure tomorrow’s cases run.
Reps stop being unpaid logistics coordinators. The 9pm text marathon goes away. The “is my kit going to be there?” anxiety goes away. They go back to selling — the thing the company hired them to do.
Leadership starts seeing reality, not lagging exports. Territory health, kit utilization, rep performance, case volume — all of it pulled from one record, in real time, instead of stitched together at the end of the month from three different systems and a Slack scroll.
Inventory variance shrinks. Not because anyone’s getting better at cycle counts. Because chain of custody is captured at the moment a kit moves, not reconstructed three months later from memory.
The 4pm crisis call becomes a 4pm app notification. “Kit didn’t arrive at SPD” stops being something you find out when the surgeon is gowning up. It becomes something the system flagged six hours ago, with enough lead time to actually fix.
None of those changes require ripping out your ERP. None of them require buying a CRM you don’t want. They all happen by closing one gap.
The honest pitch
We’re not here to replace your ERP. It’s doing its job — track the dollars, close the books, satisfy the auditor. Keep it.
We’re not here to sell you a CRM. If you have one, fine. If you don’t, you don’t need us to give you one.
We’re here for the layer in the middle — the one your ops team has been holding together with spreadsheets and group texts because nobody built the system that should have lived there. We’re here to fill the gap.
If you’ve spent your career working around it because the tools to close it didn’t exist, you already know what we’re talking about. The gap is real. It has a cost. And it has a fix.
See how Covalt fills the gap.
If your ops team is reconciling an ERP against a group chat — and you’d rather they were doing something else — we’d like to show you Covalt.