Every land team I talk to has the same quiet line item: engineering reports on sites that were never going to work.
A traditional feasibility or yield study typically costs $3,000 to $10,000 and takes weeks. That's money well spent on a site you're serious about. It's money lost on a site that falls apart the moment someone accounts for the wetlands along the back property line.
This month, a regional builder in the Southeast told our team they were looking for a way to avoid costly engineering studies on sites that wouldn't pencil. They're working under strict spending limits, and every study they skip is budget they can use somewhere else. A national builder's division in New Jersey made the same point from the other direction: they want early feasibility so their engineering spend goes to the right sites.
You should engage an engineer on every site you're serious about. Preliminary yield isn't engineering. The real question is which sites earn that study, and you can usually answer it with four questions, in this order.
1. What does the zoning allow?
Zoning tells you which uses are permitted by right, which are conditional, and the standards that come with them: density, minimum lot size, setbacks, height, floor area ratio, parking and open space. A surprising number of sites fail right here, and it should take minutes, not a call to the planning office.
2. What would it take to get approved?
A land investor asked our team a question this month that belongs in every first look: what does the zoning allow, and what has actually been approved on this land? They aren't the same thing.
At the screening stage, you aren't entitling anything yet. You're sizing the path. Can the project you have in mind be built by right, or will it need a rezoning, a variance or a planned development approval? Each step adds time, cost and risk, and some jurisdictions move much faster than others.
It's also worth checking whether a previous owner already secured approvals, like an approved plat or a planned development. Approvals already in place can shorten the path considerably. They often carry conditions or expiration dates, though, and the rules vary by state and municipality, so confirm current status with the jurisdiction and your counsel before you count on them. And zoning itself changes, so what a parcel allows today may not be what it allows next year.
3. Can it be served?
This was the question our team heard most this month. A land broker in Texas called utilities the critical gap in his San Antonio diligence. A developer in Raleigh said utility data was one of the first things he compared across platforms. A custom builder in North Florida described utility and permitting answers scattered across several city departments.
Utilities are hard because the providers are fragmented, because a line on a map tells you where a main runs but not whether it has capacity, and because some providers still work from PDFs and paper maps. In the end, a capacity or will-serve letter is what a committee needs, and that only comes after a conversation with the provider.
For industrial, energy and data center land, "can it be served" usually means power. An industrial sourcing team in Charlotte, a developer in the Sun Belt moving into data centers, and a solar developer in Georgia filtering for parcels near specific 115kV and 230kV transmission lines all started their searches from power, then worked outward.
4. What does it actually yield?
Once you subtract the constraints (wetlands, flood zones, slopes, setbacks, stormwater and easements), acreage on paper and acreage you can build on often part ways.
A builder in the Northwest was pursuing a 20-acre parcel. A preliminary analysis showed only 13 acres were actually developable, and the team caught 7 acres of unbuildable land before the offer, not after the close. A constraint you find before the offer is a negotiating point. One you find after closing is a loss.
How to do it in Prophetic
Here's how teams run all four questions on a site in minutes.
- Start from the cited zoning summary. Open the parcel and read the plain-English zoning summary: permitted and conditional uses, density, setbacks and other standards, with citations to the actual code so you can check the source.
- Size the approval path. Note on the project whether what you'd build works by right or would need a rezoning, variance or other approval, and record any approvals a previous owner already secured, with the date and the approving body.
- Check the constraints and service layers. Review flood zones, wetlands, slope, soils and schools on the parcel, plus utility and transmission line layers where they're available. Mark anything unknown as unknown, so it becomes a question for the provider instead of an assumption.
- Run a preliminary yield. Generate a lot or unit layout on the net developable area, with roads, open space, stormwater and, for multifamily, parking accounted for.
- Hand off the winners. For the sites that pass all four questions, export the preliminary site plan so your engineer starts from your work instead of from scratch.
Feasibility in seconds, not weeks, replacing $3,000 to $10,000 engineering reports on the sites that don't deserve them, changes how a team spends its week. One habit I always recommend: label preliminary yield as preliminary everywhere it appears, including every committee memo.
If you'd like to see the four questions on a market you know well, we'll run it with you. Or bring a single parcel you're weighing, and we'll walk through all four together.
