One engineer, one car, one bus.

The specific thing you couldn't find out: you had GPS traces and you had GoPro clips, and neither one told you what your hands and feet were doing through a corner, or whether it was the same on the lap that was three tenths quicker. Then the car already knowing all of it — gear, throttle, brake, steering, yaw — and none of it reaching the tools people use at a track day.

How the order of events actually went: read the bus, decode it, align it to GPS time, put it on the video — and only then discover that was the interesting part and the hardware was just what it took to do it repeatably. Worth saying, because it explains why the browser tools exist before the board does.

Say plainly that this is not a company. A batch of five, hand-built, to find out whether anyone other than you wants one — which is why there is no team page, no logos, no “trusted by” and no price.

There is no email address published on this site, deliberately — a scraped address is permanent and a form isn't. The list is the way in, and it has a free-text box on it.

Name the three people whose messages are worth most — a ZD8 owner who tracks the car, a RaceChrono DIY builder, someone who has already fought a closed lap-timer app for clean data — and ask them for the one specific thing that would shape what the first five do.