A HIPAA-compliant healthcare forms platform had grown to serve thousands of medical practices across multiple specialties. Their product handled patient intake — forms, submissions, EHR integrations — for solo practices through to multi-location enterprise accounts. The compliance requirements were non-negotiable: HIPAA BAA, PHI-free analytics, compliant data pipelines.
Before the engagement, the team had evaluated several analytics platforms without a structured framework for making the decision — Amplitude, Mixpanel, and PostHog each had different compliance postures, pricing models, and architectural tradeoffs for a HIPAA use case. Once a platform was selected, the implementation had been done without a formal taxonomy, governance structure, or capture controls. An audit of the live setup caught a developer implementation error: autocapture was firing on high-traffic patient-facing routes — /practice, /submissions, /login — generating thousands of events per day that delivered no analytical value and created avoidable HIPAA compliance exposure. The cost of this single implementation error was material and the trajectory was still climbing.
Alongside the billing crisis, the team lacked a systematic picture of their customers: no validated segmentation, no JTBD framework, no churn prediction model, no automated win-back infrastructure. The product was growing, but growth was not being measured — and customers were leaving without warning.
A multi-track engagement covering analytics architecture, billing remediation, product research, and lifecycle marketing — run in parallel with the product team's development roadmap.
This is not a one-off project. The analytics architecture, churn prevention, and product research tracks are running in parallel, sequenced against the product team's release schedule. New work — event verification, in-product churn prevention, Customer.io win-back, and messaging analytics — is delivered as each phase completes. The depth of context built over a long engagement is part of what makes the work fast and accurate.
Analytics on a healthcare product needs a PHI-free event schema, compliant person identification, and governance on what gets collected. The architecture is built. You are not choosing between compliance and visibility — you have both.
The implementation audit caught an error that was simultaneously driving cost and creating compliance exposure — both resolved in the same remediation. Governance controls, a billing limit, and correct capture scoping mean a similar error cannot silently compound again.
The Customer.io win-back sequence targets trial users who did not convert with an automated, segmented email flow. Suppression logic ensures converted users do not receive it. It is live, it runs without manual intervention, and it is built to expand into V2 without re-architecting the foundation.
10 years building analytics and growth systems for B2B SaaS at $1M–$50M ARR. BSc Behavioural Psychology, MSc Data Science. Healthcare SaaS is uniquely hard because you’re solving compliance and growth at the same time, and they’re not separate problems. The same autocapture that creates HIPAA exposure is often the one generating 89% of your useless event volume. Fix one, fix both.
A six-week engagement covering all six growth layers simultaneously — analytics, compliance, research, competitive intelligence, churn prevention, and market sizing — with full documentation at the close.
A 15-minute call is enough to know whether what we do is relevant to where you are.