Proof Without Hype: Writing Case Studies and Numbers People Believe

When we wrote the ARKIELLO homepage, the first draft had a neat statistic in it: “7+ platforms”. It looked good. Before it went live, we asked a plain question: seven of what, counted how? Once we counted every project the work actually covered, the honest number was different, and much bigger. The homepage now says 1,000+ projects, because that is what the count supports.

The lesson was less about the number than the habit. Every claim on a website is a small promise, and visitors sense an empty one better than most businesses expect. This guide is part of our website copywriting and brand storytelling service, and it is the third chapter of the story. The homepage makes the promise and the About page introduces the guide. Proof is what makes both believable.

Why vague proof quietly costs enquiries

“Trusted by hundreds of happy clients.” “Proven results.” “Industry-leading.” Readers have seen these phrases so often that they skim past them. Worse, unsupported claims can make a careful buyer more suspicious. Proof works when a sceptical reader could check it.

Specific proof has a few traits:

• It names something: a project, a place, a measurement, a person who agreed to be quoted.
• It has a date or a context, so the reader knows when and where it was true.
• It admits its limits instead of implying more than it shows.

Date your numbers and say how they were measured

Our homepage has a row headed “Measured, not promised”. It shows the homepage’s PageSpeed Insights scores from 18 October 2026: 98 for performance, and 100 each for accessibility, best practices and SEO. The date is part of the copy on purpose. Scores change as a site changes, so a dated measurement tells the reader exactly what was true and when.

The same principle works for any business. “Average reply time under two hours in September” beats “fast replies”. “Forty weddings hosted last year” beats “a popular venue”. Each works only if the number is real and you can show where it came from.

Let a case study tell a before-and-after story

A good case study is a short story with a beginning, a middle and an honest ending:

1. The starting point. What the customer had and what was in the way.
2. The decisions. What you chose to do, and why.
3. The work. Specific, countable details where they help.
4. The result so far. Only what has actually been measured.

Our Shuttersteve case study follows that shape. It opens with a couple who wanted a premium site without losing the pages that already brought in enquiries. It counts the work: 50 live URLs mapped before any design, 2,173 original photos optimised and 23 films carried across. And it ends honestly. The site is described as a preview in client review, and the search visibility line says only that results will be reported after launch.

That last line may be the most persuasive one on the page. It shows the reader that we will not dress up a result we do not have yet.

Ask for testimonials the right way

A testimonial is borrowed trust, so it needs the client’s permission and their real words. Ask soon after a good moment in the project, and make it easy with one or two questions. For example, ask what they worried about before starting and what changed. Answers to those questions tend to read like a story rather than a slogan.

Publish the client’s name and business only with their consent, and keep their wording apart from small typo fixes. Never write a review on a client’s behalf. If a client prefers privacy, respect it. We describe some projects without naming the client at all, and the scope and process can still show what we are capable of.

Place proof where the doubt appears

Proof is most useful at the moment a visitor hesitates. Put a relevant case study link beside the service it supports. Put a review beside the price or the enquiry button, and a dated measurement beside the claim it backs up. A testimonials page that nobody visits proves very little.

Proof is part of SEO too

Specific, first-hand detail is the kind of content search engines say they want to reward. Google’s guidance on creating helpful, reliable content stresses demonstrated experience and trustworthiness. A case study with real numbers, dates and decisions is exactly that kind of page. It gives people searching for your type of project something worth clicking. Link it to the relevant service page so the proof and the offer support each other.