What this site claims, and how it is checked
Most of what a studio website says about itself cannot be checked by the person reading it. This page sets out the rule everything here is written to, and how that rule is enforced on every build rather than by good intentions.
One rule, three kinds of sentence
Everything written here is a fact, a stated intention, or nothing at all. There is no fourth category.
-
A fact
Something that can be shown: what a system does, what it refuses to do, what you receive, what the scope is. Most of this site is this.
-
An intention
Something being built or aimed at, named as such. A target turnaround is an intention. So is a system marked as in development.
-
An unproven result
Hours saved, error rates, revenue, satisfaction, market demand. None has been measured here, so none is written here. This is the category that is simply not used.
Enforced by the build, not by good intentions
A rule nobody checks is a preference. This one fails the build.
- A script reads the rendered pages
- scripts/claims-scan.mjs runs on every build, over the built HTML and the source copy. It carries a list of banned strings: the unsourced figures and invented client names from the previous version of this site, and the hype vocabulary the brand rules out. A match fails the build, and the site does not ship.
- Exceptions have to be written down
- A banned phrase can be allowed only as an exact longer phrase with a stated reason, held in the same file. "No ranking or traffic promises" is permitted because it states that no promise is made. The exception list is short on purpose.
- Metadata is checked too
- Separate checks fail the build if a page has more than one H1, skips a heading level, duplicates another page’s title or description, or is unreachable from the homepage. The demonstration data has its own test: an outcome that disagrees with its own figures fails.
- None of this proves the work is good
- It proves the writing is checkable. Whether a system is worth building is a separate question, and the only honest answer to it is to show you one running.
What the label on each demonstration means
- Working demo
Runs end to end. You can be shown it working on data prepared for the purpose.
- In development
Parts of it run. It is not finished, and it is not offered as a service yet.
- Illustrative interface
A drawing of an interface, not a running one. The layout is real; nothing behind it is.
- Not offered yet
Built far enough to show, held back for a stated reason — usually a control that is not finished.
Every demonstration on this site carries one of these four, in the panel itself rather than in a footnote. All of them currently run on data generated for the purpose: no client file has ever been used, and none will be without a written agreement covering it.
What is missing, once
Stated here so it does not need restating on every other page.
- No client results
- No case studies, testimonials, logos, project counts or return figures, because none has been verified and published with permission. When that changes they will appear with the client named and the figures sourced, on this page first.
- No measured savings
- The time a process currently takes is described from the processes the studio has been asked about. What a system would save has not been measured, so no figure for it appears anywhere.
- Timelines only where the process supports one
- The supplier price sprint targets about three working days once inputs and scope are agreed, because the scope is fixed. Everywhere else a timeline comes out of scoping rather than a pricing page.
Judge it on a process you already have
The fastest way past a page like this is to put a real workflow in front of it. Describe one and the reply will say whether it fits, what scoping involves, and where the limits are.