PayPal’s Budget Reallocation Playbook Has One Rule Finance Teams May Not Like: No Sacred Cows

The annual budget has somehow become the only corporate document that people treat as both a forecast and a property deed.

Once a department receives $4 million, it apparently owns that $4 million forever. The money may have been approved for a product customers no longer want, a marketing campaign that isn’t working, or a strategic initiative whose original assumptions have quietly left the building.

Doesn’t matter. It’s in the budget.

Try moving $500,000 of it to something producing a better return and suddenly Finance has started a constitutional crisis.

I’ve always found this fascinating. We’ll spend months building a plan based on what we believe will happen. Then, when reality provides new information, we behave as though updating the decision would be a personal insult to the spreadsheet.

That’s why a recent piece by Prince Oppong, Senior Director of Strategic Finance at PayPal, caught my attention. In his October 8, 2026 article for FP&A Trends, he argues that organizations need to agree in advance that no investment is exempt from review. He calls the principle “no sacred cows.”

An August interview with the Association for Financial Professionals adds an important point: this only works when the CEO and CFO back the process.

I agree with the principle. But I think there’s a harder question underneath it: how do we make reallocating money feel like a normal management decision instead of an accusation that someone has failed?

Because identifying an underperforming initiative is usually not the difficult part. Asking its executive sponsor to hand over the funding? That’s where the meeting acquires a second meeting.

A Budget Is Permission to Spend, Not a Lifetime Achievement Award

Here’s how the familiar ritual works.

In October, every department submits its priorities. In November, Finance negotiates the assumptions. In December, leadership approves the budget. By January, each department is emotionally attached to the number.

By June, the market has changed. Customer behavior has changed. A competitor has launched something unexpected. One initiative is ahead of plan; another is behind. The business has new information.

And yet the budget is defended as though Moses carried it down from the mountain on a laminated worksheet.

I understand why. Department leaders are accountable for delivering commitments, and losing funding can look like losing confidence. Budgets are tied to headcount, compensation, vendor contracts and promises made to teams.

But the purpose of capital allocation isn’t to protect the dignity of the original forecast. It’s to direct scarce resources toward the most valuable opportunities available now.

I’d make one distinction explicit: a budget establishes an approved allocation and accountability framework. It doesn’t guarantee that every dollar must remain attached to its original initiative regardless of performance.

That doesn’t mean Finance gets to confiscate funding whenever a variance turns red. It means every investment should have a thesis, a review cadence and agreed rules for what happens when the thesis changes.

What PayPal’s Example Actually Shows

Oppong describes a midyear case in which PayPal had allocated spending to encourage product adoption and deeper customer engagement through incentives on selected merchant platforms. The original investment case anticipated payback over two to three years.

At the midyear review, the expected return was not materializing. According to his account, softer demand in the targeted consumer base was a structural part of the problem, rather than merely an execution delay that another campaign could fix.

Instead of increasing the incentive spend, the team redirected funding within the existing budget toward stronger capabilities to identify and respond to fraud and higher-risk platform activity.

He reports that the strengthened capability improved transaction-loss performance without a negative impact on the customer experience for the original target population. The new allocation was expected to pay back within the same year.

That is the reported case, not my own firsthand experience at PayPal. The article does not provide the investment amounts or a complete return calculation, so I wouldn’t manufacture either.

The important point isn’t that fraud prevention always beats customer incentives. It doesn’t. In a different market, the customer-growth initiative might be the better use of money.

The point is that the organization reconsidered where the next dollar would produce the most value instead of treating the original approval as a permanent claim.

That’s a much more interesting story than “Finance cut Marketing’s budget,” although I suspect the latter would get more clicks.

Before We Move the Money, Let’s Diagnose the Problem

I wouldn’t pull funding simply because a project is below its original forecast. That can be just as shortsighted as refusing to change anything.

Suppose a product was expected to grow 15%, the market was expected to grow 10%, and the product actually grows 8%. We have at least two problems to investigate: the product missed its own plan and it underperformed the market.

Now suppose the product grows 8% but the entire market shrinks 5%. Same eight-percent actual result, very different competitive story.

The budget variance alone doesn’t tell me which situation I’m looking at.

I’d separate market conditions, execution, competitive positioning and the original forecast assumptions. Did demand change? Did we fail to launch something? Is the sales channel underperforming? Did we assume adoption would be faster than reality could reasonably support?

Those diagnoses lead to different decisions. A temporary launch delay might justify patience. A fundamentally weaker market could justify resizing the investment. An execution problem might call for a different team, not less funding.

