FREEFirst project with us? Your landing page design is on the house.See the offer

Process

How to structure a case study page that helps close deals

A case study page structure for B2B sites: problem, client, what changed, proof, quote and next step, plus the CMS setup in Webflow and Astro and honest schema.

By Abdul QuadirUpdated 2026-11-127 min read
TL;DR
  • A case study page answers one buyer question: have you solved this for a team like mine?
  • Use one order: the problem, who the client is, what changed, the proof, a quote, and one next step.
  • Only publish numbers the client agreed to share and you can check. Build facts work when results are not public.
  • Set it up as a CMS collection with clear fields so every case looks the same and is fast to add.
  • Use Article markup if you like, but do not add star review markup for quotes about your own company.

The short answer

A case study page that helps close deals reads in this order: a headline that names the problem in the buyer's words, a short line on who the client is, the problem, what you changed, the proof, a quote from the client and one clear next step. Keep each part short so a buyer can scan the page in a minute and a sales rep can send it after a call.

Put it in a CMS collection so every case follows the same structure. And only publish results you can stand behind.

Who reads a case study page

Most people who open a case study are close to a decision. They are comparing two or three options and want to know if you have done this before, for a team like theirs. Some arrive from your work page, some from a link a sales rep sent, some from search.

That shapes the page. They do not need your process in detail. They need to see their own problem, the fix and a reason to believe it worked.

The sections, in order

  1. Headline. The problem and the change, in plain words. For example: "Crumb moved 60 pages off WordPress without losing its blog traffic." Crumb is a made-up company we use for examples.
  2. Who the client is. One or two lines: what they do, their size or stage, their market. Add the logo if you have permission.
  3. The problem. What was slow, broken or blocked, and what it cost the team. Use the client's own words if you can.
  4. What changed. What you did, in three to five points. Name the work, not the hours.
  5. Proof. Screenshots, the live site, facts about the build and results the client agreed to share.
  6. Quote. A real client, named, saying something specific.
  7. Next step. One button that fits the reader, such as "Book a call about your migration".

Under the main story, add a short facts strip (industry, services, platform, timeline) and links to similar cases. Buyers often open two or three.

Proof without making things up

The weakest case study is the one with numbers nobody can check. Buyers notice, and so do the clients named on the page. Use only what is true and shareable:

  • Results the client approved. If a number goes on the page, get the client's OK in writing and keep the source.
  • Build facts. Page count, templates, integrations, the stack, how long it took. These are true and easy to check.
  • Screens and the live site. A real screenshot or a link to the live page says more than a mock up.
  • What the team can do now. "The marketing team publishes landing pages without a developer" is a real change, even without a percentage.

This is how we run our own case studies: until a client confirms results we can publish, the stat row shows the build facts instead.

The quote

A good quote is specific and named. "Great to work with" tells a buyer nothing. "We launch a new landing page in a day now, without asking a developer" tells them what they would get.

  • Use the client's real name, role and company, with permission.
  • Place it next to the proof it supports, not at the very bottom.
  • Keep it to two or three sentences. Trim, but do not change the meaning.
  • A short video from the client is even stronger, if they are happy to record one.

One next step

End with one action that matches what the reader just saw. A migration case ends with a migration call. A care plan case ends with the care plan. Under it, link to the matching service page and two similar cases.

Avoid five buttons in a row. One clear step works better than a menu. The same idea runs through a good homepage, which we cover in how to structure a B2B homepage.

Setting it up in Webflow CMS

Make a Case studies collection and give every section its own field, so each case looks the same and editors cannot skip a part. The field types below are from Webflow's Collection fields help page:

FieldType
HeadlinePlain text
ClientReference (to a Clients collection with name, logo, site)
IndustryOption
ServicesMulti-reference (to your Services collection)
Problem, What changed, ResultsRich text
Hero image and screensImage and Multi-image
QuoteReference (to a Testimonials collection)
Live siteLink
Show resultsSwitch, off until the client approves the numbers

Webflow says a Switch field can drive conditional visibility, so the results block stays hidden until it is on. References mean a quote or a client logo lives in one place and shows on every page that uses it.

Setting it up in Astro

In Astro, make a content collection for case studies with a schema. Astro checks every entry against the schema, so a case missing its problem or quote fails the build instead of going live half done.

// src/content.config.ts
import { defineCollection, reference } from 'astro:content';
import { glob } from 'astro/loaders';
import { z } from 'astro/zod';

const cases = defineCollection({
  loader: glob({ base: './src/content/cases', pattern: '**/*.json' }),
  schema: z.object({
    headline: z.string(),
    client: z.string(),
    problem: z.string(),
    changes: z.array(z.string()),
    quote: reference('quotes'),
    showResults: z.boolean().default(false),
  }),
});

export const collections = { cases };

Then build one page per case with getStaticPaths() and getCollection('cases'). reference() links each case to a quote in its own collection, much like a Reference field in Webflow.

Schema, only where it is true

Structured data helps search engines and AI tools read the page, but only add what is true.

  • Article markup fits a case study. Google's Article guide has no required properties and recommends headline, image, author, datePublished and dateModified.
  • BreadcrumbList shows where the page sits on your site.
  • No star ratings for your own quotes. Google's review snippet guidelines say that when a business controls the reviews about itself, its pages with Organization or LocalBusiness markup are not eligible for review stars.

Our schema generator builds markup you can paste in.

What to do next

Pick your best project and rewrite it in the order above: problem, client, change, proof, quote, next step. Send it to the client for approval before it goes live. Then turn the structure into a CMS collection so the next case takes an hour, not a week.

We build case study templates in Webflow and Astro as part of our site work. See our work or tell us about your site.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Astro

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

A headline with the problem, who the client is, the problem, what changed, proof, a client quote and one next step, plus a short facts strip and links to similar cases.

Short enough to scan in a minute. Three to five points for what changed, two or three sentences per section and one quote is usually enough.

Use true build facts instead: page count, stack, integrations, timeline and what the team can do now. Never invent numbers.

Create a Case studies collection with a field per section, Reference fields for the client and quote, and a Switch to hide results until they are approved.

Not for quotes about your own company. Google says self-serving reviews on Organization or LocalBusiness pages are not eligible for review stars. Article markup fits better.

At the end of the story, as one button that fits the case, such as a migration call after a migration case.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.