You raise a price by 10% to protect a thin margin. Volume falls 3%, revenue climbs, and a competitor quietly thanks you for the umbrella. Or you raise it by 10%, volume falls 25%, and you spend the next quarter explaining the dip. Same decision, opposite outcome, and the difference was knowable in advance. The four ideas in this guide are how you'd have known.

The quick version

  • Scarcity is the starting condition: limited resources, unlimited wants. Every price exists because something can't be had in infinite quantity for free.
  • Demand (how much people want at each price) and supply (how much sellers will offer at each price) settle at a price where the two match. That price is a signal, not a scoreboard.
  • Elasticity is the follow-up question: when price moves 1%, how much does quantity move? It decides whether a price rise grows revenue or shrinks it.
  • The leadership move: before changing any price, wage, or fee, estimate the elasticity. Guessing the direction is easy; the magnitude is what costs you.

The idea in depth

Economics begins not with money but with a constraint. Lionel Robbins gave the field its working definition in 1932: economics is "the science which studies human behaviour as a relationship between ends and scarce means which have alternative uses." That is scarcity, not poverty, but the simple fact that you cannot have all of everything at once, so every choice spends something you could have used elsewhere. A team has finite engineering hours; a budget has a bottom; your own week has 168 fixed slots. Price is the mechanism a market uses to ration scarce things among the people who want them most.

The cleanest picture of how that rationing happens is the supply-and-demand model, and the person who fixed it in the modern mind was Alfred Marshall in his Principles of Economics (1890). Marshall's enduring image is the pair of scissors. Asking whether price is set by demand or by supply, he wrote, is like disputing "whether it is the upper or the under blade of a pair of scissors that cuts a piece of paper." Neither blade cuts alone. Demand slopes down, cheaper means people buy more; supply slopes up, higher prices coax out more product, and the price settles where the blades cross. So the move is to stop treating your price as a statement of worth you defend, and start treating it as the point where two curves currently meet. When demand shifts (a new competitor, a recession, a fashion), the meeting point moves. That isn't a failure of nerve; it's the model working.

flowchart LR
  A(["Scarcity: limited means, unlimited wants"]) --> B("Demand: more buyers as price falls")
  A --> C("Supply: more sellers as price rises")
  B --> D(["Equilibrium price where the two meet"])
  C --> D
  D --> E("Price acts as a signal to both sides")
Marshall's "scissors": price is where the two blades cross, not a verdict from either one alone. Leaders Loop

The price is a message, not a scoreboard

Why care that price is a meeting point rather than a judgement? Because of what that meeting point carries. Friedrich Hayek's 1945 paper "The Use of Knowledge in Society" (American Economic Review, vol. 35) argued that the economy's hardest problem isn't computing the best allocation, it's that the relevant knowledge is "dispersed bits of incomplete and frequently contradictory knowledge which all the separate individuals possess." Nobody holds the whole picture. A price solves this by compressing it: when tin gets scarce, the price rises, and a manufacturer half a world away economises on tin without ever learning why. The number does the work a memo never could.

The move, then: read prices and wages as inbound messages about your environment, not just outbound levers you pull. A supplier's quote jumps 15%, that's data about scarcity upstream, not merely a negotiation to win. Salaries for a role you're hiring have run away from your band, the market is telling you the talent is scarcer than your last offer assumed. The leaders who get blindsided are usually the ones who treated a moving price as an insult rather than a signal. This is also where supply, demand and scarcity connect to marginal analysis and incentives: the price is the incentive every actor in the system is quietly responding to, one decision at a time.

Elasticity: the magnitude that decides everything

Knowing demand slopes downward tells you the direction a price change pushes volume. It tells you nothing about how hard. That second question is price elasticity of demand, and it is where most pricing instincts go wrong. The formula is plain: the percentage change in quantity demanded divided by the percentage change in price. If a 1% price rise cuts volume by more than 1%, demand is elastic (the ratio exceeds 1) and the price rise shrinks revenue. If volume falls by less than 1%, demand is inelastic (under 1) and the same rise grows revenue. The threshold of 1.0 is the whole game (OpenStax, Principles of Economics 3e).

