Makes sense! I would love to hear more about that method (if it's something you can talk about)
For Tesla auto sales couldn't you just look at tesla vin numbers?
For iPhones, sample mac address's?
You’ve definitely intuited some of the method, yes :). The rest of it entails:
1) how to get all VINs both authoritatively and legally,
2) how to distinguish between valid VINs and assigned VINs,
3) how to reverse the actual revenue projection from the set of all assigned VINs.
The first requirement is the hardest. Tracking self-reported VIN delivery from users isn’t rigorous enough. You could use an endpoint and scrape from it, but how would you do it legally and reliably?
The second requirement is also difficult. Assuming you’ve found an authoritative source for valid VINs, how do you distinguish which VINs are assigned?
Once you have those two, the third requirement is mostly straightforward. You can implement your own VIN decoder using public NHTSA documentation, map each VIN field to options and prices across models, and track sequential VINs using the distinguishing method of requirement 2 on the data you’re getting from requirement 1.
Naturally, there are other ways to do this that don’t involve VINs at all.
Sometimes it's just good old illegal insider information.
I say “simply” because it doesn’t require any of the infrastructure you mentioned, which is what the public typically associates with “alternative data.” It was actually quite impressive and novel at the time, and inspired other projects of mine.
I can talk about this now because (to my knowledge) it no longer works, though it did for a while. He was in charge of approximately $100M when he was working on this.