Stage 1

The misery hypothesis, explained

The misery hypothesis is your best guess at the problem a buyer has right now. Here's how to write one, why it works and how to recover when it's wrong.

Kevin French
· 3 min read

The misery hypothesis is the line in your opener where you say what you think is hurting. Not what you sell. What hurts. It's the third part of a Hypothesis Opening, and it's the part that earns the reply.

Everything before it sets up the guess. Everything after it invites the buyer to fix the guess.

What it is

A misery hypothesis is a specific, falsifiable claim about a problem this buyer likely has, based on something real you found. It sounds like "my guess is" or "I suspect" followed by a concrete pain.

It's a guess on purpose. You're not pretending to know their business. You're showing you did enough homework to make an educated bet, and you're putting it on the table where they can see it.

And it's about misery, not opportunity. Senior buyers get pitched on upside all day. Upside is easy to ignore. A problem they're living with this week is not.

Why it works

A senior buyer reads an opener in a couple of seconds and asks one question. Does this person understand my situation?

A pitch answers no. It's about the seller. A compliment answers no. It's about nothing. A misery hypothesis answers maybe, and maybe is enough to get a reply.

There's a second reason. People correct mistakes almost by reflex. When you name a problem that's close but not quite right, a busy executive will often take ten seconds to set you straight. That correction is gold. It tells you the real problem in their own words.

So the hypothesis works whether you're right or wrong. If you're right, they say yes. If you're close, they correct you. Only a vague hypothesis fails, since there's nothing to agree with and nothing to fix.

How to write one

Start from the signal and the seat. Say a mid-size logistics company names a new COO, and its last 10-Q mentions rising cost per shipment and an ongoing warehouse systems upgrade. The research hook is the new seat. The personal trigger is the first 90 days and the board wanting a cost story.

Now ask what's painful about that combination. A new COO with a cost problem and a half-finished systems upgrade probably can't get trustworthy cost data by site. That's the misery.

Here's the full opener.

Saw you stepped into the COO role, and the last 10-Q flags cost per shipment going the wrong way. In the first 90 days, the board will want a site-by-site cost story. My guess is the warehouse systems upgrade means you can't get clean cost data by site yet, so every answer takes a week of spreadsheets. Is that accurate, or is the bigger issue something else?

The misery line names one problem, in plain words, that this person would feel personally. It doesn't name your service. It doesn't stack three problems in case one lands.

What a weak one looks like

"I suspect you're looking to drive efficiency" is not a hypothesis. Every company wants efficiency. There's nothing to confirm or correct.

"My guess is you're struggling with digital transformation" is worse. It's a category, not a problem.

"I bet your data is a mess" is closer, but it's rude and it's vague. Which data? A mess how? What does it cost them?

The test is simple. Could the buyer answer "yes, exactly" or "no, it's this instead"? If neither answer makes sense, rewrite it.

When you're wrong

You'll be wrong a lot. That's fine. That's the design.

When a buyer writes back "not really, our problem is carrier contracts, not data," don't argue and don't pivot to a pitch. Thank them, ask one follow-up about the carrier contracts and listen. You've just learned more in one reply than a discovery call usually gets you.

I wrote more about this in the method. The short version is that a senior buyer's correction is the most honest data you'll get in the whole cycle.

One problem, one person

Write a different misery hypothesis for each person on the committee. The CFO's misery on the same event is different from the IT director's. The CFO can't defend the forecast. The IT director is running two systems at once with the same headcount.

Same research, different pain, different line.

And keep it to one sentence. If your misery hypothesis needs a paragraph, you don't have a hypothesis yet. You have notes.

The misery hypothesis is the bravest line in the email. It's where you stop describing and start guessing. Guess with precision, guess kindly and let the buyer finish the thought.

See which of your accounts are moving.

Stage 1 reads your site, finds accounts that fit and checks their filings and news. Your first Board in about two minutes. Free for 14 days, no credit card.