Glow A2 has two audiences inside the same demo. One sees a landing page. The other can open a tour explaining the intention behind the page's headline, comparisons, sample prices and consultation step.
I built it for a fictional laser-hair-removal med spa in Ann Arbor. The build uses React 19, TypeScript, Vite and Tailwind CSS v4, deployed as static assets on a Cloudflare Worker. The original theme uses gold and stone, with Playfair Display headings.
01 / FIELD NOTESLet the page explain its choices
The page includes an outcome-focused headline, starting prices for eight treatment areas, a comparison against waxing and shaving, reviews, an FAQ and a free-consultation call to action. Those describe the fictional demo's content, not services or prices offered by MRoot.
The owner tour is the distinctive part. It walks through four strategies and places the explanation beside the section it refers to. Instead of asking an owner to infer the rationale from the finished page, it gives them a way to inspect it.
THE REASONING, IN CONTEXT
One page. An extra layer of explanation.
Select a section, or play the four-step owner tour. The note follows the part being discussed.
Illustrative content. No treatment claims or prices.
Owner notes for section 1 of 4. Design intent, not measured effects.
Read the explanation without interacting
The source tour covers an outcome-focused headline, a visual comparison, pricing transparency and a consultation step labeled No-Risk Lead Capture. Those names describe the demo rationale. The comparison values are illustrative, the form is front-end-only, and no conversion or medical outcome is established. Every note is also available in the article text and original excerpt.
The local map above explains the four section roles without importing treatment comparisons, fake testimonials or numerical claims. It is a new teaching figure, not the original owner-tour component.
02 / FIELD NOTESThe strategies are data
The supplied CONVERSION_STRATEGIES excerpt contains two entries and comments for the other two. The omitted entries remain omitted here.
The phrases about benefits, trust and “No-Risk” below are the original fictional marketing rationale. They are not findings from an experiment, verified clinical claims or guarantees offered by the portfolio.
export const CONVERSION_STRATEGIES: ConversionHighlight[] = [
{
title: "1. Outcome-Focused Headline",
description: "Instead of saying 'Laser Hair Removal Services', we state the precise benefit: 'Smooth skin, no razor'. It speaks directly to the reader's frustration.",
strategy: "Reduces friction by showing immediate value."
},
// … "2. Visual Comparison Table"
{
title: "3. Total Pricing Transparency",
description: "Med spas usually hide prices behind a 'call for quote' wall. Publishing starting rates establishes trust and filters qualified leads.",
strategy: "Builds instant authenticity and confidence."
},
// … "4. No-Risk Lead Capture"
];Storing the strategies as records lets the same interface present the title, description and stated purpose consistently. The full rendering code is not in this excerpt, so it does not establish how every highlight or tour transition is implemented.
03 / FIELD NOTESSeparate the intention from the result
The stated purpose of publishing sample prices is to establish trust and help qualify leads. It does not supply a before-and-after measurement of either effect. The same limit applies to the headline and consultation call to action.
That leaves two different statements: what I designed a section to do, and what would be needed to evaluate whether it did it. The inspector below keeps those statements separate.
EXPLAIN, THEN QUALIFY
An intention is not a result.
Read the design rationale without turning its marketing language into a measured outcome.
Outcome-Focused Headline
The headline leads with the intended visitor benefit rather than only naming the service.
This is a stated design intention. The supplied account includes no headline experiment or measured lift.
Intention and evidence are shown together. No measurement is implied.
Read the explanation without interacting
The four source strategies are stated aims, not experiment results. The pricing and comparison values are fictional; No-Risk is a source label rather than a guarantee. The article retains the partial original data array and makes its omitted entries explicit.
There is another boundary in the comparison table. The original article identifies its numbers as illustrative copy and says that a real version should use the client's actual pricing and session counts. This page does not turn those demo values into medical guidance.
04 / FIELD NOTESWhat I would improve next
The documented booking form is front-end-only. A Worker endpoint with spam protection is the proposed next step for the intake. A polished confirmation screen would not, by itself, establish delivery.
The comparison content needs its own review alongside that implementation work. Prices, treatment descriptions, customer statements and outcome language need a real basis before the fictional demo becomes a client page.
The owner tour still has a useful role before any of that: it makes the rationale visible and open to discussion. An owner can point to a section, understand the intended job, and challenge the assumption instead of being handed an unexplained design.
Source, dates, and what this page verifies
This rewrite describes the supplied fictional-business project and its article published July 17, 2026. The original publication date and canonical source address are preserved. The original application and current deployment have not been audited.
New miniatures are explicitly illustrative, not screenshots or full reproductions. All teaching inputs stay in memory. No booking tool, enquiry service, message provider or outside page is loaded by an interaction. Original code excerpts remain unchanged and are displayed rather than executed as application code.
The named source limits and exact explanation of each new model are recorded in docs/batch-4/SOURCE-REVIEW.md. No business, medical, conversion or performance outcome was measured for these demos.