Smoke Shop POS: The Under-30 ID Rule Is Your Opening Line
Smoke shop POS sales start with compliance, not features. Four questions on age checks, product lists, tax rates and shipping to ask before you demo.
A surgical case doesn't fit inside an opportunity stage.
Picture a device rep sitting in a hospital parking garage after a long case. The surgeon mentioned a different implant size for next time. A nurse asked for an in-service. The materials manager wants a pricing answer by Friday. The rep has three open loops, and the CRM offers one field: "Next step."
By Monday, two of the three are gone. That gap is what a medical device CRM exists to close. Most CRMs assume a deal moving left to right, but a device rep's week is shaped by surgeons, hospital committees, procedures, and compliance rules that follow no pipeline.
Below: what the system needs to hold, where it should stay out of the way, and which numbers nobody has published. You'll also get a way to collect your own.
A device purchase rarely hinges on one person. The surgeon may want the product, but hospitals also run value analysis committees to screen new products and control costs, and have for decades.
Here's the catch. Your surgeon champion is one contact among several, and a single "primary contact" field can't hold the rest. The committee ends up in the rep's head, and it leaves when the rep does.
The medical device sales strategy guide covers selling tactics. For a medical device CRM, the narrower question is what the system of record should hold.
Four things separate a device-ready system from a contact database.
A stakeholder map by role. Surgeon, OR staff, value analysis members, materials management, finance. Each gets a role, a stance, and open requests.
The case as a record. Surgeon, hospital, procedure, products used, follow-ups owed. Look back at the garage scene: the implant size, the in-service, and the pricing question each attach to a case or an account, and none attaches to a deal stage. Opportunity stages can sit on top, but the case is the unit of work.
Product identifiers, not nicknames. The FDA requires device labels to carry a unique device identifier, in plain text and machine-readable form. Free text like "the 5.5 screw" can't match it, or anything in the hospital's or your own inventory records. Capture the identifier by scan or entry.
A pre-visit brief. Open issues, last conversation, what the surgeon asked for last time. This field sales intelligence guide lays out what a good brief contains.
Under the Sunshine Act, device manufacturers report payments to covered providers through CMS's Open Payments program, including general, research, and ownership payments. The AdvaMed Code of Ethics adds industry guidance on dealing with health care professionals.
Your compliance team owns the system that reports spend, and the CRM shouldn't pretend to replace it. What it can do is give reps one structured place to note a meal, a training session, or a sample when it happens. Compliance then reconciles from clean inputs instead of rebuilding a quarter from memory. Ask your compliance team which fields they need, and build the form around their answer. This isn't legal advice; your counsel decides what applies to your products and company.
Every buyer eventually asks four questions: how many cases a rep covers per day, how long a call lasts, what a deal is worth, and how long a sale takes.
We looked for sourced benchmarks on all four and found none we trust. The figures that circulate trace back to nothing we could verify, and they vary by device type. An implant rep's week is driven by cases that get scheduled around a surgeon's calendar. A consumables rep's week looks more like office visits. So we left the numbers out rather than hand you something that sounds precise.
Measure your own. For two weeks, have every rep log four things:
Two weeks of that tells you more about your team than any industry average. It also becomes the baseline you test every new tool against.
A rep in a sterile field can't type, and no tool changes that. Logging happens afterward, in the hallway or the car, when details are already fading. The test for any mobile CRM is how little effort it takes to finish a record in that window.
Voice capture helps, and this explainer on voice to CRM shows how it works. One design question matters more in healthcare than anywhere else: what happens when a rep says a patient's name out loud? Leadbeam's voice capture is architected to store no PHI, so patient details mentioned in a voice note are filtered out before anything is saved. Whatever tool you evaluate, ask the vendor to explain in writing what it stores and what it discards.
Adoption is the other half. A system reps avoid is worse than a spreadsheet, which is why field reps skip CRM and what to do about it deserves its own read.
Run these questions in a pilot, not a demo:
For the wider picture of how a field team's CRM fits together, start with the field sales CRM guide. If your reps cover a defined set of hospitals and surgeons, territory management is worth a look too.
Go back to the rep in the parking garage. Which of those three open loops does your system catch today?
You can't answer that from a demo. Run the two-week log first, then judge any medical device CRM against what you measured. When you want to see how voice capture works for a territory team, look at Pulse.
Leadbeam Blog
Discover tips, strategies, and success stories to empower your field sales team and drive results.
