How Buffer Runs a 75-Person Remote Company With Transparent Salaries and No Office

Snapshot

Buffer is the social media management tool. Its December 2025 shareholder update reports 198,537 monthly active users and 69,760 paying customers. These are dated operating results, not today’s live metrics. (Source) The company reported 75 profit-share recipients in February 2026, supporting an approximate early-2026 team size of 75. (Source) Joel Gascoigne announced the decision to go fully remote in 2012; Buffer’s last physical office closed in late 2015. (Source)

Buffer’s standout contributions include financial transparency (public salaries since 2013) and operating documentation that explains its choices and revisions. (Source)

Their 2023 post “Buffer is Remote but not Async-First, Here’s Why” is one of the most candid pieces of remote-work operating documentation written by a practitioner. It is worth reading directly.

Core Philosophy

Buffer’s published communication philosophy emphasizes judgment about when to use synchronous or asynchronous communication, with flexibility in both directions. (Source)

Buffer’s current published values are Default to transparency, Improve consistently, Be a no-ego doer, Show gratitude, Choose optimism, and Reflect to unblock. (Source)

Inference: a public salary system makes it easier to inspect whether pay follows the company’s stated principles. It cannot by itself establish that every employee considers the outcome fair.

Communication Model

Buffer is explicitly not async-first. This is their own description, not a criticism. From their published documentation:

“Some remote companies are async-first. A few are even fully async with no live calls or in-person time at all. However, this isn’t what we’ve chosen for our culture.”

(Source)

Buffer’s published 2023 communication framework — three-way split by tool:

(Source)

Why they keep synchronous communication:

1. Speed for complex problems. Waiting for async replies during a crisis is genuinely worse than a 30-minute Zoom call.
2. Relationship building. Video calls humanize people in a way that written communication does not. Facial expressions, tone, and real-time response build trust that text cannot.
3. Things that only surface in live conversation. “In live conversations, sometimes topics come up naturally that wouldn’t have otherwise.”

(Source)

Slack usage has explicit norms — Buffer has published “10 Slack agreements” governing expected response times, use of notifications, and what belongs in Slack vs. elsewhere. Slack is not abandoned; it is governed. (Source)

“Give flexibility to get flexibility” is the summary principle. Team members are expected to occasionally stretch their hours to accommodate others’ time zones — and in return, they receive the same flexibility. It is not a one-way demand. (Source)

Planning and Cadence

Buffer’s public operating accounts describe several cadences and learning practices:

• Profit share tied to annual performance. In February 2026, Buffer reported its seventh profit share: $377,005 for 75 teammates, based on 15% of 2025 net profit. Allocation combines equal, salary-based and tenure-based portions. (Source)
• Transparent shareholder updates. Monthly public reports to shareholders covering revenue, customers, active users, and profitability. These are not marketing documents — they include negative months. (Source)
• Four-day schedule with a flexible fifth day. Buffer’s current careers page describes four workdays and a meeting-free fifth day available for overflow work or personal time. (Source)
• Company Build Week. The August 2026 AI build event is documented in the AI section. It is a one-week output count, not the planning cadence.

Decision-Making Model

Buffer’s decision-making model is not publicly documented in detail, but their transparency norms give it shape:

• Public salary system makes the calculation inspectable. Buffer’s 2024 explanation separates market data, internal role-and-level benchmarks, and individual salaries. It applies high/global location factors and retains a legacy salary-choice adjustment for some employees. (Source)
• Co-founder Joel Gascoigne (CEO) makes major decisions and publishes reasoning publicly via shareholder letters and blog posts.
• Ownership culture. Buffer’s current values emphasize initiative, adaptability, and considering the wider team. (Source)

Org Structure

• ~75 employees as of early 2026. (Source)
• Traditional structure with executives, managers, and ICs — not manager-less.
• Multiple continents. Teammates are listed by name and country on the public About page, which currently shows the team in countries including the USA, Canada, UK, mainland Europe, Australia, Nigeria, South Africa, and Singapore. (Source)
• Fully-remote decision in 2012; last physical office closed late 2015. The office was abandoned deliberately, not closed by circumstance. (Source)
• Joel Gascoigne (CEO) and Hailley Griffis (Head of Communications) are among the most public voices on how the company operates.
• Hiring context before the first interview. Buffer sends a role-specific Q&A document when inviting candidates to interview. The practice began in engineering and had spread to most open roles by July 2026. (Source)

