We hear it more and more.
We reach out to a MedTech company, or we walk a prospect through Nuvue as a content system with a CRM built into it, and the answer comes back: "Oh, don't worry. We're building our own CRM with AI."
One of our own clients said it. We told them we were adding CRM functionality, and they said they had it handled. They were building their own.
And here's the thing. They're probably right that they can.
The Build Was Never the Hard Part
AI has made building a CRM genuinely easy. A contact table, a deal pipeline, a few dashboards. A capable person can stand that up in a weekend now. That's real, and pretending otherwise would be silly.
But building the CRM was never the thing standing between a MedTech company and knowing what its sales team is doing.
The thing standing in the way is a rep opening it on a Tuesday.
Your Reps Struggle With Every CRM
Not your CRM. Every CRM.
We've watched it across a lot of MedTech sales teams, and it's remarkably consistent. Companies buy Salesforce. Reps don't use it. So they switch to HubSpot, or Zoho, or something newer. Reps don't use that either. Somewhere in the shuffle a project management tool gets added, and now there are three systems nobody logs into.
The reasons aren't mysterious. A lot of these platforms are simply too technical for a sales rep who isn't tech-forward. They log in, they don't know what they're looking at, and they leave. Others are set in their ways, and honestly, why wouldn't they be? They have a list of accounts on their laptop and a way of working that has closed deals for fifteen years. A new system asks them to do more typing so that someone else can look at a chart.
We'll say the uncomfortable part out loud, because it applies to us too. We've had onboarding friction with Nuvue. Getting a rep to change how they work is hard no matter what you've built or bought. Anyone who tells you their software solves that with a login screen is selling you something.
So when a company says "we're going to build our own with AI," the honest question is: what exactly are you fixing?
You will have changed the vendor. You will not have changed the reason nobody opened the last one.
What Actually Changes It
Reps go where their work already lives.
That's the entire insight, and it took us years of watching to see it. If you want a rep inside a system every day, the system has to hold something they cannot do their job without. Not something their manager needs. Something they need.
In MedTech, that thing is the sales content.
Reps need the current presentation. They need the one-sheet, the clinical data, the case study, the thing they can send to a physician between cases. That content is not optional and there is no workaround for it. A rep who ignores three other platforms will open the one that has the deck they need in ten minutes.
So the question was never "how do we get reps to use a CRM." It was "where does a CRM have to live for reps to actually use it."
The answer is: on top of the content.
We Didn't Set Out to Build a CRM
This is the part we didn't plan.
For years, the single most common request we got in training sessions and demos was the same one. A rep would look at a presentation in the system and ask: can I email this right from here?
Simple question. But to do that properly, you need contacts. And once you have contacts, you need to know who you sent what to. And once you know that, you're one step from tracking whether they opened it, and one more step from attaching it to a deal.
The only real way to answer that question was to build a CRM.
So we did. Not because the market needed another CRM. Because the reps in our system kept reaching for one that wasn't there.
That's the difference, and it's not a small one. Most CRMs are designed backward from what leadership wants to see on a dashboard, then handed to reps who are asked to feed it. Ours got pulled forward out of what reps were already trying to do. The pipeline data fills in because sending content is the job, and the sending happens inside the system.
Nobody had to be convinced to go somewhere new.
The Analytics Nobody Else Has
Once the content and the pipeline live in the same place, something opens up that a standalone CRM structurally cannot give you.
You can see which presentation a rep actually sent. Whether the physician opened it. What they spent time on. And then you can put that next to the deal and ask the question every MedTech leader actually wants answered: what content is winning, and what's being ignored?
This is where the AI-built CRM argument really breaks down. The newest tools are getting good at capturing emails and calls automatically so reps never have to type anything. Fine. That's a real improvement on data entry.
But it still can't see what your rep put in front of a physician.
In a sales cycle that runs a year and turns on clinical evidence, that content is most of the sale. Build your own CRM with AI and you'll reproduce the same blind spot faster and cheaper than Salesforce did. You'll have a beautiful record of activity and no idea what was actually presented.
When Building Your Own Makes Sense
Sometimes it does, and we'd rather say so than pretend otherwise.
If you have a handful of reps, a simple pipeline, and someone in-house who genuinely enjoys maintaining internal tools, build it. You'll get exactly what you want and you'll spend very little.
What gets underestimated is year two. Someone has to own it when the person who built it moves on. Someone has to handle security, access control, and the compliance questions that come with holding customer data in a regulated industry. Someone has to keep it working when your team doubles and the requirements change. That's not a weekend. That's a job nobody was hired to do.
And none of that effort solves adoption. You'll have built, at real ongoing cost, a system with the exact same empty-login problem as the one you were trying to escape.
The One Thing AI Can't Generate
You can build the database. You can build the pipeline view, the dashboards, the automations. AI will help you do all of it faster than anyone expected.
What you cannot build in a weekend is a reason for a rep to open it.
That reason has to already be there. For MedTech, it's the content your team needs to sell, sitting in one system, current and ready to send. Put the CRM around that, and adoption isn't a change management project. It's a side effect.
Want to see what a CRM looks like when it lives where your reps already work? Book a demo.