Building an Audience Before a Product

Ask most people how to start a magazine and they will describe the magazine first: the format, the design, the launch issue. Ask someone who has done it more than once, and the order tends to reverse. The publications that last are usually built on a readership that existed before anyone had settled on exactly what to publish for them.

The second of the three magazines I have edited started this way almost by accident. What became the publication's founding editor spent nearly a year writing a personal newsletter about a fairly obscure corner of design history, with no plan beyond curiosity. By the time she decided to formalise it into something closer to a real publication, she already had a modest, genuinely attentive readership who had been asking, unprompted, for exactly the kind of coverage the eventual magazine went on to provide. The launch issue wasn't really a launch. It was closer to a promotion, delivered to people who had already decided they wanted it.

This isn't a fashionable trick borrowed from software, where "build an audience first" has become a familiar piece of startup advice. Independent publishing has worked this way for longer than the advice has existed as advice. A newsletter with three hundred committed readers, built slowly around a specific curiosity, has a better foundation than a beautifully designed magazine with no readers at all, because the newsletter has already answered the one question a launch issue cannot: does anyone want this.

The uncomfortable part of this approach is how little it resembles a plan. There is no launch date to work toward, no clean before-and-after to point to in a portfolio. Progress looks like a slowly growing reply rate on a newsletter, or a handful of strangers forwarding an essay to someone else who might care. It is easy to mistake this for a lack of momentum, especially compared to the visible milestones a formal launch provides. The publishers who stick with it long enough to see it pay off tend to be the ones who stopped needing the visible milestones to feel like the work was going somewhere.

Why the order matters

Building the product first and the audience second inverts the riskiest part of the process. A product built without a readership is a guess dressed up as a plan — an editor's theory about what people want, tested only after significant time and money have already been spent. If the theory is wrong, the publication finds out at the worst possible moment, with a print run already committed and a subscription page already live.

Building the audience first turns the same risk into an ongoing conversation instead of a single bet. A small, consistent newsletter, a modest social presence, even a personal habit of writing publicly about a subject — each of these lets an eventual publisher learn, in real time, what specifically holds a reader's attention and what doesn't. By the time an actual product gets built, most of the guesswork has already been resolved through evidence rather than assumption.

This matters more in publishing than the startup-world version of the advice usually acknowledges, because a publication's product genuinely is its editorial judgment, and judgment is exactly the thing that can't be validated through a survey or a landing page. You cannot ask a prospective reader whether they would trust your taste. You can only demonstrate it, issue after issue, and watch whether they keep showing up. An audience built this way has already voted, repeatedly, with the only currency that matters in publishing: their continued attention.

There is also a quieter benefit that rarely gets mentioned: an audience built slowly, before there is anything to sell them, tends to trust the eventual product more than an audience acquired at the moment of launch. They have watched the judgment behind the work develop over time. That history is difficult to manufacture after the fact, no matter how strong the eventual launch issue is.

What this looks like in practice

None of this requires a dramatic pre-launch campaign. In my experience, the publishers who do it well tend to follow a fairly unglamorous, repeatable pattern:

• Write in public, consistently, before there is a formal publication to point to — a personal newsletter, a series of essays, anything that lets a reader form an opinion about the judgment behind it.
• Pay closer attention to which specific pieces earn genuine engagement than to overall subscriber growth; growth without engagement is a number, not an audience.
• Resist the pressure to formalise into a "real" publication before the audience has told you, through its own behaviour, what it wants more of.
• Treat early readers as collaborators rather than as a captive test market — ask what they'd want to see more of, and take the answers seriously even when they complicate the original plan.
• Launch the eventual product to the audience that already exists, rather than treating launch day as the moment the audience is supposed to appear.

The pattern is slow by design, and that slowness is often mistaken for a lack of ambition. It isn't. It is closer to due diligence, done in public, over a longer timeline than most launch plans are comfortable with. It also produces a specific kind of confidence that a fast launch cannot manufacture: by the time the product exists, its editor already knows, from direct evidence rather than hope, roughly how many people will show up on day one.

None of this guarantees success — plenty of patiently built audiences never convert into anything sustainable, and plenty of confidently launched products succeed despite skipping every step above. But the publishers who build the audience first tend to fail more cheaply when they do fail, and to succeed on firmer ground when they don't. That asymmetry, more than any particular tactic, is the real argument for doing it in this order.