Pick Two

You can't win on everything. Pick exactly two things your product will be known for and build your entire strategy around them. Here's how to choose and why three is too many.

Ask a founder what makes their product different and you'll usually get a list. It's fast. It's accurate. It's easy to use. It integrates with everything. It's affordable. It's secure. It's customizable.

That's not a positioning strategy. That's a features page. And features pages don't win customers. Clear positioning does.

The clearest positioning I've seen comes from products that picked exactly two things to be known for and made every other decision in service of those two things. Not three. Not five. Two.

Why two

One isn't enough. If your product is only "the fastest," someone faster will come along and you have nothing left. Two pillars create a compound position that's much harder to replicate. Being the fastest AND the most accurate is a different claim than being either one alone. The combination is the moat.

Three is too many. The moment you try to win on three dimensions, your messaging gets fuzzy, your roadmap gets pulled in competing directions, and your users can't finish the sentence "I use this because it's ___." If they can't finish that sentence in five words, you don't have positioning. You have a brochure.

I've watched this play out with products I helped build and products I've advised on. The ones that struggled were always trying to be good at everything. The ones that grew were the ones that said no to dimensions they weren't going to compete on, and doubled down on the two that mattered.

The eight pillars

Every product differentiates on some combination of these. You can't pick ones that don't apply. You pick from what's real.

Look at the "who wins" column. Notice that the strongest companies appear once or twice, not everywhere. Stripe wins on ease of use and coverage. Not speed. Not price. Not compliance. Ease of use and coverage. Every decision they make reinforces those two things. That's why developers choose Stripe even when cheaper alternatives exist.

How to choose yours

Step 1: Map your competitors. For each competitor, identify their two strongest pillars. Where is there a gap? The combination nobody is serving well is your opportunity. If every competitor competes on accuracy and speed, maybe ease of use and specialization is wide open.

Step 2: Be honest about your strengths. Which two pillars can you actually win on? Not which ones you wish you could win on. A solo builder probably can't compete on reliability against AWS. But a solo builder can absolutely compete on specialization and ease of use for a narrow niche that AWS will never serve.

Step 3: Check that customers pay for it. Not every pillar is equally valued in every market. In healthcare, compliance is table stakes. In developer tools, ease of use is the whole game. In enterprise, reliability matters more than price. Ask your users, or potential users, what they'd pay a premium for. If your two pillars don't match what they value, pick different pillars.

Step 4: Make every decision pass the test. Once you've picked two, every product decision, pricing decision, and marketing decision should reinforce them. If you chose speed and ease of use, don't spend three months adding compliance features because an enterprise prospect asked. That prospect isn't your customer. You chose your two. Serve them.

The discipline isn't choosing the two pillars. It's saying no to the other six.

What this looks like in practice

I talked to a founder building an AI transcription tool. When I asked what made it different, he listed: accuracy, speed, price, multiple languages, speaker identification, and a beautiful interface. Six things. I asked which two he'd choose if he could only keep two. Long pause. "Accuracy and speed."

We mapped his competitors. Two of them already owned accuracy and speed with massive engineering teams and VC backing. He wasn't going to out-engineer them as a solo builder.

But when we looked at specialization, something opened up. Nobody was building a transcription tool specifically for podcast producers. Not a generic transcription API that podcasters happened to use. A tool designed around their workflow: show notes, pull quotes, timestamp markers, chapter generation. Specialization plus ease of use for one specific audience.

His six-thing list became two things. His messaging went from "fast, accurate AI transcription" (which described everyone) to "transcription built for podcasters" (which described only him). Same underlying technology. Completely different position.

The mistake I keep seeing

Builders add pillars instead of committing to two. A user asks for better compliance support. Now you're working on compliance. Another user wants more integrations. Now you're building integrations. A competitor launches a cheaper plan. Now you're rethinking pricing.

This is the Feature Factory pattern from the eight builders piece, applied to strategy. You end up good at everything and known for nothing. The product that tries to compete on five pillars loses to the product that competes on two, because the two-pillar product is clearer about who it's for and why they should choose it.

Pick two. Build everything around them. Say no to the rest. That's the whole framework.