Call Extraction: CDL MedScout Feedback Sync — Roadmap and Rollout Planning

DDX ID: 1015 Date: 2025-11-11 Duration: ~26 minutes Participants: Phil Cranmer (CDL), Kathryn White (MedScout CSM), Skylar Talley (MedScout Product Lead). Call type: Product roadmap planning and pre-rollout pressure testing session. Focused on mapping CDL’s workflow requirements to MedScout’s development cycle. Triage: Moderate. Mostly platform roadmap and configuration logistics. Three distinct fingerprint insights surface: the field rep parking lot use case, the Acuity-to-MedScout UX benchmark, and Phil’s differentiated leadership vs. field views.

Distinct Insights

1. The “parking lot” use case — field reps qualify opportunities from the car

What: Phil: “I’m out in front of hospital X or clinic Y and I’m using the MedScout app, the mobile app. I looked those up and they’re not on my top opportunity list in my territory. They’re number 501 or whatever, number 600 from a volume standpoint, what do we do there?”

So what: CDL field reps are physically traveling and encountering facilities opportunistically — driving past a hospital, getting a tip from a contact, spotting a competitor’s mobile unit. In that moment, the rep needs to qualify the opportunity on the spot: is this facility worth walking into right now? The mobile app is the tool, and the answer needs to come in seconds, not minutes. But the current system only pre-loads data for the top 500 accounts per territory. Account #501 hits a dead end — no procedure volumes, no qualification data. This means every CDL rep has a qualification blind spot for roughly the bottom half of their addressable territory. The “parking lot” use case is structurally different from territory planning (done at a desk) or strategy scanning (done weekly). It’s real-time, location-triggered, and requires zero-click qualification. CDL’s field selling model depends on serendipitous encounters being convertible to qualified meetings.

Speaker credibility: Phil, articulating a use case he’s heard from his field team. High — he’s translating real field behavior. Scope: Both motions — field reps in both PP and HS encounter this. Motion: Both.

2. Acuity’s UX benchmark — volume visible on the map card without any clicks

What: Phil: “In Acuity, our use case that we had before is the dot would be representative of SPECT… But on the right underneath the account name, they had the volume listed. So I could see SPECT 3,000, PET 300, oncology 10,000. So I knew without having to pop a blade out in one view without any clicks what their procedural behavior was.”

So what: AcuityMD displayed procedure volumes directly on map location cards — no hover, no click, no blade. Phil could glance at a map pin and see all four data points (SPECT, cardiac PET, oncology PET, and implicitly cardiac SPECT) in one visual unit. This is the UX standard every CDL rep has internalized. MedScout’s current approach requires clicking a map pin to open a “blade” (side panel), which then shows only the strategy’s primary code, not all four data points. Every click is a step away from Acuity’s zero-click baseline. Phil’s description reveals exactly what “good” looks like for CDL: dot size encodes primary procedure volume, text below the account name lists all four volumes, and the rep’s eyes never leave the map. This is the design target.

Speaker credibility: Phil, describing daily prior experience. Factual. Scope: Both motions — map-based exploration affects all reps. Motion: Both.

3. Leadership and field reps hit different blind spots — the “20% vs 80%” distinction

What: Skylar predicted the cold opportunity problem would be a “20 percent use case versus an 80 percent use case” for field reps. Phil agreed for reps but pushed back for leadership: “It’s Lynette who is looking at a national level… or me for that matter, at a national level, we’re going to be the ones that get tripped up on that.”

So what: Field reps work in small geographies where the top 500 accounts likely cover 80% of their encounters. But Phil and Lynette operate nationally — they need to pull up any account in the country for strategic conversations, board preparation, or executive meetings. A rep in Georgia rarely encounters an account outside their top 500. Phil encounters accounts outside his top 500 constantly because his “territory” is the entire US. The same platform limitation has a 20% impact on reps and an 80% impact on leadership. This creates a prioritization tension: should MedScout optimize for the daily workflow of 6 field reps or the strategic workflow of 2 national leaders? CDL’s answer is both, but the timelines and solutions differ. The insight for CDL’s operating model: national leadership’s data needs are structurally different from field reps, not just broader.

Speaker credibility: Phil (leadership perspective) and Skylar (product assessment). Both high in their domains. Scope: Organizational — describes a structural difference in how different levels use the tool. Motion: Both.

Transcription Notes

• “Catherine” — Kathryn White referred to as “Catherine” by Phil, consistent with other calls.
• Megan / Meaghan DePeter — mentioned as Kathryn’s maternity leave coverage. Kathryn’s due date: December 6. Rollout target: November 20-21. This timing is confirmed in later calls.
• Skylar Talley — MedScout Product Lead. Described six-week sprint cycles with two-week cooldowns. Next delivery target: January 2.
• Rob and Scott — Phil’s org has “Rob handles hospitals, Scott handles private practices” at the regional manager level. Note: in later transcripts Rob Gosling is identified as private practice, not hospital. This may reflect a pre-promotion structure or a transcription/attribution error. By Feb 2026, Rob is leading national PP and Lynette leads hospitals.
• No term bank transcription errors detected in this call note. The MDCN was already well-cleaned.