CS-06 Allē Teaser Audit — The Page Does Its Job, the Homepage Card Doesn't

Verified state, June 30, 2026

Verified against live HTML fetched June 30, 2026. The teaser page is resolved. Meta title reads "Allē · Dual-Surface Loyalty Redesign · 30M Members, 40K Practices · Juno Chen." OG and Twitter cards match. The old "Editorial Mosaic" framing is gone. The H1, hero fact grid, Track A / Track B architecture, and closing synthesis all communicate dual-surface scope with outcome proof. Once a buyer lands here, the page does its job.

The homepage card is where you're losing them. It describes Allē as "Loyalty redesign for 30M medical aesthetics patients," tags it Consumer Loyalty / Dual Surface / Med Aesthetics, and links to the teaser. No mention of 40K provider practices. No provider backoffice. No 3.2× redemption, no 47% reactivation, no $42 CAC. The "Dual Surface" tag is carrying all the structural weight, and tags are the lowest-salience element on any card.

A buyer scanning your homepage encounters a consumer-loyalty case with a dual-surface footnote. Fix the card first. Everything else is refinement.

The homepage card is the only thing that matters this week

The homepage card is the first thing a buyer sees after clicking your name in an email or a LinkedIn message.

Current card copy:

Replace with:

Three changes. Each one solves a specific buyer-legibility problem.

Add "40K-practice provider backoffice" to the card description. Headway's Provider Experience director role asks for someone who can connect provider EHR workflows with patient-side flows and deliver cross-pillar design coherence. Their buyer is scanning your homepage for one signal before anything else: has this person held both sides of a healthcare-adjacent platform simultaneously? Your current card answers "consumer side." Your teaser page answers "both." The card needs to match the page.

Ramp's Director Product Design role asks for systems thinking by name, workflow and operations tooling experience, and the ability to own product vision across product areas serving different user types. A card that says "30M medical aesthetics patients" reads as a single-surface consumer case. The systems-thinking signal stays invisible until you name the provider surface.

Add at least one outcome metric to the card. "3.2× redemption" and "$42 CAC" are the two most scannable. They convert the card from a scope description into an outcome claim, and that changes click motivation from curiosity to verification. For Headway, where patient and provider acquisition cost is a structural challenge across healthcare-adjacent platforms, $42 CAC against a $92 industry average is proof that the dual-surface approach reduced cost alongside improving experience. For Ramp, where the director role asks for demonstrated customer and business impact, it signals that systems-level design decisions produced measurable business outcomes. Both buyers have a reason to click through.

Replace the "Med Aesthetics" tag with "Consumer + Provider" or "Loyalty Systems." "Med Aesthetics" positions this as a vertical case. Neither Headway nor Ramp is searching for med-aesthetics experience. Both are searching for dual-surface complexity.

What each buyer sees on the teaser page

The page is largely doing its work. Walk through it with each buyer's eyes to see where the remaining friction sits.

Headway's scan

A Headway hiring manager evaluating provider-surface experience will go straight to Track B. The provider-side outcome metrics (47% reactivation, $42 CAC, 3.2× redemption, $380 LTV) appear inside Track B's practice analytics section. Verify these are visible without scrolling past Track B's workflow content. If the metrics require additional scrolling within the provider section, a fast-scanning buyer evaluating provider-surface impact may never reach them. Headway's roles emphasize making complex technical details easy to understand. They will evaluate whether your provider-surface outcomes are as legible as your consumer-surface ones.

The closing synthesis names "one information model with role-specific views." That maps directly to Headway's "cross-pillar design coherence" language. It's the strongest Headway signal on the page and it's doing exactly what it should.

Ramp's scan

A Ramp buyer reads for systems thinking demonstrated through shipped work. Your Track A / Track B architecture makes the structural separation visible. The H2 frames the case as "one live loyalty system across two surfaces." The closing synthesis reconnects the tracks through a shared information model. All of this registers.

Where Ramp's buyer may hesitate: the H1. "When the product is someone's face, points aren't enough" leads with the vertical context (facial aesthetics) rather than the structural problem (dual-surface loyalty architecture). A Ramp buyer hooks on the structural problem and treats the vertical as backdrop.

Increase the H2's visual weight to co-headline scale. The structural premise, one system across two surfaces, is the hook for buyers like Ramp. It should hit at the same visual priority as the H1. If the H2 currently renders at a smaller size or lower contrast, bump it. A Ramp buyer who sees "one live loyalty system across two surfaces" in the first screen will keep reading regardless of what the H1 says.

Craft signal

The teaser page carries more visual evidence than most teasers. Sixteen images span both surfaces: consumer-side member dashboards (Emma Holloway's point balance, tier progression, saved care plan, treatment catalog, before/after evidence), provider-side workflow UI (appointment queues sorted by urgency, patient profiles with expiring points, campaign-message previews, practice analytics). The CSS renders Track A in dark cells and Track B in light cells, making the two-surface separation visible as a design system choice carried through the visual layer.

For Headway, this matters. Their Provider Experience role asks for experience with "complex B2B SaaS platforms with consumer-grade UX." The provider-dashboard mocks, with urgency-sorted queues and tier-context patient profiles, demonstrate exactly that: enterprise workflow complexity rendered with consumer-grade clarity. For Ramp, whose director role asks for demonstrated product vision and design craft, the dual-surface visual treatment shows architectural thinking made tangible. The buyer sees the system at work.

One gap: the three named design decisions per track (static balance to progress milestone, appointment queue to intelligent workflow, etc.) are strong craft signals, but they read as text. If any of these decisions can be shown as before/after UI pairs within the teaser, add them. A Ramp buyer evaluating craft wants to see the decision rendered.

CTA refinement

"Request the full case study" is clear and functional. One line would lower friction: tell the buyer what the full case contains that the teaser does not.

Specific copy:

A Headway buyer wondering whether the full case covers the research rigor behind the provider workflow redesign gets their answer before asking. A Ramp buyer wondering whether the full case shows systems-architecture decisions in detail knows it does. The CTA becomes a preview of what's behind it.

Homepage positioning order

Allē sits fifth of five case studies. Alibaba is the only card with the featured class.

If you are actively pursuing Headway, Allē should be in the top three. The healthcare-adjacent, dual-surface signal needs to land before the buyer forms their mental model of your work. If Alibaba frames you as an enterprise-platform leader and Allē is an afterthought at the bottom, the dual-surface signal never reaches the buyers who care about it most.

For Ramp, the call is closer. Alibaba's enterprise-platform complexity and Allē's dual-surface systems architecture both speak to their brief. Leading with Alibaba and placing Allē second or third is defensible. But fifth is a default, and defaults work against you for both buyers.

Priority order for this week

• Update the homepage Allē card. Provider-surface scope, at least one outcome metric, revised tags. Highest leverage, lowest effort. Do this Tuesday.
• Move Allē up in homepage case-study order if Headway or Ramp outreach is planned before the holiday weekend.
• Increase H2 visual weight to co-headline scale on the teaser page.
• Verify Track B outcome metrics are visible without scrolling past provider workflow content.
• Add before/after UI pairs for at least one named design decision per track, if assets exist.
• Add the content-preview line above or below the full-case CTA.

The teaser page has done the hard work. Meta layer is clean, dual-surface architecture is legible, outcomes are present and specific. What remains is making sure the door to this page tells the same story the page tells. Right now it doesn't. Fix the card, and the page does the rest.