The case for continuous feedback is obvious to most People professionals. The challenge is making it obvious to a CFO or CEO who sees it as an HR initiative rather than a business decision. Here's how to make the argument in terms that land.
Start with the cost of what's already happening
Turnover is expensive, and the cost is rarely calculated. A useful starting point is replacement cost: typically estimated at 20% of annual salary depending on the role, when you factor in recruiting, onboarding, lost productivity, and the time of whoever is doing the hiring. For a team of 50 people with 20% annual turnover, that's 10 departures a year. At 20% of an average professional services salary in Australia (AU$119,000.00 as at July 2026), you're looking at $238,000 in churn costs before you've addressed what those departures do to team morale and institutional knowledge.
Leadership tends to know this abstractly. The argument is most effective when you make it specific to your organisation: take your actual headcount, your actual average salary, your actual turnover rate, and calculate what that's costing. Then frame the feedback programme as early-warning infrastructure that can reduce that number.
Make the data lag visible
Most leadership teams don't realise how out-of-date their people data is. Walk through the timeline explicitly: your last survey went out in month X, results were reviewed in month Y, action plans were approved in month Z. You are currently making people decisions based on data that is N months old. In that window, here's what happened: [list of real events].
This reframes the question from "should we survey more?" to "would you run any other part of the business on data this old?" The answer, applied to sales or operations, would be obviously no. The same logic applies to your people.
Frame it as leading indicator infrastructure, not a listening programme
"Listening programme" sounds like an HR spend. "Early warning system for retention risk" sounds like a business investment. The framing matters. What you're proposing is a mechanism to see sentiment shifts before they become resignations, to identify manager problems before they become team problems, and to catch the downstream effects of major changes while there's still time to respond.
If your organisation has recently lost someone important and that departure was a surprise, use it. Not to assign blame, but to make the point: this signal was available. You didn't have a channel to see it. You're proposing to build one.
Address the objections before they're raised
Survey fatigue is the most common objection. The response: fatigue comes from asking without responding, not from asking frequently. A weekly check-in that produces a visible, acted-on summary doesn't exhaust people — it builds trust. What exhausts people is completing a survey and hearing nothing back.
The second objection is cost. Relay costs $99/month. One retained employee who would otherwise have left pays for years of it. That's the comparison.