The front desk at location two can't see location one's calendar. A staff member gets asked "does she have an opening Thursday at the other site" and has to make a phone call to find out. If that's happened in the last month, the software you picked for one location is already showing its seams.
What Actually Changes at Location Two?
Four things change operationally when you add a site.
- Shared client records — a client's history has to exist independent of which building she walked into.
- Provider eligibility by location — who can perform what, where, stops being a single list.
- Consolidated reporting — one view across sites, not a spreadsheet stitching two dashboards together.
- Membership and package portability — a package balance bought at site A has to draw down correctly at site B.
If none of those four are breaking yet, you may not be at the moment. If two or more are, you are.
The Single Most Expensive Mistake
The wrong-size system is the priciest mistake in this category — more expensive than any monthly fee, because it costs you in daily friction or in a contract you outgrow before it pays for itself.
Buying down: a single-location tool stretched across two or three sites, running on a calendar that doesn't know location B exists when you're booking from location A's desk. You pay twice — once for the software, once in staff time working around what it can't do.
Buying up costs just as much, in the other direction: an enterprise platform sized for large chains, bought for a two-location group that has no use for consolidated reporting across forty sites or the account-management layer that comes bundled with it.
Where Lumè Fits — and Where It Doesn't
Lumè is built for smaller medspa groups — solo injectors, single-site spas, and practices adding a second or third room and provider. It is not built for large enterprise chains. That's Zenoti's lane, and we'll say that plainly rather than pretend otherwise.
The Pro tier, at $349/month, includes the full medspa CRM — scheduling, client records, memberships, payments, marketing, retention automations — plus the AI SMS agent, on one record. Evaluate us against the two or three locations you actually have, not a roadmap you haven't built yet. See the pricing page for how that scales as you add sites.
One Client Record, Not One Per Location
A client record on Lumè carries treatment history, provider notes, dosages and lot numbers, and before/after photos, regardless of which site logged them. E-signed, versioned consent is auto-sent on booking and stored on the chart — same form, same signature trail, whichever front desk sent it.
A client who had her first neurotoxin visit at location A and books her follow-up at location B shouldn't be starting from a blank chart. If she is, your provider at location B is charting blind. And your consent trail has a gap in it.
Provider Eligibility Has to Work Per Location
Provider-column calendars with drag-to-reschedule and buffer time work fine at one location with one eligibility list. At two locations, eligibility stops being a list and becomes a set of rules: who can perform what treatment, in which room, at which site.
A nurse injector credentialed for filler at your flagship location isn't automatically eligible to book filler at a satellite site if she doesn't work there. A booking page that doesn't know the difference will book her anyway — on the wrong calendar, at a site she's never set foot in. That's the mechanical detail that separates real multi-location software from a location dropdown bolted onto single-site software, and it's usually the first thing that breaks when a salon-first tool gets stretched past one site.
Retention Compounds Across Sites — or It Leaks
Rebooking prompts, treatment-cycle reminders, membership renewals, and lapsed-client win-backs all fire off the client record. Retention is growth in disguise — a CRM pays for itself on rebooking and win-backs, not on the next ad you buy.
At multiple locations, that only holds if the record is shared. A client who goes quiet at site A is invisible to a win-back campaign at site B if the two sites keep separate client lists. She hasn't churned from your business. She's fallen into the gap between two systems that don't talk to each other, and no automation running against a single-site list will ever find her.
Total Cost, Not the Sticker
Look past the headline price. The cheapest headline plan is often not the cheapest system once you stack in what multi-location actually adds — per-location fees, add-ons billed separately, and functionality reserved for a higher tier.
Podium is a useful example, and not one we picked because it's a competitor of ours specifically — it's a widely used standalone add-on for messaging, priced in the neighborhood of $400 to $600 a month on top of whatever scheduling or CRM system you're already running. Across the category broadly, medspa CRMs run from roughly $100/month for a single-location starter tier to $600+/month for multi-location plans with AI and marketing built in. That's market framing, not a quote for what we charge — where any given platform lands in that range depends on what you have to add back in after the sticker price.
The HIPAA Floor Shouldn't Change by Location
Queries scoped to the right practice on every request, an uneditable audit log on every PHI read, encryption both in transit and in storage, and a signed Business Associate Agreement — on the one-location plan too, not an enterprise add-on you chase once you've grown past your starter plan.
A compliance upcharge should bother you more, not less, as you add locations — more sites means more PHI moving through more logins. This is architecture we can point to and explain. It is defensible, and we frame it that way rather than as a guarantee. Read the specifics on the HIPAA page before you take anyone's word for it, including ours.