CS-06 Allē Teaser Audit — Your Metadata Passed. Your H1 Didn't.

Current-State Verification — July 24, 2026

Live page fetched: junochen.com/cs-06-alle-teaser.html

Element	Current State
Meta title	Allē · Dual-Surface Loyalty Redesign · 30M Members, 40K Practices · Juno Chen
Meta description	Names Product Design Director scope, consumer iOS for 30M+ members, provider dashboard for 40K+ practices, and all three outcome metrics (3.2× redemption, 47% reactivation, $42 CAC)
OG/Twitter titles	Frame the page as loyalty redesign across consumer iOS and provider backoffice
Hero layout	Two-column .hero-split on desktop. Left: eyebrow, H1, intro paragraph. Right: six rows (company, product, role, team, scale, outcome)
Body structure	Track A (Consumer iOS App), Track B (Provider Backoffice), closing strategic summary, footer nav
CTA	Two links to cs-06-alle.html — "Request the full case study"
Image assets	16, with alt text naming member dashboard, product cards, provider outreach, Diamond tier profile, treatment imagery

The publisher note said the meta title reads "Allē · Editorial Mosaic · Juno Chen." That phrase is nowhere in the live HTML. The page has already been upgraded to dual-surface, outcome-forward metadata. Several dimensions I came in expecting to flag as broken are not broken.

Which means the remaining gap is sharper than I expected, and more specific.

Passing Dimensions — Quick Confirmation

Dual-surface signal: passing. Hero right column names 30M+ members and 40K+ provider practices. Body splits into Track A and Track B. Closing section states "two surfaces, one loyalty system." A CPO at Gusto or Headway sees two-sided scope without effort.

Outcome proof in first screen: passing on desktop. Hero outcome row shows 3.2× redemption, 47% reactivation, $42 CAC above the fold. On mobile, the single-column stack likely pushes outcomes below fold. Add a condensed mobile hero bar that surfaces the lead metric (3.2× redemption) before the column stack begins. The CPO clicking a Slack link on their phone at 9 PM is a real evaluation scenario. Right now they'd scroll past the H1 and intro before hitting a single number.

Craft signal: passing, and the teaser/full-case boundary is correct. Sixteen image assets with design decision labels ("static balance → progress milestone," "appointment queue → intelligent workflow") show reasoning, not output. The teaser reveals what changed and why without revealing process methodology, research approach, or the full design system. A CPO who reads every word still has clear reason to request the full case. The teaser proves you made deliberate moves and they worked. The full case shows how you arrived at those moves. Correct boundary.

Meta title: passing with one optional refinement. Names scope (dual-surface), domain (loyalty redesign), scale (30M + 40K). Already top tier for portfolio sites at this level. The refinement: swap the scale numbers into the description and put one outcome in the title. Allē · Dual-Surface Loyalty Redesign · 3.2× Redemption · Juno Chen. 30M/40K describes the playing field. 3.2× describes what you did on it. CPOs respond to the outcome. But this is polish, not repair.

The One Fix That Matters

Current H1: "When the product is someone's face, points aren't enough."

Memorable line. Signals domain understanding. Implies the strategic insight. But it's doing the wrong job in the wrong position.

A CPO at Maven or Headway scanning for 30 seconds already feels the domain from the imagery and the Allē brand. What they need from the single largest text element on the page is confirmation that you redesigned both sides of a two-sided loyalty platform from a single strategic premise and that it produced measurable results. The intro paragraph beneath the H1 names consumer iOS and provider backoffice. The right column shows outcomes. Strategic signal is present in the hero, present everywhere except the one place the eye lands first.

Recommended replacement:

The full case confirms the strategic insight: medical-aesthetics loyalty is a trust problem, not a rewards problem. That insight should be the first thing a buyer reads. It proves you think at the level of product strategy. The current H1 proves you can write. Only one of those gets you past the 30-second scan.

A longer alternative if you want a subtitle beneath a tight H1:

That's a subtitle. Don't use it as an H1. Nineteen words is not a clean hit at the top of a page.

This is the single highest-value change.

One Metric Worth Elevating

Track A microcopy already contains a number that deserves better placement: members who planned in-app converted at 2.4× the rate of front-desk enrollment.

This is a different category of evidence than the business outcomes in the hero. The 3.2× redemption rate could have been influenced by marketing, pricing, timing. The 2.4× in-app planning conversion proves a specific design decision drove a measurable shift in behavior. CPOs notice this distinction. It shows that design moved a metric, not that a metric moved while design was happening nearby.

Elevate the 2.4× planning metric to the hero outcome row. It's already on the page. Buried in Track A microcopy it reads as supporting detail. In the hero it becomes the single strongest proof of design-caused behavior change on the entire site.

The CTA Verb Is Right. The Gate Behind It Is Not.

Current state: Two links to cs-06-alle.html with "Request the full case study."

Path is clear. "Request" creates friction. The question is whether the friction is productive.

It is. Allē is medical-aesthetics work for AbbVie. The gating is appropriate. A buyer who won't send a request email wasn't serious enough to matter. The friction itself is a trust signal: this is real client work with real constraints, and you treat it accordingly.

The problem is behind the CTA. As I flagged in issue #3: the full case page returns complete HTML before a client-side localStorage redirect checks authentication. The teaser promises gated access. The full case delivers it with a gate that any browser's developer tools can bypass in seconds. For a candidate whose positioning centers on trust architecture, this remains a contradiction worth resolving. Not a teaser problem, but the teaser's "Request" CTA is where the promise gets made, and the full case page is where it breaks.

The AI Bridge Does Not Belong Here

The assignment asks whether this frame should appear at teaser level:

Do not include this on the teaser.

The teaser proves scope and outcome for one case. The bridge is a positioning argument that connects cases to a buyer's current problem. Different instruments. A CPO scanning the Allē teaser is evaluating whether this case demonstrates the scope they need. They are not ready to hear a cross-portfolio thesis about AI trust.

The bridge works precisely because it reframes Allē from "healthcare loyalty" to "dual-surface trust design" in conversation with a Maven or Headway buyer. That reframe loses its power if the buyer already read it on your website before you said it in outreach. The case page shows the work. The outreach names the connection. You want the CPO to feel the click of recognition when you draw the line between Allē and their problem. They can't feel that click if you already drew it for them.

One thesis per surface. The teaser is carrying "I redesigned both sides of a two-sided platform and tripled redemption." Adding "and this is also about AI" splits attention at the exact moment you need it focused.

Priority Actions, Ranked

• Replace the H1. Move the current line to a subhead. Lead with dual-surface scope and the trust insight. This is the gap between a teaser that reads as a visual design exercise and one that reads as strategic product leadership.
• Elevate the 2.4× in-app planning metric to the hero. Already on the page in Track A microcopy. In the hero outcome row it becomes the strongest single proof of design-caused behavior change.
• Add a condensed mobile hero bar that surfaces the lead metric before the column stack. The phone-at-9-PM scan is real.
• Optional: swap one outcome metric into the meta title. Current title is strong. Refinement, not repair.
• Resolve the client-side gate on the full case. Site-wide issue, but the teaser's "Request" CTA is where the gap becomes visible to the buyer.

The CPO scan-behavior patterns from issue #4 predicted this: metadata and structure would pass, the H1 would be the gap. The page is better than expected. Dual-surface structure is clear. Outcomes are above the fold. What remains is the H1 doing aesthetic work where it should be doing strategic work. Fix that, and this teaser is ready for the buyers you're targeting.