Marketing block

Case Study Card Grid

A grid of case-study cards that lead with the metric rather than the company name, each one linking out to the full write-up — the block a customer-stories section or a home page needed and only had a full case-study page for.

136 lineslucide-react

case study
customers
testimonials
results
proof

What's included

components/case-study-grid.tsx
Needs lucide-react

Works with

React
Next.js
Tailwind CSS
TypeScript

npx hoverlab add case-study-grid

Or over MCP, from your editor's agent — no account needed.

License

Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.

Was this useful?

Start a page with this section — add more, order them, and leave with the page source.

Preview

What changed for them

Three teams, three different problems, one number each that a colleague can check.

Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.

Source

components/case-study-grid.tsx

/**
 * <CaseStudyGrid> — a grid of case-study cards, each leading with the number.
 *
 * The catalog already has a full case-study PAGE (`case-study-page.tsx`) and
 * a table for the results section inside one (`<StatsComparison>`). What was
 * missing is the block that links a reader to several of those pages at
 * once — the "customer stories" section a marketing site puts on its home
 * page or its own `/customers` index, one card per company.
 *
 * Every card leads with the metric, not the company name or a photo,
 * because a card in a grid is competing with five others for a glance: a
 * reader deciding which of six case studies to open is scanning for the
 * biggest number, not the prettiest logo. The quote and the company come
 * after, as the evidence for the number rather than the headline.
 *
 * `window` — a measurement period, authored per card — is required by the
 * type rather than optional, for the reason `case-study-page.tsx` and
 * `customer-outcome-band.tsx` both give: "-63%" with no period attached is
 * not a checkable claim, and a component that makes the field optional
 * teaches the person filling it in that it is fine to leave out.
 *
 * The whole card is the link, matching `<BlogPostGrid>` next door — a metric
 * and a quote that are not clickable read as clickable and are the most
 * common card papercut in this catalog.
 */

import * as React from 'react'
import { ArrowRight } from 'lucide-react'

export interface CaseStudy {
  slug: string
  company: string
  industry: string
  /** The headline figure, already formatted: "68% faster", "3.2x", "$1.2M saved". */
  metric: string
  /** What the metric measures, in a few words: "Time to close the books". */
  metricLabel: string
  /** The period it was measured over — see the note above. */
  window: string
  quote: string
  attribution: string
}

export interface CaseStudyGridProps {
  heading?: string
  standfirst?: string
  studies?: CaseStudy[]
  className?: string
}

const DEFAULT_STUDIES: CaseStudy[] = [
  {
    slug: '/customers/lumen-finance',
    company: 'Lumen Finance',
    industry: 'Fintech · 210 employees',
    metric: '68% faster',
    metricLabel: 'Days to close the month',
    window: 'over two full quarters',
    quote: 'Reconciliation stopped being the thing that ate the first week of every month.',
    attribution: 'VP of Finance',
  },
  {
    slug: '/customers/northbridge-logistics',
    company: 'Northbridge Logistics',
    industry: 'Logistics · 1,400 employees',
    metric: '9 days → 2',
    metricLabel: 'Year-end audit prep',
    window: 'measured across two audit cycles',
    quote: 'Our auditors got read-only access instead of a folder of screenshots. They noticed.',
    attribution: 'Head of Compliance',
  },
  {
    slug: '/customers/hearthside-retail',
    company: 'Hearthside Retail',
    industry: 'E-commerce · 60 employees',
    metric: '31% lower',
    metricLabel: 'Cost per resolved ticket',
    window: 'over the first six months',
    quote: 'We automated the boring 80% and kept the exceptions in front of a human, on purpose.',
    attribution: 'Head of Support',
  },
]