Oppong makes a similar distinction in his article, and I think it’s essential. “Behind plan” is a symptom, not a strategy.

If the recommendation is to stop an initiative, I want to know what evidence would have made us continue it. Otherwise the decision risks becoming a retrospective explanation for whichever executive won the argument.

The $5 Million Budget Fight Nobody Needed

Let’s build a hypothetical example. These numbers are illustrative and unrelated to PayPal.

A company has $5 million of discretionary investment funding. It allocates $3 million to a customer-acquisition program and $2 million to a product-retention initiative.

The acquisition program originally expected 10,000 incremental customers at a $300 acquisition cost. At midyear, it has spent $1.5 million and acquired 3,000 customers. Actual acquisition cost is $500 per customer.

Meanwhile, the retention initiative has spent $1 million and generated promising early results. The team believes an additional $750,000 could accelerate adoption of a feature that reduces churn.

The worst response would be to say, “Acquisition has $1.5 million left, so it should spend it. Retention only has $1 million left, so it should wait until next year.”

That is not capital allocation. That’s spreadsheet feudalism.

But the best response is not automatically to move $750,000 either. We need comparable economics, confidence ranges, time horizons and capacity constraints.

If the incremental customers from acquisition still produce an attractive lifetime contribution after the higher acquisition cost, continuing may be justified. If the retention opportunity has a stronger risk-adjusted return, reallocating may be justified.

The decision should turn on forward-looking incremental value, not the emotional significance of the remaining budget balance.

Sunk Costs Are Not a Loyalty Program

One phrase that should make every finance professional suspicious is “We’ve already spent so much on it.”

Yes. We have. That money is gone.

The relevant question is what we expect to receive from the next dollar, compared with the alternatives available today.

Suppose an initiative has consumed $2 million and needs another $800,000 to launch. Management expects the remaining investment to generate $1.1 million of incremental contribution on a present-value basis, after the remaining relevant costs and risks are considered.

Continuing might make sense. The $2 million already spent is not automatically a reason to stop.

Now suppose the remaining $800,000 is expected to produce only $400,000 of incremental present value. The original investment doesn’t rescue the economics of the next decision.

I would still check contractual obligations, shutdown costs, strategic dependencies and any value created by completing the project. “Ignore sunk costs” is not permission to ignore consequences.

But I wouldn’t approve more funding just to avoid admitting the original business case changed.

That is how an underperforming initiative turns into a multiyear relationship with the company’s cash.

And unlike most relationships, it keeps sending invoices.

Not Every Return Fits Neatly Into One ROI Percentage

I like the discipline of comparing investments, but I get nervous when every initiative is forced into one tidy ROI number.

A marketing program, fraud-control investment, infrastructure upgrade and compliance project do not necessarily create value in the same way.

Some increase revenue. Some protect existing contribution. Some reduce expected losses. Some prevent a serious operational or regulatory failure. Some are prerequisites for growth that cannot happen without them.

An investment in fraud detection may improve economics by reducing expected transaction losses. A customer-incentive program may improve economics through incremental contribution and retention. A security requirement may be non-discretionary even if its standalone ROI looks uninspiring.

I’d define the relevant value measures for each class of investment, then translate them into a comparable decision framework where possible.

For risk initiatives, that may involve expected loss reduction, probability-weighted outcomes and tail-risk considerations. For growth initiatives, it may involve incremental contribution, customer lifetime value and payback. For mandatory investments, it may involve minimum required spending and the consequences of noncompliance.

Trying to rank everything by a single ROI percentage can make a spreadsheet look wonderfully objective while hiding the most important differences.

The math should clarify the choice, not cosplay as a universal referee.

The Hardest Number in the Model Is the One Nobody Wants to Give Back

Here’s the political problem: people often interpret a budget reduction as a judgment about their competence.

If a leader built a strong case in November and the market changes in May, that doesn’t automatically mean the leader made a bad decision. Good decisions can produce disappointing outcomes when assumptions change.

Yet in many organizations, the manager who returns unused funding gets punished during the next budget cycle. The manager who spends every dollar gets praised for “execution.”

That incentive structure is practically an invitation to buy things in December.

If leadership wants money to move freely, it has to reward good reassessment rather than treating every change as failure.

I’d want executives to be able to say, “The thesis was reasonable, the evidence changed, and we’re moving the remaining investment,” without triggering a career-limiting event.

