When Tricia Sterling, Executive Director of Patient Experience, described her first CRM implementation in one word, she didn’t hesitate: “a headache.” Her most recent one? “Collaborative” and “enjoyable.” The difference wasn’t luck. It came down to a specific set of lessons learned the hard way.
In a recent webinar, Tricia sat down with Karishma Desai, Associate Director of Data Strategy at Claritas Rx, to count down the 10 things every team should know before implementing a patient services CRM. As Tricia put it, most teams assume a CRM rollout is a technology project. In reality, success here comes down to people, not just the technology. Here’s the full countdown.
10. Your CRM Is Only as Powerful as the Data Behind It
Data readiness is the foundation everything else sits on. Without clean, normalized data, a CRM is just an expensive place to store bad information: think inconsistent data feed formats, patient IDs that don’t match across partners, and gaps in payer and provider data.
The worst time to discover this? After go-live, when fields that were supposed to populate arrive empty, duplicate patients show up across hub and pharmacy feeds, and patient IDs can’t be reconciled.
Before you sign a contract: review the vendor’s data specs against your actual sample data, and ask whether they’ve already worked with your specific hub and specialty pharmacy partners. If they know your data partners’ formatting nuances going in, it will save enormous amounts of time later.
9. Evaluate for Your Workflows, Not the Demo
A striking stat discussed at the session: 73% of CRM demos never show exception handling. Vendors demo the happy path: clean intake, every field populated, everything flowing smoothly. Real referrals show up with missing data, and your team has to work around it on day one.
The fix: bring your messiest, most edge-case scenarios to the vendor and ask them to show you how the system handles those, not just the “happy path” version.
Just as important: get the right people in the room during vendor demos. Too often it’s just IT and leadership. Bring in frontline case managers and field teams who’ll actually live in the system daily, plus your data team, who tend to ask the questions a demo can’t dodge. Involving end users early also builds the buy-in that carries a program through implementation.
8. Configuration vs. Customization Is a Budget Decision in Disguise
Every customization adds cost to every future upgrade. The rule of thumb: configure first, and reserve customization for genuine regulatory requirements or true program differentiators.
Where to draw the line: ask whether a field will actually be used, and whether it can be reported on. If the answer to either is no, configure around it instead of customizing.
A common regret example: too many overly granular patient statuses (a program with dozens of discontinuation reasons, for instance) make reporting a nightmare. Fewer, well-defined statuses with clear rollup categories lead to much better reporting.
7. Integrations Are the Project, Not a Line Item
The CRM is just one node in a larger data ecosystem, including EHR, hub data, specialty pharmacy data, telephony, benefits verification/prior auth, and more. Integration scoping should happen before vendor selection, not after.
The most underestimated piece is field mapping: how long it takes to map fields from one system to another, plus the sheer number of data feeds involved, each with its own source, timing, and file transfer setup. These unglamorous details are what delay a launch.
Ask vendors directly: Have they run implementations with your specific specialty pharmacy and hub partners before? Have they already solved the problems you’re likely to hit? Starting this conversation too late is a reliable way to blow both your timeline and your budget.
6. Consent Management, Built In, With Every Case in View
Unconsented referrals are going to happen. It’s simply how the process works. If a CRM can’t handle unconsented patients, those cases sit invisible and stall progress, and discovering that mid-program is too late to fix.
The system should be able to de-identify unconsented patients so teams retain compliant visibility and can still support them while consent is pending. Once consent is on file, appropriate role-based team members should get full access to PHI and the complete patient journey. A CRM needs to handle both sides well, giving visibility for consented and unconsented cases alike, so no patient falls through the cracks while paperwork catches up.
5. Compliance Should Be Built In, Not Bolted On
Retrofitting compliance later is far more expensive and difficult than building it in from the start. Compliance gaps most often hide in access control: who can see PHI, and which roles shouldn’t. When those gaps go undetected, root-cause investigations during a review become slow and unreliable if activity history is missing.
A good question to ask any vendor: What guardrails do you have in place, and can you show me an activity log during evaluation? Ask about SOC 2 and HIPAA certifications specifically. A vendor confident in their compliance posture will walk you through it without hesitation; one that hedges is a signal worth noting.
4. Reporting Requirements Should Drive System Design, Not Follow It
You can’t report on data the CRM was never built to capture. Define your KPIs before the build starts, and work backward from there.
A real example from experience: leadership wanted a “time to first fill” report, but the system hadn’t captured a reportable date/timestamp field for it, a gap that only surfaced months in. The lesson: every field needs both a date and a timestamp, and just because data is entered somewhere in the system doesn’t mean it’s reportable.
Non-negotiable KPIs from day one: time to first fill, persistence, and refill/fill rate. These are the metrics that show whether patients are starting and staying on therapy. Consent and enrollment capture should be close behind. Beyond defining these upfront, get vendors to commit contractually and ask to see sample report visuals before you sign.
3. Change Management Eats Your CRM for Breakfast
Even the best CRM fails if patient services teams don’t trust or adopt it. What actually drives adoption: involving teams in the implementation from the start so they help shape the system, making the tool intuitive enough to genuinely simplify their day, and giving them visibility into the full patient journey so they can spot bottlenecks themselves.
Watch for quiet non-adoption before it shows up in metrics. Login counts aren’t enough. Look for “shadow spreadsheets,” where teams keep working outside the system, as a clear early warning sign that adoption hasn’t really taken hold.
2. Implementation Is a Relationship, Not a Transaction
You’re choosing a partner for years, not just a go-live date. What separates a true partner from a signed contract is the day-to-day team: direct, accessible contacts you’re comfortable calling when something breaks, not a ticket in a queue.
Here are some red flags: a vendor who claims they can do everything (over-promising or a costly custom build in disguise), or one who’s vague about who’s actually on the implementation team before you sign.
Here are some green flags: a sales process that brings the real implementation and client-facing team to the table pre-signature, references who are actually willing to talk, and a documented escalation path with real turnaround times.
1. Design Around the Patient Journey, Not the System
The number one item, and as promised, not what most teams expect to hear first, is this: the CRM should mirror how the patient journey actually happens, from prescription and enrollment to benefits verification, starting therapy, and staying on therapy, rather than reshaping that journey to fit the software.
Every other item on this list, from data and integrations to KPIs, consent, and compliance, depends on first mapping what the patient journey actually looks like at each stage, then defining what information the CRM must capture at every step. Get this right, and the other nine become dramatically easier.
The Bottom Line
Implementation doesn’t end at go-live. It starts well before and continues well after. As Tricia put it, if a vendor treats go-live as the finish line, “you’ve signed a contract, you haven’t picked a partner.”
Want to talk through your own CRM strategy? Book a 20-minute consult with our team.
Prefer to hear this discussion in full? Watch the on-demand webinar for the complete conversation.Request a demo to see how the platform can support your brand’s market access goals.
