Start Publishing

You can be published before you finish your coffee.

That isn't a figure of speech. The sequence below is three actions long, and the only one with any real duration is the one where you decide what to publish.

Account

Email and a password. That's the whole thing.

No verification queue. No application. No questions about your experience, your following, or what you intend to write about. Nobody is assessing whether you should be here, because that isn't how this works.

Account created.

Thirty seconds, most of which was typing your email.

Bring what you already have

If you've written anywhere before, you don't start from nothing.

Point import at it — a Substack, a blog, an export file, a folder of documents — and the archive comes across. Not one piece at a time. The whole thing, in one operation, while you watch.

Imported 214 pages. Reviewed 3 issues. Published.

That's what the screen says when it's done. Not a progress bar with a spinner and an estimate. Completed actions, counted.

The part you're actually worried about

Everyone who has ever moved an archive has the same fear, and it's a reasonable one: this is going to arrive as a wall of broken text with dead links and no images, and I'll spend a weekend fixing it.

Here is what happens instead.

Formatting holds. Headings stay headings. Bold stays bold. Lists stay lists. Block quotes, italics, code blocks, footnotes — all preserved. Your paragraph breaks are where you put them.

Links survive. Internal and external, both. Links between your own pieces are rewritten to point at their new addresses, so a two-year-old post referencing an older one still works.

Images come with it. They transfer as files, not as hotlinks to a server you're leaving. Captions and alt text come too. When the old site goes down, your images don't.

Dates are real. Original publication dates are preserved. A piece from March 2023 shows March 2023. Your archive reads as an archive — a record running backwards — not as two hundred things that all appeared today. This matters more than people expect, because the dates are what turn a pile into a body of work.

Issues are flagged, not hidden. Some things don't transfer cleanly. An embed from a service that no longer exists. An image the old platform lost years ago. A malformed link. These get flagged individually, with the piece and the line, so you can look at three specific problems instead of auditing two hundred pages.

Three issues out of 214 pages is a typical result, not a best case.

Before and after

Before: 214 pieces across a Substack and an abandoned WordPress. Inconsistent formatting from two different editors. Eleven pieces with images that were hotlinked to a hosting service that shut down. Internal links pointing at URLs that redirect twice before landing. No paywall anywhere. Earning nothing.

After: 214 pieces at your own addresses, in one place, under one name, dated correctly. Images hosted with the work. Internal links resolving directly. Three flagged issues — the eleven dead images consolidated into one flag, plus two malformed embeds. Tiers applied. Payments live.

Elapsed time: under four minutes for the import. Ten minutes to clear the flags, if you bother clearing them today.

Publish

If you're not importing, you're writing. Same outcome, different starting point.

Type it in the editor, or paste it in from wherever you wrote it. Give it a title. Choose a tier — free if you want it read widely, higher if it's the kind of thing people pay for. You can change that decision later, on any piece, at any time.

Then publish.

Published.

No review. No queue. No approval. It is live at that moment, at a URL you control, and you can send it to someone right now.

Look at the page

Go and look at it.

Your name is at the top. Under it, the title you chose, the date, and your words — formatted properly, on a page that belongs to you rather than sitting inside somebody's feed.

If you imported, scroll. Two hundred pieces running backwards through several years, all under that name. You've been building this the whole time. It just wasn't anywhere you could see it.

That's the thing worth pausing on. Not the individual piece — the stack.

Now the one decision worth making today

You're looking at a published page with your name on it. Here's the honest observation about it: the writing is yours and it's good, and the presentation is default.

Default cover. Unproofed — you wrote it, you read it twice, and you missed the same three things everyone misses in their own work. Listed, but nothing pointing at it.

The support package is $30 and it changes those four things:

A designed cover. Not a template. The reason a stranger stops.

Proofreading. Someone who didn't write it reads it properly.

Listing. Placed where people looking for the subject will find it — not just people looking for you.

Promotion. A push in front of readers.

$30, per piece, once. No subscription. Nothing recurring.

You don't need it. The free page is a real published page and it will stay one. But you have a piece live right now that you'd like people to take seriously, and thirty dollars is the difference between it looking posted and looking published.

Apply it to the page you just put up.

Add support — $30

And when your work sells

You keep 80%. A reader pays $10, you receive $8. That doesn't change as you grow, and if nothing sells, nothing is taken.*

Write the next one. The first piece is the hard one. By the tenth, there's a shape to it — and people arriving see a record instead of an opinion.

* Payments are processed by third-party providers; standard processing costs apply to transactions.