June 24, 2026 · 2 min read · Tom Hall

Buy or build? How to decide when your med spa outgrows its software

At some point every growing practice hits the wall: the off-the-shelf tool that got you to $1M doesn't fit how you actually run at $3M. The membership program your patients love is held together with spreadsheets. The vendor's roadmap doesn't include the feature you need.

Now you're facing the buy-or-build question, and everyone you can ask has a conflict of interest. The vendor says buy. The developer says build. Here's the framework we use when neither answer is ours to sell.

Start with the workflow, not the software

Write down the workflow that's breaking, step by step, before you look at a single product. Most "we've outgrown our software" problems turn out to be one of three things:

  • A configuration problem. The tool can do it; nobody set it up. (More common than anyone admits.)
  • An integration problem. Two tools each do half the job and don't hand off.
  • A genuine gap. Nothing on the market does what your operation needs.

Only the third one is a build decision.

The buy checklist

Buying is right when a vendor's product covers 80% or more of the workflow out of the box, the missing 20% is inconvenient rather than strategic, and the vendor's roadmap and pricing look stable for the next three years.

Be honest about the 80%. A demo always looks like 100%.

The build checklist

Building is right when the workflow is your competitive advantage — the thing patients mention in reviews, the reason your retention beats the practice down the street. Custom software makes sense for the 20% that makes you you, layered on top of boring, bought software for everything else.

Build small. A patient portal, a membership engine, an internal dashboard — these are weeks of focused work, not year-long projects. If a proposal starts with "phase one, six months," walk away.

The question nobody asks: who maintains it?

Software you build is software you own — including its bugs, its hosting bill, and its behavior the morning after a booking-platform API change. Before you build anything, know who answers that 7am call. If the answer is "nobody," that's not a reason never to build; it's a reason to have a technology partner on retainer before you do.


This is exactly the kind of decision we help practice owners make — including recommending against hiring us to build things you should buy. Book an intro call if you're staring down this question.