What to Look For in a Field Sales App for Medical Device Reps
September 9, 2026
If you are looking for something to help you hold a territory together, you have probably already found the feature grids. Voice capture, AI summaries, pipeline visibility, integrations. Every tool has all of it, which is another way of saying the grid tells you nothing.
The grid is not what decides this. What decides it is whether the tool survives a Tuesday: three hospitals, a case that runs long, a text from a surgeon you meant to reply to four hours ago, and forty minutes of driving between all of it. Most tools are designed for someone at a desk who has decided to spend twenty minutes maintaining their system. That person is not you.
Here are seven questions that actually predict how a tool will go. The last section says plainly where Continuo, which we make, answers them badly, because a guide where every criterion happens to favour the author is not a guide.
1. How long does one capture take, one-handed, in a parking lot?
Not “does it have voice capture.” Time it. Open the app, get a thought out of your head and into the system, and put the phone down. Anything over about thirty seconds will not survive a real week, because the moment you have to capture something is never a moment when you have thirty spare seconds.
Test it like this: walk out of a meeting and try to log what happened before you start the car. If you find yourself picking a category from a dropdown, or filling a required field, or choosing which account it belongs to before you can type, you have your answer. Required fields are where good intentions go to die.
A bad sign: the demo shows capture happening at a desk, in a browser, with two hands.
2. What happens to your account history when you change companies?
Reps move. It is one of the most normal things about this job, and almost no tool in this category will talk to you about it.
If the tool is deployed by your company, everything you have learned about your accounts stays behind when you leave, which is correct and appropriate and also means the tool is not really yours. If the tool is yours personally, the relationships you have built travel with you, but you now have a genuine responsibility to think about what belongs to your employer and what belongs to you.
Neither answer is wrong. But you should know which one you are choosing before you put two years of relationship history into something.
Ask directly: who owns this data, can I export all of it, and what format does it come out in?
3. Does it replace your CRM, or sit beside it?
You do not get to stop using Salesforce. Whatever your company mandates, you are still going to be logging into it, and any tool that requires you to abandon it is describing a world you do not live in.
The useful question is what the tool does about that reality. Does it pretend the CRM does not exist and quietly become a second place to keep things, which is just a new inbox? Does it read from your CRM so you are not typing the same account names twice? Does it write back, so your manager still sees what they need to see without you doing double entry?
Write-back is the expensive one, and most tools this size do not have it. Find out before you assume.
4. Does it hold relationships, or just tasks?
This is the difference that matters most and shows up least on a feature grid.
A task tool knows you owe someone something. A relationship tool knows who they are, what you last talked about, what they care about, where the referral pathway stands, and what changed since the visit before. When you walk into an account you have not seen in six weeks, the task tool gives you a to-do. The relationship tool gives you the last conversation.
Test it like this: put in three real accounts, use it for two weeks, then open the account you have thought about least. Does it tell you where you stand, or does it just show you an overdue reminder?
5. What happens after a bad week?
Every tool works when you are diligent. The question is what happens after the week where you did not touch it: the case that went sideways, the quarter close, the week you were sick.
Some tools punish you. You come back to ninety-four notifications and a wall of red, and the honest reaction is to close it and never open it again. That is not a discipline failure on your part, it is a design failure.
Test it like this: deliberately ignore the tool for five days during your trial. Then open it. If your first feeling is dread, that tool is going to lose to your notebook within a month.
6. Where is patient information allowed to go?
This is the question that should be first and is usually not asked at all.
Most tools in this category are not healthcare systems. They are general-purpose software that happens to be sold to people who work in hospitals. That distinction matters enormously, because it determines whether patient information is allowed anywhere near it.
Ask three specific things, and be suspicious of vague answers:
- Is this system HIPAA-compliant, and do you hold Business Associate Agreements with your subprocessors? “We take security seriously” is not an answer to this.
- If I connect my work email, what happens to patient names that appear in it? Are they redacted before processing, and where exactly does that happen?
- What is your stated policy on me putting patient identifiers in? “Prohibited” is a much better answer than silence, because silence means nobody has thought about it.
A vendor that tells you plainly what you are not allowed to put in their system is being more careful with you than one that implies everything is fine.
7. Does it work where you actually work?
Hospital basements. Shielded rooms. The loading dock. Signal in the places you spend your day ranges from bad to nonexistent, and a tool that needs a connection to accept a thought is a tool that fails exactly when you need it.
Test it like this: put your phone in airplane mode, try to capture something, then turn the connection back on and see whether it arrived. Do this during the trial, not after.
Where Continuo fits, and where it does not
We make Continuo, so treat this section accordingly. Here is what it is genuinely built for and what it is genuinely not.
It is built for question 4. Continuo exists because account history lives in people’s heads and falls out. Every conversation, promise, email and meeting stays attached to the account and the person it belongs to, so walking in after six weeks does not start with reconstruction. That is the whole thesis, and if that is not your problem, you do not need us.
On question 6, our position is on the record. Continuo is not a system of record for patient data and not a care-delivery system. PHI is prohibited, we are not HIPAA-compliant, and we hold no Business Associate Agreements today. Connected email is passed through redaction that strips patient identifiers before anything is processed. We would rather tell you that plainly than let you assume otherwise. It is all on our security page.
On question 3, partially. Continuo reads from Salesforce. You can connect it and it pulls your accounts and contacts across, so you are not retyping a territory you already have. It does not write back.
That is a limitation and it is also a deliberate line. Your CRM is the record your compensation is calculated from, and we are not willing to write into it automatically on your behalf. Getting that wrong is not a bug you shrug off, it is a corrupted account record in the system your company runs on. So for now, if your manager needs activity logged in the CRM, you are still logging it there yourself. If that double entry is the single thing you are trying to eliminate, be honest with yourself that we do not eliminate it.
On question 7, this is where I would tell you to be actively careful. Recording and typing work with no signal. Saving does not, because the work of pulling a capture apart into accounts, people and follow-ups happens on our side rather than on your phone. So in a dead zone you can talk, and you will need bars before it lands.
What we do not have is an outbox. Captures do not stack up while you are offline and send themselves when signal returns, which means one capture needs to land before you start the next. If your morning involves a stretch with no signal and several accounts in a row, that is a real constraint and you should know it before you lean on us for it. Test it the way question 7 describes, on your own phone, in your own buildings, before you decide.
Two places we simply do not compete:
iOS today, Android planned. There is no Android app right now. It is on the roadmap and it does not have a ship date, and I would rather tell you that than write “coming soon” over it, because you have read enough vendor pages to know what that usually means.
So if you carry an Android phone, this is not a tool you can use yet. What is worth your thirty seconds is telling us you want it and saying you are on Android. How loud that gets is genuinely what decides where it sits in the queue, and right now we are guessing.
No team or manager reporting. There is no rollup, no dashboard for your director, no team deployment. If you are evaluating on behalf of a team, we are not what you are looking for.
That second one is worth a sentence more, because reps and directors read it differently. Continuo is bought by you, holds your account history, and reports to nobody. Nothing you put in it appears on a manager’s screen. For a director trying to get visibility across eight reps, that makes it the wrong tool, and you should buy something built for that. For a rep who has watched a “productivity rollout” turn into a surveillance dashboard, it is the entire point.
On question 2, that same choice again. Continuo is yours and it travels with you when you change companies. The flip side is that it is not company-deployed or company-owned, so if your organisation needs to own the data, this is the wrong shape of tool.
Here is the short version. If questions 4 and 5 are the ones you keep coming back to, that the account history lives in your head and the tools you have tried all collapse after a bad week, that is precisely what Continuo was built for and it is worth your two weeks. If question 3 is what matters most, or you are buying for a team, something else will serve you better and we would rather you knew that now than three weeks in.