Tools and Stack

(2023 communication framework, February 2025 project-management update)

Rituals

Annual team retreat. Buffer holds in-person retreats as a fully remote team. Details vary year to year.

Profit share. Annual distribution of 15% of net profit to all teammates. This is a ritual that reinforces the “we win together” operating principle. (Source)

Monthly public shareholder reports. These are as much an internal ritual as an external one — they force honest accounting of performance every month, publicly, which shapes internal discussions about what matters.

Transparent salary system. The published benchmarks and calculations make compensation an inspectable operating practice. (Source)

AI

Every teammate can expense AI tools. On February 28, 2025, Buffer made all teammates eligible for $250 per year for AI tools of their own choosing, after the stipend began as an engineering discussion. The post encourages sharing experiments. It does not report uptake, savings, or whether that exact allowance was unchanged later. (Source)

Build Week 2026 put that access into a company-wide build. The August 28, 2026 recap describes the prior week: 72 people stopped regular work and each directed an AI-assisted project. Earlier Build Weeks used teams and pre-selected projects. By Friday the company reported 112 projects completed, 57 internal tools live from 41 people, 1,083 pull requests merged across 26 repositories, 15 changes shipped into the admin product, and six first-ever pull requests. Two help-center editing tools were paused over security and write-access questions, and an application-screening agent stayed local during security review. These are event outputs, not a measure of lasting adoption or lower maintenance cost. (Source)

What They Do Well

• The honest documentation of where they diverged from prevailing norms. Most companies publish the idealized version of how they work. Buffer published why they chose NOT to be async-first. That specificity — “here is where we deliberately disagreed with the trend, and why” — is more useful than another generic remote-work manifesto.
• Salary transparency as an operating system. Buffer documents how its compensation approach evolves, rather than treating a formula as permanently settled. (Source)
• Shared financial outcomes. Inference: the approximately $5,000 average 2025 profit share may reinforce a connection between company performance and individual reward. The size of its cultural effect has not been measured here.
• Small team, mature product, sustainable economics. 2025 was their strongest year in years — Buffer’s 7th profit share post reports $2.51M net profit, with 15% redistributed to teammates (Source); the December 2025 shareholder update reports ~$1.95M MRR (≈$23.4M annualized) across ~69,760 paying customers (Source). Running a profitable bootstrapped-style company with 75 remote people is a different playbook than hypergrowth SaaS — and it works.

Tradeoffs and Weaknesses

The balanced sync/async approach requires judgment calls. Inference: Buffer’s routing guide leaves room for individuals to assess communication needs. A growing team may need more explicit response and escalation norms as interpretations diverge.

Small team means fragility. At 75 people, a handful of departures in a key function creates disproportionate impact. Buffer has experienced this — the company was larger at peak and has operated through multiple years of reduced profitability.

“Give flexibility to get flexibility” can erode if not enforced. The norm asks individuals to accommodate off-hours calls sometimes, in exchange for schedule autonomy. In practice, the people with the least institutional power (new hires, contractors, more junior employees) often give more flexibility than they receive. The norm requires active management to prevent this asymmetry.

Limited public documentation depth. Compared to GitLab’s multi-thousand-page handbook or 37signals’ public guides, Buffer’s operating documentation is lighter. The blog posts are high-quality; the systematic operational documentation is thinner.

What Founders Can Copy

Buffer is a 75-person profitable case. The transparency-and-routing practices below transfer cleanly at small-to-mid scale; the profit-share and salary-formula items have known scale-and-stage constraints noted per item.

