A conversation with the founder of Buttondown

Justin Duke built Buttondown because he was tired of newsletter tools that got in the way. What started as a weekend project has grown into one of the most respected independent email platforms on the web.

We spoke with Justin about the philosophy behind Buttondown, the economics of indie software, and why he thinks the best tools are the ones you barely notice.

The accidental product

"I built Buttondown for myself. I wanted to send a newsletter, and everything available was either too complex, too expensive, or too ugly. So I spent a weekend building something simple."

That weekend project turned into something larger when friends started asking to use it. Then their friends. Then strangers on the internet. Justin describes the growth as "organic to the point of being accidental."

What makes Buttondown different isn't any single feature — it's the absence of features. There are no drag-and-drop email builders, no complex automation flows, no AI-powered subject line generators. You write in Markdown. You hit send. Your readers get a clean, readable email.

On independence

"I've been approached by investors a few times. The conversations are always polite, but they always end the same way. I don't want to build a billion-dollar company. I want to build a good tool."

Justin runs Buttondown as a solo operation, with occasional contract help for specific projects. He's profitable, sustainable, and — by his own admission — happier than he's ever been as a software engineer.

The economics are straightforward: charge a fair price for a good product. No free tier subsidized by venture capital. No aggressive upselling. Just honest pricing that reflects the actual cost of running a reliable email service.

On the newsletter renaissance

"People talk about the newsletter boom like it's a trend. I think it's a correction. Email has always been the most reliable way to reach people. We just forgot that for a while."

Justin sees newsletters not as a content format but as a relationship format. The inbox is intimate. When someone subscribes, they're inviting you into a space they check every day. That's a privilege, and it should be treated as one.

On building in public

"I share my revenue numbers, my roadmap, my mistakes. Not because transparency is trendy, but because it keeps me honest. When your users can see exactly what you're working on, you can't hide behind vague promises."

"The best software feels like it was made by someone who uses it every day. Because it was."