How we count.
Every number on the front page is a row count from our production database. This page says what each number means, what we leave out, and when it was last refreshed.
Counts we can point to
We publish what the system has done, as rows in a database we can point to. There are no percentage lifts, composite scores or anonymous quotes on this site.
The ledger must sum
The headline number of pieces of work is the exact sum of the ledger rows beneath it. If the arithmetic fails, the site refuses to build.
Claims are checked at publish time
The "100% with cited evidence" tag on signals is re-verified on every refresh. If one signal lacks evidence, publishing stops until the copy is corrected.
The window
Counting starts on 16 April 2026, the day the system produced its first piece of work in a live customer deployment, and runs to the date on the stamp above. An automated job refreshes the numbers every week. It re-runs the same queries against production and republishes this site, and the stamp shows the day the queries ran. Between refreshes the numbers are up to a week old.
What is included
Live customer deployments only, currently two. Our own workspace and the demo environments run the same software and are excluded from every count. Nothing here comes from us using our own product.
What each number means
Accounts under continuous watch
7,855Every company the system holds a record for in a live deployment and re-examines as new email arrives. This is the full book, with no sampling and no "active only" filter.
Emails read
561,158Every email ingested from the mailboxes our customers connected: read, threaded and checked against the book of accounts. Vendor noise and internal chatter are read and set aside, so this counts what was read rather than what matched an account.
Account assessments written and kept current
25,099Full written assessments of an account's health and state of play. When new evidence arrives the system writes a new assessment that replaces the old one on screen. Each one written counts once, because each was a real piece of work.
Record updates suggested
21,345Field-level record changes the system proposed from evidence: a title change spotted in a signature, or a deal stage that moved in reality before anyone moved it in a system. Every one was queued for a person to review. None was typed by a person.
Signals raised
10,330Named patterns such as "Champion Gone Silent", raised against a specific account and carrying the evidence that triggered them. The build enforces the evidence claim: at every refresh we recount the signals that cite evidence, and the site will not publish if that recount is anything less than all of them.
Attachments and documents read and filed
3,996Files found in the flow of email, such as proposals, contracts and decks, parsed and filed against the account they belong to.
Outside events tracked against an account
1,417News and market events, for example funding, leadership changes or expansions, matched to a watched account and recorded with a source.
Outreach emails drafted
1,179Emails the system wrote for a rep to review and send. Counted from the drafts store, so this is the one number that can go down: a draft a rep discards leaves the count. We publish it anyway, because that is what the store says.
Morning briefings written
186Daily written briefings delivered to a team's morning: what changed, what needs attention and what the system did overnight.
What we leave out
Numbers that are real but would flatter: anything produced in our own use of the product, anything from demo environments, and any metric still too small to stand behind. If a number you might expect is missing from the front page, it is either not ours to claim or not big enough to mean anything yet.
Why there is no live ticker
With a small number of deployments, a live counter would publish our customers' operating rhythm. A new deployment would show up as a step change and a quiet week as a flat line. Weekly, dated aggregates keep the numbers honest without turning anyone's business into a public chart. The stamp tells you how fresh they are.