How we keep ourselves honest

Anyone can say they are honest. Here is the mechanism instead: 512 automated checks across 100 files run before every deploy, and some of them exist to stop us — not bugs, us — from promising something the product does not do. If one fails, the site does not ship.

Rules that are enforced by code, not by good intentions

1. Nothing we publish can promise more than the product does. If a claim on this site and the feature behind it drift apart, the build fails.
2. Any file we hand a customer must be read start to finish first. Materials marked internal can never reach a paying customer — a rule we added the day we broke it.
3. Buyer lists ship only for markets where cold outreach is lawful. The gate is code, not a policy note.
4. Every language version is generated from one dictionary and byte-compared. A promise cannot exist in one language and quietly not in another.
5. Your acceptance rate counts only work you actually approved or sent back. Silence is never counted as approval.
6. Client names never appear in our marketing — not in case studies, not in logos, not in screenshots. Results are published anonymously or not at all.

This page is generated from the test suite itself — the counts above are read from the files at build time, never typed in by hand. A page about honesty that goes stale would be the worst kind of lie.