The Tesla Theory: When Less is More

Published on March 5, 2026

When you buy a Tesla, something surprising happens: there are almost no choices to make. No endless catalog of options, no ten thousand possible configurations with incomprehensible variants. Wireless charger? Included. Premium interior lighting? Included. Premium audio system, air purifier, 360° panoramic camera? It's all already there.

With other car manufacturers, it's the opposite. Each model exists in dozens of variants: base trim, Sport, Luxury, Premium Plus... And for each one, a list of options to check that extends over several pages. You want keyless entry? Option. Heated seats? Option. In the end, two cars of the same model can be radically different.

This approach seems logical: offer the customer choice, allow them to customize their vehicle and pay only for what they really want. But Tesla made the opposite bet. And that's what I call the Tesla theory.

The Paradox of Systematic Inclusion

The Tesla theory is based on a counter-intuitive idea: it's sometimes more advantageous to make just one version with a bit of everything in it than several variants with fewer options to "reduce costs."

Yes, it costs more to integrate a wireless charger and include premium speakers in every vehicle. Not everyone necessarily wants all these features. But it's a "gift," a bonus you get no matter what. At Tesla, the only real option is the Autopilot package, because it represents a significantly different hardware and software cost.

But where's the advantage for Tesla?

Simplified production. When there are only one or two configurations per model, the manufacturing line becomes much simpler. No need to manage dozens of different variants, no risk of error in assembling a specific configuration. Every Model 3 that leaves the factory is virtually identical.

Inventory management. And this is where it gets really interesting. Storing vehicles costs a fortune: in space, in transportation, in insurance. The more variants you have, the more of a logistical nightmare it becomes. Because each customer will want a specific version and, as luck would have it, you'll never have exactly the right model in stock.

That's why when you go to an ordinary car dealership, the salesperson tries to sell you first — with "reduced" prices — the vehicles already available at the dealership or at other dealerships. These cars are expensive to keep. They're ready to offer a discount to get rid of them quickly.

Tesla, with its unified approach, completely avoids this problem. A Model 3 in stock will suit any customer interested in that model. The turnover is much faster, storage costs decrease drastically.

Free and the Paradox of Gratuity

The Tesla theory doesn't only apply to cars. We find it in very different industries, often in surprising ways.

Take mobile operators. I'm with Bouygues, and there are tons of paid options on my plan: pay more to get more data, buy specific packs for abroad by country... When you travel, you check the rates on the mobile app, you buy a pack of 5 or 35 GB of data in advance for your destination. Convenient, but it requires constant anticipation and management.

Orange works the same way. But Free took a radically different direction: the Tesla theory applied to mobile telephony.

Free made a simple but brilliant calculation. They looked at what percentage of their customers went on vacation per year and to which countries. And they judged that it was more profitable to "offer" a data pack in certain countries rather than pay engineers to develop a complex application to manage on-demand pack purchases.

Think about everything that implies: developing the user interface, managing dynamic billing, customer service for activation problems, refunds in case of malfunction, not to mention third-party service companies that take their cut...

Here, the service is "free" for the user, but it actually costs the operator less than if they had to develop all the features to make it paid and manageable in a granular way. That's the paradox of the Tesla theory: give more to spend less.

Costco and the Radicalization of Simplicity

Other companies have pushed this principle even further. Costco, the American retail chain, applies this philosophy radically: they voluntarily limit their catalog to about 4,000 items, compared to more than 30,000 for a classic supermarket.

For each product category, they only offer one or two options, often in very large formats. Result: incredible stock turnover, minimal management costs, and very competitive prices. It costs less for everyone, and everyone's happy.

Imagine participating in a meeting in this industry. Someone suggests: "What if we reduced our catalog by 90%?" Everyone would find it counterproductive. "No, we need more products, more choice to satisfy the customer!" You'd hear: "Oh no, we can't remove this item, it's essential for certain customers!"

But in the end, what matters to the customer is that they find everything they need. They don't want to waste time. They want rice? They want to choose between two products, not fifty variants that are all more or less identical. And it's the same for each product.

Yet our intuition tells us the opposite: we always need more, always more choice. But is that really what users want?

The Paradox of Choice

Look at dating apps. Women have an almost infinite quantity of matches. At first glance, it's great: just swipe until you find the right person. But when there's too much choice, you no longer know how to choose and end up choosing nothing at all. That's what creates a lot of disappointment on the part of female users on these apps. Plenty of choice, but they don't find the right one.

This psychological phenomenon — the paradox of choice — is well documented. Beyond a certain point, multiplying options doesn't create satisfaction, but anxiety and indecision.

Southwest Airlines understood this principle. They offer a single type of "all-inclusive" ticket: free checked bags (up to two suitcases), open boarding (no paid premium seat assignment), and basic snacks at no extra charge. No business or first class, no à la carte options like with Ryanair, EasyJet, or Air France (where you pay extra for legroom, WiFi, or baggage).

Advantage for Southwest: a 100% Boeing 737 fleet (a single aircraft model) simplifies maintenance, pilot training, and spare parts management. The "services" inventory is unified, avoiding unsold items on rare options. This allows them operating costs 20 to 30% lower than the industry average, while attracting occasional travelers with an included "gift" that builds loyalty.

Basecamp and Single Pricing

