Case Study — Healthcare Forms Platform (FormDR)

Onboarding architecture review uncovered 7 critical gaps. 40+ events specified. 3 churn archetype flows built.

A healthcare forms platform was redesigning its onboarding for a new pricing model. The proposed architecture had timing mismatches, missing persona routing, and a cancellation system that found out about churn after the fact.

Stack PostHog Chameleon Stripe
7
Critical gaps found in proposed onboarding architecture
40+
Events specified across 8 categories for state-machine onboarding
3
Churn archetype flows with segment-based winback offers
40–50%
Target cancellation save rate across all 3 archetypes

Before.

"We’re redesigning onboarding for the new pricing model. We think it’s ready to build." The product team had 40+ strategy documents, a full email copy library, and a guided tour strategy. But when we reviewed the architecture against 60 recorded sales calls and existing analytics data, critical gaps emerged.

What they didn’t know: the 10DLC SMS approval process introduced a 7–14 day delay that would complete after the onboarding email sequence had already finished. Invited users had no post-tour nurture. The V1 progressive feature disclosure system had been abandoned. And the cancellation system was passive — users could leave without ever being asked why.

The hidden root cause: the architecture was day-based, not event-driven. It assumed users would progress through onboarding on a fixed timeline, ignoring the reality that different personas (solo admins, multi-location ops, tech-forward physicians) activate on completely different schedules with different needs.

The Architecture Gaps
  • 10DLC SMS approval (7–14 days) completes after email sequence finishes
  • Invited users reach empty workspaces with no guidance beyond initial tour
  • No re-segmentation path for misconfigured account setup
  • Integrations onboarding was a "ghost config" — no dedicated flow existed
  • 6-persona system from V1 reduced to 5 configurations
  • Day-based sequence breaks when users complete steps out of order
  • Progressive feature disclosure abandoned in the transition

What we did.

A comprehensive onboarding architecture review that resolved implementation contradictions, shifted from day-based to event-driven sequences, specified 40+ events for state-machine orchestration, and built 3 behavioural cancellation prevention flows to intercept churn at the moment of intent.

Phase 1 — Architecture Critical Analysis
Reviewed 40+ strategy documents, email copy libraries, HTML mockups, and the proposed V2 architecture against 60 recorded sales calls and existing PostHog data. Identified 7 critical issues and 7 significant gaps across segmentation logic, timing, 10DLC handling, invited user flows, and V1→V2 transition.
Phase 2 — State-Machine Orchestration Model
Resolved the fundamental contradiction between dedicated onboarding sequences and override stacking. Adopted a state-machine approach with 40+ events across 8 categories: account creation, setup completion, feature discovery, tour progression, first value, reactivation, cancellation, and invited user readiness. Each event mapped to computed properties for Customer.io segment conditions.
Phase 3 — 10DLC State Machine
Built a 5-state model for 10DLC SMS approval: submitted, pending, approved, rejected, cold-start reactivation. Added rejection handling with remediation emails, resubmit flow, and a reactivation trigger that fires when approval arrives after the email sequence completes. Closed the 7–14 day gap completely.
Phase 4 — Invited User & Integrations Onboarding
Specified 4 readiness states for invited users (not-ready, ready, pending-setup, active) with role-based rules per persona (Front Desk, Provider, Billing, Manager). Built a dedicated Integrations onboarding flow with IT delegation workflow for EHR integration — closing the "ghost config" gap.
Phase 5 — Cancellation Prevention Flows
Designed a 6-modal in-app retention system that intercepts cancellation intent with 3 churn archetype-specific winback offers: price-sensitive (discount), under-utilisation (pause), and feature-missing (roadmap preview). Each flow triggers real-time Slack alerts to CS with user tier, churn reason, and account context.

After.

7
Critical architectural issues found and resolved before any code was written on broken assumptions
40–50%
Target save rate across all 3 churn archetypes via segment-specific winback offers
40+
Events specified for state-machine-driven onboarding orchestration
5
10DLC SMS approval states with full rejection handling and cold-start reactivation
6
In-app cancellation prevention modals with behaviour-based routing
10 weeks
Full phased implementation roadmap across 5 tracks with dependency mapping

What you can do now.

Your onboarding architecture shifts from day-based sequences that break when users don’t follow the script to event-driven state machines that respond to what users actually do. The 7–14 day 10DLC gap closes automatically with cold-start reactivation.

Your cancellation system intercepts churn at the moment of intent — before the account is lost, not after. 3 archetype-specific flows present the right winback offer (discount, pause, roadmap) based on the feedback users give in a structured 6-step modal sequence.

Your persona system routes different buyer types to different onboarding paths. Solo admins get white-glove support. Tech-forward physicians get self-serve. Multi-location ops get integration-focused setup. Each path has its own activation milestone and measurement.

See Growth OS Offer → Book a 15-Minute Call
Jake McMahon
Jake McMahon
ProductQuant

10 years building growth systems for B2B SaaS companies at $1M–$50M ARR. BSc Behavioural Psychology, MSc Data Science. This engagement required deep architecture analysis across 40+ documents, cross-referencing proposed onboarding logic against 60 validated sales call transcripts to catch gaping assumptions before they shipped.

What this looks like for your company

Onboarding & Retention Architecture.

From day-based sequences that break to event-driven state machines that adapt. Plus a cancellation prevention system that intercepts churn before accounts are lost.

  • Architecture critical review: catch timing mismatches, persona gaps, and missing flows before they ship
  • Event taxonomy for state-machine onboarding: 30+ events across account creation, activation, feature discovery, and reactivation
  • Invited user flow with role-based readiness states and post-tour nurture
  • Integrations onboarding and IT delegation workflow specification
  • Behavioural cancellation prevention system: 3 archetype flows with winback offers and real-time Slack alerts
$3,497 · 3–4 weeks
Right for you if
  • Redesigning onboarding for a new pricing model or product launch
  • Know users are churning but can’t intercept the decision to cancel
  • Your email sequences are day-based and break when users don’t follow the script
See Full Details → Start a Conversation

Redesigning your onboarding?

A 15-minute call is enough to know whether what we do is relevant to where you are. No pitch. Just a conversation about your specific onboarding and retention challenges.

Start a Conversation → See All Offers →