dGENIX
Log inJoin waitlist
AuthorityNovember 6, 2026 · 7 min read · dGENIX Team

One job, one page, one lesson: showing expertise with short case studies

One job, one page, one lesson: showing expertise with short case studies

A case study is the strongest proof that you know your trade, for customers, Google and AI assistants. How to turn every finished job into a short case study without losing an afternoon.

Updated October 28, 2026Lees in het Nederlands
Share

New to this topic? Start with Building authority as a solo business: why a small company can beat a big brand

The short answer

A short case study describes one job in four parts: the customer's situation, what you did, what it delivered and what you learned. Five to eight hundred words, with a few photos and, where possible, a figure you actually measured. Such a page convinces a hesitant customer, and for Google and AI assistants it is proof that you have experience with exactly that kind of work. Have GENI write a first draft from your notes after every job, and you finish it.

Why case studies work

Anyone can write on their site that they are experienced. A case study shows it. A visitor who wonders whether you can solve their problem wants to know whether you have done something like it before. A case study with a situation similar to theirs answers that question better than any promise.

The same goes for search engines. When judging a site, Google looks at experience and expertise: did this writer actually do it? A case study with concrete details, photos of your own work and an honest lesson is the strongest signal of that. More on that assessment in E-E-A-T for small business owners.

And AI assistants that need to recommend a business look for sources that show a business can deliver. A page with a concrete job in the questioner's location and trade is exactly that kind of source.

The structure of a short case study

1. The situation

Who was the customer, what was going on, why did they look for help? Two or three sentences. Recognisable for a reader with the same problem.

"A bakery with three shops in the Utrecht region got the same questions about allergens every day, by phone and email. Shop staff had to answer them in between serving customers."

2. What you did

The approach, in steps. Not everything, but the choices that mattered. Why this solution and not another?

3. What it delivered

The result, ideally with a figure you actually measured. No rounded promises, but what you saw. If you have no figure, describe what changed in the customer's work.

4. What you learned

One honest lesson. Something that was disappointing, something you would do differently next time. This is the part that makes a case study credible, and the part almost nobody writes.

Images

Photos of the real work, before and after if possible. No stock photos. A photo of your own engineer on the actual job says more than a perfect picture from a website.

Customer permission

Always ask permission before naming a customer. If the customer does not want to be named, describe them in general terms: "a bakery with three shops in the Utrecht region". That is just as recognisable for the reader. Never mention details the customer does not want to share, such as revenue or internal problems.

How GENI helps

Writing is usually where it gets stuck. After a job you do not feel like writing a page. Have GENI make the first draft:

"Write a short case study of at most seven hundred words about the bakery job. Use my notes and the quote in this customer's folder. Structure: situation, what we did, what it delivered, what we learned. Do not name the customer. Write in my tone."

GENI reads your notes and documents, if you have connected Google Drive or Google Docs, and prepares a draft. You check the facts, add the lesson and choose the photos. You always write the lesson yourself: it comes from your experience, not from a document.

Make it a fixed step in wrapping up a job. Then after a year you have twenty case studies without it ever becoming a project.

Where to publish case studies

  • On a separate page per case, with a title that names the problem: "Answering allergen questions for a bakery with three shops".
  • Linked from your service pages. A case belongs with the service you delivered.
  • In your Business Profile, as a post with a photo and a link.
  • On LinkedIn, as a short post that opens with the lesson.

How to spread such a piece across channels is covered in AI content repurposing.

Case studies and the Authority Engine

Case studies are one building block of authority. Others are mentions on other sites, reviews and articles that show your knowledge. The Authority Engine in dGENIX helps you track where you stand and what is still missing. Why mentions without bought links pay off more is in earning mentions without buying links.

Case studies as a source for AI assistants

A case study is also a source AI assistants can cite. Someone who asks which business in their region has experience with a certain kind of job more often gets an answer naming a business that described exactly such a job. So put the location, the type of customer and the problem clearly in the title and first paragraph.

Frequently asked questions

How long should a case study be?

Five to eight hundred words is enough. Short and concrete beats long and general.

Do I need to mention a figure?

Only if you actually measured it. A made-up percentage is easy to see through. Otherwise describe what changed.

What if a job did not go entirely well?

That can be a strong case study, if you honestly explain what you did to fix it.

Where do I start?

dGENIX is in early access. Join the waitlist, or first read building authority as a sole trader.

Ready to get started?

Create a free account and your assistant is active in 5 minutes.

Start free →

Related articles

Earning mentions without buying linksEarning mentions without buying linksWhy automating cold outreach backfires (and what works instead)Why automating cold outreach backfires (and what works instead)Building authority as a solo business: why a small company can beat a big brandBuilding authority as a solo business: why a small company can beat a big brand

In the documentation

Authority EngineDocumentationCMS PublisherDocumentationThe 5 Growth EnginesDocumentation

Get started

Authority EngineFrom measuring to publishing.SEO EngineRank higher on Google.
← Back to blog