Continuity from July 10
One gap flagged last time: a generic browser title (Equinox+ · Teaser · Juno Chen) while the body carried strong proof points.
Title tag unchanged. No meta description. No og:title, no og:description, no Twitter card metadata. Equinox+ is the only teaser in the portfolio with none of these surfaces populated. Fix it before anything else in this audit matters.
Every sibling page already carried mandate-forward metadata when the Buyer-Angle Map was published on July 9. Alibaba leads with B2B trust and $50B+ GMV. Thermo Fisher leads with pharma supply chain and $20M+ margin. Red Cross leads with national disaster-relief platform. Allē leads with dual-surface loyalty redesign and 30M members. Equinox+ leads with nothing. That's the gap.
The agentic question, answered
I've been applying the human-agent coherence lens to every case in this portfolio. The discipline matters. So does knowing when the lens doesn't fit.
Equinox+ doesn't fit. The full case contains zero instances of agent, agentic, AI, automation, delegation, or coherence. The KB classifies it under 0-to-1 high-stakes builds, not agentic product. Forcing the frame onto a 2020 connected-fitness platform would be dishonest positioning. A hiring manager would catch it in seconds, and the attempt would contaminate the cases where the coherence argument is genuine. Nothing to retrofit. No reason to try.
So what is this case actually for?
It solves a problem the rest of the portfolio creates. A hiring manager who has read Alibaba and Thermo Fisher sees enterprise credibility, regulated-domain sophistication, research-driven decision architecture. What they worry about next is speed. Consumer instinct. Whether someone with that background can operate at the pace and craft bar a consumer product demands, or whether they'll over-deliberate and under-ship.
Equinox+ is the answer to that worry. Zero to MVP in 90 days. Five brands unified without flattening. 4.8-star App Store rating at launch. The Buyer-Angle Map already identified this role: support case for regulated-platform buyers who might assume enterprise means slow. Correct framing.
The teaser page doesn't execute it. The body has the proof points. The metadata, the eyebrow, and one missing architectural sentence keep those proof points from registering at scan speed.
The whole audit follows from that. Is this case doing the job it's actually here to do?
Six-point audit
Each point evaluated against one risk: "consumer fitness" triggers a domain-prestige discount at scan speed. You have roughly three seconds to override that reflex.
1. Page title
Current: Equinox+ · Teaser · Juno Chen
Highest-priority fix on the page. A hiring manager with twelve browser tabs open sees this title and it tells them nothing. It sits next to Alibaba.com — Redesigning B2B Trust at $50B+ GMV — Juno Chen and loses before the tab is clicked.
Implement these exactly:
| Tag | Copy |
|---|---|
| Title tag | Equinox+ · 5 Brands, 1 Platform, 0→MVP in 90 Days · Juno Chen |
| Meta description | Product Design Director, Equinox Holdings. Led product design for a connected fitness platform unifying five premium brands for 600K+ members. Shipped 0→MVP in 3 months with a 4-designer team. 4.8-star App Store rating at launch. |
| og:title | Equinox+ · Five Brands, One Platform, 90 Days to MVP |
| og:description | Led product design for Equinox Holdings' connected fitness platform — five premium brands, 600K+ members, 200+ clubs, one unified experience. 0→1 in 3 months. 4.8★ App Store. |
Not suggestions. Copy to ship.
2. First screen
Strong, with one soft spot.
The hero headline, "Five brands / One platform / No compromise," is doing real structural work. Immediately signals this is not a single-product consumer app. The intro paragraph reinforces: 600,000 premium members, five distinct brands, Product Design Director role, 0 to MVP in 3 months. Brief rows are well-constructed. Role, team composition (4 designers, 1 researcher, PM, engineering leads, brand partners, data partners), scale, outcome all visible before scroll.
The soft spot is the hero eyebrow: "Equinox · Consumer Fitness · iOS & Android · 2020."
"Consumer Fitness." Those two words are doing damage you can't afford. A hiring manager at an enterprise AI company sees them and their pattern-matching brain files this as lower-stakes before the headline intervenes. The full case has a better frame: "Beat Peloton without becoming Peloton." That's a competitive-strategy constraint, not a domain label.
Replace "Consumer Fitness" with "Connected Fitness Platform" or "Multi-Brand Platform." If the eyebrow format allows it: Equinox · Connected Fitness · 5 Brands · iOS & Android · 2020. Either version signals architectural complexity rather than app category.
3. Platform architecture signal at scan speed
Visible but under-leveraged.
"Five brands / One platform" in the headline does heavy lifting. The intro adds "without flattening brand distinction." Below the hero, the product gallery text surfaces SoulCycle, Equinox, Precision Run, Pure Yoga, and HeadStrong as distinct brand presences.
What's missing is the how. The full case contains the most architecturally interesting decision in the entire portfolio: instructor followership as the cross-brand navigation model, derived from retention data showing members who followed an instructor within 30 days retained at nearly double the rate. That's a data-driven IA decision with real business consequence. The full case also names the token architecture that let five brand expressions share one component base and one deployment.
The teaser doesn't need the whole story. It needs one sentence that converts "five brands, one platform" from tagline to evidence.
Add one line to the hero intro or a visible brief row. Two options:
"Followership as navigation model, derived from retention data across 600K members."
"One token architecture. Five brand expressions. One deployment."
Pick one. Either converts the architectural claim from assertion to signal.
4. Speed framing
The domain-prestige risk is handled by the eyebrow and architecture fixes above. Here the risk shifts: does "90 days" read as disciplined constraint-solving or rushed execution?
Well-handled in the brief. Under-developed in the closing.
"0→1 in 90 days" in the brief rows reads as a constraint metric, not a boast. Team composition provides implicit evidence this was resourced, not a skeleton-crew sprint. The closing CTA section adds useful texture: "75 hours of research, four member archetypes, five architecture decisions, and zero to MVP in three months." That sequence works. Research discipline under speed constraint is exactly what prevents "3 months" from reading as "they skipped the hard thinking."
The full case reveals a decision that would strengthen this further. Six weeks out, engineering capacity for only three brand worlds. Juno prioritized SoulCycle, Equinox, and Pure Yoga based on instructor-followership density in retention data, then shipped Precision Run and HeadStrong in the first post-MVP update. That's scope management under constraint, driven by data. It separates a Director from a senior IC.
Add one clause to the closing CTA text: ...and a data-driven scope call that shipped three brands at launch and two in the first update. Converts the speed narrative from "we moved fast" to "we made hard prioritization decisions fast, using evidence."
5. Craft signal
Source-level evidence solid. Visual confirmation limited by audit method.
The page references 12 image assets, all returning HTTP 200. Source text surfaces detailed UI states: output/watts/cadence/resistance for live classes, beat match, QR check-in, schedule/booked states, activity analytics, streaks, badge systems. The variety (live workout, scheduling, check-in, analytics, gamification) demonstrates breadth of product surface.
For a Director+ evaluation, craft should be visible but not dominant. The page should read as "this person ships at a high craft bar," not "this person is a visual designer who happens to manage people."
Assessment: likely strong, with one self-check you need to do. I can't evaluate pixel-level craft from source alone. Structural indicators are right. But verify this yourself: do the images visually demonstrate that SoulCycle and Pure Yoga look like different brands sharing one system, or do they read as one brand with different labels? The full case claims the token architecture let each brand's Creative Director own their visual DNA independently. If the teaser images show that distinction, the craft signal is doing exactly what it should. If they all look the same, the "five brands" claim loses its visual proof. Thirty-second check. Do it.
6. CTA
Clear and functional. Two CTAs, both labeled "Request the full case study," both linking to the full case. One in the hero, one at the closing. Placement and language appropriate for a gated case study. No issues.
What's blocking it
Four changes. None requires restructuring the page.
- Title and meta tags. Copy is in the table above. Ship it.
- Eyebrow. Replace "Consumer Fitness" with "Connected Fitness Platform" or "Multi-Brand Platform."
- One architectural-insight line in the hero section. Followership model or token architecture.
- One scope-decision clause in the closing CTA text.
The body is ready. The surfaces a hiring manager sees before deciding whether to read the body are not. Four edits. None of them hard. All of them overdue.
- Amplitude's human-agent workflow: The live Head of Product Design posting explicitly asks for someone who can define how agents and humans work together in the same workflows, which is the kind of role where Equinox+'s speed proof pairs well with the Trust essay as the agentic lead.
- Atlassian's token-architecture parallel: Atlassian's design-system team published a piece on design systems as context engines for AI-native product work, and the token-architecture language in Equinox+'s full case maps surprisingly well to how enterprise buyers are now thinking about scalable design infrastructure.
- Suno's consumer-speed signal: The Head of Product Design role at Suno asks for consumer product design at scale with speed and experimentation, which is exactly the buyer anxiety Equinox+ was built to answer if the metadata fix lands first.
- Full-case gate consistency: The site trust-surface audit flagged that full cases still return complete HTML before the client-side localStorage check, and the Equinox+ full case confirmed the same pattern on today's fetch.