Infrastructure

Twelve years getting land ready to build on.

865 sites across 23 states, carried from search ring through due diligence, entitlement, permitting, and construction handoff. Three denials in twelve years of public hearings. Still delivering sites under contract today.

What the work covers

Search ring to shovels, and everything that stalls in between.

01

Identification and feasibility

Search-ring analysis, raw-land availability, tower inventory, zoning feasibility, restrictions, and the recommendation that says build here or do not.

02

Land records and title

Ownership research, landowner identification and outreach, title review, easement verification, and curative work when what is recorded is not what was agreed.

03

Entitlement and zoning

Permitting strategy, applications, jurisdictional negotiation, code compliance, and testimony before the body that decides.

04

Environmental and geotechnical

Phase I and Phase II environmental assessment, NEPA and SHPO review, geotechnical investigation, and land survey management.

05

Utilities and airspace

Utility coordination, power engineering, and FAA and FCC coordination where structures and airspace interact.

06

Lease and handoff

Ground lease negotiation, renewals and extensions, construction drawing and constructability review, and a handoff construction can build from.

How a site actually goes

A dot on a map, and eighteen months of reasons it might not work.

A carrier decides it needs coverage in a particular place and draws a circle. That circle is the whole brief. Somewhere inside it there has to be a piece of ground whose owner will lease, whose title is clean, whose soil will hold a tower, whose jurisdiction will permit one, and which is close enough to power and fibre to be worth building. Nobody knows which parcel that is, and roughly six candidates get researched for every one that gets built.

The work is finding out, in an order that spends the least money before the first thing that can kill the site kills it. That order is the craft. Ground is cheap to evaluate and expensive to survey. Zoning feasibility is a phone call and a code section; a variance is nine months. So the questions that can end it get asked first, and the expensive work only starts on ground that has survived them.

Then the parallel phase. Survey, title, environmental, geotechnical, and the utility and structural coordination all run at once, against one schedule, because running them in sequence adds a year nobody has. Each comes back correct on its own terms, and the failures are almost always in the seams: a survey that assumes an easement footprint the title work has not confirmed, a geotechnical report that answers a question about a tower position the design has since moved.

Then the public part. An application, a staff review, and a hearing in front of a body that can say no in a room open to the neighbours. That is the only step that cannot be quietly redone, and it is the one everything upstream was protecting.

Then the handoff, which is the part that determines whether any of it was worth doing. Construction gets a package, or construction gets a phone call, and a project that lives in one person’s head has to be rediscovered by whoever inherits it, usually under schedule pressure.

Where the method started

Ten to fifteen locations, before getting in the car.

It was not the first engagement. It was the second. UScellular gave a new firm a shot on the strength of my business partner’s history with them, and handed us a block of sites across Wisconsin and Nebraska. That was a real risk on their part, and it is the engagement that made me build the way I build.

Stated as I remember it: around 68 sites. That figure is recollection rather than a count, and the archive cannot separate that first block from the years of work on the same program that followed it, so I am not going to present it as exact.

There was already a working process, and it was a good one. What I found on those sites is that it could not carry that volume in the form I inherited. So I modernized it: online land records, property owner searches, GIS mapping against parcel shapefiles, and my own records rather than a chain of recollection.

The first version was still mostly legwork. Map the search ring in Google Earth, pick out the parcels that actually fit the zoning and permitting requirements, research contact information for the owners, then drive around until I could find them.

What it became is the thing worth describing. Letters go out to owners before any field work. The letter says what it is: a national carrier needs coverage, we need a small amount of land, the carrier requires at least three properties to compare, and it chooses on coverage, constructability and lease terms. No one is told their parcel has been selected when it has not. The research is carried far enough that I arrive with ten to fifteen candidate locations already identified, ranked, and checked against the ordinance. The drive stops being a search and becomes a confirmation.

The desktop work behind that is specific. Plot the ring and the existing tower inventory. Pull the jurisdiction’s code and search it for the words that matter, then write down the setbacks, separation requirements and anything unusual or slow. Map the separation requirements if there are any. Find the parcel GIS, check it against the assessor for owner detail, and export its layers where they can be exported. Review topography and floodplain. Then pin the candidates against zoning, setbacks and access.

And screenshot every map before leaving. Rural parcels do not have service, and a plan that depends on connectivity you will not have is not a plan.

