For Land Directors: 'Sites Assessed Per Head' Is the Only Metric That Matters Now

Two land teams in the same region. The same headcount on the org chart. The same five people coming in on a Monday morning.

One team assessed nine sites that month. The other team assessed three.

The three-site team has the same calibre as the nine-site one. The people are as experienced. From a round of interviews you'd hire from either bench. The thing that separates them, the difference between a land team that compounds and one that treads water, is throughput per head. And most directors aren't measuring it.

This is the metric that decides which land teams will still be in the game in five years.

Why headcount stopped being the answer

For most of this industry's history, the answer to "we need to assess more sites" was "we need to hire." That equation worked for a long time. It stopped working somewhere in the last decade, and the small and mid-sized land teams that have been disappearing without comment are the proof.

Hiring is dear, the ramp is long, the management drag is real, and the unit economics of a five-person team adding a sixth have become hostile in a way they weren't twenty years ago. The land teams winning are the ones whose existing people are pushing more sites through the same week. Headcount stopped being the variable.

Sites assessed per head is the cleanest expression of that. It strips out the noise of team size, market conditions and headcount cycles, and asks the only operational question that matters: how much site work is each person actually putting out?

Most teams don't track this because the answer is uncomfortable. The team that feels overworked usually has the lower number. Effort isn't throughput.

The hidden ceiling lives below the talent line

If you walked into your land team this afternoon and asked your best buyer where the hours go in a typical first-pass appraisal, the honest answer would unsettle you.

Roughly four-fifths of the time goes on gathering inputs: pulling location data, planning history, ownership, constraints, comparable evidence. Roughly a fifth goes on the actual judgement that makes an appraisal valuable. Your highest-paid analytical hours are spent doing administrative work. The reason is structural. The inputs live across a dozen places, and someone has to assemble them.

The same pattern repeats across the week. Board notes get rebuilt from scratch because there's no living record. Planning updates need manual monitoring because nobody set up the alerts. And approaches end up tracked across spreadsheets, inboxes and memory because the team hasn't standardised the record. Each of those is an hour. Add them up across five people across four weeks and you have your missing six sites.

The ceiling here is leverage. Talent has nothing to do with it.

What changed (and why most teams haven't moved yet)

The reason "sites assessed per head" is becoming the metric now, rather than ten years ago, is that for the first time, the input-gathering layer of the work can be compressed.

The industry hasn't caught up to this yet. Most land teams are running 2019 throughput on 2025 deal flow, and burning out as a result, without making it a board conversation. The early movers (and there are early movers) are pulling away precisely because the gap between "ten sites a month" and "twenty sites a month" stopped requiring a hire.

What it does require is that the input-gathering layer of every workflow (appraisals, approach tracking, planning monitoring, pipeline freshness) runs in the background rather than consuming your team's most expensive hours.

The number to measure (and what to do with it)

If you want to test where your team actually sits, the exercise is straightforward.

Take any month in the last year that wasn't unusual. Count the sites your team assessed to first-pass standard. Divide by the number of land people you had. You now have your sites-per-head figure for that month.

Do the same exercise for the team you compete with most closely on bids. If you don't know the answer, ask. People talk in this industry, and the number is often startling.

If your figure is below two sites per person per month, the bottleneck is input assembly. Almost guaranteed.

If your figure is below one and a half, the bottleneck is also your team's morale, because you're burning out the people you can least afford to lose.

The fix lives in the input-assembly tax. Remove it from every workflow that imposes it.

What the throughput teams are actually using

The land teams hitting six, eight, ten sites per head per month have a system underneath the work that holds the firm's site memory in one place: every approach, every appraisal input, every planning update, every consultant note. That memory makes the next workflow start at minute thirty rather than minute one. There are no heroics; just less re-work.

That's the category we built Harold for. A property-trained system configured around your firm's sites, pipeline and documents, designed to compress the input-gathering layer of every workflow your team runs. It gets a first-pass appraisal to the point of judgement in twenty minutes instead of two hours, inside the tools your team already uses.

What to do about it

If you're prepared to look honestly at the sites-per-head number in your own team, book a 30-minute walkthrough and we'll model the lift on a real workflow you choose. Bring an appraisal you'd normally have your best person spend half a day on. We'll show you what that day looks like when the input-gathering is already done.

If you're not yet ready for that, calculate your number this week. The figure itself is the conversation. The teams that compound from here are the ones who can answer it.