Pricing Simulation Tools: Test a Price First

A pricing simulation tool lets you test a price change before you make it: you enter a new price and it estimates what happens to units sold, revenue and profit. The estimate is only as good as the demand model behind it, so the useful tools build that model from your own sales history and show a range of outcomes, not a single confident number. When the range points both ways, the right answer is often to hold and gather more data rather than move.

What Is a Pricing Simulation Tool?

A pricing simulator, sometimes called a price simulation tool or pricing scenario tool, answers "what if?" questions. What if this product cost $33 instead of $30? What if we cut the whole category 10% for a month? What if costs rise and we pass half of it on? Instead of changing a live price and waiting to see, the simulator predicts the outcome from a model of how customers respond to price.

Every simulator has the same three parts: a baseline (current price, cost and sales), a demand model (how sales change when price changes) and an objective (usually profit, sometimes revenue or units). The demand model is the part that separates a useful tool from a spreadsheet that just multiplies numbers.

Types of Pricing Simulation Tools

Type	Where the demand model comes from	Best for	Main weakness
Spreadsheet what-if	You type in a guess for how much sales will change	Quick margin checks	The answer is only as good as your guess
Elasticity-based simulator	Estimated from your own past prices and sales	Products with sales history and some past price changes	Needs price variation in the data to be reliable
Survey-based (conjoint) simulator	Customer choices in a structured survey	New products and feature-and-price trade-offs	Stated choices tend to overstate what people will pay
Enterprise scenario planning	Demand, competitor and cross-product models together	Large retailers modeling whole categories	Cost, setup time and data requirements

Survey-based simulators are well established in market research. Sawtooth Software's choice simulator, for example, uses conjoint survey results to estimate the share of customers who'd choose each product at different prices and feature sets. The caution is that what people say in surveys isn't quite what they do: a 2020 meta-analysis by Schmidt and Bijmolt covering 77 studies found hypothetical willingness to pay was 21% above real willingness to pay on average. Simulations built on survey data should be read with that bias in mind; the trade-off is explored in price survey vs price testing.

Worked Example: Simulating Four Prices

A product sells for $30, costs $12, and sells 500 units a month, for $9,000 of monthly profit. An elasticity-based simulator estimates its price elasticity at −1.8, with a plausible range of −1.4 to −2.2. Here's what it predicts for four prices under each value:

Price	Profit if elasticity is −1.4	Profit if −1.8 (central estimate)	Profit if −2.2
$27	$8,692	$9,066	$9,456
$30 (current)	$9,000	$9,000	$9,000
$33	$9,188	$8,845	$8,514
$36	$9,297	$8,643	$8,035

The central estimate says a small cut to $27 is marginally better, by $66 a month. But look across the row. If the true elasticity is −1.4, raising to $36 would earn $297 more; if it's −2.2, cutting to $27 earns $456 more. The plausible range points in opposite directions, and the central estimate's gain is smaller than the uncertainty around it.

A tool that only showed the central estimate would recommend a price cut with false confidence. A tool that shows the range tells you the truth: this product needs more price variation in its data before anyone should move its price. The practical move is to hold, or run a small, controlled test, as covered in how to run a price A/B test the right way. The formula behind these numbers is explained in the price elasticity of demand formula.