That requires behavior from the top. Oppong is explicit that CEO and CFO sponsorship matters. Finance can show the numbers, but it cannot independently change an organization’s definition of success.

Without that support, the reallocation meeting becomes a storytelling competition. Finance arrives with a forecast. The budget owner arrives with twelve slides about strategic importance and a promise that next quarter will be different.

Guess which one has more adjectives.

Agree on the Rules Before Someone’s Budget Is on the Line

I would not wait until a struggling program needs funding removed to announce that every initiative is subject to review.

That’s like introducing the rules of a card game after seeing everyone else’s hand.

I’d establish a reallocation charter when the annual plan is approved. Not a 40-page policy that requires its own governance committee. A practical agreement on which investments are reviewed, what evidence matters, who makes decisions and when.

Each material initiative should have an owner, an investment thesis, expected milestones, measurable outcomes, dependencies and explicit assumptions. We should know what would trigger a deeper review.

Some thresholds can be quantitative: customer acquisition cost above a limit, adoption below a milestone, expected payback extending beyond a defined range. Others will be qualitative, particularly where regulatory obligations or strategic options are involved.

I’d also define the decision rights. Who can move $100,000? Who can move $1 million? Which reallocations require CEO approval or board consideration? What happens to contractual commitments and people assigned to the project?

Then I’d put the review dates on the operating calendar.

If the rules are agreed before the results arrive, Finance isn’t inventing a punishment in the middle of the year. It’s operating the process everyone accepted.

The Forecast Should Move Even When the Budget Doesn’t

One mistake I see in budget discussions is the assumption that changing the forecast and changing the allocation are the same action.

They aren’t.

The original budget is a record of the commitments and assumptions approved at a point in time. The latest forecast should reflect the best current estimate of what will happen. A reallocation decision changes where resources will be deployed.

I want all three views available.

If we overwrite the original budget every time something changes, we lose the ability to learn what we believed and why. If we refuse to update the forecast, management loses visibility into reality. If we update the forecast but never reconsider resource allocation, we become very sophisticated spectators.

That last one worries me most. A finance team can produce an elegant rolling forecast, identify every variance and still watch the company continue funding a weak investment.

The forecast isn’t valuable because it predicts disappointment accurately. It’s valuable because it gives leadership time to respond.

That’s also why I prefer driver-based budgeting that challenges historical assumptions to simply carrying last year’s numbers forward. A forecast should tell us what changed in the business, not just which cells turned red.

A Better Reallocation Meeting Has Four Questions

If I were running the quarterly investment review, I would keep the discussion centered on four questions.

First: What did we believe when we approved the investment? Not the polished narrative we remember today—the actual assumptions, milestones and return expectations.

Second: What have we learned? Separate the market, execution, competitive and timing effects. Don’t let a disappointing outcome automatically become a personal indictment.

Third: What are the alternatives for the remaining resources? Continuing, redesigning, pausing, reducing scope or moving funding elsewhere should all be on the table.

Fourth: What decision will we make now, and what evidence would cause us to revisit it?

I’d want the team to bring a one-page decision brief with the original thesis, current evidence, forward-looking options, risks and recommendation.

Not a 70-slide deck designed to make everyone too tired to disagree.

The purpose of the meeting is to allocate resources. If we leave with only a list of follow-up analyses and a promise to reconvene, the budget has won another round.

A Midyear Reallocation Is Not a License to Chase Every Shiny Object

There’s a danger on the other side of this argument, too.

If leadership reallocates money every time one metric misses for a month, teams will stop investing in anything with a long payoff. Product development, infrastructure and market entry often need patience.

An initiative can be below plan because the assumptions were wrong, because execution needs improvement or because the payoff was never supposed to appear in the current quarter.

That is why I want decision thresholds, time horizons and confidence ranges established before the review.

A three-year strategic investment should not be judged as though it’s a six-week advertising campaign. Equally, a short-term marketing test should not receive a three-year grace period just because its sponsor describes it as “transformational.”

I’d distinguish leading indicators from realized financial outcomes and ask whether the evidence is consistent with the original thesis.

Sometimes the right answer is to keep funding the project and fix execution. Sometimes it’s to reduce scope. Sometimes it’s to stop.

Capital discipline is not the same as impatience.

Although I admit there are projects whose only demonstrated capability is generating more steering committees. Those deserve special scrutiny.

The Hidden Cost of Moving Money Is Execution

A decision to reallocate $1 million does not necessarily free up $1 million of cash tomorrow.

