Panic Buys Patches. Planning Buys Products.

Every founder has heard the advice: find the customer whose hair is on fire.

Demand has an opinion about that advice.

Take one problem and watch two businesses buy their way out of it. The first one is on fire: the support inbox blew past two hundred unanswered emails the week the product got featured somewhere. The second one is calm: they know support is becoming a function, and they are picking the system it will run on.

Same problem. The urgent buyer budgets around a quarter of what the deliberate one does. In social media the gap is wider still, closer to a sixth. Across almost every problem businesses pay to solve, the pattern repeats: the emergency version of the ask is the small version.

Urgency gets you the signup. It does not get you the contract.

What the two purchases actually look like

The on-fire buyer is not shopping for Zendesk. They are searching "clear shared inbox fast", installing whatever promises relief before lunch, and paying the smallest number on the pricing page. Next week, when the fire is out, that tool is a line item someone questions.

The deliberate buyer is doing something else entirely. They are mapping how tickets should route, asking whether the tool connects to their Shopify orders, checking what the help-centre looks like under their own logo. They take weeks. And they arrive with several times the budget, because they are not buying relief. They are buying infrastructure.

Builders meet the first buyer constantly and the second one rarely, and draw exactly the wrong conclusion from it. The desperate signups are not your market. They are your market's waiting room.

The exception that proves the rule

One kind of emergency pays properly: revenue leaking in real time.

When the urgent problem is hot leads going cold, the money roughly doubles instead of shrinking. A lead that waited an hour is a sale that went somewhere else, and the buyer can count it. This is why speed-to-lead tools, abandoned-cart recovery, and instant quote responders get to charge like serious software while other urgent fixes get haggled down: they are the only patches priced in lost revenue per minute.

Everything else that is urgent, the backlog, the deadline, the mess, buys the cheapest tier and cancels early.

What this means for your product

• Build the fire-hose tier on purpose. A self-serve plan that delivers relief in the first session, priced low without apology. Its job is not margin, it is being already installed when the calm, funded evaluation starts next quarter. The upgrade path from "cleared the inbox" to "runs our support" is the actual product strategy.
• Calibrate pricing on the planner, not the panicker. If your paid tiers were shaped by what desperate signups tolerate, you have priced the whole product off your smallest buyers. The deliberate buyer comparing you against Zendesk was always going to pay several times more, and your pricing page should have a floor that respects it.
• If you stop live revenue leaks, charge like it. The cart recoverer and the lead responder sit in the one category where urgency doubles budgets instead of cutting them. Most tools in that spot price like utilities out of habit.
• Read your churn honestly. The user who arrived in a panic, fixed the week, and left was never the deal. Watch instead for the trial that moves slowly and asks about integrations. Slow and thorough is what a real budget looks like from the outside.

The customer with the burning inbox wants a bucket of water. The customer who just realised support is a function wants plumbing. Hand out buckets to meet people. Sell plumbing to build a company.

This reading comes from millions of demand signals, collected continuously. Not surveys and not commentary, but real buying activity, the same intelligence that runs inside the product. It is also one more case of what we keep finding since the market started moving at the speed of AI: the loudest demand and the valuable demand are rarely the same demand.