惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

文章列表

Compulsive curiosity, or, how I built an infinite idea machine Gift details on the subscriber portal Portal link in the archive nav The physicists who convinced Fermilab to send Brazil's emails First, add no friction: How micropayments lost and subscriptions won Filter subscribers and automations by source Automations, rebuilt What email will look like in the future Filter subscribers by bounce date and reason Email could have been X.400 times better Three features are moving behind the paywall Firewall changes and improvements Put your name and voice into your company newsletter Simplified email address settings Subscription wall Inboxes were overwhelming before we'd even named them The US government tried really hard to screw up email Public postmortem: database connection exhaustion Ask a nerd: what is the best way to unsubscribe from newsletters? Bookshop.org embeds Email was into agents before they were cool Passwordless login Rename metadata keys in bulk A spring cleaning for our legal docs Ask a nerd: what happens when you click the spam button? Passkey support for two-factor authentication How Buttondown's API versioning works Safer defaults for the email creation API How to send email to space How we enabled Content Security Policy for everyone Recovery codes for two-factor authentication Filter sent emails by engagement rate How we migrated to TypeIDs without breaking clients How we check every link in your email Use newsletter metadata in your emails Should we bring back email exploders? Sort and filter by open and click rates Custom click tracking domains More newsletter settings in the API Revamped replies Custom email templates for everyone Simplified cancellation Ask a Nerd: Does email length affect deliverability? The changelog, reborn Swedish localization Forwarding an email is not always straightforward Public descriptions for tags OpenAPI spec for archives How Rodrigo brings a humanistic view to consumer technology Survey responses on the web How Brandon Lucas Green shares his music and supports artists Subscribers can come from anywhere. Even another newsletter platform's form. Your newsletter's archives are more valuable than your list Better tag self-management Smarter automation filters Granular API keys New design settings pages Snippets Ask A Nerd: How does newsletter cadence affect deliverability? Starred views More ways to customize your archives Inbox filtering Mastodon follower analytics Ask a Nerd: What are good open, click, and response rates for an email newsletter? How we migrated our database to PlanetScale Two new archive themes Custom buttons now work in Markdown mode Ask a Nerd: Does attaching files to your newsletter hurt deliverability? Seline and Tinylytics support Unban subscribers Announcement bars for your archives Bang paths, source routing, and how email trips were planned Public postmortem: archive downtime 2025 disposables.app Russian localization Ask a Nerd: Can you improve email deliverability with a personal domain? More locale options How we interview customers at Buttondown Bluesky analytics Reply to conversations Minimum viable complexity How Jeffery Hicks goes behind-the-scenes in his newsletter Changes to our stack in 2025 2026: Emails TK reminders in the editor Randomize survey answer order What the hell is a UTM? Why we insourced analytics Scroll sync in the editor 2026: Archives How Jamie Thingelstad uses Buttondown to explore tech topics How Kelly Jensen uses Buttondown to discuss key library issues Keeping feature creep at bay Improved filters Content Security Policy in archives Open source Sniperl.ink Auto-activating RSS reader subscriptions What the hell is ActivityPub? How Igor Ranc built Berlin's largest expat tech newsletter
How we welcome new customers at Buttondown
nickd · 2025-09-12 · via

Let’s say you sign up for Buttondown as a new customer. Hi! Welcome! Okay, now what?

I’ve been tasked with answering this question. It’s a surprisingly hard question! That’s because Buttondown customers have a wide diversity of:

  • needs (migrating from somewhere else? running automations?)
  • experience levels (never run a list before?)
  • backgrounds (business? creator? just for fun?)

Looking at some examples, you can see how this would break down:

  • If I run a small business with lots of automations and I’m migrating my list from a competitor, then I’ll want someone to help with migrating everything, set up analytics, and I’ll probably need to invite other team members.
  • If I’m a journalist with paid & free tiers, I’ll want to move my readers over, get set up on our billing, and turn on analytics.
  • If I’m building a brand-new newsletter for my block club, I’ll want to set a name and figure out how to share it with my neighbors.

Yes, there’s some overlap, but it all comes down to one thing: our customer base is diverse, and their needs will vary. We can’t really figure out what to do with a new customer by guessing. We have to ask them.

We’ve historically done a lousy job of this. We know roughly who our customers are, because we pay attention and talk to them a lot. We don’t know this with any degree of precision. We’re guessing as to what they do next.

Worse yet, there’s a bit of an unknown-unknown problem, where we may not know that some cohorts exist. We’re guessing as to the categories. Any guess is informed – but, by definition, will never be fully correct.

Welcome to Buttondown. Help us help you.

And so, as I’ve begun creating an onboarding process for Buttondown, I’ve broken the process down into three steps:

1. Who are you?

Think the basics, like name, email address, user name: the bare minimum that you need to run a newsletter from us.

2. What best describes you?

This is where we get to answering the question in this post. We want to know the answer to this for two reasons: it radically affects what we’re about to ask you, and as a business, selfishly we want to know who our customers really are.

For the time being, we’ve broken that into four categories:

  • Casual
  • Creator
  • Technologist
  • Business

If you answer “casual”, then you don’t get another question. For the others, we want to know what type of creator, technologist, or business you are – with the classic “other” option for all of the types we’ve forgotten.

We say “for the time being” because we fully plan on changing these lists of categories & sub-categories over time. It is truly hilarious to ship something that we know we got a little wrong, but here I think it’s the right move, since there’s no way we’ll know how we got it wrong until we put it in front of real people.

3. Can you do what we think you need to get started?

Based on how you respond to who you are, we’ve then created a series of custom-tailored steps that help you get started with Buttondown.

Every step is skippable. In fact, the whole process is skippable with one click.

Here, we’re also shipping something that we know is “wrong.” As our customers skip or fill out various steps, we’ll learn more about how to serve future customers like them – which will allow us to remove steps and avoid hassling people.

Oh right, the home screen

In order to make this all work, we also had to build a brand-new home screen for all customers in Buttondown. Doing so gives us a place to ask these questions and get people acclimated to the product, and it also helps existing customers better understand the health & progress of their lists at a glance.

Launch, adapt, repeat

As we roll out the first version of this process, I meet the moment with no small amount of excitement & nervousness. If you’re new to Buttondown, I hope you take our brand-new first impression as a sign of our wanting to help you make the most of your newslettering experience. And if you’ve been around for a while, thanks for sticking with us while we threw you into a blank screen with no life preserver. We made it better now.