The Missing Cash Flow

---

I. The Value Engineering Gauntlet

A typical hotel or resort development project produces a number of Value Engineering proposals at every stage. Each proposal represents a decision — spend more now in exchange for lower operating costs later, or hold the budget line and accept the higher ongoing expense.

In theory, these decisions should be straightforward. If the present value of future savings exceeds the present value of the additional cost, the rational decision is to invest. In practice, the decision is almost never that clean — not because the math is difficult, but because the organizational structure through which the proposal must travel was not built to evaluate it correctly.

The First Filter: Design and Engineering Self-Censorship

Architects and engineers usually understand DCF and payback analysis. They understand the mechanics. What they do not typically understand — because it falls far outside their area of expertise and concern — is how a capital improvement’s effect on operating expenses translates into exit value through the income capitalization method.

The practical consequence is self-censorship. A mechanical engineer evaluating a high-efficiency HVAC system sees a 6-year payback period and a modest positive NPV based on operating savings alone. She knows from experience that the owner’s representative will push back on anything that costs more if it does not pay back within 3–4 years or show a commanding return. So the proposal is either never made, or made weakly, inviting rejection.

What she cannot see — because no one in her professional ecosystem has ever framed it properly — is that the same proposal, when evaluated through the lens of value added, may show an NPV two to three times larger than the operating-savings-only model suggests. The proposal that looked marginal is actually often very compelling. But it seldom makes it to the design meeting or if it does, seldom leaves it.

This is not a failure of competence. It is a failure of framing. The engineers are doing exactly what they were trained — and hired — to do. They are simply working with an incomplete model — and that incompleteness is invisible to them.

The Second Filter: Misaligned Teams and Incentives

Of the proposals that do get made, many are evaluated by owner’s reps — usually project managers or construction managers — overseeing the design and construction. These are typically experienced professionals. They are also, in most project structures, incentivized primarily to deliver the project on time and on budget.

This creates a structural misalignment. A VE proposal that increases the construction budget by $45,000 is, from the PM’s perspective, a budget overrun to be managed. The fact that this $45,000 may generate $128,000 of net present value for the asset’s owner is not their problem.

The result is predictable: proposals that increase cost get filtered out at the project level by professionals whose job — as they understand it — is to prevent budget overruns. The added value that many of those proposals would have generated for the project owner never enters the conversation. The conversation instead often focuses on the proposals that reduce cost.

The Third Filter: Incomplete Information

Even when a VE proposal survives the first two filters and reaches the finance team, it still arrives stripped of the context needed to evaluate it correctly and make the right decision. The proposal document often shows an initial cost. If lucky, it also shows an annual savings estimate and a simple payback period. If really lucky, it is presented as a full cash flow of the initial cost and running costs in comparison with cash flows of the other options under consideration.

But almost never do they show the marginal upfront cost and the marginal annual benefits. There is no consideration or mention of the impact of those marginal annual benefits on terminal NOI, and therefore the value of the asset at exit. The consultants prepared it the way they always have, and the owner’s reps didn’t tell them the information to provide for a fully-informed decision. In the industry, Project teams simply are not built to think in terms of adding value.

The decision-maker, in the best case, is presented with a choice that looks marginal: spend $45,000 to save $11,000 per year, payback in about 4 years, modest IRR. In a context where dozens of competing demands exist for every dollar of capital, however, a “modest” IRR is easy to defer or reject so they can stay under budget and avoid the uncomfortableness of making a capital call. So unless all levels of your project team — or at least your central project lead — understands capital decision-making and has the authority to actively control what and how information is provided and should be presented, that incompleteness flows directly to the decision-makers and influences decisions as well.

The Cumulative Effect

The end result of these three filters is that only VE proposals with overwhelming, self-evident payoff — the ones that would survive any analytical framework, however incomplete — actually get implemented. The proposals that require a more sophisticated analysis to justify, the ones where the exit value impact is the difference between “marginal” and “compelling,” are systematically killed.

On any given project, this might mean five, ten, or twenty individual value-creation opportunities that were identified, evaluated with an incomplete model, and rejected. Each one, evaluated correctly, might have added tens or hundreds of thousands of dollars of Net Present Value to the asset. Across a portfolio, across a decade of development or investment activity, the cumulative value destruction is substantial — and almost entirely invisible, because no one involved in the decision knew what they were leaving on the table. And it is irreversible value generation entirely unaffected by business cycles. It is true, persistent alpha.