How I Position a Product (What It Actually Does)

Every founder can describe their product for ten minutes. Almost none of them can do it in one sentence a stranger would repeat. The ten-minute version is a tour of the mechanism — the fields, the flow, the clever part under the hood. The one-sentence version is positioning, and it does a completely different job: it makes exactly one kind of person read it and think that's for me, while everyone else correctly moves on. This is the companion to building narrow. Build-narrow is the decision about who the product is for. Positioning is what you say to that who — and the two either agree or the product reads as confused.

Positioning is a sentence, not a feature list

Positioning is the one line that lands a chosen problem in front of a chosen person. Not "here is everything it can do" — a chosen problem, for a chosen who, stated so plainly that the right reader recognizes their own situation in it. A feature list is the opposite instinct: pile up capabilities and hope the reader assembles the point themselves. They won't. Nobody arrives at your product wanting to do the assembly. They arrive with a problem, and they're scanning for whether you're about it. The feature list makes them work; the positioning does the work for them.

The tell is who the sentence is about. A feature list is about the product. Positioning is about the reader's problem. When I catch myself listing what a thing has, I know I've drifted into describing the product to myself instead of describing the change to the person who might buy it.

Say what changes, not how it works

Here's the move that took me longest to internalize: the reader does not care how the product works. They care what becomes true for them.

Delivery Sheet is positioned as turn a vague leadership ask into a clear, reviewable delivery decision before your team commits. That's the change. It is not positioned as "an AI intake form with structured fields" — which is the mechanism, and which is exactly the thing I was proud of building. The structured fields are real. They're just not what the engineering lead with a fuzzy directive from their VP is looking for. That person wants the vague ask to stop being vague before the team burns two sprints on the wrong reading of it. Name that, and they're in.

Listemizde is positioned as local places you can trust, ranked by real people, not paid. That's the change — trust, and the confidence that no one bought their way to the top. It is not positioned as "a community directory platform." The platform is the mechanism. "Trustworthy local businesses through real community recommendations" is what becomes true for the person deciding where to eat or who to hire.

"

The reader doesn't want to know how the machine works. They want to know what changes for them. Describe the change; the mechanism is yours to be proud of, not theirs to decode.

The gap between what it is and what it does for me is where most products quietly lose the person who would have bought. The builder writes the mechanism because building it was the hard, satisfying part. The reader skims it, doesn't find their problem, and leaves — not because the product was wrong for them, but because the description was written about the wrong subject.

Narrow beats broad, again

The same logic that makes building narrow work makes narrow positioning work. A sharp claim for a specific person out-pulls a vague claim for everyone, every time. When a line tries to be relevant to all readers, no single reader recognizes their exact problem in it — so nobody feels it's for them. Positioning for everyone positions for no one, in precisely the way a product for everyone is a product for no one.

Breadth feels safer. Say less specifically what it does and surely more people qualify? In practice the opposite: the broad line is skimmed and forgotten because no one's particular problem is in it, while the narrow line stops the one person whose problem it names cold. I would rather one reader be certain than ten be vaguely interested. The certain one converts; the vaguely interested ones were never going anywhere.

The test: can a stranger repeat it?

There's a single test I hold every positioning against: can someone who has read it once tell a friend what the product does?

If they can, the positioning is doing its job — it's living in the reader's head in their own words, which is the only place distribution actually happens. If they can't — if the best they can manage is "some tool, does something with delivery, I think?" — then the positioning is describing me, not helping them. It made me feel understood as the builder and left the reader with nothing repeatable. A positioning the reader can't repeat is a positioning that stops the moment they close the tab.

This is the same discipline as writing the expected output before the screen: decide the exact thing that has to be true for the reader, then work backward. The output here is a sentence the reader can carry.

Positioning is a decision, not a tagline exercise

The thing I most want to land: positioning is not wordsmithing. It's choosing.

It's deciding which problem, for whom, you want to be known for — and by direct consequence, which problems and which people you're saying no to. That's the same cut as building narrow, applied to the words instead of the roadmap. When I position Delivery Sheet on the vague-ask-to-clear-decision problem, I am declining to also be about project tracking, about status reporting, about a dozen adjacent things it could plausibly touch. Every one of those would dilute the sentence, and a diluted sentence is one no stranger repeats.

So the work isn't finding prettier words for everything the product does. It's the harder, quieter work of picking the one problem and one who to stake the sentence on, and letting the rest go. Founders resist this for the same reason they resist scoping an MVP — saying no to real capability feels like leaving value on the table. It isn't. The value you leave on the table is what makes the sentence sharp enough to be remembered at all.

Get it right and positioning stops being a marketing chore and becomes the front door: the right person reads one line, recognizes themselves, and walks in. Get it wrong and it doesn't matter how good the product is behind the door — they never knew it was for them.

Part of Building AI Products. The companion piece is why I build narrow — who a product is for, before what you say to them. The newsletter sends one practical build lesson every two weeks.