The homepage shows how many units of the current production run are still available. It reads from the order system. It goes down when someone orders and it does not go back up.
We cannot prove any of that to you, and that is the interesting part.
The problem with telling the truth here
Countdown timers that reset on refresh. "Only 3 left" on infinite digital goods. "17 people are viewing this" generated by a random number function. These are common enough that most people have learned to discount urgency signals entirely.
Which puts an honest counter in an awkward position. It looks exactly like a dishonest one. There is no visual difference between a number read from a database and a number that counts down because a script says so.
The rational response from a visitor is to assume it is fake, because usually it is. We think that response is correct and we cannot argue with it.
Why we built it anyway
Because the alternative was worse for us internally.
The number is real because our production genuinely works in batches. Twenty units get built, checked and shipped together. When they are spoken for, the run closes and the next opens. The counter is not a marketing device bolted on — it reports a fact that already governs how we operate.
Given that the constraint exists, showing it is simply accurate. Hiding it would mean someone orders a device from a run that filled yesterday, and finds out from an apologetic phone call.
What we did to make it defensible
It comes from the order system. Not a config value someone edits, not a number in the HTML. The page asks the same system the dashboard reads.
It does not reset. When a batch fills, the page says the batch is closed. It does not quietly roll over to a fresh twenty to keep urgency up. Closed means closed until we open the next run.
It fails to nothing, not to a guess. If the count cannot be fetched, the panel shows no number at all rather than a plausible default. A wrong number that looks right is worse than no number, and a default would eventually get shipped as a fake.
No countdown timer. We know when a run is full. We do not know when, and inventing a deadline would be manufacturing exactly the pressure we are trying not to.
What we will not do
- Set the batch size for urgency. Twenty is what we can build and check by hand. If we could comfortably do fifty, it would say fifty.
- Show "X people viewing". We do not know, because we do not track visitors.
- Add a countdown. There is no deadline. Inventing one would be a lie with a clock on it.
- Reopen a closed batch quietly. If we add units to a run, that is a different, larger run and we would say so.
The uncomfortable conclusion
Honest scarcity signalling is probably less effective than dishonest scarcity signalling. A fake counter can be tuned; a real one says what it says. If ours shows plenty available, it removes urgency we might otherwise have manufactured.
We accept that. Not from principle alone — the practical reason is that we intend to be selling this in five years, and the compounding cost of being a company whose numbers cannot be trusted is larger than the conversions a fake counter would buy.
You still have no way to verify it. The only thing we can offer is that everything else we publish is written to the same standard: we removed a performance figure from this site because we could not substantiate it, and we wrote about doing so. A company willing to delete its own headline number is at least consistent about which way it errs.