$10K MRRin 5 years

3 milestones

Last known revenue

$75K MRRas of May 2023Source

Last public figure; founder stopped disclosing in early 2025.

Construyendo un negocio de newsletters exitoso al construir menos

Founder

Justin Duke

Fundador en Solitario•Technical•USA

Commitment

Side Project

Experience

First-time

Product

Buttondown

Una herramienta pequeña y elegante para producir newsletters, enfocada en la simplicidad para escritores técnicos.

Type

SaaS

Industry

Creación de Contenido

Model

Suscripción

Marketing Strategy

How Justin acquired customers

Growth Channel

Boca a Boca

Also Used

Twitter / XSEO / Contenido

Tech Stack

Tools used to build Buttondown

DjangoVue.jsPostgreSQLStripe

The Full Story

TL;DR

Justin Duke construyó Buttondown como un proyecto secundario en Stripe hacia un negocio rentable con media docena de empleados - sin recaudar capital de riesgo.

Cuando Justin Duke comenzó a construir Buttondown, no tenía la intención de iniciar una empresa. Solo quería una herramienta de newsletter que no se sintiera rota.

El origen

"Estaba usando TinyLetter", explica. "Me encantaba. Pero fue comprada en 2011; años después, simplemente había acumulado telarañas. Había errores muy obvios."

Estaba trabajando a tiempo completo como ingeniero en Stripe, enviando un newsletter a familia y amigos. En las noches y fines de semana, trabajaba en su propia versión.

Negocio accidental

"Solo iba a ser auto-hospedado. Pero mostraba a la gente y decían 'usaría esto! ¿Cuánto cuesta?'"

Eso fue en 2017. Hoy, Buttondown es una plataforma accesible que potencia newsletters para miles de clientes con aproximadamente media docena de empleados.

El enfoque anti-crecimiento

Justin nunca recaudó capital de riesgo - no por falta de interés. "Le debo mi carrera a la industria tecnológica. Pero si hay una queja, es la mentalidad de abundancia o escasez donde tienes este único final posible correcto: salida por mil millones de dólares o fracaso."

Vendiendo lo que no tienen

"Encontramos mucho éxito en vender a los clientes lo que no tenemos. Deliberadamente hacemos referencia a Markdown en landing pages como un shibolé. Si te aterroriza Markdown, Buttondown probablemente no es para ti."

Comenzó: 2017 como proyecto de noches/fines de semana
Dejó Stripe para dedicarse a tiempo completo: 2021
Equipo: ~6 empleados
Recaudó: $0 en capital de riesgo

Key Takeaways

Rascar tu propio picor puede llevar a un negocio real

Los proyectos secundarios pueden crecer de forma sostenible sin financiamiento de capital de riesgo

Ser opinionado sobre tu producto filtra a los clientes ideales

Puedes competir con gigantes siendo intencionalmente enfocado y pequeño

Originally published onOpen Source Pledge Blog

Founder proof brief

A one-page proof brief turns Justin's Buttondown playbook into your next test.

See what it covers before you sign up: the pattern worth copying, the channel to test, and the risk to avoid when you adapt this story.

Pattern

$10K MRR

Channel

Boca a Boca

Output

Action checklist

What a proof brief covers

A one-page brief that turns Justin's pattern into a testable plan
Channel bet: start from Boca a Boca
A risk check before copying the Buttondown playbook

See what a proof brief covers

See what it covers first. Create an account only if you choose to unlock.

Inspired by Justin's journey? Generate a business idea in the Creación de Contenido space using AI and real founder data.

Milestone Journey

Justin achieved 3 milestones on the path to $10K MRR

Primer Cliente

3 months

July 2017

9% faster

vs avg 3 months

+1 year to next milestone

$1K MRR

2 years

January 2019

Avg: 11 months

+3 years to next milestone

$10K MRR

5 years

January 2022

Avg: 1 year

5 years

Total journey time

Milestones achieved

Justin's Path to $10K MRRPremium

The journey, decisions, and context behind this milestone

How Justin actually did it

7/7 funnel stages sourced

Reconstructed from Justin's own published sources. Quoted claims are the founder's words, verified verbatim; anything marked as our analysis is exactly that.

Where the idea came from

Personal pain

Justin was already using a comparable newsletter tool and had the familiar side-project impulse to build something better. Rather than start immediately, he set himself a six-month deadline: if the itch to build his own version hadn't gone away by then, he'd start working on it. A separate, later HN comment (s3) frames the same decision as picking a sub-niche (Markdown, a REST API, developer-adjacent functionality) he was personally well-equipped to build.

