Case Study
5 min read

Bella Skin Institute: a medical spa's own loyalty app

Bella Skin Institute is a cosmetic dermatology practice in Calabasas, California, led by Dr. Anna Guanche. Its work runs on a slow rhythm. Patients come in for Botox, fillers, and laser treatments, and then they are due back three to six months later, when the effect fades.

LoyaltyPass built the practice an app of its own, in the App Store and Google Play, plus an admin panel for the team. This post sets out what was built and why.

The full record is published by RaftLabs, our parent studio: the Bella Skin Institute case study.

The problem, in plain terms

A medical spa does not make its money on the first visit alone. The value sits in the return visit months later, when a patient comes back on schedule. If that visit slips, or goes to another practice, the work of winning the patient is wasted.

Bella Skin Institute had no reliable way to bring patients back inside that window. Nothing reminded a patient that her next treatment was due, or gave her a reason to book here rather than drift elsewhere.

The loyalty tools rented through booking platforms could not fix this. Those tools run the platform's rules. They could not run a points system shaped around this practice's treatment timings, rewards, and deadlines. The practice needed a program it controlled itself.

What we built

We built the practice an app of its own in the App Store and Google Play, for iPhone and Android phones. It was built from a single codebase, which means one set of code runs on both types of phone, so the practice does not pay to build the same app twice.

Patients earn points worth 10% of cash payments. At checkout, the front desk scans a QR code, the square code the patient shows on her phone, and the points land in under 15 seconds. There is no paper card to lose and no manual entry for staff later.

The central mechanic is called Pressure Points. Points carry a deadline, and they lapse if they are not used in time. Patients get a reminder 28 days before the deadline and another one 7 days before the points lapse. The reminders arrive as push notifications, the alerts that appear on a phone screen, and as countdowns inside the app. A deadline, clearly warned about, gives a patient a reason to book before she drifts past her treatment window.

The app also carries a before and after gallery, so patients can see treatment results, and a service catalogue with appointment requests, so a patient can browse treatments and request a booking in the app.

Behind it sits an admin panel, the private control screen for the practice team. The front desk uses it to process transactions. Management uses it to adjust rules and rewards without a developer, changing what points are worth or when they expire on its own.

The build took 12 weeks. The practice owns the code outright. There is no vendor lock-in, which means the practice is not tied to us to keep the app running, and there are no licensing fees.

What we can and cannot claim

This section matters, so it is kept separate.

We can claim the delivery facts. The app was built in 12 weeks. It is live for iPhone and Android. Points credit in under 15 seconds at checkout, and points are worth 10% of cash payments. Reminders go out 28 days and 7 days before points lapse. The practice owns the code.

We cannot claim results. No visit frequency figures and no revenue figures were published for this build, so this page shows none and claims none. No enrolment, retention, or revenue figure is attached to this app here, because the record does not provide one.

That honesty is the point. This is a build story, not a results story. It shows what the practice ordered, what was delivered, and how the program is designed to work. This page keeps a build described accurately apart from an outcome that has been proven.

What this means for a program like yours

If your business also works on long gaps between visits, a discount scheme may be the wrong tool. A discount waits for the customer to return on her own. An expiry deadline with reminders gives her a date, warns her well before it, and ties the warning to the moment she is due back.

That pattern fits any business where the next visit has a natural window: treatments that fade, services that need renewal, or care that runs on a cycle of months. The reminder does the remembering staff cannot do by hand for every customer.

The second lesson is ownership. Renting a loyalty module inside someone else's platform is quick to start, but the rules stay under that platform's control. Owning your own app and code leaves you free to change the rules, keep the program if you change platforms, and run loyalty as part of your own business.

Talk to the studio

LoyaltyPass is a studio that builds custom loyalty software for mid-size and large organisations. If your customers return on a cycle of months and you need a program built around that cycle, with rules and code you own, start with a conversation about what you need.

Book a scoping call. Projects start at $9,500.

Sacha Blanc

Written by

Sacha Blanc

Part of the LoyaltyPass editorial team. All articles draw on primary sources: brand announcements, industry research, and academic literature. Statistics are attributed inline. About our editorial team

No demo wall, no jargon. Here's what brands ask us.