[{"data":1,"prerenderedAt":241},["ShallowReactive",2],{"blog-\u002Fblog\u002Fhow-i-position-a-product":3,"blog-surround-\u002Fblog\u002Fhow-i-position-a-product":221,"blog-related-\u002Fblog\u002Fhow-i-position-a-product":229},{"id":4,"title":5,"audience":6,"body":10,"cluster":188,"date":189,"description":190,"draft":191,"extension":192,"faq":193,"featured":191,"language":203,"meta":204,"navigation":205,"order":206,"path":207,"pillar":208,"primaryKeyword":209,"relatedProject":203,"reviewCycle":210,"searchIntent":211,"seo":212,"stem":213,"tags":214,"type":219,"updated":189,"__hash__":220},"blog\u002Fblog\u002Fhow-i-position-a-product.md","How I Position a Product (What It Actually Does)",[7,8,9],"indie-founder","solo-developer","product-builder",{"type":11,"value":12,"toc":179},"minimark",[13,40,45,48,55,59,62,73,83,89,100,104,110,113,117,120,128,136,140,143,146,154,157,160],[14,15,16,20,21,25,26,31,32,35,36,39],"p",{},[17,18,19],"strong",{},"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 ",[22,23,24],"em",{},"that's for me",", while everyone else correctly moves on. This is the companion to ",[27,28,30],"a",{"href":29},"\u002Fblog\u002Fwhy-i-build-narrow-choosing-who-a-product-is-for","building narrow",". Build-narrow is the decision about ",[22,33,34],{},"who"," the product is for. Positioning is ",[22,37,38],{},"what you say to that who"," — and the two either agree or the product reads as confused.",[41,42,44],"h2",{"id":43},"positioning-is-a-sentence-not-a-feature-list","Positioning is a sentence, not a feature list",[14,46,47],{},"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.",[14,49,50,51,54],{},"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 ",[22,52,53],{},"has",", I know I've drifted into describing the product to myself instead of describing the change to the person who might buy it.",[41,56,58],{"id":57},"say-what-changes-not-how-it-works","Say what changes, not how it works",[14,60,61],{},"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.",[14,63,64,68,69,72],{},[27,65,67],{"href":66},"\u002Fblog\u002Fwhy-i-built-delivery-sheet","Delivery Sheet"," is positioned as ",[22,70,71],{},"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.",[14,74,75,68,79,82],{},[27,76,78],{"href":77},"\u002Fprojects\u002Flistemizde","Listemizde",[22,80,81],{},"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.",[84,85,86],"pull-quote",{},[14,87,88],{},"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.",[14,90,91,92,95,96,99],{},"The gap between ",[22,93,94],{},"what it is"," and ",[22,97,98],{},"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.",[41,101,103],{"id":102},"narrow-beats-broad-again","Narrow beats broad, again",[14,105,106,107,109],{},"The same logic that makes ",[27,108,30],{"href":29}," 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.",[14,111,112],{},"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.",[41,114,116],{"id":115},"the-test-can-a-stranger-repeat-it","The test: can a stranger repeat it?",[14,118,119],{},"There's a single test I hold every positioning against: can someone who has read it once tell a friend what the product does?",[14,121,122,123,127],{},"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 ",[27,124,126],{"href":125},"\u002Fblog\u002Fhow-i-think-about-distribution-as-a-solo-builder","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.",[14,129,130,131,135],{},"This is the same discipline as ",[27,132,134],{"href":133},"\u002Fblog\u002Fwhy-i-write-the-expected-output-before-the-screen","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.",[41,137,139],{"id":138},"positioning-is-a-decision-not-a-tagline-exercise","Positioning is a decision, not a tagline exercise",[14,141,142],{},"The thing I most want to land: positioning is not wordsmithing. It's choosing.",[14,144,145],{},"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.",[14,147,148,149,153],{},"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 ",[27,150,152],{"href":151},"\u002Fblog\u002Fhow-i-scope-an-mvp","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.",[14,155,156],{},"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.",[158,159],"hr",{},[14,161,162],{},[22,163,164,165,169,170,173,174,178],{},"Part of ",[27,166,168],{"href":167},"\u002Ftopics\u002Fbuilding-ai-products","Building AI Products",". The companion piece is ",[27,171,172],{"href":29},"why I build narrow"," — who a product is for, before what you say to them. The ",[27,175,177],{"href":176},"\u002Fnewsletter","newsletter"," sends one practical build lesson every two weeks.",{"title":180,"searchDepth":181,"depth":181,"links":182},"",2,[183,184,185,186,187],{"id":43,"depth":181,"text":44},{"id":57,"depth":181,"text":58},{"id":102,"depth":181,"text":103},{"id":115,"depth":181,"text":116},{"id":138,"depth":181,"text":139},"process","2026-07-25","Positioning is the one sentence that makes exactly the right person say 'that's for me' — a chosen problem and a chosen who, not a list of features.",false,"md",[194,197,200],{"question":195,"answer":196},"What is product positioning?","Product positioning is the one sentence that makes exactly the right person read it and think 'that's for me.' It's a chosen problem and a chosen who — not a feature list, not a tagline, not a description of how the thing works. Positioning names the change the product makes true for a specific person, so that the person with that exact problem recognizes themselves in it and everyone else correctly moves on. It's a decision about which problem, for whom, you want to be known for solving.",{"question":198,"answer":199},"How do you describe what a product does?","Describe what becomes true for the user, not the mechanism that makes it true. The reader doesn't care how it works; they care what changes for them. Delivery Sheet turns a vague leadership ask into a clear, reviewable delivery decision before a team commits — that's what changes, and that's the description. 'An AI intake form with structured fields' is the mechanism, and it's what the builder is proud of, not what the buyer is looking for. Lead with the change; the mechanism can come later, once the person already knows it's for them.",{"question":201,"answer":202},"Why is a narrow positioning stronger?","Because a sharp claim aimed at a specific person out-pulls a vague claim aimed at everyone. Positioning for everyone positions for no one — when a description tries to be relevant to all readers, no single reader recognizes their exact problem in it, so nobody feels it's for them. A narrow positioning names one problem and one who precisely enough that the right person is certain and everyone else self-selects out. For a solo builder that certainty is most of the battle: the reader has to place the product in seconds or they're gone.",null,{},true,20.5,"\u002Fblog\u002Fhow-i-position-a-product","building-ai-products","product positioning","annual","informational",{"title":5,"description":190},"blog\u002Fhow-i-position-a-product",[208,215,216,217,218],"positioning","messaging","product","solo-saas","text","shruKCtRuPCxiuFBL37WuzmkfZnZGSEfZeVCQ1tWcbI",[222,226],{"title":223,"path":224,"stem":225,"type":219,"language":203,"draft":191,"children":-1},"How I Onboard Users to a Solo SaaS","\u002Fblog\u002Fhow-i-onboard-users-to-a-solo-saas","blog\u002Fhow-i-onboard-users-to-a-solo-saas",{"title":227,"path":151,"stem":228,"type":219,"language":203,"draft":191,"children":-1},"How I Scope an MVP","blog\u002Fhow-i-scope-an-mvp",[230,234,238],{"path":231,"title":232,"description":233},"\u002Fblog\u002Fmy-product-operating-system","My Product Operating System for Building Multiple AI Apps","The product operating system I use to build several focused AI products solo: choosing which problem to build, shipping fast, and killing what isn't working.",{"path":235,"title":236,"description":237},"\u002Fblog\u002Fhow-i-decide-whether-an-ai-product-idea-is-worth-building","How I Decide Whether an AI Product Idea Is Worth Building","How to decide what product to build: the short filter I run every idea through — real recurring problem, one-sentence outcome, small enough to ship solo.",{"path":133,"title":239,"description":240},"Why I Write the Expected Output Before the Screen","Define the outcome before design: I write the exact result the user should get before building any screen, because the screen is only the path to an outcome.",1784914210518]