Capital Allocation for CFOs: When Every Investment Looks Good

There are worse problems than having too many good investment opportunities.

I can think of several.

But if you’re a CFO looking at three attractive business cases and enough capital to fund only two, congratulations.

You have reached the part of financial planning where the spreadsheets stop being the main event.

Now you have to make a decision.

And, inconveniently, everyone has a perfectly reasonable explanation for why their project should go first.

Sales wants capacity.

Operations wants automation.

Technology wants infrastructure.

Each proposal promises measurable returns, strategic benefits, and a brighter future.

I’m delighted we’re all so optimistic.

But we still have one capital budget.

Which means somebody has to decide what gets funded, what waits, and what doesn’t happen.

This is where I think FP&A can be particularly valuable.

Not by producing a more elaborate investment template.

By helping leadership choose the combination of investments that creates the most value the business can realistically deliver.

The First Question Isn’t Which Project Has the Best IRR

Let’s imagine a U.S. company has $10 million available for discretionary capital investment.

Three business units submit proposals.

Each has a positive net present value, or NPV, using an appropriate discount rate.

Each has a credible strategic rationale.

And each project is assumed to be independent, with its initial capital requirement paid from this year’s investment budget.

Here are the proposals.

Investment	Initial capital	Estimated NPV	NPV per dollar invested
A: Expand production capacity	$6.0M	$2.40M	0.40
B: Automate fulfillment	$4.0M	$1.90M	0.475
C: Upgrade customer infrastructure	$3.0M	$1.35M	0.45
Available budget	$10.0M

All figures are hypothetical. NPVs are assumed to be calculated using consistent, risk-appropriate cash flow and discount-rate assumptions.

Every project looks attractive.

Project B creates the most estimated value per dollar invested.

Project A creates the greatest total standalone value.

Project C has a smaller capital requirement and a compelling operational case.

I can already imagine three enthusiastic presentations.

Possibly with animations.

And somebody will undoubtedly have included a photograph of a sunrise.

But here’s what interests me.

We don’t need to decide which presentation we like best.

We need to decide which portfolio creates the greatest value within the constraints.

Let’s Put the Projects Together

Assuming the projects are independent and their NPVs are additive, we can compare the feasible combinations.

Portfolio	Capital required	Combined NPV	Within $10M budget?
A only	$6.0M	$2.40M	Yes
B only	$4.0M	$1.90M	Yes
C only	$3.0M	$1.35M	Yes
A + B	$10.0M	$4.30M	Yes
A + C	$9.0M	$3.75M	Yes
B + C	$7.0M	$3.25M	Yes
A + B + C	$13.0M	$5.65M	No

Under these assumptions, A + B is the strongest feasible portfolio.

It uses the full $10 million and produces an estimated $4.3 million in combined NPV.

That is $550,000 more estimated value than A + C.

And $1.05 million more than B + C.

That’s a useful result.

But I wouldn’t send the approval emails just yet.

Because we’ve answered one question.

We’ve established the mathematically attractive combination under the stated assumptions.

We haven’t established whether the organization can actually execute it.

Those are two different things.

And confusing them can become expensive.

Capital Isn’t the Only Resource We’re Allocating

This is the part of the discussion I would enjoy.

Suppose projects A and B both require the same engineering and implementation teams.

Project A needs 18,000 specialist hours.

Project B needs 12,000.

Together, that’s 30,000 hours.

But the company has only 24,000 hours of realistically available specialist capacity over the implementation period.

Now what?

The capital budget says yes.

The operating plan says absolutely not.

We can hire contractors, change the sequence, delay another initiative, or redesign the implementation.

All legitimate options.

But each has a financial consequence.

Perhaps the company needs an additional $700,000 of external implementation support.

Perhaps one project’s benefits arrive six months later.

Perhaps other work must be postponed.

Those costs and delays belong in the investment analysis.

They don’t disappear because they were omitted from the original business cases.

This is why I prefer to examine capital allocation alongside capital expenditure forecasting, the operating plan, workforce capacity, cash forecast, and strategic priorities.

The projects aren’t being implemented by imaginary employees who work unlimited hours and never need to attend a meeting.

Although I suspect several annual plans were built on that assumption.

I’d Give Every Project the Same Financial Rules

Before comparing investment proposals, I’d establish a common evaluation standard. That includes reviewing the financial model before trusting it.

Otherwise, we risk comparing a conservative operating team’s forecast with a particularly imaginative growth proposal.

Both might be beautifully formatted.

That doesn’t make them comparable.

At a minimum, I’d want consistency around the following.

Cash flow, not just accounting earnings

