49% of CFOs Vetoed a Deal Their Own Team Already Approved in 2026. Renewals Aren't Exempt.

Most renewal forecasting runs on one quiet assumption: if the champion is happy and the budget line exists, the deal closes. CS teams chase that one relationship, get a verbal yes, mark the account green, and move on. G2's newest buyer survey says that assumption is wrong for roughly half of B2B software deals right now — not because the champion changed their mind, but because somebody above them didn't get a vote until it was too late to matter.

What G2 actually measured

G2 surveyed more than 1,000 B2B software buyers and decision-makers for its 2026 Buyer Behavior Report, plus interviews with over 50 B2B sales and marketing leaders. The headline number: 49% say a CFO reversed a deal the buying team had already approved, sometime in the past year. That's not "the deal stalled" or "procurement asked more questions." It's a deal that cleared the people actually using and championing it, then got killed by someone who wasn't in those earlier conversations at all.

The report splits that 49% in a way that points straight at the cause. Organizations that carve out a dedicated token or LLM spend budget — now 80% of orgs, per the same survey — see a CFO veto rate of 54% on approved purchases. Organizations without that budget line see 29%. Nearly double.

Why finance is suddenly in the room

This isn't CFOs becoming generally more obstructive. It's a specific new line item pulling them into reviews they used to skip. G2's data shows finance involvement in software buying decisions rose from 31% to 46% in a single year, and the proximate cause is AI spend: token and LLM usage costs are variable, hard to forecast month to month, and large enough now that finance wants a say before — not after — the commitment gets made. A flat per-seat SaaS line item is predictable and easy to rubber-stamp. A usage-based AI feature bolted onto that same subscription is exactly the kind of cost CFOs have historically clawed back budget authority over — the pricing model that's easiest to justify to a buyer up front is often the one finance scrutinizes hardest later.

The downstream effect shows up in what buyers ask for next. Among buyers who've experienced a late-stage veto, 75% still expect positive ROI within six months of eventually signing — they're not walking away from the category, they're walking away from the current deal structure. And they push hard for shorter commitments: 40% of veto survivors want contract terms under 12 months, versus 18% of everyone else. Two separate signals pointing at the same thing — a buyer who's been burned by a finance override wants less commitment and faster proof, not more negotiation on price.

Source: G2, 2026 Buyer Behavior Report. Outcome-based pricing preference is measured across all respondents year-over-year, not isolated to veto-affected buyers specifically.

Where this actually bites at renewal

G2's survey asked about approved deals broadly — new purchases and renewals both fall under "a deal the buying team already approved" — but it doesn't publish a renewal-only veto rate, so don't read this as "49% of renewals get vetoed." What it does establish is the mechanism, and the mechanism doesn't care whether the deal in question is a first purchase or a fifth-year renewal: a champion's genuine, enthusiastic approval is necessary but no longer sufficient, because there's a second decision-maker in the loop who wasn't part of the relationship that got you the approval in the first place.

That's a different failure mode than the two renewal risks we've covered elsewhere. Champion turnover is about the advocate leaving the building entirely — a clean, visible event you can monitor for with job-change alerts and bounce signals. Fiscal-year budget timing is about the decision landing on a calendar your renewal reminders never check. A CFO veto is neither. The champion is still there, still a believer, still telling you the renewal is "basically done" — and it's true, right up until someone they don't control reviews the number and says no. Your account team can do everything right with the person they have access to and still lose, because the actual approval chain runs one layer higher than the relationship they've been managing.

It also compounds with pricing structure in a specific way. A flat, all-in annual contract is the easiest thing for a CFO to flag, because the whole commitment reads as one number with no way to scope it down. A contract with a usage-based or outcome-tied component — even a modest one — gives finance a lever to narrow rather than kill, which is part of why preference for outcome-based pricing nearly doubled (11% to 23%) over the same period veto rates climbed. We've covered the mechanics of structuring that kind of pricing concession without triggering a race to the bottom in how to raise SaaS prices without spiking churn, and the same logic runs in reverse at renewal: a flexible term is often cheaper to offer than the all-or-nothing renewal you'd otherwise be defending against a veto you can't see coming.

What to actually do about it

None of this requires restructuring your whole renewal motion. It requires treating the buying committee, not the champion, as the unit you're managing.

• Ask who else reviews software spend, every renewal, not just the first sale. The same way we've argued for capturing a customer's fiscal year-end as its own CRM field in our piece on fiscal-year budget cycle churn, capture "does this account have a dedicated AI/token budget line, and who signs off on it" — it's the single strongest predictor G2 found for veto risk, and it's a direct question most champions will answer honestly.
• Keep an ROI one-pager current year-round, not assembled the week of renewal. 75% of veto-affected buyers expect proof of ROI within six months of signing. If the first time your champion sees a clean ROI summary is the renewal deck, they're walking into the finance conversation with nothing to defend you with. Our payback period calculator is a fast way to put a real number behind that claim before you need it.
• Start the renewal conversation earlier on accounts flagged as veto-exposed. We've written before that buyers who start renewal reviews 90+ days out save 49% versus waiting — on an account with a visible finance gatekeeper, that lead time matters even more, because it's the only way to get in front of the CFO's own internal review before it happens without you in the room.
• Offer a shorter term or a usage-tied component before the CFO asks for one. Veto survivors push for sub-12-month terms at more than double the baseline rate. Proposing a shorter renewal with a check-in point, instead of defending a multi-year ask you'll likely lose anyway, keeps you in the negotiation instead of out of it.

On the self-serve side, this shows up as a downgrade or seat cut initiated by someone in finance or ops who was never your actual user — a cancellation that reads, on the surface, exactly like a product complaint but has nothing to do with the product at all. That's precisely the distinction a cancellation flow needs to catch: "finance cut our software budget" and "this didn't work for us" call for completely different follow-ups, and a generic exit survey tends to file both under the same vague "too expensive" bucket. CancelFlow is built to separate the two at the moment of cancellation, so the save offer — and the account note — actually matches what happened.

Frequently asked questions

Stop losing subscribers today

One script tag. One function call. A live cancellation flow in under 10 minutes.