Sell the problem first. The solution can wait.

Teams love leading with solutions. Features are concrete, screenshots are ready, and the roadmap looks busy. Buyers, inconveniently, are still stuck on whether you understand the problem. Leading with the answer before the question is how you get polite nods and empty pipelines.

The best products sell the problem first. Features are answers. Problems are the reason anyone listens. Name the stuck moment in customer language, prove you recognise it, then show the solution. Reverse that order and marketing becomes a translation job for a language nobody asked to learn.

Solution-first vs problem-first

**Bad SaaS:** homepage opens on integrations and AI badges. **Good SaaS:** homepage opens on the weekly chaos you remove, then shows how. Slack’s early wedge was not “another chat app.” It was stopping decisions from dying in email.

**Bad outdoor / consumer:** fabric specs before the weather problem. **Good outdoor / consumer:** “stay comfortable when the weather flips,” then the fabric. Hospitality and travel win when they name anxiety (unknown city, bad timing) before amenity lists.

How to lead with the problem

1. Interview five customers: what they tried before you, what they stopped after switching.
2. Rewrite the homepage headline from their sentence, not your feature map.
3. Reorder demos: pain moment, then product as the response.
4. Cut features from the story that do not serve the named job.
5. Add one before/after proof tied to that job.
6. Freeze marketing claims that invent problems customers never mentioned.

Jobs-to-be-done framing is still useful via Harvard Business Review. For sharper problem discovery, Y Combinator’s Library rewards talking to users over polishing decks. Related: how I decide whether a product is worth building.