Every device we ship
makes everything easier to find.
Our devices listen for the network the moment they power on. Teaching them to notice a tag nearby is a firmware change — and it turns every device we ship into part of something new.
Finding networks work.
We’re not going to pretend we invented one.
Apple and Google run enormous finding networks on phones. Amazon runs one across most of the United States on home devices. They work, they’re well engineered, and they’ve proved the principle beyond argument.
What they have in common is where they live: consumer homes and consumer pockets, in wealthy urban markets.
None of them reach a mine shaft. Or an irrigation pivot, a plant room, a rural depot, a farm gate, or most of a continent. That isn’t an oversight — those places have no phones and no smart speakers to host a network on.
They have Justworx devices. Because somebody bought a switch, a sensor or a controller to do a job, and it arrived with a radio that never stops listening.
A market thirty times larger,
structured completely differently.
The industrial side is served today by cellular trackers with per-device subscriptions. Every tracked asset carries its own radio, its own SIM and its own recurring bill.
A tag on Beacon needs none of that. No cellular radio, no subscription per asset, no connectivity contract. It needs to be seen once, by one Justworx device, anywhere. Every product a partner ships makes every tag more findable — the same compounding principle as Justworx Air, applied to location instead of connectivity.
Coverage as a by-product of products people bought anyway.
Beacon is the programme with the strongest flywheel, because it makes the growing fleet more valuable without changing what it’s for.
Every Justworx device deployed for its own reasons extends finding coverage. Denser coverage makes tags more useful. More useful tags sell more devices into the same sites. Coverage as a by-product of products people bought anyway — which is precisely the mechanism that failed when networks tried to sell coverage as the product itself.
The section that makes the rest believable.
- Concurrent scanning is a real engineering constraint. Asking a module to maintain mesh duties and scan for beacons simultaneously has power and timing implications we need to validate on current silicon before promising anything.
- Privacy regulation is now formal, and we intend to be ahead of it. The unwanted-tracking specification developed by Apple and Google is now an IETF working group. Any accessory capable of tracking location must advertise its presence, allow a nearby phone to make it sound, and publish clear disablement instructions — or both mobile operating systems will flag it as a stalking device. Whether that framework binds a business-only industrial network is a genuine legal question. Our position is that we’ll build to the spec regardless. A finding network that mishandles this doesn’t get a second attempt.
- Density is a chicken-and-egg problem in new territories. Beacon works where the fleet is dense. In regions with early deployment, coverage will be patchy before it’s useful, and we’d rather set that expectation than oversell early coverage maps.
- We’re competing with well-resourced incumbents in their core markets. We don’t intend to fight Apple for consumer key finders. Beacon is aimed squarely at the industrial and commercial segment where our coverage is genuinely differentiated and theirs is genuinely absent.
Honest about the distance.
A mesh network, and devices that listen for it the moment they power on — the mechanism Beacon needs. Coverage is early, and grows with every deployment.
Validating concurrent scanning on Pro silicon, and a beacon-only tag SKU designed to the unwanted-tracking specification from the first schematic.
Finding-as-a-service across our partner network, priced against per-asset cellular subscriptions rather than against consumer trackers.