Introducing Buffer’s Family Support Fund
Director of People @ Buffer
One of the most conversation-provoking perks we’ve ever launched at Buffer is our Dependents Grant.
This benefit provides a $3,000 USD stipend to teammates for each person who depends on their salary (including spouses, partners, children, grandparents, aunts, uncles, etc.).
When it first launched in 2016, the grant was designed to show support for Buffer teammates as they navigated various life situations.
“We we want to help our teammates feel taken care of if they happen to have children or others in their family who rely on their income,” we said back then.
We’ve gotten a lot of comments, feedback and thoughts about this perk over the years, both within the team and outside it. And as the team grows and evolves, we want to be fully aware of the financial and cultural impact of all of our benefits and perks.
That’s why we recently decided to take a deep dive into the Dependents Grant to review the intent of the grant, how it has evolved over time, how it has/will scale, and team-wide perception of it today.
Read on for the full story, our process and methodology, and our conclusions and changes as a result of this review.
The Dependents Grant by the numbers
First off, we wanted to know the data behind the grant.
As of October, 2019, when we began the review, 44 teammates claimed 99 dependents total.
- 58 in the US → $174,000
- 11 in Canada → $33,000
- 4 in the UK → $12,000
- 26 in other countries → $78,000
That means we spent $297,000 in 2019 on the Dependents Grant.
Over time, we’ve seen a slight uptick in use of this benefit:
- The average in 2018 was 1.04 grants per teammate across the whole company
- In 2019, the average was is 1.1123 per teammate
- In 2020, we project an increase to 1.2 per teammate
As part of our overall benefits and compensation package, the Dependents Grant falls in the upper middle when it comes to costs. Here’s a look at it in context of all our benefits and compensation and their budgets for 2019:
- Salaries: $11.6 million
- Retreats + Onsites: $700,000
- Healthcare: $450,000
- Dependents Grant: $300,000
- Retirement matching: $180,000 (US + Canada only right now)
- Growth Mindset Fund: $80,000
- Coworking Spaces + Coffee Shop Coworking: $72,000
- Accounting fees: (contractors only; $50,000)
- Home office + personal equipment: $40,000
- Lawyer fees (for immigration assistance): $35,000
- Free Kindle and physical books: $30,000
At this level, the grant is sustainable, though if it were to grow much larger in scale it might become difficult to keep it up.
Interviewing the team
Next we went to the team to conduct dozens of interviews in order to understand the overall perception of this benefit across the team. It felt important to take care with our questions: How many people would say they didn’t want more money at the end of the day?
How could we ask and learn teammates’ true feelings about this particular benefit? Everything stemmed from understanding the true “problem” we were trying to solve: Does the Dependents Grant accomplish our goal of providing a comfortable wage and work environment where teammates don’t have to worry about money and are able to do their very best work at Buffer?
We needed to know: Did teammates feel distracted by finances? Did teammates feel Buffer was equitable and inclusive in our benefits philosophy?
Having established these as the key questions, we broadened our questions and approach to a more holistic benefits interview, with a few questions near the end specifically about the Dependents Grant.
Some of the questions I asked:
- Which of our benefits do you find the most essential in your life?
- Which of our benefits do you find most essential to you feeling productive and able to focus on work?
- What worries or concerns fill your mind most often?
- If you could wave a magic wand, what else would you have Buffer provide to our teammates?
- If you could have more of any one of these, which would it be: time, money, influence?
Overall, I spoke with 24 teammates, 13 of whom receive the grant currently, 11 who did not (four had received it in the past).
The overwhelmingly conclusion from these interviews: The Dependents Grant did meet our goal of providing additional support for teammates to feel they can do their very best work at Buffer.
Teammates shared that the amount, though not huge, was a significant way of taking the edge off costs relating to supporting dependents.
“When I think how much it is, $3k per year, it’s more of a message of, ‘Hey we’re supporting you through this life.’ It’s not about actually monetary support.”
Many teammates shared it wasn’t about the amount, but the statement the Dependents Grant made to the team.
“There’s definitely a symbolic level of support and practical level of support in it too.”
Amongst single-income households, we learned that the grant has been part of allowing for some dual-income households to move down to single-income, creating a happier and better balanced Buffer teammate experience.
Most teammates who don’t use the Dependents Grant (and might never do so) still view the Dependents Grant positively.
A few teammates did feel it would be better to allocate the money to other things within Buffer, such as raises. But several teammates mentioned that it was important to create a positive example in the tech industry, which can be less-than-friendly toward families and work-life balance.
From this phase, we learned that the team’s feeling toward the benefit was overall positive, and their perception of its meaning was in line with our intention.
Other distribution approaches we explored
The Dependents Grant in its existing format used a simple model of distributing the grant over the course of the year, listed as “additional earnings” on a teammate’s paycheck.
While this format did meet the goal of supporting teammates, we still wondered: Was there possibly a better, different way to utilize Buffer’s dollars?
For full-time employees (those in US, UK, Canada, and more countries as we incorporate), we currently cover teammates’ healthcare premiums at 100%, and 50% of dependents’.
What if instead of the stipend, we used those funds to cover 100% of dependents’ healthcare (while keeping the stipend for our international contractors)?
We spent many, many weeks in financial projections and queries to look at the costs and benefits of this approach.
The benefits of this approach:
- More clearly spoke to the intent of the grant (it’s not about providing more money to people with more kids)
- More stability for teammates’ incomes and budget
- An immediate $60,000 savings (subject to change year-to-year based on healthcare premiums)
- Paying 100% of dependents’ healthcare premiums is fairly rare and could have been a recruitment advantage
The negatives:
- Less of a “perk” for our UK and Canadian-based teammates, who have fairly low insurance premiums
- Would have required a lot more paperwork
- Would have been a predominantly US-centric benefit
We also considered childcare and in-home elder care reimbursement, but there are many hurdles to this with a global, remote workforce. (If we were all located in one city, the dollars from this might be funneled into a really amazing childcare center at the office!)
In the end, we opted not to go down any of these routes, but it was a very helpful exercise to consider each of them.
Introducing the Family Support Fund
Although this was a fairly lengthy and involved process, it answered some important questions for Buffer.
We learned that the grant is sustainable. That it works and is perceived as intended. And that the funds create a deep sense of goodwill within our team.
So after this long journey, we ended up keeping the grant much as it has always stood, with a few new changes – including the name.
“Dependent” as a term always felt a bit fuzzy and is often used synonymously with children, though a full 1/3 of the total number of dependents claimed aren’t children.
Thus the newly-renamed “Family Support Fund.”
Another tweak is a limit of 4 dependents per teammate and a new, annual application process. The yearly application will help us keep a better accounting of the benefit and also help us reinforce the meaning of this fund.
As before, the grant remains a $3,000 per dependent per year sum that is pro-rated and paid bi-monthly as “additional earnings” on a teammate’s paycheck.
Over to You
Though this intense deep dive yielded us with a nearly identical program as when we started, this was nonetheless an immensely helpful exercise to validate the intent, sustainability and parameters of this cornerstone benefit.
If nothing else, I hope it will illustrate just how much we think about and care about every benefit we roll out to the Buffer team, and our drive to always keep evolving and improving.
How do you think companies can support working families (of all shapes and sizes?) What about our process stands out to you?
Try Buffer for free
140,000+ small businesses like yours use Buffer to build their brand on social media every month
Get started nowRelated Articles
Nine years ago, we decided to launch a new free product alongside Buffer. We called it Pablo, and it was a huge hit in our community. Within just seven months of its launch, half a million photos were created using Pablo. Similarly, we had the initial ideas for Stories Creator and Remix many years ago now. All three of these tools have been an important part of Buffer’s story. They’ve taught us lessons and helped us connect with a wider audience. In Pablo’s case, the idea for this tool happene
If you use Buffer, you might have experienced us having more downtime than usual recently. We want to start with an apology for not sharing more transparently along the way what’s been happening. We’ve been caught up in the work and haven’t invested enough in communicating with our community, and we’re so sorry about this misstep. We know some of our customers have had a frustrating time using Buffer recently and we need to do better by you. This past August and September were the months we’ve
As part of our commitment to transparency and building in public, Buffer engineer Joe Birch shares how we’re doing this for our own GraphQL API via the use of GitHub Actions.