# WACC in Practice: Hurdle Rates That Hold Up
In 2015, GE ran most of its industrial portfolio against a corporate hurdle rate that hovered around 10–12%. Inside that single number lived jet engines, oil-field services, healthcare imaging, and a sprawling finance arm. The problem wasn't that the WACC was wrong on average. It was that "on average" is where capital allocation goes to die. A high-cyclicality energy project cleared the same bar as a stable healthcare contract, so the energy business kept winning capital it shouldn't have, and the stable business kept getting starved. When the cycle turned, the subsidized bets detonated. The postmortems blamed strategy. The mechanism was arithmetic.
This lesson is about that mechanism—how a CFO builds a WACC that survives a board challenge, and then splits it into hurdle rates that actually route capital to where it earns.
You already know the formula. The judgment lives entirely in the inputs, and every input is a defensible range, not a point estimate. Your job is to defend the range and pick a number you can hold under cross-examination.
CAPM is still the workhorse, but the three inputs are where a sharp board member will press you.
The risk-free rate. Use the current 10-year (or 20-year for long-lived assets) sovereign yield, matched to the currency of the cash flows. The rookie error is anchoring to a stale rate or averaging over a period that no longer reflects the regime. In a rate environment that repriced violently between 2021 and 2023, a WACC built on a 2020 risk-free rate wasn't conservative—it was fictional. Refresh it. If your risk-free rate is more than a quarter old, your hurdle rate is lying to your allocators.
Beta.
The equity risk premium. This is the input people fudge. A range of 4.5–6% is defensible for developed markets; pick one, document your source (Damodaran's implied ERP, a survey series, historical data), and—critically—use the *same* ERP everywhere. Inconsistency here is how two analysts in the same building produce WACCs 200 basis points apart.
Use the marginal, forward-looking after-tax cost of debt—what you'd pay to issue today, not the coupon on legacy paper. For an investment-grade issuer, take the current risk-free rate plus your credit spread (from your own secondaries or a rating-matched index). Apply the marginal tax rate, and be honest about whether you can actually use the shield: a company with limited taxable income is discounting a benefit it won't collect.
For the weights, use target capital structure at market values, not book, and not last quarter's snapshot. Book equity is an accounting artifact. And if you weight to a structure you have no intention of maintaining, you're computing the cost of capital for a company that doesn't exist.
The output is a number—say 9.2%. But the honest deliverable to your board is: "Our WACC is 9.2%, within a defensible range of 8.4% to 10.1%, and here is what moves it." Sensitivity is not a weakness in the analysis. It is the analysis.
Here is the failure mode that costs more than any input error. Most firms compute one WACC and apply it to every project. It feels rigorous. It is corrosive.
The logic is simple once you see it. Your company-wide WACC is a weighted average of the risk of your businesses. A stable, low-beta division has a true cost of capital *below* the corporate number. A volatile, high-beta division sits *above* it. When you discount every project at the blended rate, you systematically do two things:
The portfolio drifts toward risk—not because anyone decided to take more risk, but because the measurement system rewarded it. This is precisely the GE pathology, and it repeats in every conglomerate, every multi-segment tech company, and every firm with both a mature cash cow and a speculative growth arm running on the same hurdle rate.
Consider a concrete case. A company with a 9% WACC evaluates two projects, each returning a projected 10% IRRIRRThe Internal Rate of Return is the discount rate that makes a project's net present value equal zero. It expresses an investment's expected annualized return.View full definition →. Project A is a utility-like contracted asset whose true cost of capital is 7%. Project B is a speculative expansion whose true cost of capital is 13%. Against the single 9% hurdle, both pass. But Project A is creating 300 bps of value and Project B is destroying 300 bps. Same IRRIRRThe Internal Rate of Return is the discount rate that makes a project's net present value equal zero. It expresses an investment's expected annualized return.View full definition →, opposite economics. The single rate is blind to the only thing that matters: risk-adjusted return.
If your riskiest division consistently proposes the projects with the highest headline IRRs, and those projects consistently disappoint after funding, you don't have a strategy problem. You have a hurdle-rate problem. The division isn't better at finding opportunities; it's better at gaming a rate that undercharges it for risk.
The fix is to build divisional (or project-class) hurdle rates, and you already produced the machinery when you built the bottom-up beta.
For each business unit, take the unlevered pure-play beta you assembled, relever it at the structure appropriate to *that* business (a stable division can carry more debt than a volatile one—reflect that), and recompute the cost of equity. Combine with a division-appropriate cost of debt and weights. You now have a healthcare WACC, an energy WACC, a software WACC—each anchored in the risk of its own comparables rather than the corporate blend.
The discipline check: your divisional WACCs, weighted by each division's capital, should reconcile back to the corporate WACC. If they don't, you've made an error or you're carrying risk in one segment you haven't priced. That reconciliation is also how you defend the split to skeptics—it isn't arbitrary; it decomposes the number they already accepted.
Even within a division, not all projects share the division's risk. A capacity expansion in an existing plant is not the same risk as entering a new geography. Rather than compute a beta per project—spurious precision—use a small number of risk tiers layered on the divisional rate:
The premiums must be documented, consistent, and defensible—otherwise they become a lever for managers to justify pet projects. The tier framework works precisely because it's transparent and hard to game.
Any hurdle-rate system creates incentives to beat it, and the beating happens in the numerator, not the denominator. Once managers know the hurdle, they inflate terminal values, backload cash flows into years no one will audit, and assume synergies that never materialize. A CFO who fixes the discount rate but ignores forecast discipline has moved the problem, not solved it.
Two defenses. First, hold post-audits: compare realized returns to the projections that won funding, and make the results visible to the people who submitted them. Nothing disciplines optimism like knowing the forecast will be graded. Second, stress the cash flows, not just the rate—run the downside case and ask whether the project clears its hurdle when things go moderately wrong, because the base case is almost always a story the sponsor wants to be true.
Knowledge check
1. Why does the lesson argue that applying a single corporate WACC across a diversified portfolio can systematically misallocate capital?
2. The lesson insists that a risk-free rate more than a quarter old makes 'your hurdle rate lying.' What is the underlying conceptual reason?
3. Why does the lesson recommend the Blume adjustment (roughly two-thirds raw beta, one-third toward 1.0) rather than trusting a raw regression beta?
4. Select ALL correct answers: what principles does the lesson advocate for choosing the risk-free rate in a WACC?
Select all the correct answers.
5. Select ALL correct answers: what does the lesson imply about defending WACC inputs to a skeptical board?
Select all the correct answers.
A hurdle rate that lives in a spreadsheet reviewed once a year is a hurdle rate that's wrong most of the time. Two practical disciplines separate CFOs who use WACC as a tool from those who use it as a ritual.
Refresh cadence tied to regime, not calendar. Update your WACC when the inputs move materially—a 100 bps shift in the risk-free rate, a ratings change, a capital-structure move—not merely at year-end. In stable regimes, annual is fine. In the 2022–2023 repricing, firms that held stale hurdle rates approved a wave of projects that the higher cost of capital would have rejected, and they're living with those assets now. Your hurdle rate should reflect the world in which the capital is actually being deployed.
Currency and geography matching. For cross-border investment, don't take a domestic WACC and bolt on a vague "country risk" fudge. Either build the discount rate in the local currency (local risk-free rate, local ERP) and discount local-currency cash flows, or model the cash flows in your home currency using forward rates and apply your home WACC plus a defensible country risk premium. Mixing the two—home-currency cash flows discounted at a local rate, or vice versa—double-counts or omits risk and is one of the most common errors in emerging-market capital budgeting.
Finally, know the limit of the tool. WACC assumes a project shares the firm's business risk and roughly its capital structure. When a project's financing is genuinely separable—a project-financed infrastructure asset, a highly leveraged acquisition with its own debt—WACC is the wrong engine. Use Adjusted Present Value: value the project unlevered at the cost of equity, then add the value of the financing side effects (the tax shields) separately. APV is the honest tool when leverage is a deliberate, changing part of the project's design rather than an inherited backdrop. Reaching for it at the right moment is a mark of a CFO who understands what WACC is actually assuming.