← All articles
Operator Playbooks November 2, 2026

How to Keep Power Claims Credible

power claimssales enablementcolocationgo-to-market

Your power claims stay credible when every number is tied to a specific site, delivery stage, dependency, and evidence file. Don’t let “available,” “contracted,” “under construction,” and “in study” become interchangeable just because a prospect wants a fast answer.

For colocation and wholesale teams, this is now a revenue discipline. A loose capacity statement may get you into an early call, but it can kill trust at technical validation, legal review, or the customer’s executive investment meeting.

Why are broad power claims failing more often?

The market has become much better at distinguishing a request from a commitment. Utilities themselves are drawing those lines in public disclosures, and your buyers are reading them.

Exelon, for example, reported about 11 GW of high-probability data-center load, while also describing another 23 GW in current or future cluster studies. It separately noted that roughly 45% of the high-probability load was backed by FERC-approved transmission security agreements and collateral (Exelon). That is a useful model: not all prospective load carries the same evidentiary weight.

A buyer may tolerate uncertainty. They will not tolerate discovering, after a proposal is issued, that the number they understood as utility-deliverable was actually a target contingent on a network upgrade, a study result, land control, equipment delivery, or an internal financing decision.

Honestly, “we have power” is no longer a helpful sales statement. It is the beginning of a set of follow-up questions:

  • How much can be delivered to this exact parcel or building?
  • On what date can the customer take the first meaningful block?
  • What has been executed, approved, ordered, or merely requested?
  • Which party owns each remaining dependency?
  • What happens if the primary delivery path slips?

If the account executive has to chase operations, development, and the utility team for answers every time, the deal will move at the speed of internal confusion.

What should a power claim actually contain?

Build a standard claim card for every market and major site. This is not a glossy data sheet. It is the controlled internal record behind every external statement.

At minimum, each card should include the sellable capacity, the earliest defensible service window, and the applicable configuration: utility supply, on-site generation, behind-the-meter arrangement, or a combination. Then add a plain-language status label that sales can use without reinterpretation.

We recommend four practical labels:

  • Operating: capacity is energized and commercially available, subject to the normal allocation and contracting process.
  • Committed: a defined delivery path is supported by executed agreements or approvals, with known remaining construction work.
  • In delivery: construction or procurement is underway, but the customer should see the milestones and schedule dependencies.
  • Prospective: capacity is being studied, requested, or planned. It is a market-development opportunity, not inventory.

The labels matter less than the discipline behind them. A “committed” claim needs a named agreement, counterparty, effective date, capacity block, and a responsible internal owner. An “in delivery” claim needs a schedule, critical path, and a clear explanation of what would change the date.

Portland General Electric’s disclosures illustrate why a capacity number must carry its timing and status with it. The utility said 473 MW of executed data-center contracts with five customers was under construction, while a separate executed contract for up to 420 MW was expected to energize in 2028 and reach full capacity in 2033 (Portland General Electric). Those are both meaningful commitments. They are not the same commercial claim.

Who gets to approve what sales says?

Put one owner in charge of power-message governance. At a mid-market operator, that may be the head of development, a commercial operations leader, or a senior executive who can resolve conflicts between sales urgency and delivery reality. It should not be an informal committee that meets after a problem appears.

Create a lightweight approval path based on claim risk. Routine statements drawn directly from an approved site card should be available to sales without further review. Claims involving a future in-service date, a utility upgrade, new generation, or a customer-specific power structure should require sign-off from the designated technical and commercial owners.

That approval should answer three questions:

  1. Is the statement factually correct today?
  2. Is it likely to be interpreted correctly by a nontechnical buyer?
  3. Can we show the backup when procurement, legal, or an engineering adviser asks?

The second question is the one teams miss. “Up to 100 MW available” may be technically defensible, yet still misleading if the first block is available sooner than the remainder, or if the number assumes a particular voltage, load factor, contract term, or infrastructure contribution.

Write the qualification into the sentence. It is usually shorter than the cleanup call later.

How do you give buyers proof without oversharing?

Create a proof pack with layers. The first layer is buyer-safe: a one-page capacity and timeline view, a diagram of the delivery architecture, and a short list of assumptions. The second layer is for serious opportunities under NDA: milestone schedules, relevant utility correspondence, interconnection or service-agreement excerpts, equipment-order status, and contingency plans.

Do not send raw internal project folders to prove you are transparent. That often creates more doubt, not less. Buyers need evidence that maps to their decision, not a thousand pages of engineering material without context.

A strong proof pack also separates the customer’s decision dates from your project dates. For example: by what date must the buyer reserve a block, complete diligence, sign a power agreement, or make a construction election to preserve the proposed schedule? This prevents a common late-stage argument where sales has described a date as fixed while development has assumed a customer decision that has not happened.

The need for this precision is growing because grid projects can have long and conditional paths. AEP disclosed agreements for a proposed 10.4 GW campus in Piketon, Ohio, where the broader project still requires approvals from PJM, PUCO, and FERC; its planned transmission lines also carry different target service dates (American Electric Power). Your prospects know this pattern. Show them which parts of your offer are real now and which approvals or build steps remain.

When should you update the message?

Update a site card whenever a material fact changes: a utility milestone moves, a contract is signed, equipment lead times change, a construction package is released, or a dependency becomes uncertain. Review every active card on a fixed cadence as well, because silence from a project team is not proof that the old claim remains true.

Then audit the places where old language lingers: proposal templates, broker briefs, web pages, conference slides, recorded webinars, and sales sequences. Marketing is often blamed for stale claims, but the harder problem is usually an old deck attached to an opportunity six months ago and forwarded internally by the buyer.

Keep a dated change log. If an account team needs to explain why a delivery window changed, they should be able to state what changed, when the company learned it, and what alternative is available. That is a far better conversation than pretending the earlier slide never existed.

Common questions

Can we market capacity before every approval is complete?

Yes, if you call it what it is and state the conditions plainly. Prospective capacity can start useful buyer conversations, but it should never be presented as equivalent to operating or committed inventory.

Should sales share utility documents with every prospect?

No. Give early-stage buyers a clear summary and reserve sensitive source documents for qualified opportunities under the appropriate confidentiality terms. The key is that the summary must faithfully reflect the source material.

What if a broker asks for one simple availability number?

Provide a headline number with a status and time qualifier, then offer the breakdown. A broker can work with a concise answer; they cannot defend an ambiguous one when their client’s infrastructure team starts diligence.

Who should own the final delivery date in a proposal?

The commercial owner should own the customer commitment, but the date must be approved by the delivery team that understands the critical path. Sales should not be left to translate construction risk alone.

Where this leaves you

The best power message is not the biggest number in the market. It is the number your team can explain, evidence, and stand behind when the deal reaches scrutiny.

GridReach helps data center and energy companies turn expertise like this into qualified pipeline.

Every article on this blog is reviewed by Joe before publishing.

Need pipeline, not just traffic?

GridReach builds demand-gen programs for data center and energy companies.

Book a 15-min strategy call