The Hidden Math Behind "Dynamic" Pricing: How AI Quietly Replaced the Spreadsheet

They said dynamic pricing was too complicated. The CFO pulled up a spreadsheet with 47 columns. The operations lead crossed her arms. The regional managers nodded in that particular way that meant we’ve tried this before and it broke.

And then we let AI take over.

Not as a gimmick. Not as a dashboard with a sparkly "AI-Powered" badge. As the actual pricing engine. The thing that looks at 2,300 SKUs, 14 regional markets, supplier lead times, competitor scrapes, weather data, and the Tuesday-afternoon demand dip in Midwest warehouse districts—and sets a price for every single one of them, every four hours.

The article you're reading is the after. What came before was a year of "let's just do it with a formula" that produced a 12-page Excel model nobody could explain in a board meeting. This is what happened when we stopped explaining the math to humans and let the model do the explaining for itself.

The Problem Wasn't Pricing. It Was the Explanation.

Here's the thing nobody says out loud: dynamic pricing isn't hard. Dynamic pricing is expensive to explain.

A static price is a contract. $4.20 for a pallet of polymer resin, effective Q3, review in October. Everyone knows it. Nobody questions it. If the market moves, you all sit in a conference room and decide together whether to adjust. It's slow, it's consensus-driven, and it's legible. You can point at the number and say "this is what we agreed to."

Dynamic pricing is a conversation that never ends. The price moves every time an input moves. And the inputs don't just move—they move together, and the way they interact is where the actual economics lives. A 2% increase in natural gas futures and a 5% drop in competitor availability and a regional port delay aren't three separate signals. They're one signal, decomposed. The question isn't "what's the price?" The question is "what's the joint effect of these three things on the marginal customer's willingness to pay, net of our cost curve at the current volume commitment?"

You can write that formula. We wrote that formula. It was 14 lines of nested conditionals. The CFO could read it, but could you explain it to a board member who's asking "so do we make more money or less?" You can't. Because the formula doesn't mean anything until you've run it on real data, and the real data is 2,300 SKUs × 14 regions × 4 hours a day, and the formula doesn't compress. It is the explanation. And the explanation is too long.

So people revert to the spreadsheet. And the spreadsheet is static. And the market isn't. And the gap between the two is where you quietly lose margin.

What "Letting AI Take Over" Actually Looks Like

We didn't replace the pricing team. We replaced the mechanism by which the pricing team's judgment got executed.

The pricing team still sets the constraints. They know the floor price based on cost structure. They know the ceiling based on brand positioning. They know which customers get volume commitments and which are spot buyers. They know the seasonal patterns that the model won't catch because they're cultural, not statistical—like how a particular distributor in the Pacific Northwest always over-orders in September because that's when their retail clients place Q4 POs.

The AI handles the continuous optimization within those constraints. It doesn't guess. It solves. Specifically, it's solving a constrained optimization problem that looks something like this:

$$\ max_{p_i} \sum_{i=1}^{N} (p_i - c_i) \cdot q_i(p_i) \cdot w_i$$

subject to:

$$p _i^{\text{floor}} \leq p_i \leq p_i^{\text{ceiling}}$$

$$|p _i(t) - p_i(t-\Delta t)| \leq \epsilon \cdot p_i(t-\Delta t)$$

$$\ sum_{i \in R_j} (p_i - c_i) \cdot q_i(p_i) \geq \text{MarginTarget}_j$$

$$p _i \in \mathcal{P}_{\text{competitor}}(i, t)$$

Where:

• $p_i$ is the price for SKU $i$

• $c_i$ is the fully-loaded cost

• $q_i(p_i)$ is the demand function (the learned, non-linear relationship between price and quantity)

• $w_i$ is a strategic weight (brand tier, customer relationship value)

• The second constraint is price stability—we don't want customers seeing the price jump 8% in one week

• The third is a regional margin floor

