How to build an email list without a website

You need a file people want, a link that asks for an email address before it hands the file over, and one place the addresses collect. That's the whole list. Upload the file somewhere that gates it, put the link in a bio or on a talk slide or in a reply to someone who asked, and the first subscriber can arrive this afternoon instead of after a weekend of setup.

The usual advice is three jobs before the first subscriber

Ask this question anywhere and you get the same recipe. Buy a domain and put up a landing page. Add a form — a plugin if you're on WordPress, an embed if you're not. Open an account with an email service provider, connect the form to it, set up a confirmation flow, add the DNS records so your mail authenticates.

None of that is bad advice. It's just three separate jobs — hosting, forms, sending — each with its own account, its own bill and its own ways of going wrong, and all three have to be finished before one person can hand you an address. The thing people actually want is already done and sitting on your desktop.

The recipe also quietly assumes you're building an audience for a site. If what you have is a PDF, a spreadsheet template, a dataset or a deck, the site is scaffolding: a page whose entire job is to describe the file underneath it.

One file, one link, one place the addresses land

Strip it back to what a list genuinely requires and there are three parts.

The file. This is the offer, and it is the only part that can't be substituted. A landing page doesn't rescue something nobody wanted; a plain link to something people want works fine.

The link. One URL you can paste anywhere, with a gate between the click and the download.

The place the addresses land. Somewhere you can export from later, when you finally have something to send.

What the link has to do

Ask for an address, then check it. Those are two different steps and most forms only do the first. A Replilo link looks like https://replilo.com/s/ab3xk9qp. Someone opens it and types an address; the domain is checked against a mirrored blocklist of disposable mailbox services, and its DNS is checked for MX and SPF records, so a ten-minute mailbox or a typo like gmial.com never reaches your list. Then a six-digit code goes out. Entering it starts the download and stores the person as a verified subscriber.

Come back next week and the download just starts — access is remembered per link. The gate is a one-time cost for the reader rather than a toll booth they hit every visit. If you want the longer argument for why that's worth the friction, it's in why a confirmed address beats a typed one.

Where the addresses go

Into the dashboard at /app, with who verified, what they took and when. From there you can export them, push them into a Google Sheet, or take the subscriber.verified webhook — signed with HMAC-SHA256 and retried with backoff — into whatever you already run. The point is that the addresses are in one place and they're yours, which is the actual job the ESP account was going to do on day one.

Where to put the link

Without a site, the link goes wherever you already show up.

• A bio. Most profiles give you one link slot. Pointing it at the file is usually better than pointing it at a menu of links, because the file is the thing you'd be asking people to click anyway.
• The last slide of a talk. People photograph the final slide. Put the URL on it and give them a reason to. A custom slug earns its keep here — a link someone types off a photo of a screen should be short and pronounceable.
• An answer in a forum or a group chat. Answer the question properly first, then mention that the numbers are in a file and drop the link. A link with no answer around it reads as spam, and gets treated that way.
• A direct reply. Somebody asks for the thing; you send the link instead of the attachment. They get it faster than you could have found the file, and they're on the list.

None of those is a growth engine. Together they're a pattern: the link goes where you were already going to answer, so distribution costs you nothing you weren't already spending.

What you still have to do yourself

Collecting addresses is not the same as having a newsletter. Replilo verifies the address and stores the subscriber; it does not write or send your mail. You'll still want a sending tool eventually — on the day you have something to say, which is not day one.

Two things are worth getting right before then.

Say what they're signing up for. Wherever you paste the link, one line: what else they'll get and roughly how often. "Enter your email for the dataset; I send a note a few times a year when there's a new one" is enough. People who know what's coming don't report it as spam when it comes.

Email them once, early. A list nobody has ever mailed goes cold in a way verification can't fix. The addresses were confirmed the day they joined, so the domains resolved and someone read the code — but a person who hasn't heard from you in fourteen months has forgotten who you are, and their spam filter has too.

And the trade-off, stated plainly: a code step costs you conversions. Some people close the tab rather than open their inbox. Those are mostly the people who wanted the file and never the follow-up, which is the same group that would have bounced or filed you as spam later. The list is smaller. Every address on it has been read at least once.

The short version

A website is one way to publish a link, not a prerequisite for having one. Put the gate in front of the file itself, paste the link where you already turn up, and let the addresses collect in a single place. Build the site later, if the list gives you a reason to.