What Developers Look for in the First 30 Minutes of Site Evaluation
There's a version of site evaluation that takes weeks. There's also a version that takes 30 minutes.
Both exist. The question is knowing which one a site deserves — and being disciplined enough to run the 30-minute version before you commit to anything longer.
We've spent a lot of time watching acquisitions teams work through their site queues. Not in a formal research context — just alongside practitioners who were kind enough to let us observe how they actually move. What follows is a pattern synthesis: what experienced evaluators are doing in that first half hour, and why it works.
The first five minutes: orientation
Before opening any model, experienced developers orient themselves to the site's context. Not in a vague way — in a specific, structured way.
They're asking: What kind of deal could this be?
That means identifying the likely subsidy path almost immediately. Is this a market that supports 9% LIHTC, or does the income profile push you toward 4% with bonds? Is there a local soft loan program that changes the calculus? Does the location suggest any geographic targeting from the state QAP?
This isn't guesswork. It's pattern recognition built from doing enough deals in enough markets that the subsidy landscape starts to feel legible at a glance. For less experienced analysts, this is often the hardest part to systematize — and the step most likely to get skipped.
Minutes five through fifteen: the density and zoning check
Once there's a working hypothesis about the deal type, the next question is physical: Can this site support the density the deal needs?
This involves a quick zoning read — height limits, FAR, setbacks, parking requirements — combined with a rough unit count estimate based on site geometry. The math doesn't need to be precise here. It needs to be directionally right.
A 9% LIHTC deal in most markets needs somewhere between 30 and 60 units to reach the scale that makes cost per unit workable; any larger and you risk asking for too much capital. If a site can't get there under current zoning, that's not automatically a dealbreaker — but it opens a different set of questions about variance or rezoning that need to be weighed against the timeline and risk tolerance of the project.
Experienced evaluators also flag zoning mismatches fast. Not because they can't be resolved, but because unresolved zoning issues that show up late in a deal are genuinely costly. Better to surface them in minute ten than in month six.
Minutes fifteen through twenty-five: the rough feasibility math
Here's where a back-of-envelope model comes in — not a full underwriting, but enough math to know whether the deal is in the universe of possible.
For most affordable housing deals, the key variables at this stage are:
- Estimated unit count (from the density check)
- Likely program (from the orientation step)
- Rough land basis the deal can support (working backward from anticipated subsidy levels)
- Obvious cost flags (environmental history, access constraints, unusual site conditions)
The goal is a simple go/no-go signal: does this deal, under optimistic but not unrealistic assumptions, have a path to feasibility? If the answer is clearly no, the evaluation ends here. If it's a plausible yes — or even an interesting maybe — it earns more time.
Minutes twenty-five through thirty: the market and competitive check
The last piece of the 30-minute evaluation is context: what's happening in this specific market, and is this a deal that your organization can actually win?
For competitive LIHTC markets, this means a quick read on recent allocation patterns — what's been scoring well, what land basis comparable deals are running, whether there's local political support for affordable housing on this particular site.
For deals where land is being acquired in an open market, it also means thinking about competitive positioning. If a market-rate developer is also interested in this parcel, you probably can't win on price. Are there other dimensions — affordability commitments, relationships with the municipality, existing community support — that could differentiate your bid?
This is the step most analysts skip when they're moving fast. It's also the step that tends to explain why some deals look feasible on paper but fall apart in practice.
What this rhythm is actually doing
The 30-minute screen isn't a shortcut. It's a triage system.
Its purpose is to separate the sites that deserve serious investigation from the sites that would waste your team's capacity if evaluated any further. Done consistently, it dramatically changes the ratio of time your team spends on deals that have real potential versus deals that were never going to work.
The developers who are best at this aren't moving faster in a sloppy way. They're moving faster because they've built a consistent mental model of what good looks like — and they apply it before they open a spreadsheet.
Alpha Deal is built to support exactly this workflow — surfacing program eligibility, zoning constraints, and feasibility signals so your team can make smarter triage decisions, faster.