J-BoxPlain answer. A feasibility package a lender or partner can underwrite covers the utility path and energization date, fuel and fiber, water and permitting, a basis of design built on the site's real constraints, a phased capacity plan and a financial model tied to a specific commercial structure. Anything missing from that list is a question, not a risk the capital can price.
Why screen before you validate
Feasibility work costs money and takes months. Spending it on a site that fails a two day desktop screen is the most common way owners waste the first hundred thousand dollars of a project. The gated approach, screen first and validate only what clears, is not caution. It is how the feasibility budget gets spent on sites that can actually close.
What the Validate gate produces
A complete package has seven parts. Each one answers a question a lender, a partner or a tenant will ask, and each one has a document behind it.
| Component | The question it answers | What sits behind it |
|---|---|---|
| Utility path and energization date | Will there be power, how much, and when | Load inquiry, study results, will serve position or interconnection agreement, with conditions |
| Fuel and generation | What bridges or backs up the grid | Gas supply and pipeline capacity, generation permitting, emissions path |
| Fiber | Can the tenant connect | Carrier routes, build cost and timeline, diversity |
| Water and permitting | Can the facility be built and cooled here | Water source and availability, zoning, entitlement, environmental review status |
| Basis of design | What exactly is being built | Capacity, density, resilience, cooling type and expansion plan, built on the constraints above |
| Phased capacity plan | How megawatts arrive over time | Blocks, dates and the power each block depends on |
| Financial model | Does it work, and for whom | Capital, revenue and returns tied to one commercial structure: lease, shell or turnkey |
The order matters. The design has to follow the power, not the other way around. The model has to follow the design and the structure, not a template.
Common gaps that kill underwriting
- A design sized before the utility study. The facility assumes a load the utility has not confirmed. Everything downstream is a bet.
- "Available power" with nothing behind it. No inquiry, no study, no letter. See the first gap.
- A model with no structure. Returns that do not say whether the owner is leasing land, delivering a shell or operating a platform cannot be checked.
- Tenant assumptions without a tenant. Density, timeline and lease terms that no one has asked for.
- Water as an afterthought. The cooling design and the community conversation both depend on it.
- Permitting as a date instead of a process. Entitlement, environmental and air permits each have a path and a timeline.
Each gap is a question. Capital does not price questions. It waits for answers or walks.
How tenants read the same package
A serious tenant asks the same questions a lender does, in a different order. It starts with density, cooling and energization date, then moves to the structure and the counterparties. A package built for underwriting serves the tenant conversation without changes, which is why JBox builds one package and shares it under NDA with both.
From package to data room
The feasibility package becomes the core of the project data room: control documents, utility, land, design, economics, correspondence and status, organized the same way on every project. The approval matrix, the decision log and the integrated schedule are added as the project moves to Package and Deploy. The owner approves everything in it; JBox maintains it.
Questions & answers.
The desktop screen takes days. Full validation depends on the utility's study timeline and can take months. The package is built as the answers arrive, not at the end.