The Demand Threshold: How Much Pull Is Enough?

There's a moment every product team recognizes even if nobody names it out loud.

Your product is clearly good. People sign up, complete onboarding, get to the "aha," maybe send a teammate a link. And then they go right back to whatever ugly workaround they were using before.

The usual explanations come fast: better positioning, more top-of-funnel, tighter onboarding, the two missing features everyone keeps asking for. Sometimes those help.

But sometimes they're a way to avoid the simplest, most painful possibility: you haven't crossed the demand threshold. You built something interesting. You didn't build something people switch to.

The Prediction Nobody Wants to Hear

The four forces model makes a blunt prediction about switching: people switch when push plus pull exceeds habit plus anxiety. Not when they understand your product. Not when they admire the UI. Not when they agree you're better. When the force toward change finally outweighs what's keeping them in place.

That tipping point is the demand threshold.

Below it, you get compliments. Above it, you get switching.

Your product can be objectively good and still generate insufficient pull relative to what habit and anxiety are doing on the other side of the equation. And when that's the case, no amount of lifecycle email optimization will fix it.

Pull Isn't "I Like This." Pull Is "I'm Moving. Now."

Pull gets over estimated when you’re measuring the wrong thing.

You hear "this is awesome" and "this would save me so much time" and interpret that as demand. But those sentences don't mean "I'm switching." They mean "I'm impressed." Impressed is a low-commitment emotion. People get impressed by products all day long. They also keep their spreadsheets.

Pull is behavior change. It's when the user starts doing things that only make sense if they're planning to come back.

They import real data. They set defaults. They create a template. They invite a teammate. They rebuild the workflow a second time. They stop hedging with "maybe" and start speaking in "when."

You can feel the difference. The product stops being a possibility and starts being a plan. Everything else is brand sentiment — useful, but not sufficient.

Where Pull Actually Comes From

Teams love to say "if we just add X, we'll have pull." Sometimes that's true. Usually it's not. Feature roadmaps rarely create pull because pull doesn't come from capability. It comes from contrast — moments where the user can feel the better future without doing math.

Time contrast: the job gets shorter. Not faster in theory. Shorter in lived experience. A user does something in 30 seconds that used to take 30 minutes, and they can't un-feel it.

Confidence contrast: the job gets safer. The user feels protected from mistakes. Undo. Preview. Recovery. Clear next steps. Guardrails that don't feel like punishment. Confidence is pull because it reduces anxiety — and anxiety is one of the two forces holding users in place.

Continuity contrast: the job stops resetting. The product holds the thread. History. Templates. Defaults. Reuse. Next week is easier because of what you did this week.

This last one is the most under-designed source of pull. Many products are great at first-use magic and terrible at second-use inevitability. If your pull evaporates after the first session, you'll never cross the threshold for the mainstream market. You'll get a museum of cool outputs and no behavior change.

The Most Valuable People in Your Data

If you want a leading indicator of whether you're approaching the demand threshold, stop interviewing your happiest users for a minute. The most valuable people are the ones who tried the product, got value, said it was good — and didn't switch. The almost-switchers.

They're standing directly on the threshold. They felt pull. They stayed anyway. Which means they can tell you exactly what exceeded what.

When you talk to them, don't ask what features they want. That's downstream. Ask four things and don't let them answer vaguely.

What was the last straw with the old way? Not "it was inefficient." What happened? What did it cost? What broke?

What did you see in the product that felt like relief? Not "it's easier." What was easier? What became possible that wasn't before?

What made you hesitate? Not "we need to think about it." What felt risky? What felt like effort? What felt politically difficult to justify?

What would have made you switch next week instead of "someday"? Not "better onboarding." What would have reduced anxiety or habit friction enough to move?

The pattern usually surfaces fast. Pull is real but not specific enough to feel inevitable. Or anxiety is the veto — trust, reversibility, defensibility. Or habit friction is too high — migration, integration, coordination. Or push isn't intense enough yet — the status quo still feels tolerable.

One caveat: users will often describe this as a rational cost-benefit calculation. It rarely is. They're reporting the story they can defend. The real force is usually emotional — fear, confidence, embarrassment, identity, social risk. You have to listen for that layer underneath the rational narrative.

Why "Better" Isn't Enough

This is the part that makes teams mad, because it feels unfair.

You can genuinely be better than the status quo and still not win. Switching isn't a feature comparison. It's a force comparison. The user isn't asking "which tool is best?" They're asking "is switching worth it right now, in the middle of my life, with all my constraints and risk?"

That's why so many products end up with the same growth pattern. Early adopters switch fast — strong pull, low habit, low anxiety. Everyone else admires from a distance — moderate pull, strong habit, high anxiety. And then the company calls it a marketing problem.

To be fair, sometimes it is a marketing problem. But often it's an equation problem. And when it's an equation problem, the answer isn't louder marketing. It's either strengthening pull until it crosses the threshold — through the contrasts above — or narrowing to the segment where push is already strong enough that your pull doesn't have to do all the work.

A product below the demand threshold is a product people can imagine using. A product above it is a product people can’t imagine living without.

When you're staring at a dashboard that says people like you and a business that says growth isn't compounding, don't start by asking how to improve activation. Start by asking whether your pull is strong enough to beat habit and anxiety for the people you want next. If it isn't, the experience can be beautiful and the product can still fail because it isn't strong enough to inspire someone to act.