Hudson Corporation Is Considering Three Options

Hudson Corporation's Three Options: A Real-World Look at the Decision Ahead

So Hudson Corporation is weighing three options. That's the setup, but the question that actually matters is: which one? If you're reading this, you probably already know the basics of the case — three mutually exclusive projects, a fixed capital budget, and a recommendation that needs defending. Maybe you're a finance student working through it for class. Maybe you're a practitioner thinking through a real parallel. Either way, the right answer isn't about plugging numbers into a formula. It's about understanding what each option actually means for the company.

Let me walk through how I'd think about this — and where most people go wrong when they tackle it.

What the Decision Actually Involves

At its core, Hudson Corporation is facing a capital budgeting problem. The company has a limited amount of money to invest, and three projects are competing for that pool. So picking one means turning down the other two. That's what makes the decision "mutually exclusive" — you're not just evaluating each project in isolation, you have to choose between them.

The three options are typically evaluated using capital budgeting techniques like Net Present Value (NPV), Internal Rate of Return (IRR), and payback period. The textbook setup usually involves a project with a high NPV but a long payback window, a project with moderate returns but lower risk, and a project that looks great on paper but has some hidden catches — often related to scale, timing, or how realistic the cash flow projections are.

What makes the Hudson case a classic isn't the math. It's the judgment call underneath it.

Why the Decision Is Harder Than It Looks

Here's where most textbook treatments stop too early. That said, they calculate the NPVs, rank the projects, and call it a day. But real capital decisions don't work that way.

The ranking alone can mislead you. NPV is supposed to be the gold standard — it directly measures how much value a project adds. But NPV depends entirely on the discount rate, and the discount rate is itself an assumption. If Hudson uses 8% versus 12%, the rankings can shuffle. IRR has its own quirks: a project can have a high IRR but a low NPV if the cash flows are front-loaded and the project is small. The "best" project on paper isn't always the best project in practice.

There's also the question of strategic fit. Here's the thing — does the project align with where Hudson wants to be in five years? On top of that, does it lock the company into a market it might want to exit? Does it require hiring people, building infrastructure, or taking on operational complexity that doesn't show up in the cash flow spreadsheet? Those things don't appear in an NPV calculation, but they show up in the results.

How to Think Through Each Option

Option A: The High-NPV, Long-Payback Project

This one's usually the most attractive on a pure numbers basis. The cash flows are strong, but they come later. It promises the largest absolute increase in shareholder wealth. The upfront investment is heavy.

The risk is timing. Still, if something goes wrong in years two or three, the project can quickly turn from a winner into a write-off. Long-payback projects are more exposed to changes in market conditions, technology shifts, or competitive pressure. The discount rate punishes those late cash flows, which is why the NPV is sensitive to assumptions.

If Hudson has a strong balance sheet and patient shareholders, this option can make sense. If the company is under pressure to show results soon, the long wait becomes a real cost.

Option B: The Moderate, Balanced Project

This is the safe middle ground. The NPV is solid — not the highest, but respectable. Plus, the payback period is reasonable. The risk profile is manageable. It won't transform the company, but it won't sink it either.

A lot of CFOs end up here, and there's nothing wrong with that. Sometimes the reason is rational: the company genuinely can't absorb the risk of the bigger bet. Sometimes it's just risk aversion dressed up as strategy. In a vacuum, though, choosing the "safe" project over the high-NPV one requires a real reason. The Hudson case usually wants you to articulate why you'd walk away from a higher NPV — and that's a harder question than it sounds.

Option C: The IRR-Maximizing Project

This option often looks great on an IRR basis. The trap is that high IRR can be misleading, especially when project sizes differ. Because of that, maybe it's smaller in scale, or maybe the cash flows are structured in a way that produces a high percentage return. A small project with a 25% IRR might add less total value than a larger project with a 15% IRR.

Continue exploring with our guides on classify the following triangle check all that apply 54 36 and highest common factor of 24 and 56.

There's another common issue with this kind of project: the cash flow pattern can produce multiple IRRs or an IRR that doesn't exist in the usual sense. When cash flows change sign more than once — initial outflow, then inflows, then a big cleanup cost at the end, for example — the IRR formula breaks down in ways students often miss.

Common Mistakes People Make With This Case

The single biggest error is treating it as a pure NPV ranking exercise. That's why you calculate the three NPVs, pick the highest, and move on. That's a defensible starting point, but it's not a complete analysis.

Another common mistake is ignoring scale differences. If Project A costs $5 million and Project B costs $50 million, comparing their NPVs without normalizing for size is misleading. The profitability index (NPV divided by initial investment) helps here, and it's often the tiebreaker that textbooks want you to use.

People also tend to overweight the IRR. " — but it's not directly comparable across projects of different sizes or durations. On top of that, because IRR is expressed as a percentage, it feels intuitive — "25% sounds great! Don't let a flashy IRR number drive the decision when NPV tells a different story.

And finally, many analyses ignore the real-world implementation costs. Even if a project has a strong NPV, what does it require from the organization? Retraining? Disruption to existing operations? Worth adding: new systems? Think about it: new hires? These don't always show up in the financial summary, but they absolutely show up in the outcome.

What Actually Drives the Right Answer

The "right" option in the Hudson case usually depends on what assumption set you're working with. Because of that, if the discount rate is realistic, the cash flows are credible, and the projects are truly independent of each other, the highest NPV almost always wins. That's the clean answer.

But the more interesting question — and the one worth thinking about — is what would change your mind*. If a project has the highest NPV but requires a 30% jump in operational complexity, the company might rationally pick the second-best option to preserve optionality. If two projects have nearly identical NPVs, the tiebreaker becomes strategic: which one positions Hudson better for the next round of decisions?

A good answer to this case doesn't just pick a project. It explains the conditions under which the choice would flip, and it shows that you've thought about the second-order effects.

FAQ

Should you always pick the project with the highest NPV?

In a textbook setting with reliable inputs, yes. On top of that, in practice, NPV is the starting point, not the finish line. Strategic fit, risk tolerance, and operational capacity all matter.

Why is IRR sometimes misleading?

IRR can overstate the attractiveness of smaller projects, and it can produce multiple or missing values when cash flows change signs more than once. It's a useful secondary metric, not a primary one.

What's the profitability index and when does it matter?

It's NPV divided by the initial investment. It matters when projects require different amounts of capital and you need a comparable return-per-dollar measure.

How does the discount rate affect the ranking?

A higher discount rate penalizes long-term cash flows more heavily, which can flip the ranking in favor of shorter-term projects. Always run a sensitivity check on the discount rate before committing.

Is there ever a reason to pick a lower-NPV project?

Yes — if the project reduces risk, builds capability, or positions the company for future opportunities that the others don't. The goal is to maximize long-run value, not to win a single ranking exercise.

Final Thought

The Hudson Corporation case isn't really about the numbers. It's about recognizing that every capital decision is a bet on the future, and the future is full of things spreadsheets don't capture. Because of that, pick the project that makes the most sense given what you actually believe about the business — and be honest about what could go wrong. That's the part most analyses skip, and it's the part that matters most.