A land leader at a regional builder in the Southeast told our team something this month that I keep coming back to. In each of his markets, he has one acquisition person. The builders he competes with in those same markets often have four to eight.

He wasn't complaining. He was describing the job. Budgets are tight, every expense gets a second look, and the land his company will need two years from now still has to be found today.

I hear a version of this on almost every call. A developer in Northern Virginia runs sourcing through word of mouth, local knowledge and a virtual assistant working 40 hours a week. A developer in Raleigh tracks his pipeline in Excel and wants to go from working 20 parcels to 200. These are experienced people who know their ground. What they don't have is more hours.

The limit is coverage, not skill

Every parcel takes real work. You pull the zoning code, check flood maps and wetlands, figure out who actually owns it, and find a way to reach them. With only so many hours, the work naturally narrows to what reaches the desk: broker calls, listings and the corners of the market you already know.

That isn't a mistake. It's the only rational way to work with the tools land teams have had. But it means the hours available set the size of the pipeline.

Where the hours actually go

When a new customer walks me through how their team works today, I usually end up drawing the same picture: a lot of tools, and a person in the middle moving information between them.

This month our team heard that stack described again and again. Mapping in one tool and a manual database in another. Off-market lists in one platform, texting in a second and skip tracing in a third. County GIS in a browser tab, zoning in a PDF and the pipeline in a spreadsheet. A division of a national builder talked with us about replacing roughly four platforms with one.

Most land teams I work with piece answers together across nine or more tools that were never built to work together. The subscriptions are the cost everyone sees. The bigger costs never get a budget line:

• Re-keying. Every time information moves between tools, someone types it again.
• Context switching. One parcel can mean five or six tabs, and a real share of the week goes to finding information instead of deciding.
• History that's hard to build on. When notes live in inboxes and spreadsheets, last year's research gets done again from scratch.
• Slower decisions. When an answer takes days to assemble, the deal can move on before it arrives.

A one-hour stack audit

Here's an exercise I share with teams who want to see where their time goes.

1. List every tool your land team touches in a typical week, including the free ones and the spreadsheets.
2. Write down the decision each one supports: zoning, ownership, constraints, yield or pipeline.
3. Mark every handoff, each place information has to move from one tool to another.
4. Ask where history lives. If you needed last year's notes on a parcel, where would you find them?

Most teams find two things: several tools answering parts of the same question, and a lot of handoffs that exist only because the tools don't talk to each other.

How to do it in Prophetic

Here's how the teams I work with cover a whole market without adding hours.

1. Define what you build once. Set up a search by buy box: development type, acreage, zoning, use, and limits on flood and wetland coverage. Run it across your whole market, a drawn area or a set of ZIP codes.
2. Save it, so the market comes to you. A saved search keeps watching and flags new parcels that match, so you aren't rerunning the same hunt every week.
3. Clear the noise early. Hide parcels you've ruled out so they stay out of every future result. The list you work from gets better every week.
4. Decide from the parcel, not the research. Each result already carries a plain-English zoning summary with citations to the code, plus the constraint layers, so the first look is a decision instead of a research project.
5. Keep everything on the project. Save the parcels worth pursuing to a project, where notes, contacts, tasks and files stay together, and every parcel you've touched stays useful to the team.

The result is a real change in capacity. Teams have gone from 50 parcels per month to 1,000+ per month, with the same team, and individual users regularly work 5,000+ parcels a month.

That doesn't replace judgment. One experienced person still decides which deals are worth pursuing. It gives that person their whole market to apply that judgment to, instead of a slice.

If you're covering a market on your own, that's the conversation I'd most like to have. Pick a market you know well, and we'll run it end to end with you. Or bring one parcel you know well, and see everything Prophetic knows about it.

[See it on your market]