Finance is planning 2027 around HR, not with it

Employee incentive and reward programs (HR) • Reading time: 11 minutes

You sit across from the finance committee. The incentive program line is crossed out in red on the screen, and the director has given you twenty minutes to explain why cutting it will cost the company more than it saves. You know the engagement numbers. You know the teams whose recognition depends on this program. The committee sees a flat revenue line and a bloated cost base, and the number in front of them looks small enough to remove without a second thought.

That is the 2027 budget cycle, and the incentive program sits in an unusual position inside it. It is small enough on the budget sheet to be treated as discretionary, and large enough in its outcomes that a cut shows up as attrition six months later. The defense that works in that room is not sentiment. It is the specific arithmetic the committee is already using to cut everything else.

Finance is planning 2027 around HR, not with it

The pressure is structural, not anecdotal. The reference point for the current cycle is the latest Gartner function-level budget benchmark in the public record: a survey of more than 300 CFOs and finance leaders, fielded in October 2025 and reported by the Journal of Accountancy, found that HR spending was forecast to slow the most among the nine corporate functions it covered. Only 29% of the leaders projected an increase of 4% or more in HR spending, while 22% projected a decrease of 4% or more. Those are the lowest increase and the highest decrease percentages of any function in the survey, and the pattern it captured is the one finance is carrying into the 2027 planning cycle.

For the program manager, the implication is that the incentive line is booked inside the function finance expects to squeeze. When the director asks for a number, the starting assumption in the room is that your line goes down, and the rest of the deck will be used to justify that assumption.

Two things follow. A defense built on tenure, in the form of "we have run this program for years," will not land in a room making function-level decisions. And the ask has to be framed in the currency the committee is already using: cost risk, retention outcomes, and auditability. If the document reads like a plea, it will be treated like one.

A budget that increases is not a budget that grows

Even when the number on the budget sheet goes up, the program may not. The Incentive Research Foundation's 2024 Trends Report reported that 76% of respondents in the incentive industry cited rising costs and inflation as a challenge, and the report lands a point that should change how you read your own line item: "Budgets are often increased to maintain a program, and do not indicate incentive program growth."

In practice, the nominal increase is consumed before it reaches the program. Reward unit prices rise. Exchange rates move against programs that buy in multiple currencies. Vendor minimums go up. The cost per covered employee drifts upward even when the face value of the reward stays the same. A five percent increase can buy a smaller program than last year's.

The distinction changes the ask. If you request "the same program with a 4% increase," you are asking for a smaller program with different wording. The defensible position is to separate two numbers explicitly: what it costs to maintain the program at this year's scope and prices, and what it costs to grow it. The maintenance number should be built from last year's actuals, the published price increases on your reward catalog, and the currency movement you actually experienced. Finance can evaluate those two numbers as two lines, and it is harder to cut a maintenance line that stands on its own than a blended request.

The same problem, from the other side of the table

The finance director's version of this story is not malice. It is constraint. The same Gartner data shows a committee directing its scarce increases toward the functions it expects to drive revenue, and HR is not on that list for the 2027 cycle. The CHRO sees the same pressure from above and has to decide which parts of the function carry the strategic load, and recognition and incentive programs, unless tied to a named business risk, usually do not.

The CHRO's own case gets thinner in a cycle like this. When the function-level ask is flat, every program inside the function has to earn its place against the others, and a rewards program that cannot point to a business outcome loses that internal comparison before it ever reaches the committee. The program manager who understands this does not fight the CHRO. The program manager hands the CHRO the numbers that make the program worth keeping at the function level, and the two of them walk into the room with one document instead of two competing versions of the same ask.

That is why the program manager who walks in with a sentiment argument loses before speaking, and why the argument that survives is the one that reframes the program as a control on a cost the company already recognizes: attrition. The program stops being an HR line item and becomes an instrument in the committee's own cost model.

What an underfunded program actually costs

The counter-argument to a cut is measurable, and the measurement sits on the attrition side, not the rewards side. Gallup's longitudinal research, conducted with Workhuman and tracking the career paths of nearly 3,500 US employees from 2022 to 2024, found that employees who received high-quality recognition were 45% less likely to have turned over after two years (Gallup).

That figure does the heavy lifting in the defense. An incentive program is one of the few levers a program manager controls that the attrition data connects to turnover, and the committee already knows what the outcome you are trying to prevent costs. Gallup's study carries model estimates of replacement costs: roughly 200% of salary for leaders and managers, around 80% for technical roles, and about 40% for frontline roles. These are model estimates, not measured figures, and a budget document should present them as such. Even so, they are the right order of magnitude for the comparison.

Work the example. A program that covers 50 employees at a cost of 25,000 dollars a year is 500 dollars per covered head. If one avoided departure in a manager-level role saves on the order of 100,000 dollars or more on the model estimate, one prevented departure a year covers the program two hundred times over. The honest version of the math is more modest than that, and it still holds: the program's cost per head is not the number to defend. The avoided cost is.

The arithmetic only survives scrutiny if the numbers are real, which is what the document should show: the program's cost per covered head, the historical attrition rate of that population, and the replacement-cost estimate, labeled as an estimate. A committee that catches one inflated number discounts the other two, and a defense that starts credible and ends inflated is worth less than no document at all.

