Current State — June 30, 2026
The live teaser runs four sections: a full-viewport hero, an app showcase with desktop iframe and phone mock, a thirteen-group component/design-system grid carrying roughly 1,100 words, and a closing CTA block. Two "Request the full case study" links point to the gated page. Total visible content: around 1,500 words.
The work inside this page is strong. The positioning around it is costing you both buyers.
Here's the audit across six dimensions, evaluated at scan speed through the lens of a hiring manager at Gusto and one at Headway.
1. Page Title — Domain Label
Currently: "Thermo Fisher / mySupply — 0→1 Pharma Supply Chain, $20M+ Margin — Juno Chen."
A Gusto hiring manager sees "Pharma Supply Chain" in a link preview and skips. A Headway hiring manager does the same. They are hiring for someone who can build a regulated platform from zero, drive adoption across resistant partners, and design systems that catch exceptions before they become expensive. That is exactly what this case study proves. The title hides it behind a domain label.
Replace with:
"Thermo Fisher — 0→1 Regulated Platform, 6 Enterprise Partners, $20M+ Margin — Juno Chen"
Kill "mySupply." Kill "Pharma Supply Chain." The title is a browser tab, a Slack preview, a link in a recruiter's email. It needs to trigger recognition for regulated-platform buyers in the half-second before they decide whether to click.
2. First-Screen Structural Insight — Right Diagnosis, Wrong Frame
Currently: The H1 reads "The supply chain six partners never had." The hero intro establishes that no platform existed, six partners ran nine sites on spreadsheets and phone calls, exceptions surfaced at the delivery gate, and catching them there cost 3–5× more than catching them a week earlier.
The exception-at-the-gate diagnosis is the single most transferable insight on this page. Gusto's posting explicitly asks for someone who can represent "uncertainty, surfacing errors gracefully, and preserving user agency when automation fails in high-stakes contexts." Headway wants someone who builds "predictable insurance experience" and makes operations efficient. Moving exception detection upstream is the design leadership move that maps to both roles.
The H1 buries it. "The supply chain six partners never had" forces a Gusto buyer to translate your problem into their problem. At scan speed, they won't.
Replace the H1 with:
"Six partners. Nine sites. Every exception caught at the gate instead of a week earlier."
Lead with the structural diagnosis. Let the supply chain context surface naturally in the hero intro copy below, where the reader is already committed to reading.
3. Outcome Proof — Partially Visible, Key Metric Absent
Currently: The hero brief sidebar shows $20M+ margin opportunity, 100% partner adoption, and 83% IRR. These are above the fold.
Good placement. Two problems.
First: the meta description references a 42% overhead-reduction figure, but the live teaser HTML does not surface an overhead-reduction metric on the page itself. If you have a verified overhead-reduction number from this engagement, it belongs in the hero brief. Overhead reduction is the metric that translates most directly to both buyers. Gusto's posting talks about making "payroll work disappear." Headway's posting talks about operational efficiency. A concrete overhead-reduction figure makes a Headway hiring manager stop scrolling. Get it on the first screen. If it requires the gated case to substantiate, add it with a "(full case)" note. But get it visible.
Second: "100% partner adoption" sounds like marketing copy. Reframe to "6/6 partner adoption." The fraction reads like a mandate you completed. The percentage reads like a slide deck.
Recommended hero brief line:
"$20M+ margin · 6/6 partner adoption · 83% IRR" — plus the overhead-reduction number if it holds.
4. Craft Signal — Strong Artifacts, Scan-Speed Placement Risk
Currently: The app showcase includes a functional desktop iframe with real navigation (Dashboard, Orders, Batch Tracker, Forecasts, Capacity) and a phone mock with batch detail, timeline, and stage checklist. Below that, thirteen component groups cover color tokens, status badges, buttons, type scale, KPI cards, partner scorecards, program health, delivery trends, exception summaries, forecast visualizations, site capacity heatmaps, batch pipelines, and regulatory constraint copy.
The interactive iframe is exceptional. A live product surface in a portfolio teaser is rare and immediately credible. Both buyers will register this as shipped work, not spec.
For Headway specifically: the design-system artifacts map directly to their posting's requirement for someone who has built and shipped "design systems across a variety of systems." Thirteen component groups with tokens, badges, type scale, and KPI cards is proof.
For Gusto specifically: the exception summary component ("LATE and AT RISK are the money-costing states, the red slice is the number users care about") demonstrates the judgment their posting describes as "setting the quality and judgment standard for all design work."
The artifacts themselves need no changes. The risk is placement: do they register before a buyer scrolls past? The hero's CSS sets a minimum height near full viewport, and the app showcase runs 820px tall below it. On most screens, the desktop iframe begins at the very bottom of the first viewport. A fast scanner may catch the top edge of the browser mock, but the phone mock with its batch timeline and stage checklist sits well below the fold. A Gusto buyer who scans the hero, doesn't connect "supply chain" to their problem, and bounces never sees the craft proof. Fixing the H1 and title (Sections 1 and 2) is what buys the extra scroll that lets the craft artifacts do their work.
5. Density — The Component Grid Overwhelms the Teaser
Currently: The component grid runs thirteen labeled groups with descriptive rationale copy. At roughly 1,100 words, it accounts for over 70% of the page's total content.
This is a teaser. Its job is to establish mandate credibility and drive the viewer to request the full case. The component grid is doing the work of the full case study inside the teaser frame. A Gusto or Headway buyer scanning this page hits the grid and faces a wall. Some will read it as thoroughness. Others will lose the thread and never reach the closing CTA.
Cut to five or six groups. Keep Color Tokens, Status Badges, KPI Card, Exception Summary, and Partner Scorecard. Collapse the rest into a single "additional system components" row with minimal labels. Move the descriptive rationale copy into the gated case. Show enough system to prove you built one. Save the documentation for the full study.
This also solves a buried-signal problem. The regulatory constraints group (GDP & cGMP) currently sits thirteenth in the grid. For both buyers, regulated-environment proof should be visible early. Move one regulatory sentence into the app showcase label:
"Every design decision downstream of GDP and cGMP regulatory regimes."
That sentence, visible in the second screen alongside the live product surface, does more for a Headway buyer evaluating "insurance platform" experience than the full regulatory component group does at position thirteen. The app showcase is the natural home because the hero intro is already carrying the structural diagnosis per Section 2.
6. CTA — Clear Copy, Gate Friction Unknown
Currently: "Request the full case study" appears in the hero and closing, linking to cs-02-supply-chain.html.
Placement correct. Repetition correct.
"Request" carries transactional weight. A CTA at this level should open a conversation. The closing section already teases "five failure modes, five modules, zero spreadsheets." Pull that language into the CTA itself:
"Read the full case — five failure modes, five modules, and the research that shaped each →"
The destination URL includes "supply-chain" in the slug. If you're reframing the teaser away from domain language, the URL should follow. cs-02-thermo-fisher.html is cleaner.
One thing I can't evaluate from the live teaser: what happens after the click. Whether the gated page requires an email, a form, a calendar booking, or something else determines whether a Director+ buyer completes the action. If it's a multi-field form, that's too much friction for someone scanning portfolios at 10 PM. An email-only gate or a single-click request is appropriate for this level. If you're running a heavier gate, simplify it. A Gusto design manager or Headway design director will not fill out four fields to see a case study.
Priority Order for This Week
Most hiring managers are offline Thursday through the weekend for the Fourth. Anything you ship by Wednesday evening is what sits in inboxes and bookmarks through July 6.
Sequence accordingly:
- Title and H1. Fifteen minutes. Largest scan-speed impact for both buyers.
- Reframe "100%" to "6/6." Two minutes. Immediate credibility gain.
- Add a verified overhead-reduction metric to the hero brief, if you have one that holds.
- Move one regulatory-proof sentence into the app showcase label.
- Trim the component grid to five or six groups. Takes longer, but fixes the density problem that risks losing both buyers before the CTA.
- Warm the CTA copy and simplify the gate. Low effort on copy, variable effort on gate mechanics, compounds over time.
The structural diagnosis in this case study transfers cleanly to both roles. So do the system artifacts and the regulated-environment proof. Right now the page makes the buyer do the translation work. You should do it for them before Wednesday.
- Gusto's exact evaluation language: Their Senior Product Design Manager, Payroll posting asks for experience "representing uncertainty, surfacing errors gracefully, and preserving user agency when automation fails in high-stakes contexts," which is nearly a description of the Thermo Fisher exception-detection work.
- Headway's second design director role: The Core Insurance & Design Systems posting explicitly combines insurance operations, design systems, and internal tooling, making it the tighter Thermo Fisher match compared to the Provider Experience role.
- Full-case gating vulnerability: The gated case at
cs-02-supply-chain.htmlcurrently delivers full HTML before a client-side redirect fires, which means the "Request the full case study" CTA promises a gate that doesn't technically exist. - Ramp's agentic CX signal: Their Product Manager, Agentic CX posting defines how AI agents and human operators divide work, and the exception-upstream framing from this Thermo Fisher case maps directly to that human-judgment-in-the-loop question.