Buffer

Pay calculation is disclosed through role, level and geographic band.

How it works

A salary system based on role, level, market data and geographic bands is published alongside actual salaries.

Why it is used

Reduces negotiation asymmetry and makes decisions open to scrutiny.

Trade-off

Reduces flexibility for new roles and exceptions and becomes harder to keep understandable.

Best fit

Organizations ready to use transparency as real governance.

Written work enables participation independent of time zone.

How it works

Written updates and flexible work enable participation independent of time zone.

Why it is used

Prioritizes contribution over location and time visibility.

Trade-off

Requires additional rituals for connection and rapid coordination.

Best fit

Global remote teams.

Regular manager conversations support employee experience and growth.

How it works

Regular 1:1s create dedicated space for employee experience, growth and blockers.

Why it is used

Surfaces weak signals early in remote work.

Trade-off

Depends on manager skill and can degrade into status reporting.

Best fit

Teams investing in direct relationships and growth coaching.

Policies are treated as experiments and learnings are shared publicly.

How it works

Work-week, pay and culture policies are run as experiments with results and failures shared openly.

Why it is used

Lets policy evolve through evidence and feedback.

Trade-off

Continuous change can create uncertainty and experiment fatigue.

Best fit

Small, high-trust organizations accustomed to feedback.

Buffer reports distributing a $377,005 pool, 15% of 2025 net profit, to 75 teammates. The formula allocates 40% equally, 40% by salary and 20% by tenure. Payments were zero in the loss years 2022 and 2023.

How it works

The annual net-result pool is split into equal, salary-proportional and tenure-proportional components.

Why it is used

Rewards a shared result while recognizing role scope and long-term tenure.

Trade-off

A loss can mean no payout; the salary component carries existing pay gaps into the award. The source’s stated average conflicts with pool divided by headcount and is not repeated.

Best fit

Teams measuring profitability openly and favoring shared results over individual targets.

In its company-wide Build Week, Buffer lets 72 people set aside regular work for a week to build internal tools. Earlier years paired people into teams on pre-selected projects; in the third edition everyone chose their own project, built with AI, and drew on experts across the company when needed. The week produced 112 completed projects, 1,083 merged pull requests across 26 repositories, and six people merging their first pull request.

How it works

A time-boxed week in which each person chooses and directs their own project, AI is the default tool, and experts across the company are available on request. No formal approval process is described; some work is deliberately held back over security or access questions.

Why it is used

To let people follow their own learning paths and try unfamiliar protocols, languages and platforms, with individual ownership instead of assigned team projects.

Trade-off

Some projects were paused over security or access questions, some were built but not deployed, and one was only written up to avoid pulling people from their own Build Week work. The post does not measure longer-term impact; the figures are output counts.

Best fit

Small, trust-based companies where engineering skill is widespread and where tool and data security boundaries can be clarified quickly.