The same number, told three ways, on three live pages
The trigger was a full sweep of every public surface the firm actually owns: a professional network profile, a company page, a main website, and a public wiki that, it turned out, had been live and indexable for months without anyone remembering to check it. The wiki carried figures that an internal document had already retired. The main site's own machine-readable identity data pointed a search engine at a different person's professional profile entirely, meaning the firm's own structured data misidentified its own principal. And a file written specifically for language models to read, the single surface where being current matters most because nothing else about it gets a second look, was the most out-of-date file on the whole site.
None of that was one person's mistake. It was the predictable result of never having a single place that owned the fact independent of the sentence. Every time someone wrote a bio, a proposal or a post, they wrote the underlying fact fresh, from memory or from whichever old document they had open, and each fresh telling drifted a little from the last one.
A claims register, not a brag sheet
The fix treats every claim as a row with a status, and the status answers a narrow, practical question rather than rating the win. A row can be locked (either it lives in the firm's core record or a partner has explicitly ruled on it, and it ships as written). It can be documented (a real file backs it, a contract, an approval email, a public record, but nobody has ever formally promoted it to locked). It can be gated (real, but not one person's alone to clear, with the row naming who holds the gate). It can be contradicted (two of the firm's own sources disagree, and both versions are printed on the row so the fork is visible instead of hidden). It can be never-public (true and useful, but internal forever, written down specifically so nobody reaches for it by accident). Or it can be retired (used once, now banned, with the row naming the replacement that is allowed, kept on file rather than deleted, because a retired claim has a way of coming back in someone's bio six months later if there is no record of why it was retired).
How we came at this one
The question asked first was what a given sentence is actually allowed to do today, not how impressive the underlying fact is. That question fit because the actual damage was never the size of any single win, it was live disagreement between our own documents sitting on public pages at the same time.