As we have talked about many times before, the best answer to this question is that it's worth whatever money is left in your pro forma once you've accounted for everything else. This is what is called the "residual claimant" in a development model. And it means you start with your revenue, you deduct all project costs, including whatever profit you and your investors need to make in order to take on the risk of the development, and then whatever is left can go to pay for the land.
This is the most prudent way to value development land; but of course, in practice, it doesn't always work this way. In a bull market, the correct answer to my question might be, "whatever most market participants are willing to pay." And sometimes/oftentimes, this number will be greater than what your model is telling you, meaning you'll need to be more aggressive on your assumptions if you too want to participate. (Not development advice.)
Given that determining the value of land starts with revenue, one way to do a very crude gut check is to look at the relationship between land cost and revenue. This is sometimes called a land-to-revenue ratio. And historically, for new condominiums in Toronto, you wanted a ratio that was no greater than 10%. Meaning, if the most you could sell condominiums for was $1,000 psf, then the most you could afford to pay for land was $100 per buildable square foot.
However, this is, again, a very crude rule of thumb. I would say that it's only really interesting to look at this after the fact. Because in reality, things never work this cleanly. For one thing, there is always a cost floor. Don't, for example, think you can buy land in Toronto for $80 pbsf and sell condominiums for $800 psf, because this will not be enough to cover all of your costs. You will lose money.
Secondly, there are countless variables that have a huge impact on the value of development land. Things like a high required parking ratio, development charges and other city fees, inclusionary zoning, and so on. All of these items are real costs in a development model, and so they will need to be paid for somehow.
Typically this happens by way of higher revenues (in a rising market), a lower land cost (in a sinking market), or some combination of the two. But in all of these cases, it means your land-to-revenue ratio must come down to maintain project feasibility. This is why suburban development sites typically have a lower ratio -- too much loss-leading parking, among other things.
Of course, there are also instances where the correct answer could be a land-to-revenue ratio approaching zero, or even a negative number. In this latter case, it means your projected revenues aren't enough to cover all of your other costs, excluding land. For anyone to build, they will require some form of subsidy. And this is basically the case with every affordable housing project. They don't pencil on their own. (For a concrete example of this, look to the US and their Low-Income Housing Tax Credits.)
So once again, the moral of this story is that the best way to think about the value of development land is to think of it as "whatever money is left in the pro forma once you've accounted for everything else." Because sometimes there will be money there, and sometimes there won't be.
Photo by Jannes Glas on Unsplash
One common mistake that people make when it comes to development pro forma is assuming that feasibility is easily attainable. It's not. In fact, it's best to think of a pro forma as a fragile object that is liable to break if not handled properly. So to that end, here's a non-exhaustive list of things you may want to keep in mind when trying to both forecast and create the future as a developer:
As a starting point, you're safer assuming that your pro forma isn't going to work. If the numbers look too good to be true or even just really promising -- especially at the outset -- then there's a good chance they're wrong. You've likely missed things. Be weary if it feels too easy, especially in our current market, where very little works.
Cheap land isn't enough. Just because your land cost feels cheap, it doesn't mean that your development project will end up being feasible. There are instances and entire markets where even free land isn't enough. You might actually need a negative land value. Meaning, a subsidy is required to reach feasibility. This is the case with affordable housing.
Drill down into as many line items as possible. Back-of-the-envelope math -- where you just plug in a few cost per square foot assumptions -- is fine for an initial screening. But if you're really serious, you need to get deep into the weeds. Run through the entire process in your mind and think about what might happen, and go wrong. Even with this, you will still miss things.
Stress test your assumptions. What happens if the city asks you to do X? What happens if the local councillor comes at you with Y? Can your fragile object support them, or will it shatter to pieces? The sensitivity of your fragile object to various stimuli will help you decide whether you want to do the project or whether there's simply too much risk.
Ultimately, real estate development is a creative act. You'll need to come up with creative solutions, and then you'll need to will your project to life. This is one way to tell that you're on the right path. It needs to feel really hard. So if your pro forma also feels this way, then there's a higher probability that you're narrowing in on something close to reality.
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 development charges were just increased and now you need to offset those new costs by finding savings somewhere else.
This isn't a perfect analogy, but imagine you were shopping for a new car. You might start out by wanting the fully-loaded version, but then you see the price and realize you can't afford it. So you decide to start trimming features and add-ons until you get to a place where you feel more comfortable. I would imagine this happens with cars, and I'm not sure it's right to point to that person after and say, "oh my god, I can't believe you cheaped out and didn't buy the fully-loaded version."
At the same time, I think it would be perfectly reasonable to argue that you don't need to spend a lot of money to (1) care deeply about the work that you do and (2) have taste. You can't fight the economic realities of the world, but you can care and you can be creative. And I don't think it's too much to advocate for these things.