Skip to main content

What the car industry and wallstreet get wrong about Tesla




Every time I watch a car review that includes a Tesla somewhere, it is always fascinating how the reviewers react. They try hard to compartmentalize the Tesla into their existing matrix and scorecards of what makes a good car. I sometimes roll my eyes when the subject of materials, build quality and range come up. Obviously, these things matter for car people - but what should also be discussed and what reviewers generally do not grasp is that Tesla changed forever the way we look at cars. Tesla cars are really computers with wheels whereas all the other electric cars, from the incumbent car makers, are just cars.

Why is this important? 

It changes everything - it’s the same comparison between a feature phone and the iPhone. The feature phone was primarily used to make phone calls and send the occasional text. The iPhone became a platform business where a whole new economy was created through the power of software.

Just like Apple, Tesla pursues a single-software-stack approach and by that I mean that Tesla controls every aspect of its software and thus can release new operating systems and new features at will. Compare this with an incumbent car manufacture where most components are being sourced from different companies that use their own software stack and sdk (software development kit) which then need to be painfully integrated into a single, monolithic clump of software.
This has been the model of choice for most industries and is only now changing thanks in part of disruptors with an Api first and software first approach. I’ve covered this topic in my previous API first article.

Now, back to Tesla: you’re driving a computer (or rather the computer really drives you). If we think about the implications of this approach, it becomes immediately clear that:
a)    Tesla pursues a new approach to building cars by using new technology and new ideas
b)    Incumbent car manufacturers are double-whammied

Obviously, with a) I simply state the fact that Tesla is a disruptor just like Revolut is for the banks, Apple was for Nokia, and photo sensor for Kodak - that’s just the cycle of technology obsolescence (in this case, the combustion engine) and technological awareness and best use. And it’s a natural thing that constantly happens. But, we can’t overlook the fact that we actually need to do this for our and our next generations sake. We are still driving on dead Dinosaurs “carcasses”and it’s only because we didn’t have the right infrastructure in place when the car industry started to ramp up. Nobody was thinking about the ramifications of extracting, transporting, refining and combusting dead dinosaurs. So this has to change - and that’s why the next point is so difficult to comprehend:

With B) Tesla has given two challenges for the incumbent car industry that they could have solved by themselves a long time ago:
  1. The electric drive train forced Tesla to create its own components. They have had mass production cars in circulation since 2012. In short, Tesla is years ahead. I’m not just talking about putting batteries in a car and using an electric motor, I’m also talking about the whole infrastructure that requires charging stations (read about our trip through France: here) and sophisticated software to manage it all.
  2. The aforementioned software first approach that requires a completely new way of building cars. You have to start making software for each of your components. Tesla is estimated to be around 80% vertically integrated. That’s how much you have to control in order to create an experience and platform business that Tesla has created.

This combination is very powerful, not only does it lead to a platform business it also enables completely new use cases and functions. Case in point, Tesla Arcade, Tesla’s Dog mode, Tesla’s Sentry mode, Autopilot, The summons mode and of course, full self driving (>3 hours long video). But think about the future of this system, what does it mean for insurance policies when I can clearly show them that someone scratched my car, or think about the accident avoidance. What about the data that every Tesla car collects from the street: several cameras are constantly recording, I suspect every City would be interested in having this data to better pin-point accidents or choke points. There is certainly commercial use for that data. Tracking pedestrian traffic, anyone? In the future, I would expect third parties to make software for the Tesla “computer on wheels” and Tesla will most likely have its own app store so that these apps can tap into all that data that Tesla’s connect.

Which brings me to this realization: the car industry is doomed. They haven’t realized yet but unless they are disrupting themselves NOW, most of the big players will either be gone, or reduced to a shell of their former selves. Of course, this development will happen over a 20 year time horizon but given all the other troubles the car industry has, it might just be the last nail in their coffins. This is also why I think Tesla just might be the most important company on the planet (next to Space X and maybe the GAFAs) because it will touch so many aspects of our lives. Not only is it dragging along the whole car- and power industry, it’s also helping us to get serious about CO2 emissions. And yet, Wall Street analysts treat Tesla as a car manufacturer and they use those methodologies to try and put a value on it - not that different from what the car reviewers are doing. I think both are missing the bigger picture.


Comments

Popular posts from this blog

The case for central bank digital currency as public infrastructure to enable digital assets

I have dabbled a fair amount with all sorts of crypto currencies and their respective permissionless networks. In fact, I have been dabbling since 2012 which is by my last count a whopping 12 years. While I have always maintained that I do believe the general concept for digitization and programmability of assets is on the right path, its implementation, the user experience, the accessibility, the fraudulent activities, and the overall inefficiencies permissionless DLTs have, never made me into a true believer. I have stated that opinion on several occasions, here , here and here . There are still barriers to entry when it comes to digitization of assets: sustainable- and interoperable infrastructure. To illustrate this, I recently asked a notary public here in Zurich, why they can’t store the notarized documents as PDFs, the answer surprised me: because they must keep records for at least 70 years. Now, think about what would have happened if we stored these documents on floppy disks...

I've Been Vibe Coding for 2 Months, Here's What I Believe Will Happen

In the past few months, I've embarked on an experiment that has fundamentally changed how I approach software development. I've been "vibe coding" - essentially directing AI to build software for me without writing a single line of code myself. This journey has been eye-opening, and I'd like to share what I've learned and where I think this is all heading. My Vibe Coding Journey I started vibe coding with Claude and Anthropic's Sonnet 3.5 model, later upgrading to Sonnet 3.7, Claude Code, and other tools. My goal was straightforward but comprehensive: create a CRM system with all the features I needed: Contact management (CRUD operations, relationships, email integration, notes) Calendar management (scheduling meetings, avoiding conflicts) Group management for organizing contacts A campaign system with templates A standalone application using the CRM's APIs for external contacts to book meetings direct The technical evolution of this project was inter...

Vibe Coding Alert! How I Rebuilt a Wix Site and Fed the “AI Will End SaaS” Panic

My better half is an artist and maintains a Wix.com site. For the second time in two years, Wix decided to raise the hosting fees. That’s when I suggested to my spouse that I could rebuild the website and host it on Firebase (where I host most of my projects). I assumed this wouldn’t be a big deal (I was wrong) and started researching ways to use a lightweight CMS with Firebase support. Such a system exists — it’s called FireCMS — and it’s excellent. Before I dive deeper, here’s her original site (no longer a paid Wix site):  Miyuki's WIX site Her instructions were clear: replicate it as closely as possible. So I went to work. I created a product development document with use cases, scope, screenshots from the original site, the required features, and of course FireCMS integration. I used ChatGPT to draft the document, then set up a new Firebase instance, and finally launched the Vibe Coding agent (Claude Code). The process wasn’t too different from my other projects, but what sur...