Ten days ago we wrote about what Scope's usage ping contains, and at rather more length about what it doesn't. This is the other half: the number itself, and why a person types it in.

Scope has 104 users. That is two measurements added together — 80 weekly users of the Chrome extension, and 24 Apple accounts on the Lectra side — and neither of them is a query this website can run for itself. Google publishes the extension figure on the Web Store listing page and nowhere else: no API, no webhook. The account count is a real query, but it runs against an auth schema behind a service-role key that has no business anywhere near a marketing page.

So both are checked at their sources by hand, written into a source file, and committed with the date they were checked. That is not a shortcut around building a scraper. A number that goes through code review is a number somebody actually looked at, and a page that reads its headline figure from a constant cannot quietly render a zero at three in the morning because a listing page changed its markup.

For two days the count sat above the headline on the home page, in a framed plaque with an oversized numeral. It is not there any more. Nothing about it was wrong — it was in the one position on the site where a number cannot carry its own qualifications, and this number has several.

  • It is cross-product reach, not a deduplicated count of people. Anyone who uses both the extension and Lectra is counted in both halves.
  • The products do not measure the same event, so the halves are not cleanly addable. Lectra for Mac, for one, counts hosts online rather than interactions — a background receiver has nothing to interact with.
  • Idle does not count. A browser extension is technically running for as long as Chrome is open, so a ping on a timer would report every install as active every day: a flattering number, and a worthless one.

The figure now lives at /api/public/usage, which returns the three integers and the date they were verified. It is unauthenticated and readable from any origin on purpose: they are the same integers published on this page, so there is nothing to gate, and locking it to one domain would mean a deploy every time the number gets quoted somewhere new. The CDN holds the response for an hour, and a deploy is what changes it.

104 is a small number. It is also correct as of 27 August 2026, which is a claim not many numbers on a startup's website can make.