There’s a slide in almost every B2B deck. It’s called the problem slide. It’s usually the least accurate slide in the deck.
Because most founders don’t start with a problem. They start with a product. A technology they found interesting, a feature they wanted to exist, a market they read about in a newsletter at seven in the morning. They build it. They get early users. The early users are enthusiastic, because early users are almost always enthusiastic, which is one of the crueler tricks that starting a company plays on you.
And then, when it’s time to find new customers, a problem statement has to appear somewhere. In a sales deck, a cold email, a LinkedIn post. Problem: X. Solution: us.
The problem on that slide was not discovered. It was constructed. Built backwards from the product. And a constructed problem behaves differently from a discovered one.
A constructed problem has internal logic. It holds together. You can explain it in three sentences and a diagram. What it does not have is urgency. No one went home on a Tuesday and stared at the ceiling thinking about this problem. The problem was not a problem until someone needed it to be one.
A discovered problem is different. Someone had it, wanted to be rid of it, was willing to do something about it. That difference shows up in the pipeline. In sales cycles that run just a little longer than they should.
I was at a product demo recently. There were pretzels, a sponsor banner for a company whose product I could not determine from the banner, and a presenter with slides where every word was a different weight of the same font, which gives the impression of emphasis without the inconvenience of deciding what actually matters. He opened with a lengthy company history and overview. Then a problem statement. Then the solution.
Around slide seven, by which point we had covered the founding story, the market opportunity, and a slide titled “Our Journey” that contained photographs, I noticed the problem statement sounded like it had been written after the solution already existed.
Afterwards I spoke to him by the pretzel bowl. Sharp, curious, clearly capable. Eighteen months in. He knew the product the way you know a language you learned as a child.
I asked him what problem he’d set out to solve. He told me. It was a good answer. Polished. The kind you give after eighteen months of being asked the question.
I asked him when he’d discovered that problem.
He paused for exactly the amount of time that means something.
“We refined it as we built,” he said, which is a reasonable thing to say and also means: after.
Marketing had sharpened the message. Sales had refined the pitch. Everyone had tried to understand why results were lagging. And the real cause sat one layer deeper, in the order of things: product first, problem second.
That order is not fixed by better messaging or positioning.
First the problem. Then everything else.