export function CaseStudyGrid({
  heading = 'What changed for them',
  standfirst = 'Three teams, three different problems, one number each that a colleague can check.',
  studies = DEFAULT_STUDIES,
  className = '',
}: CaseStudyGridProps) {
  return (
    <section className={`mx-auto w-full max-w-7xl px-4 py-16 sm:px-6 lg:px-8 ${className}`}>
      <div className="mx-auto max-w-2xl text-center">
        <h2 className="text-balance text-3xl font-bold tracking-tight sm:text-4xl">{heading}</h2>
        <p className="mt-3 text-pretty text-muted-foreground">{standfirst}</p>
      </div>

      <ul className="mt-10 grid gap-5 sm:grid-cols-2 lg:grid-cols-3">
        {studies.map((study) => (
          <li key={study.slug}>
            <a
              href={study.slug}
              className="group flex h-full flex-col rounded-2xl border border-border/60 bg-card/80 p-6 transition-shadow hover:shadow-lg"
            >
              <div>
                <div className="min-w-0 break-words text-3xl font-bold tracking-tight text-primary tabular-nums">
                  {study.metric}
                </div>
                <div className="mt-1 min-w-0 break-words text-sm font-medium text-foreground">{study.metricLabel}</div>
                <div className="min-w-0 break-words text-xs text-muted-foreground">{study.window}</div>
              </div>

              <p className="mt-4 min-w-0 flex-1 break-words text-pretty text-sm leading-relaxed text-muted-foreground">
                &ldquo;{study.quote}&rdquo;
              </p>

              <div className="mt-5 flex flex-wrap items-end justify-between gap-x-3 gap-y-2 border-t border-border/60 pt-4">
                <div className="min-w-0">
                  <div className="truncate text-sm font-semibold transition-colors group-hover:text-primary">
                    {study.company}
                  </div>
                  <div className="truncate text-xs text-muted-foreground">{study.industry}</div>
                  <div className="truncate text-xs text-muted-foreground/80">{study.attribution}</div>
                </div>
                <span className="inline-flex max-w-full items-center gap-1 text-xs font-semibold text-primary">
                  Read the case study
                  <ArrowRight aria-hidden className="h-3.5 w-3.5 transition-transform rtl:rotate-180 group-hover:translate-x-0.5 rtl:group-hover:-translate-x-0.5" />
                </span>
              </div>
            </a>
          </li>
        ))}
      </ul>
    </section>
  )
}

Before you paste

