Three Layers of the Problem

Name the emotional problem, not just the practical one, and copy starts converting.

Every problem your product solves has three layers stacked on top of each other, and almost every homepage only writes down the top one. The external layer is the practical task, the thing the tool literally does. The internal layer is how living with that problem actually feels, stupid, anxious, behind. The philosophical layer is the belief underneath both, that the situation itself is unfair and shouldn't have to be this way. Most copy states the external layer and calls it done. That gap is where the best positioning in the book lives.

What to do: For every problem your product solves, write three separate sentences, one external, one internal, one philosophical. Then open your own homepage and mark which sentences on the page actually match each layer. If every line you can point to is external, you are describing a feature, not selling relief.

Why it works: People decide on the internal and philosophical layers, then use the external layer to justify the decision afterward, so copy that only argues the external case is winning an argument nobody was having.

Example: Stewart Butterfield wrote an internal memo to the Slack team on July 31, 2013, two weeks before the product's preview launch, titled "We Don't Sell Saddles Here." He later published it publicly on Medium in February 2014. The memo told the team plainly that Slack was not chat software. It was relief from the stress of information overload and the anxiety of decisions buried in email threads nobody could search. The tool was the external layer. The memo sold the internal one, and it is still taught as a positioning case study more than a decade later.

Walk it through

Run the same three-layer split against Slack itself, first the 2013 pitch and then the live homepage today.

1. Write the external layer. What Slack literally does: send messages, organize channels, search old conversations. Every competitor can claim this layer too, since it describes the mechanism, not the pain.

2. Write the internal layer. How the old way felt: buried in email, unsure what your own team was working on, embarrassed that a decision got made in a thread you never saw. Butterfield's memo names this directly instead of leaving it for the customer to infer.

3. Write the philosophical layer. The belief underneath the frustration: work correspondence should not require the discipline of archaeology, and a team's collective knowledge should not quietly die in a thousand unsearchable inboxes. This is the layer that turns a purchase into a cause.

4. Now check whether a live homepage still says any of it. Here is slack.com in July 2026.

Slack's homepage headline reads "All your people and AI agents working together," with a subhead describing Slack connecting the team and Slackbot multiplying what they can do

"All your people and AI agents working together." That is the entire headline, and the subhead below it just describes Slack connecting the team while Slackbot multiplies what they can do. Both lines are pure external layer, what the product does and who it does it with. No stress, no chaos, no trace of the feeling the founding memo sold so hard. Thirteen years and a much bigger market later, even the company that wrote the definitive case for the internal layer has drifted back to describing the mechanism on its own front door.

The read

External is the mechanism, internal is the wound, philosophical is the cause. Most homepages get the first one right and stop there.
The memo that made the internal layer explicit is the exception, not the norm. That is exactly why it is still taught over a decade later. Everyone else defaults to features.
Naming a layer once does not mean keeping it forever. Slack sold relief from chaos to get to product-market fit, then let the homepage drift back to plain description once the category existed and the mechanism itself became enough of a pitch.

Steal it

Do this exercise for every core problem your product solves, not once for the whole company. Write the external, internal, and philosophical sentence for each one on paper before you open a doc to draft actual copy. Then read your current homepage line by line and mark which sentences hit which layer. If everything you find is external, you have a spec sheet, not a pitch, and the fix is not more adjectives. It is writing the sentence about how the problem feels before you write the one about what the product does.

Defend this by keeping the internal layer honest. It has to match something a real customer actually said in a support ticket, a review, or a sales call, not a feeling you invented because it sounds compelling. Butterfield's memo worked because the stress he named was the literal thing people felt about their inbox. If your internal layer is invented instead of overheard, customers feel the mismatch even when they can't name what's off.

Gotchas

The internal layer can tip into melodrama. Overstating the pain, telling someone their inbox is ruining their career, reads as manipulative instead of accurate. Match the intensity of your language to the intensity your actual customers use.
Not every product has a real philosophical layer. Forcing a cause onto a boring utility, expense reports, a URL shortener, reads as try-hard. Some products only need the external and internal layers stated well.
A great internal pitch doesn't excuse a broken external one. Slack's memo worked because the tool also did the practical job well. Fix the mechanism first, or the emotional pitch is just marketing sitting on top of a product that doesn't deliver.