← All work
MedTechB2B2CEnterprise HealthHIPAARemote Monitoring

Owning a B2C→B2B2C pivot for a neurorehab platform, from strategy to shipped product

Neurofenix, Product Lead, 2021–2025

Neurofenix platform, patient app and clinician dashboard
+50%
Activation lift
31M+
Reps tracked
680K+
Sessions
5.5 days/wk
Patient adherence

What I owned: end-to-end product across three surfaces

I operated as the product lead across the Patient app (full rebuild), the Clinician Dashboard (net new), and the Partner Dashboard (net new). No PM existed before me, I defined the strategy, drove discovery, owned the roadmap, and worked directly with engineering and clinical teams to ship.

Strategy & discovery: Stakeholder mapping, user research with patients and clinicians, metrics framework definition, enterprise requirements translation, pilot enablement

Execution: Roadmap ownership, activation experiments, cross-functional alignment, HIPAA compliance decisions, engineering handoff, launch sequencing

Context: no strategy, no traction, clinical stakes

Neurofenix builds connected neurorehabilitation technology, a medical device paired with software that helps stroke and brain injury survivors recover motor function at home. The science was strong. The product wasn't.

When I joined, the company had an early MVP built without a product process, a B2B channel that existed more on paper than in practice, and a user base of elderly stroke survivors who were disengaging at home because the app couldn't support independent use.

The strategic ambition was clear: pivot from B2C to a real B2B2C enterprise model, selling to health systems, insurers, and clinic networks. I was brought in to make that happen, across three products, with no existing product function.

What existed when I joined

The clinician / partner dashboard

Legacy clinician / partner dashboardscreenshot to add
The dashboard they had, dense, generic, and hard to act on

The patient app, on day one

Original patient app, therapy selection screen
Patient app on day one, no product process, no activation thinking
Original patient app, activities screen
Patient app, high drop-off with no data on why

Discovery: three stakeholders, one platform

Patients, stroke and brain injury survivors, many elderly, needed radical simplicity. Every friction point was a dropout risk. The clinical stakes meant there was no room for "good enough."

Clinicians managing 20–40+ patients remotely needed prioritised signal: which patients are falling behind, and who needs an intervention today. Not passive monitoring, a triage tool that surfaces the next action.

Health system administrators drove the 18-month enterprise sales cycle. They needed population-level outcomes, Medicare billing compliance, and ROI evidence to justify procurement.

The key insight that shaped the product direction: these three audiences had fundamentally different definitions of success, and the platform had to serve all three without trading one off against another.

Stakeholder gravity map

Platform 3 surfaces Patient Needs: simplicity ↑ activation & adherence Clinician Needs: signal ↑ caseload efficiency Health System Compliance + ROI 18-month sales cycle Tension: simplicity vs depth Tension: speed vs compliance Three audiences with distinct success metrics, all dependent on a single platform
neurofenix.app/hub
Intro Hub Care group
Live prototype One connected product across three surfaces. Intro is the pre-auth entry for practice leads, no registration, no ePHI, the first touch is a lightweight patient screen. Hub is the practice lead workspace: Bifurcator screening flow, Updates and Insights, and the full patient list hooked to the same data model as the clinician dashboard. Care group is the program drill-down (Stroke Recovery): patient pipeline, clinical outcomes funnel, clinician roster, and a 16 week adherence trend scoped to one program.

The Hub view sits above the clinician dashboard: same data model, different audience. Administrators see program-level performance, remote therapeutic monitoring (RTM) billing readiness, and care-group economics without dropping into individual patient data. Clinicians stay in the Overview / Patient Monitoring flow. Each role gets the view that matches their decision.

Clinician dashboard: built for triage, not monitoring

The clinician dashboard was a net-new product. The core insight from discovery: clinicians don't want to monitor all patients equally, they want to know who needs attention today. I defined the product around that question.

The primary view is a caseload sorted into four adherence tiers (Exceeded, Good, Slightly Below, Low), with one-click drill-down into session data, a 16-week adherence pattern, and a movement breakdown. HIPAA constraints (role-based access, audit logging, monitoring log) were in the spec from day one, not retrofitted. The monitoring log does double duty: it powers the North Star Metric (48h intervention rate on at-risk patients) and generates Medicare RTM billing evidence from the same data pipeline.

The two screens below are live. Scroll them, open dropdowns, toggle the sessions chart between Reps and By Body Part. They run on the same tokenised design system shipped to pilot.