“I was using a similar tool and thought to myself “man, I could make something better than this.””

jmduke, HN comment on "Ask HN: How did you find your great side project idea?"

Validation

Built first, validated after

MvpValidated

No separate landing-page test, waitlist, or presale is documented anywhere in Justin's own writing. The build itself was the validation: per his own year-end recap, he decided to build in late April 2017, had something functional enough to send emails by end of May, launched officially by end of June, and had a few paying customers by July.

The launch-to-paying-customer sequence, in Justin's own words at the end of Buttondown's first year.

“By the end of June, it was officially launched.”

Justin Duke, "2017 in review", Buttondown blog

First test users

Personal networkFree testers

Buttondown started as a self-hosted tool Justin built only for himself, then showed to a few friends, who pushed him to turn it into something more than a personal script.

Per "How I Built A $5K/Month Newsletter Tool", Rad Letters (Q&A interview with Justin Duke)

First paying customer

Personal networkDirect ask

There was no formal sales motion. Per a third-party interview where Justin is directly quoted, people he showed the self-hosted tool to simply asked to pay for it. A separate founder-authored Q&A puts the first paying customer at roughly a month after he started using his own tool, in the same range as the record's own 60-day figure.

Per Greg Kumparak, "Buttondown: How One Team Built a Successful Business by Building Less", Open Source Pledge blog (the record's existing sourceUrl)

Acquisition channels, and whether they worked

Word of Mouth · Hacker News comments and threadsScalingWorked

His standard move on HN is a short disclosure plus a link to something genuinely useful, like his own MTA/ESP comparison guide, rather than a pitch.

“I run Buttondown, which is an email-inflected product. I also have a comparison guide of various MTAs here”

jmduke, HN comment disclosing Buttondown and linking its ESP comparison guide

What didn't work

ChannelLaunchCost: time

In his only public year-end retro, Justin names weak distribution, not the product, as 2017's biggest miss.

“Didn’t market things enough, which isn't a product failure so much as a growth failure.”

Justin Duke, "2017 in review", Buttondown blog

He frames it as a deliberate trade-off rather than an oversight: he spent his limited nights-and-weekends time on the product instead of on distribution.

“I cared more about making sure the product was as strong as possible than making sure it was in the hands of as many people as possible”

Justin Duke, "2017 in review", Buttondown blog

PricingScalingCost: time

Buttondown's 2018 launch pricing paired at-cost email sending with a flat $29/mo add-on for features like custom domains and whitelabeling. It confused prospective customers before they had even signed up.

“The vast majority of new customers would have to begin their journey by emailing me some variation of "wait, so how much do I need to pay?"”

Justin Duke, "Pricing page driven development", Buttondown blog

What they did instead: Replaced in 2022 with a conventional three-column tiered SaaS pricing grid built around a $29/mo plan.

PricingLaunchCost: both

Buttondown also launched with a generous free tier (up to 1,000 subscribers). It helped early signups but hurt margins and absorbed most of Justin's support time, since the majority of his customer-service hours went to people who weren't paying.

“and it certainly helped with early adoption, but hurt almost every other part of the business — in particular unit economics and customer service”

jmduke, HN comment on curtailing Buttondown's free tier

What they did instead: Curtailed the free tier, which nearly doubled conversion rate and cut support load; the exact date of this change is not stated.

How it changed as they grew

Today: 1 person (Solo founder plus a handful of contractors for support and documentation; no other full-time (W2) hires, as of September 2023.)

Today: 6 people (Roughly half a dozen full-time employees by mid-2025, per a third-party profile; this headcount is not confirmed in any founder-authored source we found.)

Bootstrapped

Pricing restructure: Usage-based email-sending cost plus a flat $29/mo add-on for features (in place since the 2018 launch) → Conventional three-column tiered SaaS pricing grid centered on a $29/mo plan

The old hybrid model was confusing: most new customers had to email Justin just to find out what they'd owe.

“The vast majority of new customers would have to begin their journey by emailing me some variation of "wait, so how much do I need to pay?"”

Justin Duke, "Pricing page driven development", Buttondown blog

Pricing new tier: Three-column grid with no dedicated enterprise pricing → Added an explicit enterprise tier plus a Professional tier gating whitelabeling, teams, and dedicated IPs

Larger prospects had no obvious tier to land in, so Justin had to improvise pricing for them ad hoc every time they reached out.

“Enterprise/volume-based revenue was the wild west: larger customers were put off by the fact that there weren't any obvious tiers for them”

Justin Duke, "Pricing page driven development", Buttondown blog

Pricing decrease: Free tier up to 1,000 subscribers → A curtailed free tier (paid plans required much sooner); Justin does not state the new subscriber limit or the date of the change

The generous free tier helped early adoption but was hurting margins and eating most of his customer-support time.

“and it certainly helped with early adoption, but hurt almost every other part of the business — in particular unit economics and customer service”

jmduke, HN comment on curtailing Buttondown's free tier

What broke as they grew

The main constraint on Buttondown's growth reads as self-imposed rather than external. In 2019, with the product around $2-3K MRR, Justin said doubling revenue held little appeal against the added customer-support and feature-scope burden of doubling the customer base.

“I can't think of a way in which my life would be improved by additional revenue, but I can think of a lot of ways”

jmduke, HN comment on ~$2-3K MRR and not wanting to double the customer base

Sources (12 in the founder's own words)

Justin Duke, "2017 in review", Buttondown blog · founder-authored · 2017-12
jmduke, HN comment on "Ask HN: How did you find your great side project idea?" · founder-authored · 2017-08
jmduke, HN comment describing Buttondown's niching-down strategy · founder-authored · 2022-12
jmduke, HN comment on time to $2K/mo MRR and full-time transition · founder-authored · 2023-04
jmduke, HN comment on quitting Stripe to run Buttondown full time · founder-authored · 2024-01
jmduke, HN comment on balancing Buttondown with a day job · founder-authored · 2023-11
jmduke, HN comment on solo-founder team structure and VC philosophy · founder-authored · 2023-09
jmduke, HN comment on curtailing Buttondown's free tier · founder-authored · 2023-11
jmduke, HN comment on ~$2-3K MRR and not wanting to double the customer base · founder-authored · 2019-10
Justin Duke, "Pricing page driven development", Buttondown blog · founder-authored · 2023-03
Justin Duke, "Dear Tinyletter Users", Buttondown blog · founder-authored · 2023-11
Greg Kumparak, "Buttondown: How One Team Built a Successful Business by Building Less", Open Source Pledge blog (the record's existing sourceUrl) · third party · 2025-07
"How I Built A $5K/Month Newsletter Tool", Rad Letters (Q&A interview with Justin Duke) · third party · 2020-06
jmduke, HN comment disclosing Buttondown and linking its ESP comparison guide · founder-authored · 2024-08

Launch Strategy

How they introduced the product to the world

Soft Launch

Initial go-to-market approach

Low risk — lets you iterate quietly

Validation

How they tested demand before building

MVP

Method used to confirm market interest

Most common approach — build and learn fast

Launch Pricing

Price point when the product first launched

Gratis

Initial pricing strategy

Common for building initial traction

Starting Audience

Whether they had followers before launch

Started from Zero

Built audience alongside the product

63% of founders in our database started from zero

Time Investment

Average weekly hours during building phase

15 hrs

per week on average

Part-time effort — common for side projects

Initial Investment

Capital required to get started

$100

in startup costs

Minimal investment — software and domains

Biggest Challenge

Competir contra gigantes como Mailchimp y Substack mientras permanece intencionalmente pequeño

Unlock Justin's Full Journey

See the complete breakdown: launch strategy, validation methods, startup costs, expert analysis, replication playbook, and more actionable insights.

Upgrade to Premium

Instant access to all founder journeys

Frequently asked questions

How much does Buttondown make?

The last known public figure for Buttondown is $75K MRR as of May 2023. Last public figure; founder stopped disclosing in early 2025. Source: Buttondown.

What is Buttondown?

Una herramienta pequeña y elegante para producir newsletters, enfocada en la simplicidad para escritores técnicos. It operates in Creación de Contenido.

How long did it take Buttondown to reach $10k mrr?

Justin Duke took 5 years to reach $10k mrr with Buttondown.

Was Justin Duke a solo founder?

Yes. Justin Duke built Buttondown as a solo founder.

What marketing channel did Buttondown use to grow?

Buttondown grew primarily through Boca a Boca.

What industry is Buttondown in?

Buttondown operates in Creación de Contenido.

Share this story:

Explore similar stories

$10K MRR Boca a Boca Creación de Contenido Fundador en Solitario

Enjoyed this story?

Get more founder journeys like this delivered to your inbox every week.

Join founders learning from real success stories

Founder stories

Browse Stories

The Full Story

TL;DR

Justin Duke construyó Buttondown como un proyecto secundario en Stripe hacia un negocio rentable con media docena de empleados - sin recaudar capital de riesgo.

Cuando Justin Duke comenzó a construir Buttondown, no tenía la intención de iniciar una empresa. Solo quería una herramienta de newsletter que no se sintiera rota.