Engagement snapshot
- Mandate
- Convert a patchwork of membership systems into one owned product experience.
- Timeline
- 15 weeks from product definition to first cohort launch.
- Team shape
- Membership director, 1 designer, 2 engineers, and 3 operations SMEs.
The problem
Member onboarding and certification progress lived across a legacy CMS, payment tool, and manual spreadsheets, which made completion rates hard to improve and support hard to scale.
What we built
Launched a unified member platform with account flows, certification milestones, payment handling, and staff visibility into stuck journeys.
Operating context
The association had enough demand to justify a better digital experience, but the legacy stack made member journeys opaque. Staff could not easily see where people dropped off or why support volume stayed high.
Key constraints
- The organization needed to preserve historical member and payment data during migration.
- Certification timelines and renewal rules varied across membership classes.
- The platform had to feel simpler for members while giving staff more control behind the scenes.
What we built
Journey-based product model
Mapped onboarding and certification as explicit product states so progress and blockers became visible.
Payment and entitlement layer
Unified dues, access, and renewal logic so membership state no longer drifted across tools.
Operational visibility
Built staff views for stalled journeys, payment issues, and certification risk before support tickets piled up.
Delivery path
Journey redesign
Reframed onboarding around actual member friction points rather than around the limitations of the legacy CMS.
Migration and launch
Migrated member cohorts in stages, validating payment state and certification progress at each step.
Support handoff
Prepared staff workflows, admin tools, and reporting so the team could run the system without hidden vendor dependency.
Why it mattered
The platform improved completion because it treated onboarding as a product journey instead of a collection of disconnected forms. Staff also gained a clearer operational picture, which reduced reactive support work.
Implementation notes
- Member adoption rises when backend entitlement logic is cleaned up, not just when the UI is refreshed.
- Associations often need more operational tooling than they first describe.
- Migration confidence depends on validating entitlement and renewal states, not just user accounts.