Styling is Tailwind utility classes on semantic tokens (bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.
Install: npm i lucide-react
Every prop has a default, so it renders standalone before you wire it up.

Where it goes

Drop it at components/case-study-grid.tsx and import it where you need the section:

import { CaseStudyGrid } from '@/components/case-study-grid'

Customize

1 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.

Props

Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.

Prop	Type	Default
`heading`	`string`	`'What changed for them'`
`standfirst`	`string`	—
`studies`	`CaseStudy[]`	`DEFAULT_STUDIES`
`className`	`string`	`''`

Not using React?

The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.

case-study-grid.html

<!--
  Case Study Card Grid — markup from the Hoverlab catalog.

  This is the block rendered once to HTML and wrapped as a component
  file. It is not a port of the React source: the Tailwind classes carry
  the design, which is the part that took the work, and they are the same
  in every framework.

  This block has no interactive behaviour, so nothing is missing.
-->
<section class="mx-auto w-full max-w-7xl px-4 py-16 sm:px-6 lg:px-8 ">
  <div class="mx-auto max-w-2xl text-center">
    <h2 class="text-balance text-3xl font-bold tracking-tight sm:text-4xl">What changed for them</h2>
    <p class="mt-3 text-pretty text-muted-foreground">Three teams, three different problems, one number each that a colleague can check.</p>
  </div>
  <ul class="mt-10 grid gap-5 sm:grid-cols-2 lg:grid-cols-3">
    <li>
      <a href="/customers/lumen-finance" class="group flex h-full flex-col rounded-2xl border border-border/60 bg-card/80 p-6 transition-shadow hover:shadow-lg">
        <div>
          <div class="min-w-0 break-words text-3xl font-bold tracking-tight text-primary tabular-nums">68% faster</div>
          <div class="mt-1 min-w-0 break-words text-sm font-medium text-foreground">Days to close the month</div>
          <div class="min-w-0 break-words text-xs text-muted-foreground">over two full quarters</div>
        </div>
        <p class="mt-4 min-w-0 flex-1 break-words text-pretty text-sm leading-relaxed text-muted-foreground">“Reconciliation stopped being the thing that ate the first week of every month.”</p>
        <div class="mt-5 flex flex-wrap items-end justify-between gap-x-3 gap-y-2 border-t border-border/60 pt-4">
          <div class="min-w-0">
            <div class="truncate text-sm font-semibold transition-colors group-hover:text-primary">Lumen Finance</div>
            <div class="truncate text-xs text-muted-foreground">Fintech · 210 employees</div>
            <div class="truncate text-xs text-muted-foreground/80">VP of Finance</div>
          </div>
          <span class="inline-flex max-w-full items-center gap-1 text-xs font-semibold text-primary">Read the case study<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-arrow-right h-3.5 w-3.5 transition-transform rtl:rotate-180 group-hover:translate-x-0.5 rtl:group-hover:-translate-x-0.5" aria-hidden="true"><path d="M5 12h14"></path><path d="m12 5 7 7-7 7"></path></svg></span>
        </div>
      </a>
    </li>
    <li>
      <a href="/customers/northbridge-logistics" class="group flex h-full flex-col rounded-2xl border border-border/60 bg-card/80 p-6 transition-shadow hover:shadow-lg">
        <div>
          <div class="min-w-0 break-words text-3xl font-bold tracking-tight text-primary tabular-nums">9 days → 2</div>
          <div class="mt-1 min-w-0 break-words text-sm font-medium text-foreground">Year-end audit prep</div>
          <div class="min-w-0 break-words text-xs text-muted-foreground">measured across two audit cycles</div>
        </div>
        <p class="mt-4 min-w-0 flex-1 break-words text-pretty text-sm leading-relaxed text-muted-foreground">“Our auditors got read-only access instead of a folder of screenshots. They noticed.”</p>
        <div class="mt-5 flex flex-wrap items-end justify-between gap-x-3 gap-y-2 border-t border-border/60 pt-4">
          <div class="min-w-0">
            <div class="truncate text-sm font-semibold transition-colors group-hover:text-primary">Northbridge Logistics</div>
            <div class="truncate text-xs text-muted-foreground">Logistics · 1,400 employees</div>
            <div class="truncate text-xs text-muted-foreground/80">Head of Compliance</div>
          </div>
          <span class="inline-flex max-w-full items-center gap-1 text-xs font-semibold text-primary">Read the case study<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-arrow-right h-3.5 w-3.5 transition-transform rtl:rotate-180 group-hover:translate-x-0.5 rtl:group-hover:-translate-x-0.5" aria-hidden="true"><path d="M5 12h14"></path><path d="m12 5 7 7-7 7"></path></svg></span>
        </div>
      </a>
    </li>
    <li>
      <a href="/customers/hearthside-retail" class="group flex h-full flex-col rounded-2xl border border-border/60 bg-card/80 p-6 transition-shadow hover:shadow-lg">
        <div>
          <div class="min-w-0 break-words text-3xl font-bold tracking-tight text-primary tabular-nums">31% lower</div>
          <div class="mt-1 min-w-0 break-words text-sm font-medium text-foreground">Cost per resolved ticket</div>
          <div class="min-w-0 break-words text-xs text-muted-foreground">over the first six months</div>
        </div>
        <p class="mt-4 min-w-0 flex-1 break-words text-pretty text-sm leading-relaxed text-muted-foreground">“We automated the boring 80% and kept the exceptions in front of a human, on purpose.”</p>
        <div class="mt-5 flex flex-wrap items-end justify-between gap-x-3 gap-y-2 border-t border-border/60 pt-4">
          <div class="min-w-0">
            <div class="truncate text-sm font-semibold transition-colors group-hover:text-primary">Hearthside Retail</div>
            <div class="truncate text-xs text-muted-foreground">E-commerce · 60 employees</div>
            <div class="truncate text-xs text-muted-foreground/80">Head of Support</div>
          </div>
          <span class="inline-flex max-w-full items-center gap-1 text-xs font-semibold text-primary">Read the case study<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-arrow-right h-3.5 w-3.5 transition-transform rtl:rotate-180 group-hover:translate-x-0.5 rtl:group-hover:-translate-x-0.5" aria-hidden="true"><path d="M5 12h14"></path><path d="m12 5 7 7-7 7"></path></svg></span>
        </div>
      </a>
    </li>
  </ul>
</section>

This is rendered HTML, not a translation of the React source. The Tailwind classes carry the design and work in any framework.
It is one frame: the component in its initial state, with no props applied beyond the defaults.
Requires Tailwind, and the design tokens the classes reference (bg-card, text-muted-foreground, and so on). The template ZIPs ship a globals.css that defines them.

What each framework gets across the whole catalog — effects convert properly; this rung is markup.

For AI

The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.

See the prompt

11 more blocks in Content & Blog

All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.

Browse Content & Blog

Shipping one commercially

Copying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.

A commercial licence for everything in the catalog
Unlimited bundle exports, in Vue, Svelte and Tailwind
One payment — no subscription, nothing to renew

Pro — $79 once

What shipped recently

Every release, in plain language.

Dashboard blocks
v2.4.0Jul 14, 2026
- addedTwelve dashboard and data-table sections
- addedKeyboard navigation across every table block
- changedSidebar collapses below 1024px instead of 768px
Accessibility pass
v2.3.1Jun 2, 2026
- fixedFocus ring clipped inside overflow containers
- fixedMarquee ignored prefers-reduced-motion
Theming
v2.3.0May 19, 2026
- addedToken generator with contrast validation
- changedAll blocks now read semantic colour tokens

Release Timeline

A dated changelog on a vertical rail with added/changed/fixed tags and machine-readable <time> values.

Content & Blog145 linesNo deps13 Sept

Roadmap

What is done, what is being built, and what is next.

Shipped

Marketing sections
Heroes, pricing, FAQ, footers.
Dark mode tokens
Every block reads semantic colours.

In progress

Dashboard blocksQ3 2026
Shells, tables, settings.
CLI installQ3 2026
Add a block straight to your repo.

Planned

Full page layoutsQ4 2026
Composed screens, not sections.
Starter templatesQ4 2026
Multi-page projects, ready to deploy.
Vue and Svelte ports2027

Public Roadmap Columns

Shipped / in progress / planned in three columns, with status carried by icon as well as colour.

Content & Blog122 lines1 dep2 Sept

From the blog

Engineering

How we run incident reviews nobody dreads

Blameless is easy to say and hard to schedule. The template, the timebox, and the one question we ask before anyone opens a dashboard.

Priya RamanJul 8, 20269 min read

Blog Index Grid

A featured post at full width above a card grid, with drawn covers built from tokens — a blog index with no image pipeline and no broken-thumbnail state.

Content & Blog188 lines1 dep

Engineering

The day we deleted 40,000 lines of feature flags

Flags are borrowed complexity — this is what it cost to pay ours back, and the two rules that keep the debt from growing again.

Priya Raman

Staff Engineer · July 21, 2026 · 12 min read

The pull request was titled “remove stale flags, part 1 of 8” and it deleted more code than the previous quarter had added. Our flag service listed 312 active flags; production telemetry showed 41 of them had evaluated to the same value for every user since at least January. The rest were split roughly evenly between experiments nobody remembered starting and kill switches for services we had already decommissioned.

“A feature flag is a loan. The interest is every engineer who has to reason about both branches forever.”

Article Header & Byline

Kicker, headline, standfirst, byline and share row, with the opening prose and a pull quote included — the type scale of a post, decided once instead of per-article.

Content & Blog171 lines1 dep2 Sept

The people building it

A small team spread across four time zones, shipping every week since 2023.

Priya Raghavan
Co-founder & CEO
Previously led platform at a payments unicorn; still reviews PRs.
Marcus Okafor
Co-founder & CTO
Wrote the first commit in March 2023 and the incident runbook the week after.
Elena Sokolova
Head of Design
Believes every empty state deserves as much care as the dashboard.
Tom Whitfield
Staff Engineer
Owns the sync engine; measures success in p99s, not features.
Aisha Diallo
Product Manager
Turns forty support tickets a week into a roadmap the team believes in.
Daniel Kim
Developer Advocate
If you found us through a conference talk in 2026, it was probably his.

Team Grid

An about-page team section on initials avatars rather than photos, so shipping it never waits on headshots and there is no broken-image state to design.

Content & Blog166 lines1 dep

Open roles

We’re hiring across three teams. Every role lists the real salary range — no “competitive”.

Engineering3 openings

Design2 openings

Go-to-market2 openings

Nothing that fits? We read every speculative application — jobs@hoverlab.dev.

Careers Openings Board

Openings grouped by department with location, type and salary on every row — candidates self-select by craft first, and a flat list makes them scan for it.

Content & Blog186 lines1 dep10 Sept

Docs navigation

Authentication

Every request to the Acme API is authenticated with a bearer token. This page covers creating a key, storing it safely, and rotating it without downtime.

Acme issues two kinds of keys. Secret keys (prefixed sk_live_) can read and write everything in your project and must only ever live on a server. Publishable keys (prefixed pk_live_) are safe to ship in a browser bundle and can only create client sessions.

Keys are scoped to a project, not to your account. Deleting a project revokes its keys immediately; removing a teammate does not, so treat offboarding as a reason to rotate.

Creating an API key

Create a key from the dashboard under Settings → API keys, then pass it as a bearer token on every request:

curl https://api.acme.dev/v1/projects \
  -H "Authorization: Bearer $ACME_API_KEY"

Note: the full secret is shown once, at creation. Acme stores only a hash, so a lost key cannot be recovered — it can only be rotated.

Rotating keys

Rotation is overlap, not replacement: create the new key, deploy it everywhere, and only then revoke the old one. Both keys stay valid during the window, so a slow rollout never turns into an outage.

Three-Column Docs Frame

Sidebar, article and on-this-page rail — each column answers a different question, and they collapse on mobile in the order that keeps the article alive.

Content & Blog290 lines1 dep13 Sept

GET/v1/projects/{project_id}/deployments

List the deployments for a project, newest first.

Parameters

Name	Type	Required	Description
project_id	string	Required	The project to list deployments for. Passed in the path.
status	string	Optional	Filter by state: building, ready or failed.
limit	integer	Optional	Page size, 1–100. Defaults to 20.
cursor	string	Optional	Opaque cursor from a previous page’s next_cursor.

Request

curl "https://api.acme.dev/v1/projects/prj_8kq2/deployments?limit=2" \
  -H "Authorization: Bearer $ACME_API_KEY"

Response200 OK

{
  "data": [
    {
      "id": "dep_9f2c1a",
      "status": "ready",
      "branch": "main",
      "created_at": "2026-08-12T09:41:00Z"
    },
    {
      "id": "dep_8e1b0d",
      "status": "failed",
      "branch": "fix/session-ttl",
      "created_at": "2026-08-11T17:03:12Z"
    }
  ],
  "next_cursor": "dep_7d0a9c"
}

API Endpoint Reference

Method badge, path, parameter table and a request/response pair kept side by side — an example request whose response is a scroll away gets pasted blind.

Content & Blog237 lines1 dep2 Sept

Package Manager Code Tabs

One install command behind npm/pnpm/yarn/bun tabs with a working copy button — every reader uses exactly one package manager, so showing all four wastes three lines.

Content & Blog152 lines1 dep11 Sept

Aisling Moreau

Principal engineer — platform, performance and the unglamorous parts

Print or save as PDF

Ten years building systems that other engineers depend on, mostly by removing things. I am at my best on a team that has outgrown its first architecture and has to keep shipping while it changes. Looking for a principal or staff role where the hard problem is technical rather than political.

Experience

Principal Engineer, Platform · Northwind
Mar 2023 — Present · Remote
Series B logistics platform, 40 engineers, one Rails monolith and four Go services.
- Cut p95 checkout latency from 2.4s to 610ms by deleting a caching layer rather than adding one — the invalidation cost more than the reads saved.
- Led the migration off a managed search product onto Postgres full-text, against a hard contract-expiry date. Saved $310k a year with no change to result quality anyone could measure.
- Wrote the on-call handbook and cut pages per engineer per week from 11 to 2, mostly by deleting alerts nobody had ever acted on.
Senior Software Engineer · Contoso Health
Jun 2019 — Feb 2023 · Dublin
Patient records for 60 clinics. Regulated, audited, and slow to change by design.
- Rebuilt the appointment booking flow to meet WCAG 2.1 AA before the deadline the procurement contract set. It passed audit first time, which nothing else that year did.
- Introduced contract tests between the scheduling service and three consumers, ending a class of release that broke a downstream team every quarter.
Software Engineer · Umbra Labs
Sep 2016 — May 2019 · Dublin
- Second engineer. Built the billing integration that the company ran on unchanged for six years.

Skills

TypeScript · Go · Postgres · React · Next.js · Terraform · OpenTelemetry · WCAG 2.2 AA · Incident command

Education

BA (Mod) Computer Science — Trinity College Dublin — First Class Honours2012 — 2016

Selected writing and talks

“The cache we deleted” — SRECon EMEA, main track2025
“Accessibility as a procurement requirement” — Write the Docs2024

Résumé Document

A CV as a document rather than a timeline of cards — one column, dates on the end edge, and a print layer that puts it on paper without a separate PDF to keep in step.

Content & Blog347 lines1 dep

Episode 3

4:18 / 12:04

Profiling, end to end

Where the time actually goes

48,219 views · Episode 3 of 7 · Published 4 March

We take a page that feels slow and find out what is actually slow about it — with a profiler open the whole time, and no guessing. The fix at the end is two lines; finding it is the other eleven minutes.

Video Player Shell

The watch screen with no playback in it: a ratio-locked stage, a control bar drawn down to the buffered layer, and an up-next rail. Drop a video element in and wire your own player.

Content & Blog327 lines1 dep