1. Publish your compensation logic. Inference: use Buffer’s salary system as a reference for transparent benchmarks and adjustments, adapting its choices to your company’s market and roles rather than copying its formula directly. (Source)
2. Document why you are NOT doing the trendy thing. Buffer’s “we are remote but not async-first, here’s why” is more useful than most remote-work content because it explains a deliberate choice against prevailing advice. Writing this document forces clarity about your own operating principles. (Applies at any scale; especially valuable at 10–80 when operating norms are still being written into the company’s DNA.)
3. Three-way communication routing. Slack for short/urgent. Long-form async for deeper discussion. Zoom for complex/urgent. Publish this as a team norm. It removes the daily “should I message this or call?” friction. (Applies at any scale; the simple three-way version works cleanest below 100. Above ~200, you typically need additional routing rules per function.)
4. Make profit sharing explicit. Inference: when considering profit share, specify eligibility, allocation and what happens in loss-making years. Buffer’s published history and allocation formula provide a concrete reference, not a universal percentage or headcount threshold. (Source)
5. “Give flexibility to get flexibility.” Name the implicit contract explicitly. Remote flexibility is bilateral — if you want schedule autonomy, you occasionally take an early or late call for a colleague. Making this explicit prevents one-sided exploitation. (Applies at any scale; load-bearing at 10–75 where leadership is still in the room and the bilateral norm is legible. Above 100 it needs explicit policy, not just a stated principle.)

Where This Model Breaks

• At 200+ people. “Use judgment” communication norms work at 75. They break at scale because judgment varies widely across 200 people. Explicit rules become necessary.
• When profitability disappears. Buffer’s published history explicitly records no profit share in 2022 or 2023, both loss-making years. (Source) Inference: teams using profit share should explain this dependency before distributions become an expectation.
• When salary benchmarks lag market options. Inference: a published salary system still needs maintenance as roles and labor markets change. A location factor may create retention pressure where employees have alternatives at higher compensation; this is a potential risk, not a measured Buffer outcome.
• When sync availability becomes expectation. The “give flexibility to get flexibility” norm requires trust. If a manager starts scheduling mandatory early calls regularly without reciprocating flexibility, the norm collapses — and people in incompatible time zones bear the cost.

Related Practices

• Async Communication — Buffer’s honest documentation of when async fails is essential reading
• Cross-Time-Zone Collaboration — the “give flexibility to get flexibility” norm is a specific solution to this problem
• Decision Ownership — accountability and initiative in a distributed team

Related Frameworks

• Sync vs Async Decision Matrix — Buffer’s three-way routing framework is a direct input to this

Sources

1. Working at Buffer: https://buffer.com/resources/working-at-buffer/
2. Buffer is Remote but not Async-First: https://buffer.com/resources/remote-not-async-first/
3. Buffer Compensation Philosophy: https://buffer.com/resources/compensation-philosophy/
4. Reflecting on a Decade of Transparent Salaries: https://buffer.com/resources/salary-system/
5. Our 7th Profit Share — $377,005 Distributed: https://buffer.com/resources/7th-profit-share/
6. Buffer Shareholder Updates (primary source for monthly revenue / active-user / profitability data): https://buffer.com/shareholders
7. About Buffer (primary source for team count and team distribution): https://buffer.com/about
8. Join the Buffer Journey (current workweek and benefits): https://buffer.com/journey
9. February 2025 shareholder update (Linear adoption): https://buffer.com/shareholders/february-2025
10. December 2025 shareholder update (dated operating results): https://buffer.com/shareholders/december-2025
11. The Buffer Team Shipped 57 New Internal Tools in 5 Days (August 28, 2026): https://buffer.com/resources/build-week-2026/
12. We Send A Q&A Doc To Candidates Before We Meet Them (July 28, 2026): https://buffer.com/resources/buffer-q-a-doc/
13. We Added a $250 AI Tools Stipend for the Buffer Team (February 28, 2025): https://buffer.com/resources/ai-tools-stipend/

Inferences

• Buffer’s “use judgment” communication approach works precisely because the team is small and high-trust. The three-tool routing framework (Slack/Threads/Zoom) is simple enough that shared judgment can converge. At 300 people, judgment diverges — you get 300 different interpretations of “when is it complex enough to justify a Zoom call?” — and the framework breaks down unless accompanied by much more explicit norms.
• Salary transparency may reduce uncertainty about how pay is calculated, but public data does not establish that pay anxiety or disagreements disappear.
• Buffer’s recovery to profitability is a useful case for examining sustainable growth. Its financial history alone does not isolate team size or a particular value as the cause of that recovery.
• The AI stipend and Build Week widen who can ship an internal tool. The same recap shows that wider building immediately creates review work: some tools were paused for security or access. Event output does not establish that those tools stayed in use.

Work with Alex

If you are trying to design a communication system that is honest about what async can and cannot do for your team, Alex helps leadership teams build operating systems that match their actual context — not the idealized version.