Problem Sections That Show the Cost of Doing Nothing (37)

What a cost-of-inaction problem section actually is

A cost-of-inaction problem section is the decision to price the visitor's current way of working instead of just naming what hurts. A plain problem section says "this is broken." A cost-of-inaction section says "and here is what leaving it broken keeps costing you," in money, hours, or risk. That second half is what turns a nod of recognition into a reason to act, because the reader can no longer treat the status quo as free.

The best problem sections put a price on the pain in one of a few ways, often more than one at once:

• Stacked stat cards. A row of hard numbers that price the pain from every side. Nautis lines up four: 54% burnout, $500 a month, 30 tools, and 40% of time lost, so the cost is impossible to wave off as small.
• A headline that names the leak. Prodpad leads with the idea that disconnected tools are costing the reader, then backs it with a backlog of 300 items and no system, so the loss is stated before the reader can look away.
• A status-quo scene the reader recognizes. Bulkmark quantifies the waste at a glance (3,000+ saved, 97% never opened, 12 seconds to digest) so a habit the reader already has suddenly reads as effort thrown away.
• A cost that compounds. The strongest closers push the loss into the future. Voltaiq spells out that delayed launches let competitors reach the market first and trigger cash burn, so the bill is not a one-time hit, it keeps running.

Why it works

Most visitors treat their current setup as free. They already paid for it, they know how it works, and switching is effort. That inertia, not a competitor, is what usually wins. A cost-of-inaction section attacks the inertia directly by counting what the status quo quietly takes every week, so the safe-looking choice starts to look like the expensive one.

The move is a reframe of what the reader is comparing. Without this section, they weigh the cost of change against zero, and zero almost always wins. With it, they weigh the cost of change against a real, running loss they can now see. Membership does this bluntly for creators, framing the status quo as being one algorithm change away from losing an audience they spent time and money to build. The stakes stop being hypothetical.

How the best problem sections do it

Nearly three-quarters of the problem sections in the library price the cost of inaction in some form, so the examples below are the disciplined end of a common move, not a rare one. Across them, the pattern that lands is specificity. The strongest sections attach a number the reader can check against their own week, name the exact setup causing the loss rather than a generic problem, and point the cost forward so it reads as something that keeps happening. A figure like Nautis's 40% of time lost, or Bulkmark's 97% of saved items never opened again, is far harder to dismiss than "you are wasting time."

You can see the range in the full problem section gallery, and the natural next step, where the feature section has to pay off the cost with a concrete fix.

40/100

Common mistakes

10/100

The usual failure is a cost that is asserted but never priced: "you are losing time and money" with no number, no named setup, and nothing that says the loss is growing. It reads as generic and the reader moves on. The opposite failure is piling on the doom until the section only deflates, with no signal that any of it is fixable. The best examples avoid both by pairing a hard cost with a way out. Lokalise raises real pain and then defuses it in the same breath with a line that both problems are fixable, so the section motivates a move instead of leaving the reader stuck in the loss.