| Location | New Subscriptions |
|---|---|
| 359 Office | 879 |
| 359 Office | 879 |
| 359 Office | 879 |
| 359 Office | 879 |
| Location | New Subscriptions |
|---|---|
| 359 Office | 2 |
| 359 Office | 5 |
| 359 Office | 10 |
| 359 Office | 3 |
| Location | New Subscriptions |
|---|---|
| 359 Office | 879 |
| 359 Office | 879 |
| 359 Office | 879 |
| 359 Office | 879 |
| Location | New Subscriptions |
|---|---|
| 359 Office | 2 |
| 359 Office | 5 |
| 359 Office | 10 |
| 359 Office | 3 |
Membersy connects dental groups, employers and members to subscription dental plans. The enrollment path ran through forms, email and manual verification: eleven days from a member saying yes to a member being covered, and every one of those days was staff time.
Underneath, one codebase had to serve partners, groups, regions and locations — each with their own fee schedules, roles and reporting — without any of them seeing each other’s data.
We traced every hand-off between member, employer, dental group and Membersy staff before touching an interface, and cut the steps that only existed to move paper.
Account creation became a guided path with validation and eligibility checks at the point of entry, instead of a review queue three days later.
Partners, groups, regions and locations model the real hierarchy, with roles and permissions per level and fee schedules that inherit sensibly.
A dashboard that answers the two questions leadership asks — how many active subscriptions, and which locations are winning or slipping — with month-over-month movement on the same screen.
Taken from the client’s own reporting, not our estimates.
Chosen for the next five years of the product, not the first demo.
Thirty minutes with the people who would actually do the work — no discovery deck, no account manager.