NPV should be based on incremental after-tax cash flows, including relevant capital spending, working capital requirements, operating benefits, and terminal effects.

A project that improves EBITDA but absorbs substantial working capital may have a different value profile from the one in its presentation.

Risk-appropriate discount rates

Using the same discount rate for fundamentally different risks can distort rankings.

But allowing every sponsor to choose whatever hurdle rate makes the project look attractive isn’t an improvement.

Finance should establish a defensible approach to risk, discount rates, and sensitivity testing.

A common treatment of shared costs

If two investments depend on the same infrastructure, implementation team, or supporting expenditure, I want those dependencies visible.

And I don’t want the same benefit counted twice.

Consistent treatment of alternatives

Can the project be delayed?

Reduced in scope?

Piloted?

Delivered in stages?

These aren’t minor questions.

Sometimes the most valuable decision isn’t whether to invest.

It’s how much to commit before we know whether the assumptions are right.

What If We Fund the First Stage Instead of the Whole Project?

Let’s return to Project A.

Its original proposal requires $6 million to expand production capacity.

But perhaps management can divide the investment into two stages.

The first stage requires $2 million.

It provides enough capacity to test demand, establish operating performance, and learn whether the expected economics hold.

The second stage would require another $4 million.

If the initial results support the expansion, management can proceed.

If demand is weaker than expected, the company can reconsider.

I like this kind of structure because it introduces a valuable option: the ability to make a later decision using better information.

Of course, staged investment isn’t automatically superior.

Breaking a project into phases may increase costs, delay benefits, or create operational inefficiencies.

And a $2 million pilot isn’t necessarily a substitute for a $6 million expansion.

The financial model must account for those differences.

But the option to wait, learn, and adapt can have genuine value.

The CFA Institute’s discussion of capital investment decisions recognizes this kind of flexibility through the concept of real options.

For me, the practical question is simple.

What are we paying to learn, and what future commitment does that information allow us to avoid?

That’s a much more interesting question than whether a project has an attractive IRR printed in bold.

The Scenario That Changes the Recommendation

Let’s say the initial portfolio analysis favors A + B.

Before presenting it to the executive team, I would run a financial scenario that tests the assumptions most likely to change the decision.

Not twenty-seven scenarios.

Not a colorful collection of best-case, base-case, and worst-case forecasts that all somehow end with a positive recommendation.

I’d start with the important uncertainties.

For Project A, perhaps the critical assumption is customer demand.

For Project B, perhaps it’s the rate at which automation savings can be achieved.

Suppose the scenario analysis produces these revised NPVs.

Investment	Base-case NPV	Downside NPV
A: Capacity expansion	$2.40M	$0.60M
B: Fulfillment automation	$1.90M	$1.50M
C: Customer infrastructure	$1.35M	$1.10M

These are illustrative downside estimates, not forecasts of a real company.

Under the downside assumptions:

• A + B produces $2.10 million in combined NPV.
• A + C produces $1.70 million.
• B + C produces $2.60 million.

Now B + C has the highest combined downside NPV of the feasible two-project portfolios.

That’s interesting.

The original recommendation was A + B.

The downside recommendation is B + C.

Does that mean we automatically switch to B + C?

No.

We need to know how plausible the downside scenario is, how the projects’ risks are related, and whether the business has enough liquidity and strategic flexibility to absorb a weaker outcome.

We might also examine probability-weighted outcomes if the probabilities can be estimated credibly.

But now the executive team has a better decision to make.

We’re not debating whether Project A’s sponsor is optimistic.

We’re asking whether the additional base-case value justifies its greater exposure to demand uncertainty.

That’s a discussion worth having.

I’d Separate Mandatory Investments From Discretionary Ones

There is another distinction I wouldn’t overlook.

Some projects aren’t optional in the same way as others.

Safety requirements.

Regulatory obligations.

Critical infrastructure replacement.

Cybersecurity remediation.

These may require investment even when their standalone NPV isn’t attractive.

The appropriate question may be how to meet the obligation at the lowest defensible cost and risk, rather than whether the project beats a growth investment’s return.

I would identify these commitments before ranking discretionary projects.

Then I would evaluate the remaining capital available for competing opportunities.

Otherwise, the investment committee risks comparing a required safety upgrade with a new market expansion as though they were interchangeable choices.

They aren’t.

We can still scrutinize the cost, timing, design, and execution of mandatory projects.

We just need to be honest about the decision we’re making.

Who Gets to Challenge the Assumptions?

Here’s where capital allocation becomes an organizational issue.

A business-unit leader knows the market.

Operations understands delivery constraints.

Technology understands systems dependencies.

The CFO understands the financial consequences and the company’s capacity to fund competing priorities.

