Most loyalty platforms in medical aesthetics are mobile apps. That's their whole pitch: "your branded loyalty app." The argument is reasonable in the abstract — patients live on their phones, so meet them on their phones — but it's an incomplete picture of how loyalty actually happens in a clinic.
Loyalty doesn't happen on one screen. It happens on four.
The four surfaces, and what each is actually for
The screens patients and staff use to interact with a loyalty system are, in order of use:
- The phone.Where patients live between visits. Where push notifications land. Where the membership card lives. The surface most platforms cover well, because it's the most visible and the easiest to sell.
- The browser.Where patients live on their lunch break, on their work laptop, in their inbox. Where they manage memberships, gift cards, and rewards when they don't want to pull out their phone. The surface most platforms underserve.
- The clinic admin. Where owners configure the program and where front-desk staff look up members. The surface that determines whether the program is actually run or just installed.
- The POS terminal.Where the transaction actually happens. Where loyalty either lands as a points credit on the patient's account or evaporates because no one remembered to tag the visit. The surface most platforms outsource — and where the leakage starts.
If your loyalty platform only covers the first surface — the phone — you're running a quarter of a system. The phone is necessary, but it's not sufficient. It's the visible end of a pipeline that has to land at three other places to actually work.
A mobile-only loyalty platform isn't cheaper, it's smaller. You're paying for one screen instead of four.
The expensive failure modes of a one-surface platform
Here's what happens when the platform only owns the phone:
- The web fallback is a webview of the app. Cramped, slow, designed for phones, shown on a laptop. Patients abandon halfway through gifting a $200 gift card to their sister.
- The admin is a basic spreadsheet view bolted onto the API.Owners can't actually configure the app without filing a ticket. Front desk can't find members fast enough, so they stop looking up members.
- The POS is "ask the patient if they have our app." Manual, error-prone, and not enforced. Roughly one-third of eligible visits never get tagged. The leakage is invisible because no one is measuring it.
I've watched all three failure modes happen at clinics I know. The platform isn't the problem in any one moment — but the cumulative drag is enormous. By the time the owner notices that loyalty isn't producing the expected lift, they've already paid 18 months of platform fees and they're reluctant to switch.
What "one membership" actually means
It's not just having four surfaces. It's having four surfaces that share the same data model. One member record. One points ledger. One tier engine. One redemption queue. One source of truth for what the patient is owed and what they've done.
The reason this matters is operational, not aesthetic. When the patient checks in on their phone, the front desk sees it. When the front desk adjusts a tier manually, the patient's app updates. When the patient buys a gift card on the web, the front desk knows to apply it at the next visit. When the POS clears the charge, the points hit the patient's app before they sign the receipt.
None of this is hard to design. It's just a lot of work. Most platforms haven't done it because their unit economics don't support the investment — they took the rev-share model so they don't have to. The cost of incomplete surface coverage gets passed to the operator.
Why we built all four
Because I ran into all four failure modes at Prosper Health, and the workaround was always the same: carry the operational gap myself. The front desk would manually look up members in the scheduler. I'd write app-config changes as feature requests to the platform. We'd run a separate POS that didn't talk to the loyalty system. The patient would have to take their loyalty card out of one app and reload it in another. It was the kind of friction that makes you stop using the tool you're paying for.
Loyalty Flow is built on the premise that those four surfaces have to be the same product, not four products bolted together with an API. The patient who opens the app on Sunday night to reserve a Tuesday drop is the same record the front desk pulls up on Tuesday afternoon, with the same redemption code the POS clears at checkout. There are no seams.
The seams are where loyalty leaks. The four surfaces aren't features — they're a sealing strategy.
How to evaluate the platform you're looking at
Three questions to ask any loyalty platform before you sign:
- What does the web experience look like?Not the marketing site — the actual member web app. Open it on a desktop browser. If it's a cramped phone layout in a laptop window, you're paying for a fraction of a platform.
- What does the front-desk member lookup look like?Time it. If finding a member takes more than five seconds, the platform won't actually be used at the front desk.
- What does POS integration mean specifically?Press for the answer. "Our POS works with our loyalty" is a phrase, not an integration. Is it native? Webhook-based? Manual tagging? Each of those has dramatically different leakage characteristics.
If the answers to any of those don't satisfy you, the platform is mobile-only with bolted-on attachments. Which might be acceptable, but you should know it's what you're paying for.
— Robbie