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

Snapshot

Buffer is the social media management tool. Their public shareholder updates report on the order of ~198,000 monthly active users and ~70,000 paying customers in late-2025 reporting periods. (Source) The “190,000+ creators, small businesses, and marketers” line that appears in their marketing copy refers to the active-user base, not paid accounts. About 75 employees as of early 2026. (Source) Joel Gascoigne announced the decision to go fully remote in 2012; Buffer’s last physical office closed in late 2015. No office, no headquarters since.

Buffer’s standout contributions to remote work knowledge are twofold: radical financial transparency (all salaries are public, always have been) and honest operating documentation (they publish not just what they do well but where they disagreed with prevailing remote-work dogma).

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 operating model is built on flexibility over rigidity. Unlike Doist’s pure async-first stance or 37signals’ Basecamp-only rule, Buffer’s philosophy is: use judgment, communicate clearly about which tool to use and when, and give flexibility to get flexibility.

Their stated values (published on buffer.com/values):

• Default to transparency. Salaries, revenues, equity, board decks — all public.
• Act beyond your role. Ownership and initiative expected from everyone.
• Do less, do it better. Focus and quality over quantity.
• Listen first. Seek to understand before acting or responding.
• Have a bias for happiness. Not performative positivity — sustainable work that people actually enjoy.

The financial transparency is not just symbolic. It is operationally load-bearing: when salary data is public, negotiation games go away. People can see whether they are paid fairly relative to colleagues. The company is held accountable to its own compensation principles. (Source)

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)

Their 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 is a small team (~75 people) running a mature product. Their planning cadence details are not fully public, but confirmed elements include:

• Profit share tied to annual performance. 15% of net profit is distributed to all teammates annually. 2025 was their seventh profit share — $377,005 distributed across 75 teammates, average $5,095 per person, on $2.51M of net profit. (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)
• Small team dynamics. At 75 people, planning is less process-heavy than a 500-person company. The documented cadence is lightweight by necessity and choice.

Decision-Making Model

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

• Public salary formula removes compensation negotiation. Salaries are calculated via a published formula: role × cost-of-living multiplier. No negotiation. No information asymmetry. (Source)
• Co-founder Joel Gascoigne (CEO) makes major decisions and publishes reasoning publicly via shareholder letters and blog posts.
• Ownership culture. “Act beyond your role” means individuals are expected to take initiative without waiting for permission on work within their domain.

Org Structure

• ~75 employees as of early 2026. (Source)
• Traditional structure with executives, managers, and ICs — not manager-less.
• Multiple continents. Specific country breakdown not published in totality on a single page; the public salary system / about pages list teammate countries spanning USA, Canada, UK, mainland Europe, Australia, and a number of others. (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.

Tools and Stack

(Source)

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 formula. Not a one-time ritual — an ongoing operating norm that prevents the salary negotiation games that fragment team culture at growing companies.

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, not just a policy. After a decade of it, Buffer has real data on what works: it eliminates negotiation anxiety, creates trust, and makes the company accountable to its own compensation principles. (Source)
• Profit share creates aligned incentives at small scale. At 75 people, the $5,000 average profit share is meaningful enough to reinforce the “we own this together” culture. It is the financial expression of the “act beyond your role” value.
• Small team, mature product, sustainable economics. 2025 was their strongest year in years — Buffer’s 7th profit share post reports the year-end picture of ~$23.3M ARR, ~$22.5M annual revenue, and $2.51M net profit, with 15% of net profit redistributed to teammates. (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. Unlike Basecamp’s rule-based system (async by default, async mechanisms specified) or Doist’s no-meetings stance, Buffer’s “use judgment” approach means every team member must constantly assess which communication mode to use. This works well in a high-trust small team; it scales less cleanly.

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 2,000-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 a salary formula. You don’t have to make salaries public externally — but making the formula and logic transparent internally eliminates the negotiation games that create resentment in small teams. Buffer’s formula (role × cost-of-living) is simple enough to copy directly. (Cleanest at 10–100; harder above 200, where market-rate variance for senior talent strains formula-based comp.)
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. Profit share as culture infrastructure. If you are profitable and have a small team, distributing 10–15% of net profit annually sends a clearer message about ownership than any all-hands speech. (Applies at 10–100 cleanly; above 200, equity dilution and pay-band design typically displace flat profit-share as the primary ownership signal.)
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 had two years without profit share (2022–2023). The cultural hit was real — profit share is not just a financial bonus; it is a signal about collective success. Extended unprofitability decouples the team from the ownership culture.
• When the salary formula becomes an anchor. A cost-of-living multiplier formula works for current hires. It can break for retaining senior talent in low-cost-of-living regions who have market options at much higher compensation.
• 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 — “act beyond your role” is the ownership principle in practice

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

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.
• The decade-long salary transparency experiment has produced something more valuable than the salary data itself: it has made compensation a non-negotiation domain. Buffer team members do not waste energy on pay anxiety or comparison games because the data is visible. The psychological overhead freed up is significant and undervalued.
• Buffer’s strongest years coincide with relatively stable small team size. The company discovered empirically that growth itself was a risk to the operating model — the years of trying to scale faster disrupted the model that made them sustainable. “Do less, do it better” is not just a value; it is a hard-won operational conclusion.

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.