Anyone who has ever worked on a development pro forma will know that the process generally works like this: You start with a bunch of assumptions. You assemble those assumptions in a way that will allow you to determine if the project in question is feasible. And then, you realize that almost everything is more costly than you initially thought and that the project may not actually work. Oh shit.
In fact, a sure-fire way to know that you're on the right track is if the numbers sort of don't work. If the returns look too good to be true, they almost certainly are and you're likely missing something big and meaningful. As we have talked about before on this blog, development happens on the margin. That means that you have to work at it. You have to be creative. And often you have to find ways to increase revenues and cut costs.
The common way to find money is through something known as value engineering, which is just a fancy way of saying, "I need to cut costs, so let's see what I can tolerate losing from this project." That's generally how it works. And we do it on every project. You're trying to find high-cost items with relatively low perceived value.
This process often gets a lot of criticism because people view it as a distasteful cheapening of a project. But the reality is that it is usually an important part of maintaining project feasibility. You may really want to use that fancy material you can only get from Switzerland, but maybe
