Most med spa owners were never taught how the medical side of the business is supposed to work.

Start with the clinic as it actually operates

I start by asking how a patient moves through the clinic on an ordinary Tuesday. Who evaluates? Who decides? What is documented? Where does a question go when the expected path does not fit? Then I compare those answers with the policies, schedules, charts, logs, agreements, and payment flow.

This matters because a missing document and an unused document are different problems. One may require drafting and review. The other may require training, workflow changes, supervision, or a decision about whether the written policy belongs in the clinic at all.

• Who has clinical authority?
• What is delegated, and under which conditions?
• Where is the decision recorded?
• What happens when the expected path breaks?
• Who reviews drift and closes corrective action?

Review five connected operating systems

Clinical quality is affected by more than the clinical department. Service design, staffing, scheduling, inventory, compensation, ownership, and medical leadership all shape what happens in the treatment room.

A good review looks for contradictions across those systems. If a service is on the menu before eligibility, consent, escalation, inventory, pricing, and physician review are settled, the clinic does not have a form problem. It has a service-launch problem.

Prioritize without manufacturing fear

I use red, yellow, and green only when the categories mean something. Red is work that may require a pause, prompt escalation, or qualified review. Yellow is important work that can be planned. Green means the control is present and appears to be functioning based on the evidence reviewed.

Everything cannot be urgent. If a report treats every observation the same, the founder still does not know what to do Monday morning.

Keep the audit boundary clean

A Clinical Quality Audit identifies and prioritizes possible gaps. It does not correct every issue, replace qualified counsel, authorize a patient-specific clinical decision, or guarantee a regulatory result.

At the end of the review, leadership should know which questions belong with the medical director, operations, finance, counsel, a vendor, or a separate implementation engagement. That is enough for the first scope to do its job well.

Prepare the evidence before the walkthrough

The quality of the review depends on what the clinic is willing to share. I need enough information to understand the current system, including the parts that are informal, unfinished, or uncomfortable. The purpose is to make a sound plan from accurate facts.

• Entity and ownership map
• Medical-director and clinician agreements
• Service menu and marketing claims
• Standing orders, protocols, consents, and Good Faith Exam workflow
• Training, competency, chart review, incident, and corrective-action records
• Banking, payment, refund, incentive, and vendor arrangements

Clinical experience is not ownership training

I have watched highly capable clinicians spend six figures on rooms, devices, and marketing before anyone has mapped who may make which clinical decision. Clinical experience is a strong foundation for ownership. It simply does not cover entity structure, physician relationships, funds flow, delegation design, vendor contracts, or the management of a cash-pay healthcare business.

The founder does not need a lecture about staying in her lane. She needs a clear view of the new lanes that come with ownership and qualified help putting them together.

Concept comes before procurement

Before signing a device, technology, lease, or physician agreement, define the clinic you are building. State, services, owner role, patient population, delivery model, timing, and capital all affect the structure. A generic launch checklist cannot make those decisions for you.

• What will be offered—and what will be held?
• Which state and location facts control the build?
• What will the founder own and operate?
• Which decisions require independent clinical authority?
• What must be true before marketing begins?

Structure means decision rights, not a stack of entities

An entity diagram is useful only if it changes how the clinic operates. The team still needs to know who controls contracts, patient funds, staffing, vendors, records, clinical decisions, prescribing, delegation, quality review, and escalation.

The founder does not have to become a lawyer. She does need to recognize when the legal, clinical, financial, and operating plans are giving the team different instructions.

Readiness is observable

Readiness can be observed. The required relationships are active. The forms and workflows have owners. Permissions are set. The team has been trained. The clinic has rehearsed the moments most likely to expose a weak handoff.

• Patient intake and clinical evaluation
• Consent and documentation
• Medication, product, and inventory controls
• Urgent symptoms and adverse events
• Scheduling, refunds, and patient communication
• After-hours escalation and physician availability

The opening date is a gate, not a promise

I will not guarantee an opening date before the dependencies are known. The date should follow completed work; it should not be used to force incomplete work into production.

Moving a date is frustrating. Rebuilding the clinic after patients, payroll, marketing, and vendor obligations are already moving is worse and usually more expensive.

A signature is not governance

I have seen medical-director agreements that were fully executed and still left the clinic without meaningful medical leadership. The signature did not tell the team which services had been reviewed, who could perform them, when the physician had to be consulted, or what happened after an incident.

