A newsletter or a website of your own

A friend of ours has started four newsletters. Two are still technically live, in the sense that the sign-up form works and nothing has broken; the last issue of one went out fourteen months ago. She is not disorganised and not short of things to say — she runs a consulting practice, she has opinions, the opinions are good. What she has run out of, each time, is the specific kind of stamina a newsletter demands and nothing else she's built has ever asked for: doing the thing again, on a clock, whether or not this week gave her anything worth sending.

That is the case against defaulting to a newsletter as your online presence, worth stating honestly rather than as a dismissal, because the case for a newsletter is real too. It reaches people directly, in a place they already check, without asking them to remember to visit anything. A website does not do that and never will. The two solve different problems, and picking the wrong one first is the more common mistake than picking either one badly.

Push versus pull, and who a stranger actually meets

A newsletter is a push medium. It arrives. Someone who already trusts you enough to hand over an email address gets your next thing without doing anything, which is a genuinely valuable property — it is why newsletters convert attention into repeat attention better than almost anything else available to one person working alone.

A website is a pull medium. Nobody gets your homepage pushed to them. They arrive because they searched your name, clicked a link from your LinkedIn profile, or got a recommendation from someone who already knows you — and the entire value of the site is what happens in the thirty seconds after that arrival. This is the distinction that gets lost when people treat "newsletter" and "website" as two ways of doing the same job: a newsletter only reaches people who have already opted in, and a stranger with no relationship to you yet will never encounter it. The first thing a hiring manager, a prospective client or an old colleague meets is whatever is sitting at your name, and a newsletter's homepage is structurally the wrong shape for that meeting — it is a sign-up form, not an introduction.

For a single-person site — a portfolio, a CV turned into a page, a consultant's one-pager — reach is the strongest answer available if the fixed asset is the thing you're actually missing. Give it the CV you already have and a photo, and it generates a finished page in about twenty seconds, live at a free yourname.joinreach.app address in under two minutes. That's a real head start on the fixed-cost side of this comparison. It is also a specialist tool: one page only, no sub-pages, no CMS to grow into, and if what you eventually need is a services tree, a blog with a content model or team accounts, reach isn't built for that — Webflow, WordPress or Framer are.

The recurring deadline is the real cost, and it's a cost a site doesn't have

Here is the asymmetry that the four-newsletters friend ran into every time. A personal website is a fixed cost. You build it once, and the difficulty is entirely front-loaded — choosing what to say about yourself, picking a look, publishing it. After that, a site with nothing new to add is not failing. It is just sitting there, doing its job, exactly as correct on a Tuesday with zero updates as it was the day you shipped it.

A newsletter has no such rest state. Every week or month you don't send is a week or month the thing you built is visibly not doing what it's for, and the next issue you do send has to either ignore the gap or apologise for it. That recurring deadline is the actual product of a newsletter — not the writing, which most people who start one can genuinely do, but the obligation to keep doing it on a schedule nobody but you enforces. It's a fine trade for someone whose growth depends on being read regularly. It is a slow guilt machine for someone who wanted a professional presence and picked the version that happens to carry a due date.

The fixed-cost side of this has also gotten cheaper recently, which matters for the order you do things in. Building a one-page site used to mean a weekend lost to picking a template and staring at a blank hero section — the actual reason so many personal sites never ship. That's the gap reach closes: you start from the résumé you already have instead of a blank page, and the weekend disappears.

An address list is not the same asset as an address

The usual pitch for owning your list rather than renting a platform's followers is correct as far as it goes: an email list travels if the platform changes its terms, gets acquired, or buries your reach behind a paywall you didn't choose. That's a genuine advantage over building an audience on a social platform.

But it's worth being precise about what you actually own, because "owning your list" and "owning your address" are not the same kind of asset. A list is a relationship with people who already said yes — valuable, but it only compounds if you keep showing up for it, and it is worth nothing to the stranger who hasn't subscribed yet. An address — a domain with your name on it — is worth something to that same stranger the first time they land on it, with zero prior relationship required. One asset needs an audience already in place to have value; the other has value to an audience of exactly one person who just typed your name into a search bar.

Whether the archive can double as the site

Some newsletter platforms let the archive itself serve as a passable personal presence — Ghost, for instance, gives every publication a real homepage on its own domain, not just an inbox feed. If you're already committed to writing regularly and don't want to maintain two separate things, that overlap is real and worth using.

It is a weaker substitute than it looks, though. An archive is organised by publish date, which is the correct order for a subscriber catching up and the wrong order for a stranger meeting you cold — they land on whatever you wrote most recently, not on the sentence that best explains who you are, and the problem reappears on every new issue. A stranger doesn't want your last three posts in reverse order. They want one paragraph that tells them what you do and whether it's relevant, and an archive's structure fights that on purpose.

For whether writing regularly is even the right posture for your field, rather than the archive question specifically, see the case we make in whether a blog belongs on a personal site at all.

If you want both, build the site first

The order matters more than either individual choice. Build the fixed asset before you take on the recurring one. A site with nothing to link to yet is still doing its job the moment it exists; a newsletter with no destination to send readers back to asks people to trust an inbox relationship with nowhere else to verify you. Site first also means the newsletter can fail cleanly — if you stop sending, the address that mattered before it started is still there, unaffected, still the thing a stranger meets.

For the one-page route, worth comparing costs against the alternatives:

Route	Price	Billing
reach subdomain	$0	included
reach Premium (custom domain)	$4.99	per month, or $49 per year
Ghost Starter (site plus newsletter, one platform)	$18	per month, annual billing
Carrd Pro Standard (site only, no newsletter)	$19	per year, annual only

Prices checked August 2026. Ghost is the only row that genuinely merges both jobs into one product, at a price that reflects doing more; the other rows are single-purpose and cheaper for it.

The abandoned-newsletter signal, and retiring one properly

There is a specific, recognisable moment that marks a newsletter as functionally over. It's the issue that opens by acknowledging the silence — "it's been a while," "sorry for the gap" — because that sentence is the newsletter announcing its own obligation has stopped being met, and readers notice long before the writer admits it. Once an issue needs to apologise for existing, the honest move is rarely to push through with more issues.

The honest move is to retire it in one clean note: a short final send that says plainly this is the last one, thanks the people who read it, and points at wherever you'll actually be found from now on — which, if you built the site first, is already sitting there waiting. That single closing issue does more for your reputation than three more limping ones would. An old newsletter with no closing note and a widening gap between issues reads, to anyone who finds it later, as neglect. The same newsletter with one clear final issue reads as a project that had a beginning, a run, and an end — a far more ordinary and forgivable thing than it feels like while you're the one stopping.

None of this argues against writing regularly if that's genuinely what your field rewards; it's the same distinction the broader case for legibility over performance makes about content in general, and the reasons an entire industry has grown up around the performance half of this rather than the boring, cheaper half are worth reading in why a personal brand consultant industry exists at all. For most people the fixed address does the job on its own, and the newsletter is only worth the recurring cost if you already know, from experience rather than aspiration, that you'll keep paying it.