Insights
CRM for pharmaceutical and medical device sales
A pharma rep is not selling to a buyer who has to take the meeting. Access to clinicians is the scarce resource, and keeping it depends on being useful. A CRM's real job here is memory: what this consultant cares about, when you last spoke, and what you said you would send.
Published
What does a rep actually need a CRM to remember?
The specifics that make the next conversation worth having.
Which procedures a surgeon actually performs, which paper they mentioned, which colleague they referred you to, what objection they raised last time and whether it was ever answered. None of that is deal data in the conventional sense, and all of it is what separates a rep who gets ten minutes from one who does not.
How is this different from a normal sales pipeline?
The buying decision is rarely one person and rarely one moment, so a pipeline of deals with close dates fits awkwardly.
What tends to work better is tracking accounts and the people inside them: who influences the decision, who has been engaged, who has not. A hospital where you have a good relationship with one consultant and none with procurement is a specific, visible gap, and that is a more actionable view than a percentage probability on a deal.
Does it need to work in the field?
More than in almost any other sector. The record is made in a corridor, between appointments, on a phone.
If logging a call takes more than a few seconds it will be done in batches from memory at the end of the week, and the detail, which is the whole value, will be gone by then. Test the mobile experience before you buy, with an actual rep, on an actual bad connection.
How do you use it to stay useful to clinicians?
By turning what you learn into something you can retrieve at the right moment.
A note against a contact recording a research interest is worth little on its own. It becomes valuable when a relevant paper appears eighteen months later and you can find every contact it matters to in one search. That is a straightforward use of tags and notes, and it is the difference between a rep who sends things and a rep whose emails get opened.
What about compliance?
Your compliance function should specify what may be recorded before the system is configured, not after it is full.
Interactions with healthcare professionals are governed, and the details vary by market and by what is being sold. A CRM makes the record auditable, which cuts both ways: it is exactly as useful for demonstrating that you did the right thing as it is for demonstrating that you did not. That is an argument for agreeing the fields early.
When is the CRM not the problem?
When access is the problem. If clinicians are not seeing reps, better record keeping about the meetings you are not getting will not change the outcome.
And if territory data, target lists and call plans arrive from three different sources that do not agree, fix that first. A CRM built on contradictory territory data produces confident, wrong reports.