In short
- Buffer's founders ran every job in the company themselves for nearly a year, and treated that scrappiness as the whole growth strategy. Joel Gascoigne built the first version of Buffer — a two-click Twitter scheduler — in seven weeks of evenings and weekends, and didn't incorporate the company until it had real revenue. He and co-founder Leo Widrich then split every function (product, support, marketing) between the two of them for almost a year, driving 40-50% month-over-month growth with no dedicated marketing budget.
- Buffer bet engineering time on two products that made almost no money, years before that bet paid off. By 2017 Buffer split its engineering team evenly across three products — Publish (the only one making real money), Reply, and the not-yet-launched Analyze. That structural bet on unproven products is what let Buffer diversify revenue and keep growing per-employee revenue instead of just adding headcount to one product.
- By August 2019, Buffer had crossed $20M ARR with under 90 people and under $4M in lifetime funding — and used its own profits to buy out most of its Series A investors. Revenue per teammate hit $244,215. Buffer's newer products (Reply at 2.9% of revenue, Analyze at 2.8%) were still small individually, but together they gave the company more than one lever to pull, which the single-product 2016 version of Buffer didn't have.
- The widely-cited '150 guest posts' and viral-growth-hacking version of Buffer's story could not be confirmed in the six primary sources actually fetched for this teardown. Those specific figures likely trace back to Buffer's own archived 'History of Buffer' series (scouted as S7 but never harvested into this project's local archive). What is directly confirmed by founder-written primary sources: scrappy multi-role hustle, radical transparency as company identity, and a multi-year bet on unbuilt products. Treat the guest-posting-scale narrative as unconfirmed until S7 is recovered.
The mechanism
Buffer's growth wasn't one channel — it was a sequence of structural bets that compounded. Two founders doing every job for a year meant growth had to be cheap and content-driven from day one. Naming transparency as a real company value (including publishing bad news, not just wins) turned the company blog into a trust signal that generated press and word of mouth for free. And deliberately underfunding the most profitable product to build two unproven ones gave Buffer multiple small revenue streams by 2019 instead of one large, fragile one. The popular 'growth hacking / 150 guest posts' version of this story is more dramatic, but it isn't what the founder-written primary sources fetched for this teardown actually document.
Two founders doing every job themselves for a year forced growth to come from content and word of mouth, not a marketing budget
Joel Gascoigne built Buffer's MVP alone in seven weeks of evenings and weekends while working full-time, and deliberately delayed incorporating the company until it had revenue. When co-founder Leo Widrich joined shortly after launch, the two of them covered product, engineering, design, customer research, marketing, and support between them for almost a whole year. Because there was no marketing budget or team, growth in that first year (40-50% month-over-month) had to come from cheap, scrappy channels — writing, direct outreach, and community engagement — which set the company's DNA around content-led, low-cost growth well before Buffer had the resources to buy attention.
We ended up growing Buffer 40–50% month over month for the first year of Buffer.
Making transparency a stated company value turned Buffer's blog into a source of press and trust, not just traffic
Buffer's founders explicitly named transparency — including open salaries, open pricing debates, and public commentary on internal decisions like co-founder departures — as one of the questions they asked from day one ('why is it customary to keep salary information private?'). Publishing hard, uncomfortable company news openly (e.g. announcing that two co-founders were leaving, with a documented day-by-day disclosure timeline to the team, investors, and public) is what converted a blog that could have been generic content marketing into a differentiated brand signal: readers came to trust Buffer's public writing precisely because it included the bad news, not just growth milestones.
We've always done things differently at Buffer. For me, this has always come from a natural desire to question things. Why base your company and team in a single location? Why is it customary to keep salary information private?
Splitting engineering evenly across unproven products for years, before they made money, is what let revenue-per-employee keep climbing
In 2017, Buffer restructured its team so that engineering resources were split roughly evenly across three products — Publish (the only one with meaningful revenue at the time), Reply (small revenue), and Analyze (not yet launched). This was a real trade-off: it meant the most profitable product ran on a fraction of the engineering team it could have had. By 2019 that bet showed up in the numbers — Reply and Analyze had each grown into single-digit percentages of total revenue, and overall revenue per teammate reached $244,215, allowing Buffer to keep growing ARR without proportionally growing headcount or dependency on one product's growth curve.
We moved around our engineering teams and resources so that our teammates were split evenly between the three products, even though one of those products didn't exist yet and the other was making very little revenue.
How it went
Solo MVP build and multi-role hustle
2010-09 → 2013-12Joel Gascoigne coded the first version of Buffer — a bare two-click Twitter scheduling tool — in seven weeks of evenings and weekends while working full-time, and deliberately held off incorporating the company until it had revenue and its first $120K in funding. Leo Widrich joined shortly after launch, and between the two of them they covered product, design, engineering, customer research, marketing, and support for almost a year. That scrappy, self-funded, multi-role period drove 40-50% month-over-month growth in Buffer's first year — a pace the founders themselves later called crazy but achievable precisely because there was no other option.
Transparency becomes a stated value, team scales, co-founders depart
2014-01 → 2017-02As Buffer scaled past its early startup phase, the founders explicitly named transparency as a core company value — questioning norms like keeping salaries private and single-location teams — alongside remote work as one of the movements Buffer chose to be a vocal part of. The team grew from roughly 40 to more than 90 people within about a year (per Joel's June 2016 account), and by February 2017 Buffer had reached 65,000 paying customers, an 80-person team, and more than $13M in annual revenue. That same month, co-founder Leo Widrich and CTO Sunil Sadasivan announced they were leaving over a genuine disagreement about the company's future direction — a decision Buffer disclosed with a fully public, day-by-day timeline of who was told when.
Multi-product platform bet and $20M+ ARR
2017-08 → 2019-08In August 2017, Buffer announced a platform vision: the original product would become Buffer Publish, its 2016 Respond acquisition would become Buffer Reply, and a new Buffer Analyze product would launch for social analytics. The company deliberately split engineering resources evenly across all three products even though Analyze didn't exist yet and Reply generated little revenue — a bet that meant Publish, the most profitable product, ran on roughly a third of the engineering team. By August 2019, that bet had paid off structurally: Buffer had crossed $20M+ in ARR, kept the team under 90 people, reached $244,215 in revenue per teammate, and had spent under $4M in lifetime funding (using $3.3M of its own profits to buy out most of its Series A investors).
Milestones
- 2010-11Joel Gascoigne launches the first version of Buffer (two-click Twitter scheduling), pre-incorporation
- 2014-06Buffer reaches ~500K users; raises $3.9M angel round (per extract.json; original disclosure source not present in the fetched archive)
- 2016-06Team grows from ~40 to more than 90 people within roughly a year, per Joel's founder essay
- 2017-02108333365,000 paying customers, 80-person team, $13M+ annual revenue; co-founder Leo Widrich and CTO Sunil Sadasivan announce departure
- 2017-08Buffer announces multi-product platform vision: Publish, Reply, Analyze
- 2018-02Analyze gets its first paying customer
- 2019-081666667Buffer crosses $20M+ ARR; under 90 people; $244,215 revenue per teammate; under $4M total lifetime funding
Whether it fits you
Buffer's loop depends on founders willing to run every function themselves early, and to keep publishing uncomfortable truths for years, not just milestones. Run it if these hold for you; the costs are real and compound over a long timeline.
What it needs
Founders willing to personally cover every function for the first year, with no dedicated marketing hire
Buffer's early growth came from Joel and Leo doing product, support, and content themselves. If your growth plan assumes a marketing hire or budget from day one, this specific mechanism — cheap, founder-written content compounding into word of mouth — won't reproduce the same way.
A genuine willingness to publish uncomfortable news, not just wins, as a matter of company identity
Buffer's transparency value showed up most clearly when the founders publicly and specifically disclosed a painful event — two co-founders leaving — with a documented day-by-day rollout to the team, investors, and public. Transparency-as-marketing only works if it survives contact with bad news; publishing only good metrics is content marketing with a trust veneer, not the mechanism Buffer actually ran.
Enough runway to underfund your most profitable product on purpose, for years, while building unproven ones
Buffer split engineering evenly across three products starting in 2017, even though one didn't exist yet and another made very little revenue. This requires either profitability or patient capital — a company burning venture funding on a clock usually can't justify slowing down its cash-generating product to build long-shot ones.
What it costs
Founder-led multi-role hustle doesn't scale past the first year, and the transition away from it is genuinely hard
Joel's own writing describes the shift from 'startup' to 'scaleup' as a real organizational crisis, not a smooth glide — the team went from ~40 to ~90 people in roughly a year, and the operating model that worked at 2 founders didn't work at 90 employees. Expect a deliberate, uncomfortable restructuring, not a natural evolution.
Radical transparency means your competitors, your team, and your investors all see the hard numbers and hard news at the same time you do
When Buffer disclosed that two co-founders were leaving, the exact timeline of who was told when (executive team, then all-hands, then investors, then the public) was itself made public. That level of disclosure discipline is a permanent operating cost, not a one-time campaign — and once you start, walking it back damages the trust you built.
Deliberately underfunding your best product to build unproven ones can leave your core business exposed
Buffer explicitly ran Publish — its most profitable product — on a fraction of the engineering team it could have had, for years, to build Reply and Analyze. If a well-funded, focused competitor attacks your core product while you're spread across three, you may not have the resources to defend it.
The numbers we could verify
- revenue per teammate 2019
- $244,215 per teammate (Aug 2019) [S2]
- reply share of revenue 2019
- 2.9% of total revenue (Aug 2019) [S2]
- analyze share of revenue 2019
- 2.8% of total revenue, 1,085+ paying subscribers (Aug 2019) [S2]
- lifetime funding
- under $4M total; $3.3M of own profits used to buy out majority of Series A investors (Aug 2019) [S2]
- notes
- No conversion or churn rates were found in the six primary sources fetched for this run (S1-S6); Buffer's revenue and headcount figures above are the only rate-like disclosures directly confirmed in that archive.
Channels it actually used
- guest posting / outside-blog content (scale unconfirmed in fetched archive)
- company blog and founder essays (joel.is, open.buffer.com)
- radical transparency as a trust and press channel
- multi-product platform expansion (Publish, Reply, Analyze)
- remote-first team building as a talent and culture differentiator
Our read
The popular version of Buffer's growth story leans hard on 'guest posting at scale' (often cited as ~150 posts by co-founder Leo Widrich) as the single explanatory mechanism. That number doesn't appear in any of the six primary sources fetched for this teardown. What those sources actually document, in the founders' own words, is something less flashy but more durable: two people doing every job themselves for a year, a company that named transparency as a value and then tested that value against genuinely bad news (a co-founder and CTO both leaving), and a multi-year bet to underfund the profitable product in order to build two unproven ones. None of that is as quotable as '150 guest posts,' but it's what's actually in the archive.
The most underrated part of Buffer's documented story is the 2017 decision to split engineering evenly across three products when only one of them made real money. Most growth narratives focus on acquisition channels; Buffer's founders were explicit that the harder and more consequential decision was an internal resourcing bet made years before it paid off in the numbers (revenue-per-teammate, product revenue mix) that showed up by 2019.
Buffer's radical transparency is often described as a marketing tactic, but the sourced evidence (specifically the day-by-day disclosure of two co-founders leaving) suggests it functioned more like an operating discipline that happened to generate press as a side effect. The distinction matters for anyone trying to copy this: publishing only your revenue milestones is content marketing; publishing your org's hardest weeks, on a schedule, to your own team before the public, is a different and harder commitment.
Sources
- From startup to scaleup: What we're changing as we make the transition2016-06-01
- Buffer's evolution and expansion2019-08-20
- The next step in Buffer's social media journey2017-08-02
- Buffer Open (company blog / resources index)2026-08-18
- Buffer Open Hub — resources index2026-08-18
- Change at Buffer: The next phase, and why our co-founder and our CTO are moving on2017-02-20
