The expensive mistake isn't picking one brand over another. It's buying a size of software that doesn't match the size of your practice: an enterprise suite built for a ten-location chain, signed by someone running one treatment room, or a booking tool with no proper place for the clinical record, holding health information anyway. Buying up or down a size is the most common and most expensive mistake in choosing a CRM.
Who is this for?
Solo nurse injectors, single-location medspas, and practices adding a second or third provider: owner-operated businesses, not franchise rollouts. If you run ten-plus locations with corporate reporting lines and a finance team asking for consolidation across brands, an enterprise platform is built for you, and nothing here argues otherwise.
What belongs on one record
Strip away franchise reporting and enterprise add-ons, and what an independent or small multi-location medspa needs is narrower than most pricing pages suggest. Every item here has to sit on the same client record, not across three logins:
- Scheduling with a public booking page that can take a deposit
- Charting that carries treatment history and before/after photos, not just appointment notes
- E-signed, versioned consent, attached to the chart automatically
- Payments posted straight to the visit
- Memberships with recurring billing, and package balances that draw down on their own
- Follow-ups that run off that same record: reminders before a visit, a nudge when a client is due to rebook, and win-backs for clients who have lapsed
If a platform's main selling point is reporting consolidated across business units, it was built for a chain's finance team. That's a sign you're looking at the wrong size of tool.
The floor: HIPAA and a BAA
A medspa that keeps client charts, consent forms and photos is holding health information from the first booking. Under the HIPAA rules, a vendor that holds it for you needs a business associate agreement, and the Security Rule expects access controls, audit logs and encryption behind it. If that agreement is something you chase on the top plan, the base product doesn't really cover you. Lumè signs a BAA with every customer, on every plan.
Paying for an enterprise you don't run
Enterprise platforms built around multi-location chains are a legitimate choice for the buyer they're built for. They're a mismatch for a one-room injector who signs up for that scale anyway and never touches the cross-location tooling it's built around.
Paying for less than you need
The opposite mistake gets talked about less. Booking tools built for salons and gyms are genuinely good at scheduling. Before you trust one with an injectable practice, ask where the clinical record lives: is there a structured place for dosages and lot numbers, is consent versioned, and is a signed treatment note corrected with an addendum or simply overwritten? A practice that gets "a notes field" for an answer is usually fine on booking and exposed on the clinical side.
The right amount of clinical depth for most independent medspas is treatment notes with an addendum trail, consent you can prove, and photo documentation. Not the weight of a certified hospital EHR, which most cash-pay practices don't need. Not zero, either.
Compare total cost, not the sticker
The price on a pricing page is rarely the bill. Add up the base plan and every tool you'd stack on it to do the same jobs: a separate texting or AI tool, extra locations, a compliance tier. A cheap base plan with three add-ons can be the most expensive option in the room.
The honest shortlist
Many "best medspa CRM" lists earn a referral fee from the vendors they rank, which the FTC expects them to disclose. Build a shortlist from them if you like, then set the ranking aside and judge each name against your own provider count and whether it can hold a clinical record.
Where Lumè fits
Lumè is built for independent and small multi-location medspas adding providers and rooms, not chains adding regions. The AI SMS agent is included in Pro at $349 a month rather than sold as a separate tool stacked on the CRM, which is the stacking problem above. We're not built for large enterprise chains, and we'd rather say that plainly than sell past our size. See pricing.