What makes demand elastic is intuitive once named. The biggest driver is substitutes: the easier it is for your customer to buy something else, the more elastic you are. Necessities are inelastic; luxuries are elastic. And elasticity grows with time, people are stuck in the short run and resourceful in the long run. Estimates for petrol demand illustrate it well: a meta-analysis put the average short-run price elasticity near −0.34 but the long-run figure near −0.84 (Brons and colleagues, Energy Economics, 2008). Drivers can't change much this week; over years they buy efficient cars and move closer to work.

Everyone can guess which way volume moves when price rises. The money is in the magnitude, and the magnitude is measurable.

So the move is to never change a price, fee, or wage without an elasticity estimate, even a rough one. You rarely need the exact number. You just need to know which side of 1.0 you're on. Run a small experiment, look at history (the last time you moved this price, what happened to volume?), or check whether close substitutes exist. The honest limitation: elasticity is not a fixed constant. It changes with the size of the move (a 5% rise behaves differently from a 50% one), the time horizon, and your customers' mood. Treat your estimate as a current reading, not a law of nature, and re-measure after you act.

flowchart TD
  A(["You're considering a price rise"]) --> B{"Close substitutes
for the buyer?"}
  B -->|"Few / hard to switch"| C(["Likely inelastic, rise tends to grow revenue"])
  B -->|"Many / easy to switch"| D(["Likely elastic, rise tends to shrink revenue"])
  C --> E("Test small, measure volume, re-check")
  D --> E
A rough elasticity triage before any price move. Substitutes are the first thing to look at. Leaders Loop

A worked example

A regional B2B software team sells a workflow tool at $40 per seat per month. Margins are squeezed and someone proposes lifting the price to $50, a 25% rise. (All figures here are illustrative, to show the reasoning, not real benchmarks.)

The room's first instinct is the revenue arithmetic at constant volume: 25% more per seat across the base looks like a clean win. The elasticity question stops that. Two segments behave differently. Enterprise accounts have the tool wired into their onboarding and approvals; switching means retraining and risk, so substitutes are weak and demand is inelastic. Small teams can move to a free-tier rival over a weekend; substitutes are strong and demand is elastic.

A quick read of last year's smaller 10% increase showed enterprise volume essentially flat (implied elasticity well under 1) while small-team churn ticked up noticeably (implied elasticity above 1). Extrapolating the 25% rise across both segments uniformly would likely lift enterprise revenue and gut the small-team line. The move that follows from the theory: raise the enterprise price, hold or repackage for small teams, and run the increase as a measured test on a cohort rather than a blanket switch, because the elasticity reading is an estimate to be confirmed, not a guarantee. The single price was never the decision. The two elasticities were.

Frequently asked questions

Isn't this just "supply and demand", which everyone already knows?

The phrase is familiar; the discipline isn't. Most people stop at "prices go up when things are scarce." The useful part is what follows: reading a moving price as a signal rather than an insult, and quantifying how much the other side will move before you act. Direction is common knowledge. Magnitude is the edge.

How do I estimate elasticity if I've never run a formal study?

You usually don't need a study to find the right side of 1.0. Three cheap routes: look at history (when you last changed this price, what did volume do?); run a small, reversible test on one segment or region; and ask how easily your customer can substitute, easy switching means elastic. A rough estimate beats an unexamined assumption.

Does elasticity apply to wages and hiring, not just products?

Yes, a wage is the price of labour. When a role's market pay rises and you don't follow, you're betting the supply of that talent is inelastic (people won't leave). For scarce, in-demand skills that bet usually loses. The same scissors and the same magnitude question apply on the hiring side of the business.

Why did my price rise help revenue but my competitor's hurt theirs?

Almost certainly different elasticities. Your customers had weak substitutes (inelastic, they absorbed it); theirs had strong ones (elastic, they left). Elasticity is specific to a product, a segment, a moment and the size of the move. There is no universal "right" price increase, only the right one for a given demand curve.

Where does this break down?

Elasticity isn't a constant, it shifts with the size of the move, the time horizon and sentiment, so an estimate is a reading, not a law. Markets also misprice when information is hidden or power is concentrated, and prices can carry costs they don't show (see externalities below). Use the model as a lens, then re-measure after you act.

Related in the Toolkit

Where to go next