Some spending is contractually committed. Some is tied to headcount or technology dependencies. Some costs continue during a transition. The receiving initiative may need time to hire, procure or implement before it can deploy the money effectively.

I’d build a sources-and-uses bridge for every material move.

How much of the original budget is uncommitted? What termination fees or transition costs apply? When does spending actually stop? When can the receiving team deploy the funds? What incremental value can realistically be earned in the remaining year?

That timing matters. Moving an annual budget number on a slide is not the same as moving cash or productive capacity.

For example, reallocating a nominal $600,000 from a vendor program may yield only $400,000 of near-term available funding if $200,000 is already committed. If the replacement initiative can deploy only $250,000 before year-end, the immediate economics look different from the headline.

I’d also check whether the move creates stranded costs or weakens a capability we still need.

The point isn’t to make reallocation impossible. It’s to keep the implementation plan attached to the financial decision.

Because moving a number between two columns is very easy. Moving an organization is slightly more complicated.

How I’d Measure Whether the Reallocation Worked

After the decision, I wouldn’t declare victory because the budget moved.

I’d track whether the receiving initiative actually delivered the expected incremental value, whether the original initiative’s risk was contained, and whether the transition costs matched the plan.

I’d separate forecast improvement from realized results. A better-looking projection is not a realized return. I’d also track decision speed, the percentage of material investments reviewed, and the number of reallocations reversed because the original diagnosis was wrong.

That last metric isn’t necessarily a failure. Sometimes new evidence changes the decision again. What matters is whether the process learns.

I’d want to know if managers are more willing to surface underperformance early, or whether the process has simply taught them to hide bad news until the next quarterly review.

That’s a cultural metric with serious financial consequences.

An organization that learns early can act early. An organization that punishes the messenger gets a beautifully consistent forecast right up until the surprise.

My 90-Day Plan for Removing Sacred Cows Without Starting a Civil War

In the first 30 days, I’d inventory the largest discretionary initiatives and document the original investment theses. I’d identify the assumptions, owners, current performance, committed spending and major dependencies.

I would not begin by announcing a cost-cutting contest. The goal is better allocation, not to make department leaders hide their calculators.

In days 31 through 60, I’d agree on a decision charter with the CEO, CFO and operating leaders. I’d define review thresholds, governance, comparable value measures and the circumstances that require an exception.

Then I’d run a pilot review on a small set of initiatives with meaningful trade-offs. I want at least one underperformer, one outperformer and one strategically necessary project with a longer payoff.

In days 61 through 90, I’d make the first decisions, document the rationale and establish a follow-up cadence. I’d show both the financial implications and the operating work required to execute.

I’d also ask the participating leaders whether the process felt fair and whether the evidence was useful. If everyone leaves believing Finance had already decided the outcome, we haven’t built a repeatable discipline.

We’ve built a budget tribunal. Those are rarely popular.

No Sacred Cows Also Means Finance Has to Challenge Itself

There’s one final complication: Finance isn’t exempt from the rule.

If we’re asking every department to revisit its assumptions, we should be willing to revisit ours.

Did we overestimate demand? Did we build a plan around historical growth that no longer applies? Did we approve a return model with unrealistic adoption? Did we fail to distinguish committed spending from discretionary capacity?

The annual budget is a joint management decision. It isn’t a document Finance delivers from a mountain and then audits everyone else against.

I’d rather hear a finance leader say, “We learned something new, and our original assumption needs to change,” than defend a forecast simply because it has their name on it.

That kind of credibility makes difficult reallocation conversations easier.

And it prevents Finance from becoming the department that insists everyone else adapt to reality while we remain emotionally attached to cell F47.

The Best Budget Isn’t the One Nobody Changes

Oppong’s PayPal example is useful because it shows the difference between having information and acting on it. The team saw an investment thesis weaken and moved resources toward a different opportunity within the existing budget.

That doesn’t mean every underperforming program should lose funding or that every reallocation will work. It means the organization needs a process for making those decisions without turning each one into a political crisis.

I want a budget that records commitments, a forecast that reflects reality and a governance process that allows resources to move when the evidence changes.

I want department leaders rewarded for identifying better uses of capital, not merely for defending the money they were allocated last November.

And I want Finance to bring alternatives, not just a variance report with the bad numbers highlighted in red.

Because the budget is not a trophy.

It’s a plan for putting resources to work.

If the plan stops working, we should be allowed to change it.

Preferably without requiring three executive off-sites and a ceremonial farewell for the unused marketing budget.