Audience before product, and why the order costs more than the quality of either

The natural order feels obvious: make something good, then tell people about it. It is also the expensive order, because the discovery that nobody wants it arrives after all the work rather than before any of it.

The reverse order feels backwards and is much cheaper. Find the people, learn what they are struggling with, then build the thing they described. The building is the same amount of work; the difference is that you now know it will land.

This is not a marketing trick. It is a way of failing cheaply, and failing cheaply enough times is what looks from outside like judgement.

An audience for selling purposes is a group of people who have a problem in common and who believe you understand it. Size is secondary to specificity.

A thousand people who all struggle with the same thing will out-purchase fifty thousand who follow you for general interest. This is why creators with modest followings sometimes out-earn much larger accounts — their audience arrived for a reason and that reason is purchasable.

The practical implication: publish about the specific problem rather than about yourself. The people who respond are the people who have it, and that self-selection is doing the hardest part of the work.

The problem worth building for is the one you keep hearing in the same words. Not the one you find interesting — the one people describe unprompted, in comments, in messages, in the questions after a post.

Keep a file. Every time someone asks you something, write the question down verbatim. After a month the repeats are obvious, and the repeats are your product list.

The wording matters too: the way people describe their problem is the way your listing should describe the solution. You are being handed the copy along with the brief.

Describe the product publicly before making it. A post, a page, a note: here is what this would be, here is what it costs, tell me if you want it.

The responses tell you three things at once: whether anyone wants it, what they assumed it would include, and what price felt reasonable. All three would otherwise have cost months to learn.

If nobody responds, you have saved the months. That is a good outcome and it consistently feels like a bad one, which is why people skip this step.

Where you take money before delivering, be explicit about the timeline and deliver it. A pre-order that arrives is the strongest possible start; one that does not is worse than never having asked.

The other failure is deciding who the audience is from a distance — imagining a customer, inferring their problems, building for that construction. It fails for the same reason as building first: the feedback arrives at the end.

The advantage of an audience you actually have contact with is that they correct you continuously and for free. Every reply is a small adjustment to your model of what they need.

If you do not have that contact yet, getting it is the first job. Publish about the thing you know, in public, until people who have that problem find you. It is slower than building and it is the part that makes the building worth doing.

1. Contact — publish about what you know until people with the problem find you.
2. Problem — listen for the sentence that repeats.
3. Offer — describe the solution publicly, with a price, before it exists.
4. Build — only what the responses asked for.

Most people run this backwards and start at four. The work is identical; the difference is entirely in how much of it turns out to have been necessary.