Live page fetched: junochen.com/cs-06-alle-teaser.html, Sunday July 19, 2026. Every finding below reflects current HTML. Nothing carried from prior issue content or cached assumptions.
July 10 Verification
Three items tracked from the first audit. Status against the live page:
- Meta title. Now reads
Allē · Dual-Surface Loyalty Redesign · 30M Members, 40K Practices · Juno Chen. Scope-forward, metric-loaded. Done. - Hero product visual. Still absent. Hero section contains text, a right-rail proof block, and a background SVG. No product screenshot, no device mock, no interaction frame above the fold.
- Before-scroll CTA. Still absent. First
Request the full case studylink sits after Track A and the dual-surface bridge block. Nothing in the hero points to the full case.
Two of three carry forward.
The Buyer This Audit Serves
New lens for this serial: does the teaser communicate dual-surface decision architecture at the speed a regulated multi-sided platform buyer actually scans?
Name the buyers. A CPO at Headway holds provider-side clinical documentation and insurance billing against patient-side therapist search and session booking. A design VP at Gusto holds employer payroll, employee self-service, and accountant oversight in simultaneous tension. Regulated. Multi-sided. A design decision on one surface creates consequences on the other, and both of them know it because they live it.
What that buyer scans for: has this person held both sides where the stakes were real? Has she held both sides of a system where getting it wrong costs people something. Headway's provider product touches clinical notes and insurance audits. Gusto's payroll system touches tax filings and garnishments. Allē's loyalty system touches treatment plans and provider billing for medical aesthetics. The consequential dimension is the qualifier.
Five seconds. That's the window.
1. Page Title
Current state. Browser title: Allē · Dual-Surface Loyalty Redesign · 30M Members, 40K Practices · Juno Chen. OG title: Allē — Redesigning Loyalty Across Consumer iOS & Provider Backoffice.
Gap. Minimal. The OG title is actually stronger. It names the surfaces explicitly instead of relying on the abstraction "dual-surface." The browser title leads with scope and scale. This is the best metadata in your portfolio.
One refinement. Align the browser title to the OG title's specificity:
Allē · Consumer iOS + Provider Backoffice Redesign · 30M Members, 40K Practices · Juno Chen
Paste or leave as-is. Minor gain. Confidence: high.
2. Hero Framing
Current state. The H1 reads: When the product is someone's face, points aren't enough.
Strategic premise sits one level down, in the intro paragraph. The right rail carries Company, Product, Role, Team, Scale, and Outcome rows with all key metrics.
Gap. The H1 is doing the wrong job. It generates affect. Fine as a subhead. Fine as the opening line of the full case study. As the single largest text element on the page, it sets the interpretive frame for everything below it. And the frame it sets is aesthetic empathy for the patient.
A Headway CPO reads "when the product is someone's face" and thinks: skincare brand. Not: this person held a provider billing dashboard and a consumer loyalty app in simultaneous redesign. The right rail carries that information, but the right rail is a supporting element. The H1 is the anchor. Right now the anchor pulls toward the wrong reading.
Recommendation. Swap the hierarchy. Lead with the structural claim. Let the affect line support it.
New H1:
One loyalty system. Two product surfaces. Redesigned from a single strategic premise.
New subhead:
Allē manages treatment plans and loyalty redemptions for 30M members getting Botox, Juvéderm, and other medical aesthetics — decisions that affect real patients and real providers. I redesigned the consumer iOS app and the provider backoffice simultaneously, and defined the strategy that made them one system.
That subhead does three things the current hero fails to do. Names the surfaces. Names the consequential category (medical aesthetics, treatment plans). Claims strategic ownership. Keep the right rail exactly as it is. It's doing excellent proof-scaffolding work. Confidence: high.
3. Dual-Surface Signal
Current state. Below the fold, the dual-surface architecture is strong. Track A (Consumer iOS App) and Track B (Provider Backoffice) are clearly labeled. A bridge block pairs them: The patient sees the point / The practice sees the patient. The closing section headline reads Two surfaces. One loyalty system. Both live.
All of that is below the fold.
In the hero, the dual-surface claim lives in the intro paragraph and the Product row of the right rail. A scanner who reads only the H1 and bounces gets "faces and points." A scanner who reads the H1 plus the right rail gets "iOS & Provider Web" in a metadata label, which is closer but still requires assembly.
Gap. The five-second test fails. The structural claim that makes this case study relevant to a multi-sided platform buyer is present, repeated, well-structured, and buried. Not first. Not loudest.
Recommendation. The H1 swap in point 2 solves this. If the largest text on the page says "two product surfaces," the five-second test passes. Track A / Bridge / Track B below the fold then delivers evidence for what the hero already promised. Right now the sequence runs intrigue, then evidence, then claim. Reverse it. Confidence: high.
4. Outcome Proof in First Screen
Current state. The hero right rail contains all five key metrics: 30M+ members, 40K+ provider practices, 3.2× redemption, 47% reactivation, $42 CAC. They sit alongside the intro text in the hero section.
Gap. Viewport-dependent. Wide desktop, the right rail is likely visible before scroll. 13-inch laptop at default zoom, those proof rows may push below the fold. The structural risk is that proof lives in a sidebar layout, not in the primary content flow.
Recommendation. The subhead I recommended in point 2 embeds the top-line scale metrics ("30M members," "provider backoffice") directly into primary text. That guarantees they survive any viewport. The right rail becomes reinforcement rather than the sole carrier. Confidence: medium-high (can't confirm rendering from HTML alone).
5. Craft Signal
Current state. The page contains substantial product artifacts. Track A has a coded member dashboard mock with identity, balance, appointment, activity, and care plan elements. Track B has a provider dashboard mock with queue, patient tiers, point balances, campaign focus, and high-value filters. Decision cards frame specific design choices throughout.
The hero contains none of this.
Gap. A design leader scanning this teaser sees text for the entire first screen. The craft artifacts that prove you can design complex product surfaces sit below the fold. The page earns the craft signal eventually. It does not earn it at scan speed.
Recommendation. Add one product visual to the hero. Cropped side-by-side: consumer member dashboard on the left, provider appointment queue on the right, thumbnail scale. Place it full-width below the H1/subhead block, above where Track A begins. Label the left crop Consumer iOS. Label the right crop Provider Web. Keep it contained, roughly the width of the hero text column. The side-by-side reinforces the dual-surface claim visually and gives a design leader something to react to before they commit to scrolling.
You already have the assets. Both mocks are on the page. Crop, compose, place. Confidence: high.
6. CTA to Full Case
Current state. Two CTAs exist, both reading Request the full case study and linking to cs-06-alle.html. First appears after Track A and the bridge block. Second appears in the closing section.
Gap. No CTA in the hero or first screen. A buyer who landed here from a referral, already familiar with your work, has no path to the full case without scrolling past content they've already seen.
I flagged this July 10. Let me be precise this time. I am not suggesting a CTA before proof. A CTA earns clicks after proof. But the hero right rail is proof. It carries role, team size, scale, and outcomes. A lightweight CTA at the bottom of the right rail, after the Outcome row, sits in exactly the right position: after proof, before the deep dive.
Recommendation. Add a single line to the bottom of the right-rail proof block:
Same link, same destination. Text link, no button styling. Keep both existing CTAs where they are. Confidence: high.
What This Comes Down To
Below the fold, this page works. Track A / Bridge / Track B communicates dual-surface scope clearly. Decision cards show strategic thinking. Product mocks show craft. Metrics repeat at the right moments.
The hero is where it falls apart. It leads with affect when it should lead with architecture. Proof sits in a sidebar when it should sit in the headline. And there's no product visible where both surfaces should be.
Swap the H1 to lead with dual-surface scope and name the consequential category. Add a cropped side-by-side product visual below the hero text. Add a CTA link to the bottom of the right rail.
You need a name for what this teaser is proving: human-system coherence across a regulated multi-sided platform. One design leader held the consumer's experience and the provider's experience in productive tension, inside a domain where design decisions carry real consequences for real people, and shipped both surfaces from a single strategic premise with three designers. That is the proof point a Headway or Gusto buyer is scanning for. The content that delivers it is already on the page. It needs to be the first thing they see, not the last.
Right now they register something about faces. They should register that you held both sides.
- Headway's provider design role: Their Design Director, Provider Experience posting owns EHR strategy across scheduling, clinical documentation, billing, and AI-centered workflows — the exact dual-surface, consequential-decision profile this teaser should be built to answer.
- Full-case gating still leaks: The Allē full case at
cs-06-alle.htmlis one of five pages that return complete HTML before a client-side localStorage check, which means the "Request the full case study" CTA points to content that isn't actually gated for a technically literate buyer. - Equinox+ metadata remains weakest: While Allē's browser title is now the strongest teaser metadata in the portfolio, the Equinox+ teaser still carries a generic title despite having solid first-screen proof in the body — the clearest remaining metadata gap across your five teasers.
- Gusto's AI-trust language maps here: Gusto's Senior Staff Product Designer, Finance posting asks for AI-first financial UX around uncertainty, graceful error surfacing, and user agency across consequential automated decisions — language that validates framing Allē as a consequential multi-sided system, not a loyalty app.