The One-Page Offtake Brief GPU Buyers Need From a Site Owner

A site owner says they have 20 MW available.

The GPU capacity buyer asks a few follow-up questions.

How much of that is actually energised? Is the transformer already installed? Can equipment reach the building from a truck pad? What cooling architecture exists? Who has authority to sign an offtake agreement? When can a Supermicro HGX B300 deployment actually draw power?

Suddenly, “20 MW available” becomes much harder to interpret.

The first job of an offtake brief is to remove that ambiguity. A serious buyer should be able to read one page and understand whether the site deserves technical diligence.

1. Lead with usable interconnect MW

Do not start with acreage, renderings, or the theoretical ultimate buildout.

Start with power.

State the interconnect capacity, then break it into what is already usable and what still depends on construction, utility work, transformers, switchgear, permitting, or another dependency.

A buyer needs to distinguish between:

Contracted interconnect: capacity supported by the utility or interconnection agreement.

Energised capacity: power that can be physically delivered today.

Deployable capacity: power that can realistically support the proposed compute infrastructure once site-level electrical constraints are considered.

Those numbers may be different.

The brief should also identify voltage, relevant substation or interconnection details, and whether any of the stated MW is already committed to another tenant or project.

Avoid phrases such as “up to 50 MW” unless you immediately explain how much exists at each stage.

GPU buyers are trying to determine whether a site can support a real capacity requirement. If they cannot establish the first usable block of power from page one, the opportunity will move down the queue.

For context on how compute buyers think about infrastructure requirements, review Pacific’s reserved GPU capacity offering.

2. State the transformer and electrical path

Interconnect capacity does not automatically mean rack-ready capacity.

The brief should identify the electrical path between the utility connection and the compute deployment.

That includes the status of major transformers, substations, switchgear, distribution equipment, and any known procurement or construction dependencies.

If a transformer is already installed, say so.

If it is ordered, state that separately.

If it still needs to be procured, do not describe that capacity as immediately deployable.

You do not need to turn the one-page brief into an electrical engineering package. The goal is to expose the critical path.

A buyer should be able to see:

utility power → transformation → site distribution → compute load

and understand which pieces already exist.

This matters particularly for dense GPU systems such as Supermicro HGX B300 infrastructure, where the buyer is evaluating the whole deployment path rather than simply whether a parcel has an interconnection agreement.

3. Show whether hardware can physically reach the site

GPU deployments involve large, heavy infrastructure.

The brief should state whether the site has practical equipment access.

Include truck-pad or loading access, dock or grade-level entry where relevant, equipment staging space, freight restrictions, and any physical constraint that could complicate delivery.

A site can have excellent electrical characteristics and still become operationally awkward if transformers, cooling equipment, racks, or Supermicro HGX B300 systems cannot be moved into position without substantial additional work.

The buyer does not need a logistics study yet.

They need to know whether the basic route exists.

A simple line such as “full-size truck access to dedicated loading area, direct path to deployment hall” is far more useful than a general statement that the site is “data-centre ready.”

If the site is being considered for a broader compute deployment, Pacific’s colocation work provides the right frame: power, physical infrastructure, and usable compute need to line up as one system.

4. Describe the cooling reality

Do not write “cooling available.”

State what exists.

Identify the current cooling architecture, the capacity it can support, and whether additional cooling infrastructure is required for the proposed GPU load.

If the building was designed for lower-density workloads, say so.

If there is space and infrastructure for a higher-density cooling system but it has not yet been installed, distinguish that from an operating system.

For Supermicro HGX B300 deployments, the buyer will ultimately evaluate cooling against the intended rack density and system architecture. The one-page brief does not need to solve that design.

It should make clear whether cooling is:

existing, expandable, planned, or absent.

That classification prevents a buyer from assuming that available power automatically translates into deployable GPU capacity.

5. Name the decision-maker and the contracting path

A surprisingly common problem is technical diligence progressing faster than commercial authority.

The buyer spends time with a developer, broker, operator, or project lead, then discovers that another entity owns the site, controls the interconnect, or must approve the agreement.

Your brief should identify who owns the relevant asset and who can sign.

Include the contracting entity, the commercial decision-maker, and any major third-party approvals required before an offtake agreement can become binding.

If the site is held through an SPV, state the relevant entity.

If utility consent, landlord approval, lender approval, or another condition materially affects the transaction, flag it early.

GPU buyers move faster when they know the person in the room can actually transact.

Turn the site into something a capacity buyer can evaluate

Pacific Intelligent Technologies, Inc. works with site owners to package power, infrastructure, and deployment constraints into an offtake opportunity a GPU buyer can diligence quickly.

Book 30 minutes with Harper to review the site.

6. Give one date for when power is actually usable

End the brief with the question buyers care about most:

When can compute begin drawing power?

Do not substitute a construction milestone, utility date, equipment delivery date, or estimated completion date unless that event directly corresponds to usable electrical capacity.

If different blocks of power become available at different stages, show them separately.

For each block, state the MW and what must happen before it is usable.

For example:

Block A: energised and available subject to final deployment work.

Block B: dependent on transformer installation.

Block C: future expansion dependent on additional utility or site work.

Do not invent certainty where it does not exist. Buyers would rather see a clearly stated dependency than discover one halfway through diligence.

The one-page brief should compress the opportunity into a single chain:

real MW → electrical path → physical access → cooling → contracting authority → usable power date.

FAQ

How long should a GPU offtake brief be?

One page is enough for initial buyer screening. Detailed electrical drawings, utility documents, site plans, and technical studies can follow during diligence.

What is the most important number to include?

Usable MW and the date that capacity can actually support compute. A large theoretical interconnect number is less useful if the first deployable block is unclear.

Should a site owner include future expansion capacity?

Yes, but separate existing or committed capacity from future capacity that depends on additional work. Buyers need to know which MW they can underwrite today.

Does the brief need a complete GPU deployment design?

No. The site owner should provide enough information for the buyer to assess whether a deployment is plausible. Detailed system design can follow once power, cooling, logistics, and commercial control pass initial diligence.

The essence of the brief is compression. A GPU buyer needs to understand what power exists, what infrastructure connects it to compute, who can transact, and when the site becomes genuinely usable. Everything else belongs in the diligence room.