• The fourth keeps us competitive with the scraped competitor price band $\mathcal{P}_{\text{competitor}$

That's a constrained optimization problem with ~32,000 variables and ~40,000 constraints. You could solve it by hand. You would spend three years solving it by hand. The model solves it in 90 seconds. And it does it four times a day.

The pricing team's job shifted from computing the price to defining the objective. And that's a fundamentally different cognitive load. One is arithmetic. The other is strategy.

The First 60 Days: The Model Was Right, and That's What Frightened People

Day 1: The model raised prices on 14 SKUs in the Southeast region. The operations team said "those customers will call us." They didn't.

Day 12: The model dropped prices on 6 SKUs in the Midwest. The sales team said "we're leaving money on the table." Revenue was up 3.1% on those SKUs. Volume was up 11%.

Day 28: The model did something nobody expected. It decoupled pricing across regions. Same SKU, same cost, same competitor. But the model priced it $0.34 higher in Texas and $0.21 lower in Ohio. The CFO asked why. The model couldn't answer why. It had found a local optimum in the joint constraint space that a human, reasoning one region at a time, would never have identified because a human reasons sequentially and the model reasons simultaneously.

That's the part that's hard to internalize. A human pricing team is a sequential decision process. You look at Region A, you set the price. You look at Region B, you set the price. You're solving N independent problems and calling it a system. The model is solving one problem with N dimensions. And the cross-regional interactions—where a price move in Texas affects competitor behavior in Ohio, which affects the optimal price in Texas—those are the interactions that create margin. And those interactions are exactly what a human brain is bad at holding in working memory while also remembering the cost curve and the volume commitment and the seasonal pattern.

The model holds all of it. Simultaneously. Every four hours.

The Part Nobody Warns You About: Interpretability Debt

Here's the tradeoff that's in the article title but not in the subtitle: you trade interpretability for optimality. And interpretability has a cost.

The CFO still wants to know why the price moved. The model can tell you the contribution of each factor:

That's a post-hoc explanation. It's not the model's reasoning. It's a reconstruction. The model didn't reason "the competitor moved, so I'll move." It found a point in 32,000-dimensional space where the objective was maximized and the constraints were satisfied. The attribution table is a translation of that point into human language.

And that translation is where the interpretability debt lives. The CFO can read the table and say "okay, that makes sense." But if the model moves the price against the direction the table suggests—because of a second-order interaction that the attribution table doesn't capture—the CFO will ask "why did you do that?" And the answer is "because the joint optimization said so, and the joint optimization is a 32,000-dimensional function I can't draw you on a whiteboard."

We built a separate explanation layer. Not the model. A different model whose only job is to take the price decision and generate the human-readable narrative. And that layer is where most of our ML engineering time actually goes. Because the pricing model is the easy part. The explanation model is the hard part. Because you're not predicting a number. You're predicting a story that a CFO will accept.

The Numbers, Six Months In

The margin line is the one that made the CFO stop talking. 3.7 points on a $40M revenue base is $1.5M/year. The article title says "they said it was too complicated." The CFO's spreadsheet said it was too complicated. The model said it was a 32,000-variable optimization problem, and it solved it in 90 seconds.

The customer complaint rate going down is the one that surprised us. We expected more complaints. "Why is the price different this week?" is a natural human question. And it's a question the model handles well, because the price is different this week, and the model can explain why in a way that's consistent with what the customer saw on their last order.

What This Means for the Pricing Team

The pricing team didn't disappear. They got more strategic. They spend less time on the spreadsheet and more time on the questions the spreadsheet couldn't answer:

• "Should we introduce a new regional price tier for the Pacific Northwest?"

• "If we want to win the Henderson account, what's the margin cost?"

• "What's the elasticity of our mid-tier customers if we move from quarterly to monthly pricing?"

Those are judgment questions. The model answers the arithmetic. The team answers the strategy. And the interface between the two is the constraint set. The team defines the constraints, and the model solves within them.

It's a clean division of cognitive labor. Humans are good at defining what matters. Models are good at optimizing over what you've defined. And the gap between "what matters" and "the optimal value" is where the margin lives.

The Title, Revisited

"They said dynamic pricing was too complicated."

Yes. It is complicated. The explanation of dynamic pricing is complicated. The mechanism of dynamic pricing is a constrained optimization problem with 32,000 variables. And the human who has to explain it to a board of directors has to compress a 32,000-dimensional solution into a sentence.

AI didn't make dynamic pricing simpler. It made the execution of dynamic pricing effortless. And the explanation of dynamic pricing is now a separate, dedicated problem with its own model and its own team.

The spreadsheet said it was too complicated. The model said it was a 32,000-variable optimization problem. And it solved it in 90 seconds.

And the CFO stopped talking.

Dr. Julie Jones, PhD in AI Systems Design, writes about the operational intersection of machine learning and business process design. She has spent six years building pricing and allocation systems for mid-market industrial distributors.