Your case studies aren't bringing in buyers. Here's why.

Here's the draft we caught before launch: a case-studies page grouped under client names. Tidy. Complete. Proud of the work, and organized entirely around us.

Now walk in as a buyer. You don't arrive curious about our client roster. You arrive with one question: can these people fix my problem? What you see instead is a wall of company names you don't recognize. The internal monologue takes two seconds: “I'm not in that industry.” And you're gone, before a single story opens.

That's the quiet failure mode of most case-study pages. They tell the seller's story: who we worked with, what we're proud of. But nobody arrives asking who you worked with. They arrive asking whether you've solved their problem before.

1. Shelve by problem, not by client. Same case studies, regrouped under the business function each one serves: sales transformation, operations and workflow automation, content engine. A buyer scanning the page now self-identifies against a problem category in seconds. The proof lives where their pain is.

2. Let one engagement sit on every shelf it earned. Real engagements rarely touch one function. Each case study now carries a primary function tag and secondary ones where the work actually reached. One engagement that fixed an operations bottleneck and fed a content workflow shows up on both shelves. No duplicated effort, double the findability.

3. Name the address after the work. This is the move most sites miss. Our case-study URLs are named for the capability, not the client: /case-studies/spec-to-3d-print-workflow instead of a company name.

Why that matters now: a growing share of buyers don't browse to your site, they ask an AI assistant. “How do I automate my quoting workflow?” When that question gets fielded, a page whose address matches the shape of the question is the one that can get cited. A client-named URL structurally can't compete for that citation. It answers a question nobody asks.

We're honest about the state of this: the restructured page went live this week, and the citation and engagement impact is unmeasured. The claim is structural, not a result. We'll publish the numbers when there are numbers.

One more thing we kept, deliberately: empty categories.

Some functions on our case-studies pagehave no client story yet. The slot doesn't get padded with a thin write-up or a borrowed example. It says, in the live copy: “A client story posts when an engagement earns it.”

That's the same discipline that runs through everything we publish. We don't sell a level we haven't lived. The shelf admits what we haven't earned yet, and that admission is what makes the full shelves credible.

Open your own case-studies page, or portfolio, or testimonials section, and ask the buyer's question first: can you fix my problem?

If the page is organized around your roster, your awards, or your timeline, the proof is there but the shelving is wrong. The fix costs a fraction of writing new case studies, and every future story you add inherits the structure.

For us, this rebuild is also one plank in a longer build. Every change like this delivers value on the page today, and each one is a deliberate step toward the AI-first operation we're building in the open. Immediate value at the entrance. AI-first at the destination.

The work doesn't change. Who can find it does.

Vance and the GBT team