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

推荐订阅源

让小产品的独立变现更简单 - 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 Snippets New design settings pages 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 Bang paths, source routing, and how email trips were planned Public postmortem: archive downtime Announcement bars for your archives 2025 disposables.app Russian localization Ask a Nerd: Can you improve email deliverability with a personal domain? More locale options 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 What the hell is a UTM? TK reminders in the editor Randomize survey answer order 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 Gift subscriptions
How we interview customers at Buttondown
nickd · 2025-12-17 · via

As Buttondown has grown, we’ve experienced many of the typical growing pains that you’d come to expect. In particular, new customers may not fit our original customer profile, which was, for a long time, other techies like us who cared about independent software and wanted a tool that did one thing well.

If that doesn’t describe you, fair, and we’d like to figure out who you all really are and what you need. That’s where interviewing comes in.

We don’t know our customers

Admitting we don’t know our customers is a bit of a risk. You may view it as a red flag: why support us if we’re clueless about it?

But in reality, no business truly knows their customer. We think it’s a strength for us to admit that we don’t know our customers. So many businesses view their customers as an “unknown unknown”, and they succeed based on luck or guesswork.

We know we can do better. By learning what drives you, we can build the best Buttondown for everyone.

Every single customer comes to Buttondown with their own hopes & motivations. Some of them have never started a newsletter before. Others have used a spreadsheet for years and want something a little more fit for purpose. No matter your perspective, we want to know it and adapt to it.

How we interview

Every month or so, we gather a list of Buttondown users that fits a specific theme. One month we might interview veterans & power users; another month, we might ask new customers what’s holding them back from onboarding. We get a list of emails and ask them if they might have time for a half-hour call. We offer a gift card for their time, because we need to provide some form of incentive.

What we ask on that call depends on who we know we’re talking to, and what direction we find the conversation going in. We can do our best to narrow down the criteria by which we recruit new people to talk to, but at the end of the day we really have no idea who’s going to show up on the other end of the call.

As for how to guide the interview, the unfortunate answer is to spend 20 years interviewing customers before you’re asked to do it for Buttondown. Interviewing only works when you’re experienced enough to interview people specifically for design insights. It’s not enough to ask what’s broken, or what pains they felt before coming in the door. You need to listen & reflect back what the participant is saying, because you never know what will come through.

Some big things I find myself doing are:

  • Create immediate familiarity & comfort. I tell all participants that we’re looking specifically for feedback that helps us grow as a business, and that I have a direct line to the CEO (true) and they cannot hurt my feelings (false, but it gets a laugh).
  • Be actively listening to the customer’s response in order to guide your next question. “You said X there. Can you expand on that?” is a classic.
  • Create enough silence that the customer keeps talking. That’s often where the truth comes out.
  • Provide space at the end for them to ramble free-form. Every time you ask if there’s anything else they’d like to add, they say “oh, no…” and then add five things.

But the real answer is to practice by interviewing people often.

Making sense of it

I take handwritten notes on every call. Then I record & transcribe every call, and then I write up summaries of my notes. At the end of the summary, I write up some takeaways and fill our bug tracker with projects & bugs to fix. We discuss as a team, and we do it all again.

We’ll never fully understand our customers, but through interviewing we can understand more & more, and learn how to make a Buttondown that works for everyone.