The agreement matters. The way the role functions on a routine workday matters just as much.

Authority must match responsibility

Responsibility without authority is not a workable arrangement. A medical director needs timely access to service changes, clinician onboarding, protocols, records, complaints, quality trends, and exceptions. The physician also needs a defined way to require follow-up when something needs to change.

• Clinical scope and service approval
• Delegation and supervision expectations
• Consultation and escalation pathways
• Chart-review cadence and feedback
• Incident and corrective-action authority
• Sustainable availability and alternate coverage

The clinic needs the same operating truth

Vague agreements create competing assumptions. The founder may believe the physician approved every protocol. The physician may believe the clinic is escalating every exception. The clinical team may think quarterly chart signatures are the entire relationship.

Put those expectations on one role map. Name who decides, who performs, who reviews, what is documented, and which events must leave the ordinary workflow.

Quality review should produce action

Sampling charts is the beginning of review, not the end. Leadership should know what was reviewed, which standard was applied, what pattern emerged, who is giving feedback, when correction is due, and how the clinic will confirm that the issue was closed.

Design for continuity

The clinic still needs medical leadership when the physician is traveling, when conflict arises, when a second site opens, or when the relationship ends. Alternate coverage, records access, escalation, replacement expectations, and open corrective actions should be planned before they are needed.

Continuity protects the team and makes the role more realistic for the physician carrying it.

Begin with the real footprint

Before standardizing anything, map the actual footprint. For each location, record the state, entity, ownership, services, patient-funds flow, medical relationships, Good Faith Exam workflow, protocols, systems, and known exceptions. The map usually explains why teams that appear inconsistent are working from different underlying conditions.

Separate universal controls from local requirements

Some expectations should be consistent everywhere: named owners, decision rights, document control, escalation, chart review, incident handling, and corrective-action closure.

The method can remain consistent even when a state or location requires a different answer. The difference is whether leadership can explain the variation, show who approved it, and say when it will be reviewed.

Give every exception an owner

An exception record should identify the location, reason, approving reviewer, affected workflow, supporting evidence, review date, and the condition that closes or renews it. Otherwise a temporary workaround quietly becomes the permanent operating model.

Sequence change by exposure and dependency

Standardization rarely happens in one clean launch. A physician relationship may depend on entity work. A workflow change may require technology, training, and revised records. A service hold may require patient communication and financial planning.

A phased plan lets the executive team see those dependencies, assign resources, and verify the work before moving to the next location.

• Enterprise baseline
• Location and state map
• Critical holds and immediate escalation
• Shared operating standard
• Controlled local exceptions
• Ongoing location-level review

Executive sponsorship is not optional

This work needs an executive sponsor with document access, decision authority, budget, and local owners. Leadership also has to accept that some answers will differ by state or site. A mandate to make every location look identical will create new risk rather than resolve it.

The desire for autonomy is legitimate

Many founders leave hospital practice because the career structure no longer fits their life. They want flexibility, ownership, creative agency, and a different way to care for people. Those are legitimate reasons to build.

I do not believe founders should be shamed for what hospital training did not teach them. The useful response is to identify the missing business knowledge and help them build it.

The new role changes the questions

Ownership changes the question set. The founder now has to connect clinical authority with entity structure, staffing, contracts, banking, patient payments, insurance, technology, vendors, records, marketing, and growth. Clinical judgment remains essential, but it now sits inside a much larger system.

What the founder is really buying

What most founders need is translation. They need to understand which questions belong with the physician, counsel, operations, finance, or a vendor. They need practical decision gates and a partner who will be candid without making fear the pitch.

• A defensible operating structure
• A translator across clinical care, operations, ownership, finance, and growth
• A sequence that reduces expensive undo work
• Candor without manufactured fear
• Education that increases founder capability

Ask before acting

Before launch, the founder can still change the design before it is embedded in payroll, patient expectations, vendor agreements, marketing, and daily habits. That is a valuable window.

After launch, the path begins with an honest review of the current clinic and a willingness to change what the review cannot support.

Choose a partner by the boundaries they keep

Pay attention to the boundaries a prospective partner keeps. They should not guarantee a legal result, sell a paper medical director, declare the founder unlawful during a sales call, or promise an opening date before readiness is known. Those limits are signs of judgment, not hesitation.