Justin Duke: Buttondown from Side Project to $1M+ ARR Run Rate
Ex-Stripe engineer who built a markdown-first newsletter tool for himself, kept the day job for years, and grew a respectful, bootstrapped alternative in a crowded market.
Editorial profile. Written by IndieFounder Editorial Team from publicly available information. It is not a direct interview: the first-person answers are our summary of the founder's public statements, not verbatim quotes. Figures are approximate and not independently verified. Report an error.
- MRR
- ~$83K+ (run rate; self-reported 2025)
- ARR
- $1M+ (run rate; self-reported)
- Users
- Tens of thousands of writers
- Founded
- 2016
- Team
- Small (solo origin, later lean team)
- Stack
- Django, Vue, PostgreSQL, Heroku
How did Buttondown start?
Justin Duke was an engineer (later engineering manager) at Stripe and previously Amazon. Around 2016 he was using TinyLetter for a personal newsletter and found it neglected after its acquisition. The classic engineer reaction followed: he thought he could build a better version in a weekend.
It took longer than a weekend. He wanted something markdown-first, quiet, and respectful of both the writer and the reader — without the bloat of Mailchimp-style tools or the platform ownership of Medium or Substack. He built it first for himself, then shared progress publicly. People asked how much it cost and said they would use it. He added a user table, put a janky version on Heroku, and iterated.
The first paying customer arrived in August 2016. Early growth was slow: from roughly $500 MRR to around $1,500 between 2017 and 2018. A good month could be a single new customer. That pace was only sustainable because it remained a nights-and-weekends side project while he kept a full-time job at Stripe. The long runway mattered more than any single launch.
He chose Django because it matched the stack at his day job, deliberately conserving “innovation tokens.” The frontend used Vue in a hydration pattern: Django rendered a thin shell and seeded data; Vue handled the interactive parts. He has said he has never regretted Django even after years of production use, though he later expressed mixed feelings about the Vue choice.
The long side-project phase
Buttondown stayed a side project for years. Duke has described the advantage clearly: when you are not drawing a salary from the product, slow growth is painful but viable. Churn stayed low. Top-of-funnel was limited because he was not spending on ads or chasing virality. He posted on X, wrote about the process, and had solid but not explosive launches on Hacker News and Product Hunt. There was no single “product-market fit” moment — just a continuous drip of new users and customers who refined the product and its position.
By December 2022 the product was around $15K MRR (self-reported). He was still at Stripe when the Indie Bites podcast recorded an episode about the side project; by the time it aired he had left to go full-time on founder work. In a 2024 personal essay marking two years since leaving Stripe, he reflected on the decision: at 29, with savings, a supportive spouse, no children, and projects he was excited about, the conditions were as good as they would ever be. “If not now, when?”
He also co-runs Third South Capital, a holding company that acquires and operates small profitable software businesses. The independent path became a combination of founder (Buttondown) and operator/investor.
From $15K MRR to a $1M+ run rate
Growth remained steady rather than explosive. Duke has noted that the same ~5% month-over-month compounding that felt unsatisfying early on later produced meaningful absolute gains. In a 2025 Indie Hackers post he stated that the current run rate was over $1M ARR (roughly $83K+ per month). He described the business as fully bootstrapped and profitable, powering newsletters for tens of thousands of writers — from people sending to a dozen friends up to authors and companies reaching hundreds of thousands.
A metric he has highlighted: every day someone churns from a much larger, higher-valuation platform in favor of Buttondown. The product does not take a cut of creators’ paid-subscription revenue; it monetizes through its own subscription tiers. The positioning has stayed focused on being a reliable, low-drama backend rather than trying to become a social network or content platform.
Distribution has been primarily organic: word of mouth, his own writing and site (jmduke.com), high-quality support, and later some referral from LLMs. He has emphasized that being genuinely responsive is a marketing channel. In a 2025 year-end note he reported 61% revenue growth, with active authors and unique email recipients also up substantially, while remaining cash-flow positive with no outside capital.
The team started as one person and later grew into a lean group (full-time and part-time). Duke has written about support load, first-reply times, and the operational realities of running the business after leaving the safety net of a large company.
What the work looks like now
The stack has stayed deliberately boring in places. Django remains the core. Recent public posts show continued attention to infrastructure simplification — for example, removing Redis in favor of PostgreSQL for remaining queue, cache, and session needs as part of a broader Heroku migration. The product continues to add features (automations, analytics, teams, API, paid subscriptions, RSS, concierge migration) while trying to preserve the original “quiet and respectful” character.
Duke has been open that independent work is not automatically more lucrative than a high-paying industry role. In the two-year essay he noted that even with a healthy, growing business, the returns were less than what a high total-compensation FAANG-style job would have produced over the same period. The trade-off he describes is creative fulfillment, flexibility, and ownership versus the camaraderie, benefits, and raw compensation of a large company.
Lessons that still feel true
Building for yourself first can work if the problem is real and shared. The early product was intentionally narrow. That constraint limited speculative features and forced focus on what actual users needed.
Keeping the day job for years is an underrated advantage in a crowded market. It removes the pressure to make desperate pricing, positioning, or feature decisions while the product compounds slowly through word of mouth and support quality.
Respect for the user is a durable differentiator. In a category full of price increases, shutdowns, and platform pivots, a small independent tool that treats email as a utility rather than a growth-at-all-costs surface can win specific customers every day.
Finally, the long game is mostly patience plus operational excellence, not a single breakthrough. Duke’s public record shows years of incremental progress, public writing, and steady compounding rather than a viral launch. The numbers that matter are the ones he has shared himself; third-party estimates exist and should be treated as estimates.
Caveats
Revenue figures above are self-reported by Duke in interviews, podcasts, and his own writing (notably the ~$15K MRR figure for December 2022 and the “over $1M ARR” run-rate statement in 2025). They are not independently audited. Growth rates and absolute numbers can change. Team size and exact stack details have evolved. The story relies on primary and near-primary sources (his site, Buttondown blog, Indie Hackers, podcasts, and public posts) rather than leaderboard aggregators.