Nobody has the entire answer alone.

That’s why I would design an investment review that gives each function a meaningful role without allowing the process to become a contest of presentation skills.

I would want the investment sponsor to own the business case.

FP&A should challenge and reconcile the financial assumptions.

Operational leaders should confirm execution capacity.

The CFO and executive team should consider portfolio tradeoffs.

The board should receive the information needed for decisions within its approval authority.

And once an investment is approved, the sponsor should remain accountable for the results.

Not merely for spending the approved amount.

For delivering the economic outcome that justified the investment.

That’s an important difference.

Spending the budget is not a measure of success.

My children could have demonstrated that principle in approximately four minutes at a toy store.

The Approval Should Include Conditions, Not Just a Dollar Amount

Imagine the investment committee approves Project A.

Rather than simply authorizing $6 million, I would want the decision documented around the assumptions that matter.

For example:

Approval condition	What leadership will monitor
Demand threshold	Confirmed orders or other evidence supporting capacity expansion
Implementation readiness	Required staffing, vendors, and operational dependencies
Capital exposure	Actual and committed spending against authorized amounts
Expected benefits	Updated revenue, margin, and cash-flow assumptions
Decision checkpoint	Whether to continue, stage, redesign, or stop

Not every project needs a complicated stage-gate structure.

But material investments should have clear accountability and defined points for reconsideration.

If demand falls materially below the approved case, somebody should have the authority and responsibility to bring the decision back.

The original investment approval isn’t a lifetime membership.

Circumstances change.

A good capital allocation process allows leadership to respond without pretending the original assumptions remain sacred.

What I Would Put in Front of the CFO

If I were preparing this decision for an executive review, I’d want one concise view that brings together the essential information.

Not a binder that could double as a doorstop.

Something like this:

Decision area	Executive question
Strategic fit	Which business priority does this investment advance?
Value creation	What is the estimated incremental NPV?
Capital requirements	How much funding is needed, and when?
Cash and liquidity	Can the business fund the portfolio under credible downside conditions?
Execution capacity	Do we have the people, systems, and operational bandwidth?
Risk	Which assumptions could materially change the decision?
Alternatives	Can we stage, defer, resize, or substitute the investment?
Accountability	Who owns the outcome and the decision checkpoints?

I’d also show the feasible portfolio alternatives, not merely a list of individually attractive projects.

That distinction matters.

An investment committee should be able to see what it is choosing instead of something else.

The opportunity cost is part of the decision.

Even when the project we don’t fund is a perfectly good idea.

Capital Allocation Shouldn’t End When the Budget Is Approved

This is one of my favorite opportunities for FP&A to become more valuable to the business.

After approval, compare actual performance with the original investment thesis.

Did demand materialize?

Did implementation cost more than expected?

Were savings delayed?

Did the project require additional working capital?

Were the expected operating benefits achieved?

And most importantly:

What should we do now?

A post-investment review shouldn’t be an elaborate ceremony in which everyone admires a variance report and promises to do better next time.

It should influence future investment decisions.

If one business unit consistently underestimates implementation costs, improve the next business case.

If a technology program delivers benefits more slowly than expected, update future benefit-realization assumptions.

If staged investments repeatedly outperform large upfront commitments under uncertainty, consider where that approach makes sense elsewhere.

The goal is to make the next decision better.

Not simply explain the last one.

Sometimes the Best Financial Decision Is to Fund Two Good Ideas and Disappoint a Third Person

I started with three attractive projects and a $10 million capital budget.

Under the initial assumptions, A + B creates the most estimated value.

Under a downside scenario, B + C becomes more attractive.

Execution capacity may change both conclusions.

And staging an investment may create another alternative altogether.

That’s why I wouldn’t reduce capital allocation to a ranking of IRRs.

The financial calculations matter enormously.

But the actual decision also depends on liquidity, timing, operational capacity, risk, strategic priorities, and the flexibility to change course.

I think this is some of the most interesting work in FP&A.

We get to help leadership decide not only whether an investment makes sense, but which combination of opportunities deserves the company’s limited resources.

And when the process works, the business doesn’t just spend capital more carefully.

It becomes better at turning its strategy into financial results.

That’s a pretty good outcome.

Even if somebody has to remove the sunrise photograph from their presentation.

When the Investment Cases All Look Good

If your leadership team has several attractive investment proposals but no consistent way to compare their assumptions, execution constraints, and downside exposure, that’s the kind of financial decision I enjoy working through.

My Scenario Modeling & Decision Support services focus on making those tradeoffs clearer.

Because I’d much rather help leadership make a confident investment decision than produce one more spreadsheet proving that everyone has an excellent idea.