Info

  • Hardware
  • Giantommaso Fogli

Table of contents

  1. Customer Zero
  2. Why this changes the sales cycle
  3. The Journal as the customer zero’s logbook
  4. The question that changed our approach
  5. Sources
Customer ZeroCustomer Zero

Customer Zero

7/9/2026 / 2 minutes to read / Tags: lake8.dev, Case Study, Analytics, BI,

The edge infrastructure on Raspberry Pi — the code quality benchmark we use as an engineering principle — is not a metaphor. The site you are reading runs on a Raspberry Pi 4B. PageSpeed ~100/100 on mobile and desktop. Uptime verifiable at stats.lake8.dev.

Why this changes the sales cycle

A prospect evaluating Lagotto BI does not need to imagine how it works.

They can run curl https://lake8.dev/llms.txt and read the site’s semantic structure. They can open stats.lake8.dev/geo.html and see real traffic, AI crawlers, blocked attacks, live PageSpeed. They can run any lake8.dev URL through Lagotto Meter and verify the score is real. They can read the JSON-LD and verify that every claim is supported by structural evidence.

They don’t have to take our word for it. They can verify.

This is the difference between selling software and demonstrating software. The typical B2B sales cycle involves: demo, POC, reference customer, negotiation. Our cycle involves: look at stats.lake8.dev. If what you see convinces you, let’s talk.

The Journal as the customer zero’s logbook

This article inaugurates a series different from other Journal content.

Not market analysis. Not technical tutorials. Not product white papers.

The customer zero’s logbook: what we learned using our own tools on ourselves, what worked, what required iteration, what surprised us.

Coming articles:

  • How Lagotto BI’s mapper builder processed 40,000 nginx requests in one hour
  • What GPTBot, ClaudeBot, and PerplexityBot found when they crawled our JSON-LD
  • How the license server manages Docker deployments on consumer hardware
  • What we learned from launching Lagotto Meter on Product Hunt and Hacker News

All real data. All verifiable. All public.

The question that changed our approach

In May 2026, while building the site’s semantic infrastructure, someone asked us a question:

“If your software is really good, why don’t you use it yourselves first so anyone can verify it?”

It was not a rhetorical question. It was a technical and commercial challenge at the same time.

The answer we built is called lake8.dev.

lake8.dev — San Pietro in Casale, Bologna, July 2026 All data cited in this article is verifiable in real time at stats.lake8.dev

Sources

Author: Giantommaso Fogli
Publication Date: 2026-07-09

Rights and attributions

Images, logos and photographs are the property of their respective owners. Used for commentary purposes.

← Back to journal