When Europe finally got its long-awaited FSD rollout, youâd expect reliefâat least for the customers who spent years waiting. Instead, a familiar argument has reappeared, this time with sharper edges: owners with Teslaâs HW3 computer are realizing they may have bought access to something Tesla is effectively telling them, ânot yet, and maybe not at all.â Personally, I think the most troubling part isnât even that the technology is hard. Itâs that the story we were sold and the product thatâs arriving donât line up, and customers are now organizing like itâs a consumer rights fight rather than a software update.
What makes this particularly fascinating is how quickly âitâs just a technical workaroundâ turned into âit might be inoperable,â based on Teslaâs own documentation and public admissions. From my perspective, the backlash signals not only a specific hardware dispute, but a broader pattern: when companies monetize future capability, delays and segmentation stop being technical details and start becoming trust-breaking issues. And once trust breaks, people stop waiting politely.
Europeâs FSD launch exposes a contract mismatch
Teslaâs Full Self-Driving approval in the Netherlands is a milestone, and Iâll give it thatâitâs meaningful. The RDWâs type approval for FSD Supervised under UN R-171 creates a regulatory pathway for broader EU rollout, and that matters for timelines in a very concrete way.
But hereâs the catch that immediately changes the emotional temperature: the approved build runs only on Teslaâs newer AI4 computer at launch. What many people donât realize is that, in these moments, software isnât âone product.â Itâs a moving target tied to hardware capabilities, and Teslaâs branding (âFSDâ) tries to blur that distinction.
In my opinion, this is why HW3 owners are so angry. Personally, I think the anger isnât abstractâitâs arithmetic. When someone pays thousands of euros expecting a certain promised level of autonomy, and the launch condition quietly excludes them, it feels less like âevolutionâ and more like a breach of the deal.
A Dutch Model 3 owner, Mischa Sigtermans, has launched a collective claim website aimed at HW3 + FSD buyers across the EU. And this raises a deeper question: if autonomy is sold as a future capability, what exactly does the customer get todayâan assurance, a license, or a gamble?
The âv14 Liteâ problem isnât just underperformance
Teslaâs response to HW3 exclusion appears to be âv14 Lite,â a stripped-down approach Tesla has floated for a later window. From my perspective, the real issue isnât whether Lite is better than nothing. Itâs that itâs being positioned as a substitute for what customers were told they were buying.
If you take a step back and think about it, âliteâ is a marketing term that often hides a legal and functional gap. Customers arenât merely asking for features; theyâre asking for conformity with what was sold. Personally, I find it especially interesting that the system-level workaround could be âinoperableâ for certain perception units, according to Teslaâs own patent language.
This is where the narrative gets uncomfortable. Technically, a workaround can be clever; legally and ethically, a workaround can still fail the promise. What this really suggests is that Tesla is trying to manage expectations while keeping optionalityâmeaning customers may end up paying for a capability that doesnât behave the way advertising implied.
It also connects to a broader trend Iâve been noticing across tech markets: companies increasingly monetize âcapability trajectoriesâ rather than completed products. Then, when trajectories changeâbecause hardware limits, model scaling, or deployment realitiesâcustomers are left with an expectation that becomes hard to enforce. People usually misunderstand how quickly âpromise-based revenueâ turns into âdispute-based revenueâ once delivery doesnât match.
Paper trails, public admissions, and the psychology of accountability
One detail stands out to me: the escalation isnât driven only by owner speculation. Itâs supported by documented admissionsâTeslaâs patent wording, executive acknowledgments, and Muskâs own statements about needing to replace HW3 computers.
That combination matters because it shifts the debate from âfans vs. criticsâ to âcustomers vs. evidence.â Personally, I think this is the part that makes collective action more likely to succeed. When the company itself has acknowledged constraints, delays become less excusable and more calculable.
Musk previously indicated that Tesla would need to replace HW3 computers in vehicles where FSD was purchased, calling it âpainful and difficult.â From my perspective, that admission is psychologically important because it confirms what customers were already assuming: the issue isnât merely a rollout scheduleâitâs a compatibility problem.
Now layer on the time factor. In my opinion, time is where fairness collapses. Itâs one thing to say, âWeâre working on a solution.â Itâs another to say, fifteen months later, âThereâs no concrete plan,â while the product has been sold as if the solution was inherent to the purchase.
And this is a cultural pattern too. Companies often treat customer disappointment as a phaseâsomething that fades when updates arrive. But when people learn that the underlying platform may require replacement, disappointment turns into anger, and anger turns into organization.
Australia was the warm-up. Europe is the pressure test.
Australiaâs class-action momentum (triggered by HW3 revelations) shows a blueprint: the legal system becomes the mechanism for forcing clarity when the product mechanism stalls. Personally, I think Australia acted like a rehearsal, where Tesla had to face not just complaints but coordinated claims.
Europe, though, is where the stakes change shape. EU consumer law typically offers stronger rights around conformity with what was advertised at the point of sale. From my perspective, thatâs a major reason owners in multiple countries are bundling their efforts now: theyâre not only arguing technical facts, theyâre invoking the legal framing of âwhat you bought.â
What many people donât realize is that regulatory and legal friction tends to reveal business strategy. Companies can tolerate an âinnovation narrativeâ in the absence of binding remedies. But once collective redress becomes plausible, the story shiftsâbecause now there are consequences, not just rebuttals.
What this suggests about Teslaâs future relationship with customers
Hereâs my honest take: the HW3 conflict isnât just a technical footnote. Itâs a stress test of a business model that sells future autonomy before it fully exists in the exact form customers assume.
Personally, I think this raises a deeper question for the entire EV and autonomy ecosystem: can you sell âeventual capabilityâ without creating a long-term entitlement expectation? If the answer is no, then the industry needs new contracting normsâclearer scoping, stronger delivery definitions, or refund and retrofit pathways that donât arrive only after litigation.
Also, consider incentives. If a company can segment functionality by hardware generation and still claim continuity through brand naming (âFSDâ), then customers will keep absorbing the risk. The question becomes whether regulators and courts will force the company to share that risk.
I suspect weâll see more âcollective claimâ structures elsewhere too, not just for Tesla. Once one major player gets dragged into the consumer truth-versus-marketing debate, copycats follow. People donât just copy products; they copy legal playbooks.
Where I think this ends
The most sobering possibility is that this likely ends in court rather than through spontaneous goodwill. Personally, I think the longer Tesla delays a clear HW3 planâhardware retrofit, refund policy, and timelinesâthe more it makes negotiation look optional and litigation look necessary.
A âv14 Liteâ solution may or may not satisfy owners technically, but it canât easily satisfy owners contractually if the promise was materially different. What this really suggests is that the core dispute isnât âcan FSD run on HW3?â Itâs âdid we buy the same thing, and if not, who pays for the gap?â
Iâll leave you with a provocative thought: if autonomy is sold like a product you own, then accountability has to behave like a product you can enforce. Anything else is just expensive optimism dressed up as technology.
Example: Why the launch condition matters
Imagine buying a gym membership labeled âPersonal Training Included.â Then the gym opens but only members with a specific equipment package get trainers. You can still enter the building, maybe even get a class, but you didnât buy âa workaround.â Thatâs the moral logic HW3 owners are invoking with their collective action.
Would you like this article to lean more toward legal analysis (EU consumer rights and collective redress mechanics) or more toward technology critique (HW3/AI4 constraints and why workarounds fail)?