Field work still changes things, and it has to be allowed to. You see the slope, the driveway, the neighbour’s sightline, the thing no record shows. Flexibility is not optional in this work. But arriving prepared is the entire reason one person could carry that much at once.

Then I taught it. To employees and to contractors. That is where the written workflows and the permitting playbooks came from: a method is only worth having if it survives being handed to somebody else.

Even if a system or a workflow already exists, I am wired to examine how it might be improved or scaled. Some parts of work will always be a challenge. That is why it is called work. But there are often parts that can be made easier, if you are willing to invest some time in your knowledge and in the tools you use.

The move, both times

  1. 2016. The expensive resource was a car and a day. So the research moved in front of the driving, and one person covered a portfolio.
  2. 2024. The expensive resource was people transcribing site attributes by hand, hundreds of times, against a 60-day deadline. So the assembly moved in front of the analysis, and a pipeline covered the portfolio.
  3. Same move. Find out what you can before you spend the thing you cannot get back, and leave judgment for the part that actually needs it.

What that became in 2024

The hearing record

The hearing record.

Zoning boards, plan commissions, and boards of adjustment, several hundred times across twenty-three states. Three applications were denied. Two of those were decided politically rather than on the merits of the application.

A hearing is where every earlier shortcut becomes visible. The record is not a reflection of persuasive testimony; it is a reflection of what was resolved before anyone walked into the room: title clean, easements verified, ordinance read, staff consulted, findings prepared, objections anticipated.

Stated precisely: the denial count is exact: three. “Several hundred hearings” is a considered estimate rather than a counted figure, and it is not presented as anything firmer than that.

All three denials, described

Reading the brief

The cheapest lease was not the answer. The ordinance was.

A carrier ran a programme to get off its most expensive lease sites. The brief was a leasing exercise: find cheaper colocations and move onto them. That is a sensible instruction and it was written by people who knew what they were doing.

Working the first tranche, I found that several of the jurisdictions imposed no zoning or permitting requirement at all. Where that is true the arithmetic inverts. The cheapest long-term position is not a cheaper lease. It is the client owning the asset, because the barrier that normally makes building slower and more expensive than renting simply was not there.

So I took it back to them rather than executing the programme as written. They agreed, and the scope changed from relocating onto other people’s towers to building the client’s own.

The transferable part is not the answer, it is where the answer came from. Nobody had read the ordinances before the programme was scoped, because at scoping time it looked like a real-estate question. It was a zoning question wearing a real-estate question’s clothes, and the only way to find that out was to read the code for the specific jurisdictions rather than reason about the category.

Why this is the same discipline as the rest

  1. Source of truth. The controlling ordinance for each jurisdiction, not the assumption behind the programme.
  2. Structured operating data. Cost of ownership against cost of tenancy, per site, with the entitlement barrier priced in rather than assumed.
  3. Workflows and controls. A review permitted to conclude that the assignment is the wrong assignment.
  4. Tested and handed off. The programme’s own scope changed, which is the only evidence that matters here.

Programs delivered

Portfolio work, not one-off sites.

The counts and markets are exact, and the four programs below account for 825 of the 865 sites. What I built for these clients stays unattributed, which is why the documentation standards and the relocation automation appear elsewhere on this site without a name on them.

713

UScellular network program

713 sites across 19 states. Largest markets: Wisconsin 130, Iowa 81, Oklahoma 80, Nebraska 79, Maine 59, Kansas 48, Illinois 43, Missouri 42, North Carolina 41. Scope spanned new raw-land builds, network modernization, lease-cost reduction relocations, colocations, decommissions, and ground lease renewals and extensions.

48

FirstNet rural build program

48 sites across Illinois and surrounding Midwest markets, including the easement curative work that recovered a parcel other reviews had written off as unleasable.

44

TowerCom portfolio

44 sites across Georgia, Maryland, Tennessee, and Kentucky, supporting colocations and relocations for AT&T, T-Mobile, Verizon and Gogo.

20

Craig & Associates, first client, 2016

20 Verizon small cell, DAS, and heterogeneous network sites in the Tampa market, the engagement the practice started from.

·

Colocation coordination

Ongoing coordination across American Tower, SBA, Crown Castle and Horvath portfolios, alongside carrier project managers, area managers, and tower company development leads.

