Research note (plain English) - May 12, 2026
What it takes to get a data center built — and where software helps
Building a data center isn't one job. It's eight. Software helps with three of them today. The other five still depend on hiring experienced consultants who charge by the hour. This walks through what each of the eight layers is, why three have software and five don't, and what's changing in 2026 that finally makes the rest tractable.
- Layers
- 8
- Has software
- 3
- No software yet
- 5
The stack
Eight layers. Three have software. Five don’t yet.
- 1
Siting and parcel intelligence
Has softwareFinding land that is zoned, powered, water-available, and politically viable for a data center.
Players: Paces, Enverus, LandGate
- 2
Transmission and interconnection math
Has softwareModeling grid capacity, substation headroom, withdrawal risk, and queue position before signing a power deal.
Players: Nira, Pearl Street, Enverus
- 3
Load-queue deduplication
No software yetDistinguishing real vs. speculative load requests inside an interconnection queue — the phantom-queue problem.
Currently served by: Specialist consultants
- 4
Regulatory filing drafting
No software yetProducing CUP, SUP, air permits, interconnection docs, NEPA, Title V, stormwater, and FAA paperwork that every site needs.
Currently served by: Specialist consultants
- 5
Live docket intelligence and air-permit math
No software yetTracking FERC, PUC, ISO, and state DEQ rulemakings in real time and translating them into decision-grade economics.
Currently served by: Specialist consultants
- 6
Behind-the-meter generation economics
No software yetDeciding whether to build on-site power vs. wait for firm transmission, and at what size, fuel mix, and uptime tier.
Currently served by: Specialist consultants
- 7
Approval-outcomes corpus
No software yetA queryable history of what got approved, what got denied, under what conditions, in which jurisdictions.
Currently served by: Specialist consultants
- 8
Project management and collaboration
Has softwareWorkflow, task tracking, document management, external coordination. Horizontal tools work; no DC-specific product yet.
Players: Procore, Smartsheet (horizontal)
The gap
Why some layers have software and others don't
When a developer builds a data center, they aren't just buying land and pouring concrete. They are getting permission from utilities, state regulators, county boards, federal environmental agencies, and air-quality boards. Each of those approvals has its own paperwork, deadlines, math, and history of past decisions across thousands of similar projects.
For decades, the only way to handle those approvals was to hire specialists — engineers, environmental attorneys, former agency staff — who had spent years learning how each piece worked. They charged by the hour because the work required human judgment that software couldn't replicate. The regulatory documents themselves were thousands of pages of unstructured text spread across dozens of agencies and 50 states. That's why the first three layers (where the data is structured and the workflow is repeatable) got software early, and the middle five did not.
Two things changed. First, AI language models in 2023 and after got good enough to read those unstructured documents and extract the relevant rules cheaply and accurately. Second, the post-2025 regulatory landscape introduced new rules — ERCOT Batch Zero, PJM PCLR, EPA Title V updates, state-level zoning changes like Loudoun County ending data-center by-right approval in March 2025 — that even the experienced consultants haven't fully digested yet. That combination finally makes some of the consultant-only work tractable as software, while leaving the parts that require political judgment and site-specific negotiation to the people who already do it well.
Cliff read
What Cliff is building
Cliff is building software for five of the eight layers — specifically the regulatory and permitting layers (3, 4, 5, 6, 7) that don't have software today.
These are the layers where reading regulatory text, tracking what's changing in real time, and remembering what's worked in similar past projects matter most. They're also where mistakes are most expensive — a permitting cascade that breaks 18 months into a $500M project can wipe out the entire margin.
Cliff doesn't replace the layers that already have software (siting, transmission math, project management). Those work fine. Cliff focuses on the gap, and partners with the specialist consultants who hold the site-specific judgment software can't replicate.
Site readiness
Want to understand a specific layer better?
Each of the five gap layers has its own dynamics. The other research notes go into each one with concrete public-record examples.