Positioning is a decision, not a tagline
Most founders treat positioning as a wording problem to solve at launch. It's actually a set of decisions about who you're for and what you're against — and it shapes the product, not just the homepage.
Founders usually reach for positioning too late and treat it as too small a thing — a wording exercise you do the week before launch, trying to find the clever sentence that makes the homepage sing. But positioning isn't a copywriting problem. It's a set of decisions about who you're for, what you're an alternative to, and what you're willing to be worse at. Those decisions shape the product itself, not just the words wrapped around it.
Positioning is mostly about what you're against
The fastest way to make a product legible is to make its alternative obvious. People understand new things by comparison — "it's like X, but for Y," "it's what you'd use instead of Z." If you can't name what your product replaces, users have no shelf to put it on, and a product with no shelf is a product no one reaches for.
So the first positioning question isn't "what are we?" It's "what do people use today instead, and what's wrong with it?" Your answer defines the frame. Position against spreadsheets and you're the "finally, software for this" product. Position against an incumbent and you're the "same job, but without the pain you've learned to tolerate" product. Same underlying tool, completely different meaning — and the difference is a decision, not a description.
Being for everyone is being for no one
The scariest part of positioning, and the part founders resist hardest, is narrowing. It feels like leaving money on the table to say "this is for a specific kind of person." But a product aimed at everyone makes no one feel it was built for them, and "built for me" is what actually drives adoption. A sharp, narrow position that a specific group feels in their gut beats a broad, safe one that no one feels at all.
Narrowing isn't forever. It's how you get a beachhead — a group who loves you enough to pull you forward. You expand later, from strength. But you have to be someone's favorite before you can be anyone's default.
Positioning shapes the product
Here's what makes this more than marketing: once you decide who you're for and what you're against, a lot of product decisions answer themselves. The features that matter become obvious, the ones that don't fall away, the tone and defaults and even the onboarding all follow from the position. A clear position is a decision-making tool — it tells your whole team what fits and what doesn't, long after the launch copy is written.
That's why I treat positioning as an early, product-level decision, not a late, surface-level one. If you get it right, the homepage practically writes itself because the product already knows what it is. If you get it wrong — or avoid deciding — you end up with a capable product that no one can quite explain, including you.
The test
The test I use is simple: can you finish "we're the [category] for [specific people] who are tired of [specific pain], unlike [the alternative]" without flinching? If every blank is sharp and a little uncomfortable in how much it excludes, you probably have a position. If it's smooth and inclusive and offends no one, you have a description, and descriptions don't sell.
If you're trying to find the sharp version of your position — the one that excludes the right people — that's a good thing to work through together.

Written by
Entrepreneur, product strategist & experience designer
I build, advise, and invest in digital products — founder-first product strategy, AI-native experiences, and UX across industries. I run Zenith Studio, my AI-native product studio, from Kathmandu, working with founders globally.
Keep reading
Clarity is the real product work
Most products aren't confusing because the idea is bad — they're confusing because the thinking behind them was never made clear. Here's how I treat clarity as the actual work, not the polish at the end.
Read →Playbook · 7 minHow I pressure-test an idea before building it
Before I write a line of code or design a single screen, I try to kill the idea cheaply. Here's the sequence I use to find the assumption that would sink a product — while it's still free to be wrong.
Read →Turn the idea into a product.
If this maps to what you're building, let's talk it through.