Understanding where pharmacies fall off: before, during, and after launch
A service design study mapping the full pharmacy lifecycle with Nimble, from first sales contact to churn, to uncover where friction was costing us partners.
The problem
25% of pharmacies launched in a quarter were churning, resulting in loss of revenue, volume and also time. We needed to understand what really caused the churn from people, process and product.
The outcome
Cross-functional problems surfaced and got acted on: faster bug resolution, clearer communications, and fewer integration churns.
48hbug resolution + SLAs
+20NPS points
Reduce patient inbounds
Less integration churns
Background
Pharmacy churn was a symptom. We needed to find the cause.
NimbleRx grows when pharmacies stay active on the platform and process volume through it. But pharmacies were leaving. Some after a brief unhealthy period on the platform, others before they even launched. The pattern showed up in the data, but the data couldn't explain it.
Of the pharmacies launched in any given quarter, 25% were churning, and it wasn't concentrated at one stage.
Research question
Where in the pharmacy lifecycle, from sales to post-launch, are the friction points that lead to low health scores and churn?
Customer journey
How pharmacies are meant to launch with Nimble
To understand where things broke, you need to know what the journey was supposed to look like.
The ideal pharmacy journey, from first contact to active partner on the platform.
Sales
Qualification & contract
Onboarding
Setup & training
Phase 1
Getting comfortable
Phase 2
Core product
Ramp success
Growth & retention
PMS compatibility confirmed
Clear expectations set
Integration runs smoothly
Staff feel confident and ready
Launches on a simpler product
Staff and patients adjust
A lighter entry point before the full product.
Moves to the core checkout product
Patients guided through change
Phase 2 is the full Checkout product, where real volume and revenue growth begins.
Fill volume grows steadily
Turns on features like refills
Research approach
Following the pharmacy from first contact to outcome
We recruited 12 pharmacies across four segments. Distribution was uneven by design. Reaching pharmacies that churned pre-launch was significantly harder, as they had already disengaged from Nimble entirely.
01
Segment-based recruitment
12 pharmacies across four churn segments — healthy, unhealthy, post-launch churn, and pre-launch churn. Healthy segment included as a control. Distribution was uneven by design: pre-launch churns had already disengaged from Nimble entirely.
02
60-min in-depth interviews
Traced each pharmacy's full journey from sales outreach to their current outcome. Some sessions conducted on-site to observe the pharmacy environment firsthand. Included a mood mapping exercise to capture sentiment across the lifecycle.
03
Journey mapping & blueprinting
Overlaid the four journeys to find where problems clustered and where internal handoffs were breaking.
04
Cross-functional readout
Presented to Sales, Onboarding, Product, and CS. Each team could see the problems they owned.
Key insights
Dozens of issues came up. They grouped into three.
Insight 01
Seamless integration is overpromised pre-onboarding, setting pharmacies up with expectations the product can't meet
·Payment reconciliation required running two systems simultaneously, creating double-payment risks and manual correction workflows.
·Workarounds pharmacies adopted to keep Nimble running ultimately negated the efficiency gains the platform was meant to deliver.
·Sales had overpromised on integration quality. Pharmacies arrived with expectations the current infrastructure couldn't meet.
-We were selling to pharmacy systems we knew had poor integration compatibility, setting up failures before onboarding even began.
191 hrsspent on integration-related inbounds in the last 90 days, the #1 CP inbound topic at 13% of all contacts
“
We could make Nimble work. But we then had to run it still through Pioneer. Seconds matter. We're that busy. It was too burdensome for our staff to make it worth it. — Ryan
Insight 02
Ongoing communication gaps across the lifecycle leave pharmacies feeling unsupported, eroding trust over time
When a pharmacy logs a bug and hears nothing back, they stop filing bugs. Then they stop trusting the platform.
·We're cautious about raising potential issues around integration quality or patient adoption. While that makes for an effective sale, it irks pharmacies further when things go wrong.
·We don't follow up enough on issues raised: bugs, enhancement requests, or roadmap transparency. Pharmacies raised concerns and heard nothing back.
·When issues go unacknowledged, pharmacies feel like they're submitting feedback into a black hole.
·Wins are going unnoticed. There's no mechanism to surface or celebrate them.
“
I had to keep calling and keep calling and be like ‘what's the update on the issue’, he said let me follow up. Everything was let me follow up, let me follow up. — Mark
Insight 03
At the phase transition, poor patient onboarding drives more calls than before, undermining pharmacy confidence in Nimble
·Great service is the number one goal of independent pharmacies. Negative feedback from patients, even a miniscule percentage, has a heavy emotional impact on pharmacy staff.
·Lack of adoption hurts pharmacies' bottom line (already under pressure) and works against realizing their revenue goals with Nimble.
·Bag stuffers are seen as mildly helpful but often arrive too late, are too generic, or there isn't enough time from closed-win to go-live to get them in patients' hands.
8–9%typical patient adoption rate in retail pharmacies, compared to 70+% adoption at specialty pharmacies, a big difference in experience and value
“
If we have these flyers the first month that we launched, it would have been very helpful. We were told it was going to be a smooth transition and it was not.— Craig
“
This is becoming more of a problem than it's helping. Customers are getting frustrated. They got a text saying stuff's ready, but not everything is ready. — Ryan
Pharmacy lifecycle: before
Sales
Onboarding ★
Phase 1
⚡ Phase 2
Settles down
Churn risk
Journey
Pharmacy
Signs agreement
Smooth setup
Great CS support
Building volume
Staff training gaps
Phase 2 data exchange breaks down
Patients confused
Phone calls flood in
Calls die down
Volume recovers slowly
Bugs go unanswered
Revenue model unclear
Churns
Nimble CS
Account handoff
Proactive onboarding
Training & setup
Monitors health score
High inbound calls
No PMS visibility
Volume normalises
Can't triage bugs vs gaps
No triage visibility
Product
No PMS restrictions
Basic integration setup
Tracks Phase 1 metrics
Integration failures
No transition comms
Monitors Phase 2
No triage cadence
Bugs unresolved
Positive moment
Friction point
Churn risk
Standard action
⚡ High friction zone
What we changed
Each insight mapped to a cross-functional decision
Findings were presented to leaders across Sales, Product, Onboarding, and Customer Success. All four changes shipped from the research.
Sales · Integration
Restrict sales to compatible pharmacy systems
Identified which pharmacy systems consistently produced poor integrations
Built that into the sales qualification process
Prevented a known source of early churn before it started
Patient · Adoption
Deploy a patient education phase via text messaging
Introduced a dedicated patient education period triggered at the transitional phase where most confusion occurred. We used Nimble's existing text messaging infrastructure to reach patients before the phase change happened.
Engineering · Integration
Invest in smoother integration infrastructure
Secured investment to build out more robust integrations for the pharmacy systems we do support, cutting down the disruption that was driving early churn.
Product · CS · Communications
Establish SLAs for bugs and enhancement requests
Built out clear service level agreements. Product committed to reviewing and triaging all incoming requests on a defined timeline, and CS developed criteria to distinguish bugs from knowledge gaps, reducing unnecessary escalations and giving pharmacies something they'd never had before: confirmation that their issues were moving.
Service blueprint
The pharmacy lifecycle after changes
How the full pharmacy experience looks with all four changes applied, from sales qualification through to a pharmacy that actually sticks around.
Sales ✓
Onboarding
Phase 1
⚡ Phase 2
Settles down
Adoption grows ↑ (projected)
Journey
Pharmacy
Signs agreement
Smooth setup
Great CS support
Building volume
Improved staff training
Compatible PMS only
Patient SMS education
Fewer integration issues
Calls die down faster
Volume recovers strongly
SLAs for bugs in place
Features turn on
Nimble CS
Account handoff
Restricts bad PMS sales
Proactive onboarding
Training & setup
Monitors health score
SMS education deployed
Reduced inbound volume
Bug vs gap criteria clear
Product
Tracks Phase 1 metrics
Clearer transition comms
Fewer integration failures
Monitors Phase 2
SLA triage cadence live
Bugs actioned on schedule
Positive / improved
Change implemented
Friction point
Churn risk
Unchanged
Iterative
⚡ High friction zone
Impact
Cross-functional problems surfaced, aligned, and acted on
The research didn't just identify friction. It put Sales, CS, Product, and Onboarding in the same room with the same problem. That alignment was the first win.
48h
Bug resolution + SLAs
Down from weeks. Product resolved 200+ cases at pace, eliminating the black hole experience that eroded pharmacy trust.
+20
NPS points
Pharmacy NPS improved by 20+ points following changes to communication cadence and bug resolution timelines.
Patient confusion inbounds
A dedicated education phase reduced patient confusion calls at the transition point. Additional resources were allocated for patient education marketing materials and SMS copy testing to improve clarity.
Integration-related churn
Restricting sales to compatible pharmacy systems removed a known failure mode before it started.
A note on process
These improvements are meaningful, but they're not the last fix. Fixing deep integration infrastructure takes time and continued investment. What this research did was force the order of operations: clearer communication and faster bug resolution first, deeper infrastructure second.