Why generic loyalty platforms miss it.
Most platforms scope memberships to a single location. A member at your Brooklyn site shows up in Manhattan as a stranger. Patients notice. Front desks lose face. Your platform becomes friction instead of a moat.
Each location reports its own numbers. Group-level KPIs require an analyst to stitch CSVs together every Monday morning. The decisions that matter — capital allocation, marketing spend, who's outperforming — get made later than they should.
A regional manager who oversees three locations can't easily move between them. Front desks at busy sites have too much access; at slow ones, too little. Role-scoping is the difference between a platform that works at 3 locations and one that breaks at 8.
Existing features, re-pointed at your problem.
Owners see the whole group. Regional managers see their territory. Front desks see only their location's queue. Roles are independent of location — a regional manager doesn't need to re-log in to move between sites.
A patient visits Brooklyn on Tuesday, Manhattan on Saturday. Same record, same tier, same points balance, same drop reservations. The front desk in either location sees the same thing.
Every points event tags the location that produced it. Roll-up reports show points outstanding per location, redemption rates per location, and the patient flow between locations.
Run one patient app under the group brand, with per-location overrides for treatment menus, providers, and hero imagery. Patients see their local context; you don't manage seven different apps.
Run a group-wide drop for a brand-level moment, or scope a drop to a single location to test or to fill a specific calendar. The same module handles both — no separate workflow.
$599/mo Studio. Period. No per-location markup, no per-seat fee, no surprise scaling charges as you open the next site. The math holds at 3 locations and at 13.