A diversified company should not evaluate every division and project at one corporate WACC. Required returns should rise or fall with the systematic risk of the cash flows being valued.
Required return and risk
The cost of capital compensates investors for time value and relevant risk. Corporate WACC is an average required return for assets similar to the company's current portfolio, not a universal hurdle rate.
How one WACC misallocates capital
| Division | True required return | Corporate WACC | Likely bias |
|---|---|---|---|
| Stable services | 8% | 10% | Good low-risk projects may be rejected |
| Cyclical technology | 13% | 10% | Weak high-risk projects may be accepted |
Repeated use of one rate can gradually make the business riskier because risky divisions receive an artificially low hurdle while stable divisions face an excessive hurdle.
Methods for divisional rates
| Method | Process | Strength |
|---|---|---|
| Pure play | Estimate beta and capital costs from focused comparable companies | Market-based risk evidence |
| Bottom-up beta | Combine business segments or operating drivers | Useful when exact comparables are limited |
| Risk classes | Assign approved premiums or discounts around corporate WACC | Simple and governable |
| Divisional financing data | Estimate component costs and target weights for the division | Direct when reliable data exists |
Worked two-division example
Assume a company WACC of 10%. Evidence suggests its utilities division has a required return of 8%, while its construction division requires 13%. A utilities project with an expected return of 9% creates value at the correct 8% hurdle but would be rejected at 10%. A construction project returning 11% destroys value at the correct 13% hurdle but would be accepted at 10%.
Project-level refinement
A divisional rate is a useful starting point, but an unusual project may still require a separate rate. Consider operating leverage, customer concentration, country exposure, duration and cyclicality.
Use consistency across the investment pipeline. Two projects with similar risk should not receive different hurdle rates simply because different managers prepared them. A central finance review can preserve comparable assumptions without removing operational insight from divisions.
Governance controls
- Approve a documented method for each rate.
- Update market inputs consistently.
- Separate business-risk and financing assumptions.
- Review projects close to the hurdle with sensitivity analysis.
- Prevent managers from choosing the easiest rate.
Decision hierarchy
Move to a more specific rate only when the risk difference is material and supportable.
Frequently asked questions
Why not use corporate WACC for every division?
It can overstate the hurdle for low-risk activities and understate it for high-risk activities.
What is the pure-play method?
It uses focused comparable companies to estimate the market-required return for similar business risk.
Is a divisional rate always enough?
No. A materially unusual project may need a project-specific rate.
How often should rates be reviewed?
Review them when market inputs, financing targets or the division's risk profile changes materially.
Continue learning
- Project-specific cost of capital
- WACC formula and example
- Book versus market weights
- Cost of equity and CAPM
Use the formulas and examples as learning tools. Real decisions should use reliable data, appropriate assumptions and professional judgment where necessary.
We emphasize that the required rate of return, or the cost of capital is a market determined rate and it reflects compensation to investors for the time value of money and risk of the investment project. It is, thus, composed of a risk free rate (compensation for time) plus a risk premium rate (compensation for risk). Investors are generally risk-adverse, and demand a premium for bearing risk. The grater the risk of an investment opportunity, the grater the risk premium required by investors therefore, the required rate of return of a division or a project depends on its risk. Since investors are risk adverse, divisions and projects with differing risks should be evaluated using their risk adjusted rates of return.
The firm’s risk is composed of its overall operating risk and financial risk. Operating risk arises due to the uncertainty of cash flows of the firm’s investments. Financial risk arises is also a composite risk of assets financed by the firm. Thus, the firm’s cost of capital reflects the rate of return required on its securities commensurate with the perceived average risk. The firm’s cost of capital therefore cannot be used for evaluating individual divisions or investment projects that have different degree of risk. The firm’s cost of capital as a required rate of return for all projects may work well in case of companies that have single line of business or where different businesses are highly correlated. In highly diversified, multiple business firms, all projects cannot have same risk. Even a business, which basically operates in fast moving consumer products markets, has distinct markets for its consumer products. In each, market segment, business is exposed to different degree of competition and other environmental forces, which results in different risks for all its market segments. Hence, it is essential to estimate the required rate of return for each market segment or division than using the firm’s cost of capital as a single, corporate-wide required rate of return for evaluating project of divisions rather, projects within a single division may differ in risk. For example, the risk of introducing a new, innovative project will be higher than the expansion of an existing project. Hence, there is need for calculating the required rate of return for projects within a division.
The capital asset pricing model (CAPM) is healthful in determining the required rate of return (or the cost of capital) for a division or a project. The risk free rate and the market premium for divisions or projects are same as for the firm. What we need the divisional or project betas. In practice, it is difficult to estimate divisional or project betas.
No comments:
Post a Comment