Worked examples

Four of these, in full.

317 packages, 60 days

A relocation portfolio with 60 days to return feasibility and permitting recommendations across it. Not achievable by hand. 317 packages across 316 sites, delivered on a pipeline built in three days, and the point where this practice turned into a software practice.

Read it

The hearing record

Several hundred hearings and three denials, with all three described rather than counted. One I called as non-conforming before we filed. Two were decided on political rather than regulatory grounds at sites that met every published requirement.

Read it

Two contested outcomes

An eighty-acre parcel made unleasable by an easement recorded far wider than it was agreed, recovered across an international border. And a permit application approved over the objection of a tower company’s retained outside counsel.

Read it

Documents that became the standard

Two national carriers independently took documentation built for internal workflow and made it the standard their other vendors had to meet. Reviewing other vendors’ submittals against those forms then recovered sites their reviews had ruled out.

Read it

Leading the work

A bench, not a solo practice.

Team

Recruited, trained and managed full-time staff and subcontractors, and brought site acquisition specialists from their first search ring through to carrying sites independently. I came into this discipline the same way, unpaid, so I know what the gap between the two looks like.

What made that repeatable was writing it down. The raw land and colocation workflows, the permitting playbooks, the state regulatory references and the document templates all exist because a team executing against a standard beats a team asking whoever has done it before.

Founder-operator of the development firm, with ownership transferred in December 2024. The delivery work continues under contract.

Technical bench

Directed multidisciplinary consultants and vendors on every site: land survey, title, environmental, geotechnical, architecture and engineering, and power engineering. I do not perform those disciplines. I hold one schedule across all of them and read their results against each other.

The coordination is the discipline. A site does not stall because one consultant is slow. It stalls because nobody owns the sequence between them, and each report is correct on its own terms while the contradiction sits in the space between two of them.

Client-facing throughout. Carrier project managers, area managers and tower company development leads, reported to on portfolio status, schedule risk and what was being done about it.

What the work produces

What is actually in a site file.

The archive holds 16,874 files across 3,278 folders. Counted by document name, this is the shape of it.

Counted by matching document names across the archive on 2026-08-27. Approximate at the boundaries in both directions: a file named for its site rather than its type is not counted, and one document can match two categories.
Document typeFilesWhat it settles
Lease, amendment, option, letter of intent1,360Whether you can use the ground
Feasibility analysis923Whether to spend anything at all
Zoning applications and submittals673Whether the jurisdiction will allow it
Title, commitments, deeds, vesting641Who actually owns it and what is recorded against it
Search rings and mapping621Where the candidate parcels are
Hearing materials, decks and exhibits434What the deciding body sees
Survey, ALTA and boundary411Where the lines really are
Construction drawings and site plans330What gets built
FAA and FCC coordination230Whether the airspace and spectrum permit it
Environmental, Phase I and II, NEPA, SHPO215Whether the ground and its history permit it
Ordinance and statute excerpts189The standard the decision is measured against
Photo logs123What the site looked like on the day

The archive holds 89 presentation decks I built myself, including the variance and special-use presentations taken to city councils and boards. That is what “I build the materials I present” means in file terms.

It also holds the reference library the team ran on rather than asked about: state regulatory folders for eleven states, the raw land and colocation workflows, a permitting notes standard, a ground lease extension amendment template, and separate photo-log standards for candidate, colocation and rooftop sites.

On the method: these are counts of files whose names match a document type, not a hand audit of 16,874 documents. They are honest about the shape of the work and they are not exact. Where this site gives an exact figure, it says so, and this is not one of those.

Source of the figures

The figures were counted, not recalled.

The figures on this page were not recalled. They were counted by enumerating a project archive that runs from November 2006 to the present. A full enumeration in July 2026 returned 16,795 files across 45.4 GB, of which 13,875 sit under dedicated site folders. 865 sites have their own folder, 493 carry five or more working documents, and 225 carry twenty or more.

A second enumeration on 27 August returned 16,874. The difference is not an error in either count. The archive is still growing, because the work is still going on.

The archive is why the counts here are stated as figures rather than approximations, and why client names, markets, and supporting documents can be produced on request.

Read the case studies

Contact

Land, permitting, and the work that gets it built.

jwatson@thinksynergy.biz