Research Wiki · Pricing and revenue research

Demand elasticity

Demand elasticity is a concept within pricing and revenue research that helps organise evidence around what value is being priced? It should be defined operationally so different teams measure and interpret it consistently.

Direct definition

Demand elasticity is a concept within pricing and revenue research that helps organise evidence around what value is being priced? It should be defined operationally so different teams measure and interpret it consistently.

When Demand elasticity is used

Research and analytical methods for understanding value, willingness to pay, price response, pack architecture and revenue trade-offs. It is most useful when the decision owner can state what different findings would cause the organisation to do differently.

Business and research questions it can answer

What value is being priced?

Translate the question into an observable measure, comparison or decision rule before collecting evidence.

How does demand change by price?

Translate the question into an observable measure, comparison or decision rule before collecting evidence.

Which price architecture protects both conversion and margin?

Translate the question into an observable measure, comparison or decision rule before collecting evidence.

What would contradict the preferred interpretation?

Translate the question into an observable measure, comparison or decision rule before collecting evidence.

How the design should work

Start with the decision, target population and competing explanations. Choose the leanest design that can distinguish the alternatives, then specify recruitment, measurement, quality controls, analysis and reporting limits.

Frame the estimand or decision

Define the population, unit, outcome, alternatives, time horizon and consequence of error.

Specify the evidence

Choose sources, measures and comparisons that can distinguish the competing explanations.

Protect quality

Predefine recruitment, exclusions, missing-data rules, assumptions, validation and audit trail.

Translate the result

Report effect, uncertainty, limitations and the action that follows each plausible result.

Sample-size and data considerations

Sample size should follow the required precision, subgroup comparisons, incidence, weighting efficiency and expected effect size. A large convenience sample does not repair poor coverage or measurement.

Analysis and interpretation

Begin with data quality and base definitions, then use descriptive patterns, uncertainty, subgroup contrasts and driver or choice models where justified. Interpret effects in business units and test whether conclusions survive weighting and alternative specifications.

Practical example

A business is considering a price increase. Demand elasticity would test value perception, likely demand response, segment differences and the effect of package or communication, then combine the research with cost and margin scenarios.

Advantages

  • Creates a shared definition for demand elasticity across teams.
  • Connects evidence to the decision: What value is being priced?
  • Makes assumptions, uncertainty and next actions easier to challenge.

Limitations

  • The result is only as credible as the population, measurement and evidence quality.
  • Stated responses may not reproduce real behaviour in a different context.
  • A single study captures a bounded time, market and decision frame.

Common mistakes

  • Starting with a favourite methodology before defining the decision and competing explanations.
  • Using a convenient sample or metric while making claims about a broader population or behaviour.
  • Treating a single score as the diagnosis instead of tracing the drivers and counter-evidence.
  • Writing the recommendation after seeing the data without documenting the decision rule or uncertainty.

Practical checklist

Frequently asked questions

What is Demand elasticity in simple terms?

Demand elasticity is a concept within pricing and revenue research that helps organise evidence around what value is being priced? It should be defined operationally so different teams measure and interpret it consistently.

How much data is needed?

Sample size should follow the required precision, subgroup comparisons, incidence, weighting efficiency and expected effect size. A large convenience sample does not repair poor coverage or measurement.

What is the biggest interpretation risk?

Starting with a favourite methodology before defining the decision and competing explanations.

Can Ninth Atlas apply this to a live study?

Yes. The engagement would begin with the business decision and evidence gap, then specify the method, sample, quality controls, analysis and decision output.

Related terms

Editorial and methodology note

This reference is written by Ninth Atlas as a decision-oriented explainer. It separates definition, design, analysis and limitations so a method is not mistaken for an answer. Final study specifications should be reviewed against the actual population, evidence, risk and regulatory context.

Sources and further reading

Need the method applied to a live decision?

Share the market, customer, product or investment question that needs a defensible evidence design.

Brief Ninth Atlas