What does a new medspa need online before it opens?
A site that takes bookings on day one and never prints a price that breaks a supplier contract. Template builders and per-page agencies handle marketing pages. None wires the booking button to the software the front desk uses.
What went live, and when
Underneath a site that does sit three parts: the pages a patient sees, the booking path behind them, and Zenoti at the end of it.
Every time your site changes
Change a price on a Tuesday afternoon, safely
Three things that could go wrong when a live clinic site is updated, and what stops each one.
Step one
You change it once, not twice
Every word and price lives in one place, in English and Spanish together. There is no second copy to forget, so the two languages cannot end up saying different numbers.
Step two
Nothing goes out half finished
A new update never interrupts one already going out. Updates wait in line, each page is put together in full first, and your site keeps serving the old pages until the new ones are all ready.
Step three
A broken page never reaches a patient
After it goes up, every page is opened and checked. Anything that does not check out goes back before a visitor sees it, and that check is what caught a speed fix that only looked finished.
The attempt we threw away
The setting almost every site is left on
It cancels the update already going out when a new one arrives. On this site that killed the work part-way through and left half-built pages on a live clinic site, so we turned it off and made updates queue instead.
Turned off on purpose
You can change a price, fix a word, or add a whole page in the middle of a working day, and nobody visiting your site can tell it happened.
Six capabilities arrived one at a time, each on its own dated row.
May to September 2026
Your front door opens before your doors do
Six things a patient can touch, in the order they arrived. Drag the marker, or step it with the arrow keys.
May 14, 2026
A front door, before there was a front door
An Opening Soon page went up while the practice was still being fitted out, so anyone searching could already find it.
June 14, 2026
One price list, in both languages
English and Spanish had drifted apart. Both now read from one source, so a price changes once.
July 12, 2026
Patients book themselves, straight into your calendar
Booking goes into Kintsu’s Zenoti scheduling. It opened without any promotion, to prove itself on real patients first.
July 22, 2026
A way to pay for the bigger treatments
Any treatment priced at $800 or more carries a financing link with the amount already filled in.
September 2, 2026
Faster pages, and the security findings closed
An outside security test on August 26, 2026 produced findings. Every one of them was closed on the day the speed work landed.
September 3, 2026
A clearer path to booking
Twenty-six scattered booking prompts became three deliberate ones, placed where people decide, with accessibility fixes on nineteen pages.
The people who find you can look, book and pay their own way, without waiting for anyone to call them back.
Behind the booking page sits a service that retries a failed request, blocks abuse, and never writes patient health details into a log.
Why we never cancel an update in progress
Never let a new update kill the one already going out. The common setting does exactly that, which put half-built pages on a live clinic site. We queue updates instead, and each checks the live site before we call it done.
A price floor a typo cannot break. Kintsu's supplier contract forbids advertising any offer containing a HydraFacial below $149.99, and no instruction typed into a chat window can waive it. The rule is written out in full below, in the same words the software has to obey.
The rule, word for word
A price you are contracted to hold, that nothing can undercut
Not our summary of it. The clause.
No offer containing a HydraFacial may ever be advertised, proposed, or published below $149.99.
It cannot be waived by any instruction typed into a chat window.
- Where it comes from
- A clause in the practice’s supplier contract, not a preference we set.
- Where it lives
- In the house rules the software follows, in these words, not in a note to a writer.
- What holds it
- A check every piece of copy passes before it publishes. A price under the floor stops there.
A rushed promotion or a stand-in writer cannot publish a price your supplier contract forbids you to publish.
What went wrong
A fix we called verified was not. A speed fix looked clean because the author's browser had cached the files it was meant to remove. Measuring the live site caught it.
One safety check still does not block a release. The check catching banned words and invented names can flag a problem without stopping the page from going live. That gap is still open.
A portrait that pushed visitors away. One visitor said the home-page portrait pushed her away. On September 2, 2026 we replaced it with a kintsugi still life. A stock photo alternative was rejected as posed.
A booking failure we could not fully prove. A customer reported a failed booking on August 15, 2026. Our investigation on September 2, 2026 found August 18 the real anomaly: 213 visits, zero bookings, roughly ten expected. The log that would have settled it had been wiped hours earlier. We sent the booking vendor a records request, not an accusation.
Results
What we can show today. The speed work changed nothing about how the site looks, and we checked page by page.
| Measure | Value |
|---|---|
| Start to a public site | About eight weeks, March to May 2026 |
| Security test findings | All closed the same day, September 2, 2026 |
| Booking prompts | 26 scattered ones replaced by 3 deliberate ones |
| Home-page image on a phone | About a twelfth of the data it used to need |
Not yet measured. No revenue, booking volume, conversion rate, or search ranking from this build exists in any source we hold, so we claim none. The two numbers that will judge this site are Zenoti booking counts and the share of visitors who book. The full Kintsu write-up lists the rest.