I was sitting across from a CFO in late 2025 when he asked me to ‘justify the extra budget line for remote-work stipends’. I had spent the previous quarter designing a hybrid model my HR lead called a retention investment. He called it a fringe benefit. Between those two frames sat a gap of about four hundred thousand dollars a year, and I had no model that could close it in one sitting.
That gap is why I keep writing about this. As an organizational psychologist who led HR at a fully distributed company, I have seen the same pattern repeat itself on every team that tried to grow past forty people. The leadership team treats flexibility as a cost line. The engineering lead treats it as the reason good people stay. Neither of them is wrong, and both of them are stuck. The missing layer is a price.
This is the retention-asset model I use now. It is not a survey result, and it is not a slide about culture. It is a way of attaching a dollar figure to a person you are about to lose, then asking what it costs to hold onto them by adjusting their schedule instead of by adjusting their comp band.
Why the 2026 layoff wave changed the argument
The May 2026 Intuit cuts are the reason this conversation finally matters. Intuit announced on May 20, 2026 a reduction of about 3,000 jobs, roughly 17% of the workforce, and reported the cuts landed disproportionately on coordination roles: project management, business operations, and middle management.
That detail is not incidental. When coordination work disappears from the org chart, the surviving people inherit the coordination work. My client teams have told me the same thing in one-on-ones: they are not leaving because of the pay, they are leaving because they are being asked to be three people.
In 2026, where positions are being replaced by functions, flexibility becomes the cheapest retention lever left. Salary floors have risen, so a pay bump to hold a person costs more and more. Time, on the other hand, is still negotiable.
What the layoff wave is doing to coordination
- It is collapsing the layers that used to absorb slack.
- It is asking coordinators to do the work of coordinators they no longer have.
- It is making a flexible schedule the difference between staying and leaving.
The retention question is no longer whether you can pay someone more. It is whether you can schedule around someone who is running three roles at once.
The Gallup data most teams read wrong
I keep a single chart on my wall. Gallup’s State of the Global Workplace 2026 report, drawn from 263,810 employees, says global engagement is 20%, with 64% not engaged and 16% actively disengaged. That is the number leadership remembers.
The number they never pull out of the report is the one by work location. Gallup measures engagement at 30% for exclusively remote workers, 25% for hybrid, 24% for on-site but remote-capable, and 17% for on-site non-remote-capable. Fully remote is the most engaged group in the sample.
When the CFO asks whether remote work loosens the team, the answer is a number, not an opinion.
That single line of data is what shuts down the cultural argument in ten seconds flat. The remaining argument, the one that matters to the board, is financial.
How I use the location breakdown
- As the rebuttal to ‘remote teams drift’.
- As the setup for the turnover-cost model.
- As the reason to write the flexibility clause in the first place.
Do not lead with the engagement figure. Lead with the cost model, then use Gallup to answer the objection that comes back.
The full replacement cost, built from parts
A lost hire is not the salary on the payslip. It is four pieces stacked together, and only one of them is a number finance already has.
The four pieces are: recruiting spend, onboarding effort, ramp time, and the productivity gap while the seat sits empty.
Recruiting spend
Include agency fees, platform subscription months, and every manager hour spent sourcing, screening, interviewing, and closing. Most organizations count the fee and skip the hours. The hours are usually the larger number.
Onboarding effort and ramp time
Onboarding is not a checklist; it is the manager time and peer time it costs to bring a new person up to independent output. I use nine weeks as a working baseline, but that is an assumption, not a benchmark.
The productivity gap
This is the seat-empty portion. It runs from resignation to first fully productive day, and it includes the work that quietly moves to everyone else during that window.
A lost hire has one number. Build it once, use it for every conversation.
Once the number is in front of you, the retention argument stops being abstract. You are not paying someone to work from home; you are buying one more year of their contribution at a known fraction of what a replacement would cost.
Three scenarios, one forecast
I ask every team to model three twelve-month scenarios. This is where most ‘flexibility debates’ die, because a forecast beats an argument.
| Scenario | Assumed annual turnover | Replacement cost multiplier | Twelve-month cost index |
|---|---|---|---|
| All on-site | 22% | 1.6x annual salary | 100 |
| Hybrid | 14% | 1.6x annual salary | 64 |
| Fully remote | 9% | 1.6x annual salary | 41 |
These are illustrative assumptions, not sourced figures. The purpose is to show the shape of the comparison: turnover rate moves the index more than any other variable in the model. Swap in your own attrition data, keep the multiplier honest, and re-run the three rows.
Reading the index
- 100 is the baseline you already carry today.
- 64 is what the same team would cost if you offered flexibility.
- 41 is what the team would cost if the arrangement fully supported the top-performers you cannot afford to lose.
The gap between 100 and 64 is not a savings line, it is a retention line.
Writing flexibility as a clause
If you cannot name who gets it, when they get it, and what counts as a boundary, you do not have a policy. You have a habit. Habits do not survive a CEO change.
I use a four-column clause. Every team gets the same shape, so the flexibility stays defensible when someone new joins the leadership team.
| Who | Cadence | Boundary | Review date |
|---|---|---|---|
| IC roles, engineering and design | Three days remote per week | Same-hour overlap with the team hub | Every six months |
| Manager roles | Two days remote per week | In-office on team rituals and hiring days | Every six months |
| Customer-facing roles | One day remote per week | Client overlap window respected | Every three months |
| New hires, first quarter | Zero remote days | First ninety days on-site for onboarding | At ninety-day mark |
What makes a clause survive
- It names a role, not a person.
- It names a cadence, not a feeling.
- It names a boundary someone can enforce without escalating.
- It names a review date so the arrangement does not fossilize.
Unwritten generosity is not an asset. Written generosity is.
The three-page board narrative
I have been rejected on flexibility proposals and approved on flexibility proposals. The difference is never the ask; it is the frame. When I write this for a board, it is three pages and it never uses the word culture.
Page one: the cost of a lost hire
- Full replacement cost, broken into the four parts.
- Applied to your current annual attrition rate.
- Stated as a single number per team.
Page two: the three-scenario forecast
- The all-on-site baseline.
- The hybrid cost index.
- The fully-remote cost index.
- The delta between the two, in dollars.
Page three: the clause you are asking to approve
- The four-column clause, unchanged.
- The review cadence.
- The engagement data from Gallup as the rebuttal for the objection you already know they will raise.
The board does not vote on the culture of a team. It votes on the cost of a forecast.
The board does not care that a person is happier at home. The board cares that the forecast for next year is cheaper than the forecast for next year if you do nothing.
What actually moved the decision
In my experience, the CFO who resisted in 2025 approved in 2026 without a single sentence about quality of life. He approved because the replacement cost was in front of him, the three-scenario forecast was a page, and the clause was written so the approval was a checkbox rather than a philosophy.
The Gallup data did its job as a rebuttal. The turnover model did its job as the ask. The Intuit cuts did their job as context. The three pieces together stopped flexibility from being a perk and made it a line on the balance sheet.
That is what retention-asset pricing actually is. Not a survey of employees, not a deck of culture slides, and not a promise to be more flexible. It is a model that says this schedule is worth a number, and the number is the reason to write it down.