neurofenix.app/patients/millerstein-mia
Open full prototype
Live prototypePatient detail: alert banner, monitoring log (auditable clinician activity, also the RTM billing signal), KPI cards, active ADL tasks, week-by-week adherence, and a sessions chart with a Reps / By Body Part toggle.
neurofenix.app/overview
Open full prototype
Live prototypeCaseload overview: four adherence tiers (Exceeded, Good, Slightly Below, Low), sparklines, patient columns with alert badges, and a 16-week stacked trend. Scroll, hover, click patients to drill into monitoring.

Enabling the business: enterprise needs into roadmap decisions

I worked directly with the commercial team to understand what health system buyers actually needed to sign, and translated those requirements into product priorities. This included HIPAA-compliant remote monitoring, EHR integration points, and a metrics framework that gave buyers evidence of clinical ROI, not just usage stats.

Enabling the first enterprise pilot: I helped secure the company's first health system pilot by building the live demo, running stakeholder sessions with clinicians, and reprioritising the near-term roadmap around the objections we heard in sales cycles.

Metrics framework: I defined measurement across all three stakeholder groups, patient activation and adherence, clinical caseload efficiency, and partner-level outcomes, so the commercial team had data to put in front of procurement.

Patient app: phased rebuild, prioritised for activation

I sequenced the rebuild across 2–3 major releases, deliberately phased to avoid disrupting patients who had established therapy routines. The activation problem was the first priority, if patients couldn't onboard independently at home, nothing else mattered.

Accessible-first, not accessible-after: I set the principle that every product decision had to work for the most impaired user first. Oversized touch targets, simplified navigation, no time-sensitive interactions. This wasn't just a user experience call, it was a clinical safety call.

Redesigned therapy activities screen, large cards, accessible navigation

Onboarding as product strategy: Before the rebuild, there was no structured first-run experience. I defined a step-by-step flow, one action per screen, video walkthroughs for each app section, and visual confirmation at every stage. Result: a +50% activation lift.

Redesigned onboarding, step-by-step video walkthrough
Onboarding redesign: step-by-step video walkthroughs for each app section

Device calibration was a known drop-off point, a dry technical step that patients abandoned. I reframed it as a guided, encouraging sequence, turning setup into a confidence-building moment before the first session.

Calibration, left and right
Calibrating left & right movement
Calibration, grasp and grip
Calibrating grasp / grip
Calibration, shoulder
Calibrating shoulder movement

Retention mechanics: gamification with clinical intent

I defined a gamification system, streaks, challenges, progress tracking, a social leaderboard, built around one insight: stroke survivors don't want cartoon rewards, they want evidence they're improving. Every mechanic was co-validated with clinicians and patients before shipping.

Gamification, streaks, progress tracking, movement breakdown

The retention system sustained 5.5-day/week adherence, top quartile for digital therapeutics. Across the platform's lifetime, it drove 31M+ repetitions across 680K+ sessions.

Streak notification
Streak notifications, tied to clinically-meaningful frequency targets
Hearts explanation
Hearts system, earned through daily practice

The weekly leaderboard added a social layer without making recovery feel competitive. Patients could celebrate each other's milestones, a feature clinicians flagged in research as something they'd never seen in any rehab tool before.

Weekly leaderboard with patient rankings and clap feature
Weekly leaderboard: peer motivation with a clinically-safe, supportive tone
Results and stats view
Progress tracking: evidence of improvement visible to patients and clinicians alike

Outcomes: what it delivered

+50%
Activation lift, driven by a structured onboarding strategy and a phased rollout approach
31M+ reps
Across 680K+ sessions, retention mechanics that worked clinically and behaviourally
5.5 days/wk
Patient adherence, top quartile for digital therapeutics globally
B2C → B2B2C
Full platform pivot delivered: patient app, clinician dashboard, enterprise pilot secured

What I'd do differently: if I ran it again

I'd push for earlier analytics instrumentation on the clinician dashboard. We had strong behavioural data on patients but limited visibility into how clinicians actually used their tools, which made iteration slower than it needed to be.

I'd also establish quantitative accessibility benchmarks from the start. Qualitative sessions were invaluable, but task-completion metrics across impairment levels would have given us a sharper baseline for measuring progress.

Next case study
Opensignal Meteor, From concept to 5M downloads