In the SaaS (Software as a Service) world, the norm is to have three or four pricing plans: Starter, Pro, Business, Enterprise... Each with its artificial limitations: number of users, storage space, advanced features reserved for higher plans.

Basecamp, the project management tool, broke this model. They offer a single plan: $99 per month, all-inclusive. Unlimited users, unlimited projects, unlimited storage, all features. Period.

"But wait, small teams of 3 people will pay the same price as large companies of 300 people?"

Exactly. And that's the whole point.

For Basecamp, managing multiple pricing plans represents enormous complexity: developing limitation systems (blocking certain features for certain plans), managing migrations between plans, training customer support to explain the differences, creating marketing content for each segment...

With a single price, everyone has access to everything. Customer support no longer has to explain why a certain feature isn't available. The product team no longer wastes time developing artificial "paywalls." And most importantly, customers no longer have to wonder if they chose the right plan or if they should upgrade.

It's the same logic as Tesla: simplify as much as possible, offer everything to everyone, and compensate through the drastic reduction of operational complexity.

Some will say: "But you're losing money! A big company would pay much more!" Maybe. But how much does the avoided complexity cost? How many additional customers do you attract thanks to this refreshing simplicity? And how much friction do you remove from the purchase journey?

Basecamp bet that simplification pays more than complex pricing optimization. And apparently, it works.

My Experience in Software Development

I've observed this phenomenon many times in my work. We tend to always want to add features, to leave as much choice as possible to customers to try to satisfy them.

But it's counterproductive. It costs us extremely dearly, it complicates usage for the customer, and in the end, nobody's happy. Weeks of additional work to refine a feature quickly represents several tens of thousands of euros.

A concrete example I experienced: we had to integrate a notification system in an application for both email and mobile. The team wanted to make everything configurable for the user. They could choose in which cases they received email notifications and in which cases mobile notifications. But it didn't stop there. If they hadn't seen a notification for 24 hours, they could configure sending an additional email and mobile notification to remind them. And for each type of event, there were sub-options...

At first glance, you think it's great, that we're doing this for the user, that we're trying to satisfy them. But it's exactly the opposite of the Tesla theory.

It doesn't amuse the user to configure that. Everyone hates spending time fiddling with their settings to configure their notification preferences. It's a chore, not a feature.

Applying the Tesla theory would have been to make a simple, unified choice: email notifications only for the most important actions (to be sure the user is informed), and mobile notifications for ordinary actions. If we really want to give control to the user, we can let them globally enable or disable email notifications and mobile notifications.

The user would have been just as happy. And all that development time saved by doing something simpler could have been invested in a feature really expected by our users, all while avoiding wasting thousands of euros in development.

We must not forget that we operate in a world of constraints: we have limited time and capabilities. Every hour spent developing superfluous options is an hour not devoted to what really matters.

Lounio and the Trap of User Requests

I have another even more revealing experience with my personal project Lounio , a concert guide for Toulouse. Many users asked me to add a filter by musical category: rock, pop, jazz, electro... The idea seemed logical: allow everyone to see only concerts that match their tastes.

But I was always against this feature.

For me, it's useless. You want to know what concerts there are next Friday? You look at the concerts for that Friday. There are about ten. It takes two minutes maximum, you're sure to see all the available choices, and you spot what you like. Simple, fast, effective.

But adding a category filter? It's much more complex than it appears.

First, you need to integrate filters into the interface. But the application must remain simple and fast, especially on mobile where space is limited. A "simple" filter quickly becomes a feature that's not so simple to add properly.

Then there's the question of the categories themselves. Should we offer all the different types, or only the most basic ones? Should a pop-rock artist appear in the pop category or in the rock category? Or in both? How many categories should there be? Should we separate rock, punk, and metal? What about grunge or psychedelic rock?

Because if we choose to keep few categories, it's not great either. A user browsing the "rock" category who sees a punk or metal band... it's still not the same thing. It won't help them much. But some are open to more variety, so it's also useful to group them.

And then here's a philosophical question: what differentiates pop from French chanson? Have you ever asked yourself this question? After reflection, it's practically the same thing. A French chanson artist is an old artist who used to do pop. A young artist singing in French would be more considered "pop" than "French chanson."

In short, it's very very quickly complex, this category filter business. Complex to design, complex to implement, complex to maintain.

But well, faced with repeated user demand, I ended up giving in. I implemented the category filter to please them.

Result? Nobody uses it.

Which goes to show, I should have listened to my instinct. Not only are too many features not useful, but blindly listening to user requests isn't either. Because they themselves don't always use what they ask for. They think they want more control, more options. But in fact, they prefer simplicity.

It's a lesson I learned the hard way, but one that perfectly aligns with the Tesla theory: sometimes, saying no to a feature means creating a better user experience.

The Lesson of Simplicity

In the end, keeping things simple and uniform costs less. It seems counter-intuitive, but it's beneficial for everyone.

For the company: less complexity in production, in inventory management, in maintenance, in customer support.

For the customer: fewer decisions to make, less risk of making mistakes, a product or service that "just works" without endless configuration.

And because it's cheaper to produce and maintain, it allows attracting more customers with competitive prices or included features that would have been paid options elsewhere.

Next time you're tempted to add "just a little option" to your product, your service, or your application, ask yourself the question: couldn't I just include it for everyone? Or better yet: is it really necessary?

Sometimes, the best feature is the one we don't develop. And the best choice is the one we don't impose on the user.

That's the Tesla theory.