Skip to content
THE SMALL BUSINESS EDITIONTools. Decisions. Lessons.

The Useful Shift

HomeGuidesCase studiesTopicsAbout
Business Case Study

Buffer’s Open Salaries: Publishing Rules, Then Revising the Formula

Buffer’s historical salary disclosures illustrate the difference between visible rules and understandable decisions, while showing the limits of company-reported benefits for smaller businesses.

By Jayadev Paleri
September 29, 2026

Buffer describes publishing its salary policy and revising it four years later. The supplied excerpts do not establish publication dates, so this case uses that relative timeline rather than assigning calendar years. Both accounts flag subsequent updates; this is historical policy design, not current policy or salary advice. [1] [2]

Situation and challenge

Buffer’s initial account presents salary disclosure as an expression of its commitment to openness. The company linked transparency with trust and sought external feedback. It also treated its calculation method as revisable, describing career progression as a reason for an earlier adjustment. [1]

In the later account, Buffer reports difficulty maintaining location-specific benchmarks and explaining pay decisions. It says complexity encouraged subjective choices that departed from the formula’s purpose. [2]

What the organisation changed

Buffer initially published its calculation method and individual salaries. Inputs included job category, seniority, experience, location and a salary-versus-equity choice. No individual pay figures are reproduced here. [1]

For the later revision, Buffer describes a shared San Francisco benchmark, three geographic bands, role multipliers and experience factors. It reports protecting existing take-home pay during the transition. [2]

Reported results and limits

Buffer reports trust, accountability for fairness and reduced subjectivity as benefits. These assessments are qualitative; no quantified improvement is established. It acknowledges that geographic bands omit individual circumstances and experience assessments retain interpretation. Both sources are company accounts, not independent corroboration. [1] [2]

What smaller businesses can learn

Our analysis: Visibility and usability are separate design goals. Making a rule available answers where someone can find it, but not necessarily how they should interpret it. For a smaller business reviewing a policy, a useful question is whether someone other than its author could explain the inputs, the decision and the remaining uncertainties without relying on an unwritten understanding.

Our analysis: A calculation should not be treated as proof that judgment has disappeared. Instead, distinguish decisions governed by fixed inputs from decisions requiring interpretation. That distinction offers a way to discuss consistency without pretending every case is identical. It also separates two evaluation questions: whether the stated procedure was followed and whether the procedure itself deserves revision.

Consider whether: External disclosure, purchased benchmark data or transition protections would fit your resources and obligations. These are not a ready-made package for a smaller firm. A narrower internal documentation exercise may be more appropriate than a public compensation project. This case is a prompt to examine policy design, not a recommendation to publish personal information or adopt particular pay levels.

Takeaways to try

Suggested application: Choose a low-risk operational policy, such as purchase approvals. Write down its purpose, inputs, decision owner and permitted exceptions. List unresolved questions separately rather than hiding them inside apparently precise wording. This is a proposed exercise for readers, not an activity documented at Buffer.

Suggested application: Ask a colleague to apply the draft to hypothetical situations without coaching. Note unclear definitions and points requiring judgment. Where the procedure provides no answer, leave the case unresolved for the designated owner rather than inventing a consistent-looking result. Use the exercise to identify documentation questions, not to claim business benefits.

Suggested application: Add a version date, review owner and change log. Before changing the policy, identify affected commitments and unanswered transition questions. Assess explainability separately from broader outcomes: a clearer account of a decision does not, by itself, establish improved trust, fairness or business performance.

Sources

  1. Open Salaries at Buffer: Our Transparent Formula and All Our Salaries
  2. The Next Evolution of Transparent Salaries: Our New Remote-First Formula and Updated Salary Calculator

Independent analysis prepared with AI assistance from the linked public company accounts, checked on 2026-09-29. Company-reported outcomes are not independently verified. Takeaways are our interpretation, not claims of affiliation or first-hand research.

KEEP EXPLORING

One useful idea leads to another.

Browse all guides ↗
Previous: Build a Quote-Ready Lead Queue in Google Sheets
Next: Prepare a HubSpot Leave Handover with Tasks and a Record Snapshot
THE USEFUL SHIFT.

Software, automation and lessons from real businesses.

Browse guidesCase studiesAbout this blogHow we write

A publication by Jayadev Paleri.

Powered by CookieAdmin
Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
None
Powered by CookieAdmin