AI Visibility Case Studies — Measured in the Index

AI Visibility Case Studies: Movement in the Shortlist Index

There are no client case studies yet. WebPossible published the first edition of the AI Shortlist Index in September 2026 and Shortlist, the practice, has no completed engagements to report. This page exists so the rules for reporting them are public before the first one is.

How a case study will be reported

Movement measured in the Index. A case study is the client’s row at the baseline edition, the row at each edition after, and the work done in between. Mention rate per engine, shortlist rank, position score, consistency, engine spread, and source dependency, exactly as they appear on the public row, because they come from the same run files.

Before and after rows, side by side. The baseline is the edition named in the SOW. The after is whatever the next editions show, up or down. A Sprint that did not move the row is reported as a Sprint that did not move the row, with the sources entered and our reading of why it did not.

Disclosed as Shortlist clients. From the first edition after signing, a client’s Index row carries a disclosure line. A reader of the ranking table knows who is paying WebPossible before reading the number. Anonymized case studies will not be published, because a case study you cannot check against the Index is a testimonial.

Never affecting placement. Paying WebPossible never affects Index placement. The Index measures what AI engines say. Shortlist clients buy the work that earns a position, not the position. Corrections and re-checks for clients follow the same publication policy as for anyone else, and measurement is never edited on request, including a client’s request.

The public record until then

The live Index rows are the record. The September 2026 maintenance category holds one completed ChatGPT run, in which Property Meld was named first and Latchel second on the 300-door prompt, and reddit.com was the most cited domain. Neither is a client. The Property Meld row shows what a row looks like with data in it, and the category page shows the five tracked vendors that run did not name. When a client appears in any category, that is where the movement will show first, disclosed, before it shows here.

What the first case studies will be

Three founding clients, one per Index category, on a Sprint at a founding rate in exchange for a named public case study. Each one gets a Shortlist Audit first, then the 90-day Sprint scoped to it. The Index measures the result. If the result is nothing, this page will say so with the row beside it. The practice hub explains the products, and the contact page is where to ask about the founding rate.

Questions

Why publish a case studies page with no case studies?

Because the rules for reporting them should exist before the first client does, so nobody can accuse us of writing the rules to fit the result. The rules are on this page. The results will be on the Index.

Will clients be identified?

Yes, on their Index rows, as Shortlist clients, from the first edition after they sign. A case study names the client, the category, the baseline edition, and the editions after. Anonymized case studies will not be published.

What if a client's row moves down?

It is reported the same way. The Index measures what the engines said; it does not adjust for who is paying. A Sprint that did not move the row is a public fact on the row, and the before/after report says why we think it did not.

Is there a founding-client offer?

Three vendors, one per Index category, get a Sprint at a founding rate in exchange for a named public case study measured by the Index. Ask on the contact form.

Get your row explained — $3,500

Seven days. Twenty-five prompts across four engines. The cause behind your row and a 90-day fix. Ryan replies with an agreement and an invoice; no call required.