Tesla Pricing Platform — vehicle, Supercharger, Powerwall and solar alongside pricing charts
Work
Tesla · 2024

Tesla Pricing Platform

A centralized pricing platform driving pricing decisions behind 98% of Tesla's revenue across global markets — designed from zero to one.

Role
Sole UX Designer
Team
4 PMs · 12 Engineers
Scope
63 Global Markets
Users
Internal Pricing Team
Business Context

Tesla is known for changing prices frequently. Few people realize how those price changes were actually made behind the scenes.

Where It Started

The Initial Request

The finance team needs to make pricing decisions with accurate and speedy execution, implementing controls and audits required by the board.

Before jumping into solutions, I wanted to understand the problem.

  • What pain points exist today?
  • Why does this matter?
  • How should success be measured?
The Problem Behind the Problem

Understanding the Workflow

To understand the request, I visited the pricing team at Tesla's Bay Area office and observed how pricing decisions were actually made. One thing immediately stood out. Pricing decisions were spread across dozens of spreadsheets and browser windows.

Wendy Bouzid, Sr. Pricing Analyst, amid dozens of overlapping Excel spreadsheets and browser windows

"I am overwhelmed by dozens of Excel spreadsheets and windows every day."

Key Findings

01
Information was fragmented
Pricing data lived across multiple systems before any pricing decision could be made.
02
Decisions depended on manual work
Every pricing change required repetitive verification and manual updates.
03
Collaboration happened outside the product
Reviews and approvals relied on emails and offline communication.

Why It Matters

At Tesla's scale, even a small improvement in pricing decisions could translate into substantial business impact.

$96B
Annual Revenue · 2023
1.0%
Improvement — drag to adjust
≈ $960M
Potential Business Impact
Solution Evolution

A Phased Roadmap

Rather than solving everything at once, I planned a product roadmap that gradually evolved the platform — from centralizing execution to supporting better pricing decisions.

Phase 01
Build a Foundational Pricing Workflow
Phase 02
From Executing to Editing Prices
Phase 03
From Editing to Recommending Prices
Phase 04
From Recommending to Autonomous
Phase 01

Build a Foundational Pricing Workflow

Build the operational foundation for scalable pricing execution.

Support Multiple Product Lines

Unified pricing workflows across vehicles, charging, energy, service parts, and rewards.

Information architecture of the Tesla Pricing Platform: five product lines — Vehicle, Charging, Energy, Service Parts, and Rewards — each with their pricing sub-categories.

Standardize Pricing Workflows

Introduced changesets and approval workflows to replace fragmented execution with a structured, traceable process.

The changeset and approval workflow interface used to stage, review, and activate price changes.
Revamping the pricing workflow Before: pricing bounced between Edit prices and Approve through emails, Excel, and offline back-and-forth, then Activate. After: a structured, traceable flow — check current price, edit, simulate, save to a changeset, approval flow, approved and wait, new price activated — with revert and system-tracked loops. BEFORE — FRAGMENTED Edit prices Approve Activate Sending emails · tons of Excel Back and forth · offline communication REVAMPED THE EXPERIENCE AFTER — STRUCTURED & TRACEABLE Update in System Check current price Edit prices Simulate price change Save to changeset Approval Flow Approved and Wait New Price Activated Revert
Phase 02

From Executing to Editing Prices

Move pricing operations from spreadsheets into the platform.

With the execution workflow in place, the next step was to replace spreadsheet-based editing with native pricing tools for large-scale pricing operations.

The Edit Hardware Prices screen with a Bulk Edit panel — selecting multiple operation centers and applying a new price, or increasing/reducing by percent or absolute amount.

Native bulk editing transformed repetitive spreadsheet workflows into structured platform operations.

Phase 03

Enable Better Pricing Decisions

With pricing operations fully moved into the platform, the next step was to help users make faster and more confident pricing decisions through data, recommendations, and validation.

Pricing Insights

Historical sales trends provided the context needed to evaluate pricing decisions.

A service-part detail page showing a year of sales-volume trends alongside cost breakdown, price customization rules, and the final calculated price.

Price Recommendation

Recommended prices reduced the time required to set new charging prices.

76%
less time to set new prices
The Set Up Tesla Prices screen with a Price Recommendation panel suggesting a default price benchmarked against nearby sites, idle fees, and time-of-use pricing.

Price Validation

Automatically detected pricing anomalies before approval.

58%
less price-checking time
24%
fewer price errors
A price-validation screen flagging abnormal prices — drastic changes, uncompetitive prices, and significant spreads — across supercharger sites before approval.
Phase 04

Automation and Continuous Development

Product roadmap — not implemented during my time at Tesla.

This final phase remained on the product roadmap when I left Tesla. Looking back, it's interesting to see how closely its vision aligns with today's AI-native enterprise software — from workflow execution to decision support and intelligent automation.

Results

Measurable Impact

Pricing Time
82%
Reduction
Pricing Errors
42%
Reduction
Global Markets
3 63
Expanded coverage
"The platform enables us to make pricing decisions faster, with greater confidence and flexibility."
Sendil Palani, VP Finance
Sendil Palani
VP Finance
Reflection

What I Took Away

01

Designing for Decision Confidence

The most valuable enterprise products don't just help users complete tasks — they help them make confident decisions.

02

Context Before Intelligence

Improving pricing decisions wasn't about adding smarter features. It started with bringing fragmented data, workflows, and collaboration into one place.

03

From Execution to Decision Support

Looking back, the roadmap evolved from executing workflows to supporting decisions — a direction that closely mirrors how AI is reshaping enterprise software today.

Next project
Rethinking Claude Code →