Nine angles for the same product
A taxonomy. Run your product through all nine and watch which one comes alive.
5 MIN READ
Take one product, say, a tool that automatically writes tests for your codebase, and watch how differently it sells through each lens. The product never changes. The explanation does.
01 · The problem
“Your test coverage is lying to you.” Name the pain precisely enough that the right reader feels caught. The problem angle works when the pain is felt daily but unnamed.
02 · The enemy
“Stop writing tests by hand.” Every product replaces something, a tool, a habit, a default. Naming the enemy borrows all the energy the reader already has about the old way. Most categories were built on this angle.
03 · Time
“Ship Friday’s release on Wednesday.” Convert the benefit into hours returned. Time angles work on people who already believe the problem matters but think solving it is expensive.
04 · Money
“Every regression you catch in CI is a refund you never issue.” Trace the feature to a number. B2B buyers repeat money angles internally. You’re writing the sentence your champion says to their boss.
05 · Status
“The repos with green badges get the contributors.” People buy what the person they want to become would use. Status angles are quiet but durable. They never go out of date because the ladder never goes away.
06 · Fear
“The bug that takes you down is in the file nobody tested.” Risk angles work where the downside is catastrophic and invisible. Use sparingly; fear converts but doesn’t retain.
07 · Curiosity
“We let an AI write 10,000 tests for open source repos. Here’s what it found.” Lead with the artifact, not the product. Curiosity angles earn distribution in feeds where nobody clicks ads.
08 · Proof
“847 bugs caught before production, across 312 repos.” Numbers are the angle when you have them. Specificity is believability: 847 beats “hundreds” every single time.
09 · Story
“We shipped a payment bug that cost us $40k. So we built the thing that would have caught it.” Origin stories carry products before they have users, because the founder’s problem is proof the problem exists.
Run your product through all nine. Two or three will feel forced, fine. One will feel like it wrote itself. That’s the one you lead with, and the other eight become your next month of tweets.