The three numbers the committee will ask for anyway

The committee will not ask for a report. It will ask for three numbers, and the difference between a cut and a defense is often whether you can say them without reaching for the deck.

The first is the program's actual cost per covered employee last year. Not the budget: the actuals. The budget carries the reserve, the unused allocation, the rounded-up figures, and any one of those invites the question "so what does it actually cost?" once you have finished talking.

The second is the cost increase you expect to absorb this year: the published price increases on the reward catalog, the currency movement on rewards you buy in several currencies, and the vendor minimums. This is the number that separates maintenance from growth, and it is the number that makes a flat or modest budget look like the correct decision rather than a concession.

The third is the attrition rate of the population the program covers, compared with the company-wide rate for the same period. If the two are the same, that is not your argument, and you should say so in the document. If they differ, it is your first number, because it is the only one in the room that the committee cannot generate from its own systems without doing the same join you did.

A document built on these three numbers takes about a week to assemble, and it is the document that ends the debate. A document built on enthusiasm takes an afternoon, and it loses the same argument it lost last year.

The case that survives a budget review is the one with the least ambiguity

The programs that survive the cycle are not the ones with the most advocacy. They are the ones with the least ambiguity. Four elements do the work.

Start from the cost of inaction. The first number in the document should be the cost of the attrition the program prevents, not the price of the program. The program is then presented as a hedge against a larger risk rather than an add-on, and the committee is asked to cut a hedge rather than a perk.

Separate maintenance from growth. Show two numbers: the flat cost of running this year's scope at this year's prices, and the delta required for any expansion. Ask the committee to decide on the delta, not on the whole line.

Instrument before you ask. A budget request made without measured outcomes forces the committee to take your word for the value. If the program has not tracked participation, redemption, or recognition frequency this year, the first ask should include the cost of measuring. It is a smaller number than a program budget, and it buys the data that makes next year's ask self-defending.

Name the risk explicitly. The document should state what happens if the budget is cut: which population's attrition risk rises, and what that is estimated to cost. A finance committee can live with a named risk that has a price on it. It will cut what it cannot see.

On presentation: one page, the risk number first, the ask stated in the first sentence, and no feature list or screenshots of past awards. The document should be the kind of thing the director can forward to the CFO without editing.

The twenty-minute version of the defense

If the director gives you the room, the structure that works is five beats, and the clock is part of the design.

Minute one is the risk. State the cost of the attrition the program prevents, the population it covers, and the replacement estimate, labeled as an estimate. Do not open with the program's price, because a price opens the negotiation and a risk opens the decision.

Minutes two to five are the fiscal context. HR is the function finance expects to squeeze most in the 2027 cycle, so the ask is framed as a choice about which risk to keep, not about which line to save. This concedes the director's constraint instead of arguing against it, which is the single fastest way to get an advocate in the room.

Minutes five to ten are the maintenance number. The cost of running this year's scope at this year's prices, itemized from actuals. This is the part the committee may still cut, and it is the part the committee should be allowed to cut, because the named risk travels with it.

Minutes ten to fifteen are the growth number. The delta, and the outcome it buys. If the program has been instrumented, the outcome is a number you produced. If it has not, say what you will measure in exchange for the delta, and put the measurement date in the document.

The final five minutes are the decision. The committee chooses between the status quo with a named attrition risk, and the program at maintenance cost. The cut sits on the table as an option, which is exactly what makes the document defensible: you are not asking them to keep the program, you are asking them to decide which cost they carry.

When the cut is the right answer

There are cases where the correct answer in the room is yes, cut it, and the program manager who insists on defending a broken program is the one who loses the budget next year.

A program with no measurement after two or more budget cycles: if you cannot say what it does, the defensible move is a small instrumented pilot, not a full ask. A one-off event dressed as a program: a single gala or event is an event budget, not a program, and it should be funded as such. Recognition that duplicates other channels: if the same behaviors are already rewarded through promotion, spot bonuses, and a peer recognition app, the line is redundant and the committee is right to flag it. And an audience that has changed: a program designed for a fully on-site workforce, applied to a hybrid or distributed one, has lost its delivery logic, and a rewrite is cheaper than a defense.

In these cases the winning position is a rebuild with a smaller ask, not a defense of the status quo. Defending a program you cannot measure costs more credibility than a cut, and the committee remembers.

Complexity has a line-item cost too

A global incentive program carries a second cost that rarely appears in the budget document: the cost of running it. Manual approvals, regional purchasing, currency spreads, reconciliation, and the hours between the moment of recognition and the moment an employee receives anything. CY.SEND operates at that delivery layer for global programs: one rail for digital gift cards, mobile top-ups and incentive fulfillment across markets, with the reporting a finance committee can audit.

The honest qualification is that no delivery rail changes the value case. If the program itself does not produce measurable engagement, better delivery only gets employees to a reward faster that was never going to move them. Technology should absorb the complexity of running a global program rather than transferring it to the manager who owns the budget.

If the numbers in your program are unclear to you, CY.SEND can walk through the arithmetic with you before the budget room does.

Sources