How it works

Click a feature. See exactly how it works.

Not screenshots and not a slide deck. These are the actual mechanics of the build, running in your browser, so you know what you are buying before you spend fifteen minutes on a call.

Pick a feature

Booking that lands in the system you already run

We never embed your scheduler in an iframe. A patient taps once on the treatment page and arrives in Boulevard, Jane, Vagaro or whatever you run, with the treatment already selected. No re-picking, no second search.

Try it — tap Book on a treatment
Neuromodulatorsfrom $13
Dermal Fillerfrom $750
Microneedling + PRF$650

One tap. Nothing else to choose.

What happens
Patient tapson your treatment page, on their phone
We deep-linkyour scheduler URL, with ?service=botox appended
Boulevard openstreatment pre-selected, times showing, ready to confirm
  • Works with Boulevard, Jane, Vagaro, Square, Zenoti, GlossGenius and Aesthetic Record
  • Your booking data stays in your platform, where it belongs
  • Nothing to migrate and no second system to learn

A four-step flow for the $2,000 decisions

Nobody self-schedules laser resurfacing at 11pm. For high-ticket treatments we capture intent instead of a time slot, one question per screen, and hand your front desk a warm lead the same minute.

Click through the flow
Why it is built this way
  • One question per screen — a ten-field form on a phone gets abandoned
  • Day-part, not a calendar. You are capturing intent, not availability
  • No account, no password, no card
  • Nothing is stored in a database. It routes to you and is forgotten
Treatment interestpre-filled if they came from a treatment page
Provider & day partskipped entirely if you have one provider
Straight to your phoneSMS and email, within seconds

Your phone buzzes before they close the tab

The objection that kills web forms is that they land in an inbox nobody checks. So the text goes first and the email is the record. Press the button and watch what your front desk actually receives.

Simulate a consult request

Rebuilt on our server, never trusted from the browser — it is what your phone displays.

And nothing is kept
  • No database, no CRM, no analytics record of who enquired
  • Treatment interest sits close to health information, so it travels to you and stops
  • Tagged with the source, so your monthly report says "nine from Instagram, three from Google"
  • If the endpoint were ever subpoenaed there would be nothing to hand over

What we take off your treatment pages

A Meta or Google advertising pixel on a Botox page can transmit that an identifiable person viewed it. Toggle between a typical agency build and ours, and watch the network requests a patient's browser actually makes.

Requests fired when a patient opens your Botox page

    Every price visible, no clicking and no calling

    "Call for pricing" filters out the people who were ready to book and keeps the ones who want to negotiate. The menu is the signature element of the build: full-width rows, every price on the page. Tap a row on mobile to expand it.

    Tap a treatment
    What this does
    • Per unit, per syringe, per session, per month — priced the way you actually charge
    • Member and non-member pricing side by side where you run memberships
    • Config-driven: adding a treatment is one line, not a new page build
    • Feeds the MedicalProcedure schema automatically, so prices reach AI answers too

    Drag to compare, filter, then book that injector

    Patients buy outcomes, not syringes. The vault replaces a cluttered Instagram grid with results you can filter by concern, treatment or provider — and every result books the person who performed it.

    Drag the handle. Then filter.
    After
    Before

    Neuromodulators · 14 days · performed by Dr. Voss

    Built in from the start
    • Keyboard operable — arrow keys move the handle, not just drag
    • Results-vary and written-consent notices designed in, not footnoted
    • Filter by concern, treatment or provider
    • Every result links to book that exact injector's calendar

    Panels above are placeholder gradients, not patients. A real build uses your consented photography in identical light and framing.

    The markup that makes you the answer

    Healthcare is the most AI-summarised category on the web — 51% of health searches now return an AI Overview. AI engines do not read your marketing copy. They read structured data. This is the part almost no agency touches.

    What we put in your pages
    "@type": "MedicalBusiness",
    "name": "Your Clinic",
    "geo": { "latitude": 33.49, "longitude": -111.92 },
    "availableService": [{
      "@type": "MedicalProcedure",
      "name": "Botox",
      "offers": { "price": "13" },
      "provider": {
        "@type": "Physician",
        "name": "Dr. First Last, MD",
        "hasCredential": "Board certified"
      }
    }]
    What a patient then gets back

    “For natural-looking lip filler in Scottsdale, Your Clinic is a board-certified practice offering neuromodulators from $13 per unit and dermal filler from $750 per syringe, with treatments performed by Dr. First Last, MD.”

    • Nested MedicalBusiness, Physician and MedicalProcedure — not loose tags
    • An llms.txt summary of your practice, treatments and prices at the root
    • FAQ blocks written the way people speak to Siri, not the way agencies write headings
    • A visible "Reviewed by {provider}" byline on clinical pages, backed by reviewer markup

    Why one page per metro loses

    Patients rarely drive fifteen minutes for injectables. A single page targeting a whole city competes against every clinic in it, instead of the handful within reach. We build the page per neighbourhood, with the schema coordinates to match.

    One page for the metro vs one page per pocket
    One page: “Scottsdale”Competes with every clinic in the metro. Ranks for a term with high volume and low intent, where the patient still has to work out whether you are near them.
    Pages per pocketOld Town · Paradise Valley · Arcadia · Biltmore · Catalina Foothills. Each with its own zip codes, its own copy and its own coordinates in the schema graph.
    • Localised pricing per micro-market where it differs
    • Static map images, never an interactive Google Map — 300kb and a tracking surface
    • Google Business Profile claimed and matched to the same name, address and phone
    • For a local practice, the Business Profile outranks the website in value. We set up both.
    See a finished build

    Open a real one on your phone

    LUMEN Aesthetics is a complete build running live: fourteen routes, every treatment priced, a filterable results gallery, membership and financing pages, and booking wired end to end. It is a demonstration practice rather than a client, and the site says so on itself.

    View the live demo → Opens in a new tab. Look at it on a phone, because that is where your patients will.
    14routes, all built to the same standard
    42prices published, nothing hidden behind a call
    <2sload on a throttled 4G phone
    AAWCAG 2.2, checked on every change
    Book a call

    Seen enough?

    Fifteen minutes. We look at your site and your booking platform and tell you plainly whether this is worth doing for your clinic.

    Book a 15-Min Call

    Flat $4,999 · 30-Day Launch · 100% Asset Ownership

    Email us Book a 15-min call