Skip to content

We fact-checked our own case studies

Before our case studies went live, we checked every claim against the real code and the live sites. Some of our first wording was wrong. Here is what changed.

2 min read

A magnifying glass resting on blank papers on a desk, beside a dark glass tablet with a glowing gold tick.

2 min read

Our first draft of the Tziyun B’Rega case study said teachers could mark a test with a pen or a pencil. We had only ever proven the pen. So the pencil came out.

That small fix is the whole idea of this story: say only what we can prove.

Key points

  • We checked every claim on the case-study pages against the real code and the live sites.
  • Wrong or unproven claims were fixed or removed.
  • Three claims were changed: the pencil, “no back end” and “every setting is in the web address”.
  • Numbers stay only where they were counted, and we use no speed, price or customer numbers.

Why we did it

Our case studies are the part of this site that people rely on most. A visitor reading them is deciding whether to hire us. A claim that is a little too big is a bad way to start.

How we did it

For each of the three projects we read the real code, the project notes and the live site. We wrote down every claim we wanted to make and marked each one: confirmed, wrong, out of date, misleading, could not be checked, or only the owner knows.

Then the person who built the projects read the audit and corrected it wherever we had it wrong. Only after that did we rewrite the case studies from the audits.

What changed

  • Tziyun B’Rega. Marks made with a pen are proven, so the text says pen. Pencil is not claimed.
  • Shapi-Lumda. An early line said the course had no back end. That was wrong. The course uses Firebase for hosting (keeping the site online), optional accounts and optional cloud sync. The number of lessons, 306 in each language, is counted from the code.
  • Kadish Yatom. We had said every setting lives in the web address. That is true for the settings of the sheet, but not for the language and the theme.
  • Everywhere. No speed, price or customer numbers.

What is a back end?

A program has a front, the screens people see, and a back end, the part behind the screens that stores data and does the heavy work. In a shop, the front is the shop floor and the back end is the stockroom and the office.

What we left out

Things we could not prove stayed out. So did a few true things that are not ours to publish.

When you read a fact on our case-study pages, it came from those audits. Where we could not check something, we did not say it.

Read next

What we did and what the assistant didA plain list of who did what in building this site: the taste, the pictures and the corrections on our side, the building, the matching and the checking on the assistant's.We were not happy with the first designThis site started with ideas from Gemini and Claude, and a lot of movement. We were not happy with it. Here is what we built first and what we threw away.

Got something to build? Let's talk.

No sales pitch. Tell us what your business needs and we'll tell you straight how we'd tackle it, or whether you need it at all.

6 stories about BotKB.com

All 6 stories

We were not happy with the first designThis site started with ideas from Gemini and Claude, and a lot of movement. We were not happy with it. Here is what we built first and what we threw away.One picture changed the whole siteWe brought one picture, and the colors, the mood and the words of every page followed it. A story about taste, and about letting an assistant do the matching.A calm site that is also lightWe wanted this site to feel rich without feeling heavy. Here is how we kept the motion gentle and the pages light, and what a page checker said when we ran it on 28 October.Hebrew and English as equalsEvery page of this site exists in English and in Hebrew, read left to right and right to left. Here is what that meant for the fonts, the layout, the error page and the way we check our words.We fact-checked our own case studiesYou are reading this story. Before our case studies went live, we checked every claim against the real code and the live sites. Some of our first wording was wrong. Here is what changed.What we did and what the assistant didA plain list of who did what in building this site: the taste, the pictures and the corrections on our side, the building, the matching and the checking on the assistant's.
Accessibility menu

Keyboard shortcuts

Open accessibility menuAlt+A
Accessibility statement

These settings are saved on your device only and are used to adjust the display. They do not change the site content and send no information to any server.