Quick answer

Start with the publication and one real post, then configure the website around that content. Do not begin with automations or a paid plan: Launch is enough to test the core publishing workflow.

Starting planLaunch ($0)
First workflowCreate one post
Website optionsLink, blog, or news site
Paid gateActive automations

Best for: A creator setting up a first newsletter and publication site.

Think twice if: You are migrating a complex list or a revenue-critical automation without a rollback plan.

Key limit: This guide covers setup and interface orientation; it does not cover sending to a live audience or configuring paid monetization.

01

1. Create the publication before designing around it

Open the official beehiiv site and create a Launch account. Define the publication’s name, audience, and purpose. Keep the first setup narrow enough that you can change it after one test post.

02

2. Draft the first post

The Newsletter → Posts area is the operational starting point. A blank account makes the next action explicit: write the first post or begin from a template.

EvidenceWhere does a new publisher create the first newsletter post?
beehiiv Newsletter Posts screen with a Start writing button and post management navigation
The Posts screen is the direct entry point for drafts, scheduled posts, published posts, and templates. English UI · supplied capture reviewed Sep 6, 2026.
03

3. Choose the website’s job

The website setup asks whether you need a link-in-bio page, a simple blog, or a news-style publication. Choose based on the content you will maintain—not the option that looks most ambitious.

EvidenceWhat type of publication site can a new account start with?
beehiiv website builder setup showing Link in bio, Simple blog, and News site options
The builder separates three purposes before asking for templates, colors, and typography. English UI · supplied capture reviewed Sep 6, 2026.
04

4. Record the automation gate before planning a sequence

If your launch depends on a welcome sequence, check the plan boundary first. The current interface allows exploration during the trial but requires Scale or Max to activate automations.

EvidenceWhat happens when a free-plan user opens Automations?
beehiiv Automations screen with a banner describing the Scale plan requirement
The paid boundary appears inside the product, before an automation is activated. English UI · supplied capture reviewed Sep 6, 2026.
05

Pros and limitations

What works

  • A focused publishing workflow
  • The site can be shaped after content exists
  • The free plan is sufficient for core setup

What to watch

  • Automation planning can lead to an early paid upgrade
  • A complex migration needs more preparation than this starter path
  • Templates do not replace deliverability or consent checks
06

Who this route fits—and who should skip it

Good fit

You are starting from zero or a small list

Your first goal is to publish consistently

You want the newsletter and public archive connected

Probably not

You need advanced automation immediately

You need to recreate a complex legacy email design exactly

You cannot test a migration in a separate, reversible step

Sources and scope

Assessment of English UI captures supplied for this project, reviewed on September 6, 2026. A visible control establishes interface availability, not completed end-to-end performance. Screenshots were reviewed for visible names, email addresses, account identifiers, domains, and other account-specific information before use.

Editorial scope: no purchase, live campaign send, payment setup, domain publication, or external posting was performed for this guide.