Run a Better Power-Contingency Deal Desk

When power availability depends on utility work, equipment delivery, or a customer-funded energy plan, your deal desk needs to manage the dependency—not hide it in a footnote. The job is to give buyers a contractable path to capacity while protecting your sales team from promises operations cannot keep.

Why does a normal deal desk fall short?

A conventional deal desk is built to check discount levels, term length, credit, legal redlines, and maybe a standard implementation schedule. That works for a mature facility with commissioned capacity. It breaks down when the thing being sold is a sequence: substation work, a transformer slot, a generator package, a utility milestone, a commissioning window, then customer turn-up.

In that situation, the commercial team can accidentally turn a planning assumption into a delivery promise. It usually happens innocently. An AE says, “We expect to have it in Q4.” A proposal turns that into “available Q4.” Procurement reads it as a committed service date. Then an interconnection study changes, a switchgear shipment moves, or site work meets a permitting delay, and the account is suddenly a recovery project.

The market is giving buyers plenty of reason to inspect those dependencies. Riot Platforms’ lease of 191 MW of critical IT capacity at Rockdale includes a phased deployment: the first 96 IT MW are slated for December 2027, with full deployment targeted for June 2028 (Foley & Lardner). The important lesson is not the scale of that transaction. It is that deployment timing is part of the commercial product.

Your deal desk should treat every power-linked opportunity as its own operating plan, with named assumptions, owners, evidence, and decision dates.

Which deals need the power-contingency process?

Do not force every renewal or available-suite sale through a heavy approval process. That creates internal resistance and teaches sellers to work around it. Trigger the process when a proposal includes any of the following:

• capacity not yet commissioned or not yet energized;
• utility upgrades, transmission work, or a new interconnection;
• customer-funded electrical infrastructure or a power procurement arrangement;
• a phased handoff where later capacity is material to the buyer’s business case;
• density or cooling requirements that depend on equipment still to be installed;
• a right of first offer, expansion option, or reserved adjacent footprint.

That last item matters more than many teams realize. QumulusAI’s metro Atlanta agreement covers an initial amount of capacity plus a right of first offer for additional contiguous capacity (Business Wire). Expansion rights are useful, but they are not the same thing as delivered capacity. Your CRM stages, proposal language, and contract exhibits should make that distinction impossible to miss.

What should the deal desk require before a proposal goes out?

Require a short power dependency sheet. One page is usually enough if it is maintained honestly. The AE owns getting it started; engineering, development, and operations own the underlying facts.

At minimum, capture the proposed IT load, the facility and electrical configuration needed to support it, the current status of the power source, and the exact milestone that permits customer service. Then separate facts from forecasts. “Utility agreement executed” is a fact. “Utility will complete work by March” is a forecast unless the relevant agreement makes it otherwise.

The sheet should also name the commercial exposure. Ask plainly:

• What can we safely contract today?
• What is conditional?
• What event converts the condition into a firm delivery commitment?
• What happens if that event slips?
• Who pays for incremental infrastructure, carrying costs, or a temporary solution?

This is where marketing and sales often need a gentle correction. Do not call a site “power secured” because the team has a credible path. Use precise language: “in-service capacity,” “contracted utility capacity,” “capacity subject to [identified] completion,” or “customer-funded expansion under development.” The buyer will eventually ask what you mean. Better that they hear a clear answer before legal gets involved.

How should you structure the customer conversation?

Bring the power dependency sheet into the discovery and solution-design conversation early. Do not wait for a redline. Buyers with serious deployment schedules can handle a conditional path; what they cannot handle is discovering one after they have selected your site internally.

Walk through the sequence in operational terms. Explain the handoff point, required customer decisions, long-lead equipment, acceptance criteria, and the dates on which each party must act. If the customer needs initial capacity before the full build is complete, propose a phased plan with separate service commencement dates and acceptance tests.

There is a broader shift behind this. Qcells and Microsoft have described an approach in which the customer funds power needed for its operations and new data-center demand is paired with new energy resources (Qcells). Mid-market operators should not pretend they can copy that model wholesale. But they can learn from it: customers increasingly expect a transparent conversation about who funds, owns, and bears risk for power-enabling infrastructure.

For the right buyer, offer choices rather than a binary yes or no. A customer may choose an earlier, smaller deployment; pay for a dedicated upgrade; accept a later expansion milestone; or take capacity at a different facility. A choice architecture gives the account team something constructive to sell when the ideal configuration is not ready.

How do you keep sales from overcommitting?

Start with stage gates that map to real evidence, not seller confidence. An opportunity should not enter “proposal” merely because the buyer likes the site. For conditional capacity, require technical validation and an approved dependency sheet. It should not enter “commit” until the customer has acknowledged the critical assumptions and the deal desk has approved the commercial fallback.

Use a small approval group: sales leadership, operations or engineering, finance, and legal. Development should join where construction or utility work is material. Their role is not to rewrite the pitch. It is to answer specific questions fast enough that the seller does not improvise.

Make one person accountable for updating the milestone record after signature. This is frequently missed. The deal desk approves a sound transaction, then disappears, while the account team continues telling the customer an old date. A monthly review of conditional commitments is usually more valuable than another generic pipeline meeting. Review milestone movement, customer dependencies, spend already committed, and communications required in the next few weeks.

What belongs in the contract?

Legal language should reflect the operating reality, but it should not become unreadable. In practice, the cleanest agreements separate firm, currently deliverable service from future conditional capacity. Define the prerequisites for the future phase, document each party’s obligations, and specify what occurs if a prerequisite is not met.

That may include a revised service date process, a termination right after a defined delay, a capacity substitution mechanism, credits where appropriate, or a customer option to reduce the later phase. The right answer depends on your economics and the customer’s use case. What matters is that the fallback is negotiated while both sides still want the deal.

Be especially careful in jurisdictions where project visibility and local commitments are becoming more formal. Pennsylvania’s executive order on data-center development requires binding commitments and local approval before state permit review for covered applications, and it prohibits NDAs for those proposals (Commonwealth of Pennsylvania). Even if your facility is elsewhere, the direction is clear: vague development claims create commercial as well as regulatory risk.

Common questions

Should we avoid selling conditional capacity altogether?

No. Conditional capacity can be a strong product when the path, dependencies, and remedies are explicit. Refusing to discuss it may leave buyers with no workable growth plan; presenting it as firm capacity will cost you trust.

Who should explain utility and construction risk to the buyer?

The account executive should own the relationship and commercial narrative, backed by a technical lead who can answer detailed questions. Do not send a seller into a power-risk discussion with a slide deck and no operator in the room.

Can a right of first offer count as pipeline?

It can count as a qualified expansion opportunity, but not as contracted delivered revenue or firm capacity. Track it separately, with the exercise conditions and the infrastructure required to serve it.

What is the first thing to change?

Add a mandatory dependency sheet to proposals involving uncommissioned, phased, or utility-dependent capacity. It forces the conversation your team needs to have before a forecast becomes a promise.

Where this leaves you

A power-contingency deal desk will not make transformers arrive faster or utility processes simpler. It will help you sell credible paths, choose risk deliberately, and keep customers informed before a date becomes a dispute. GridReach helps data center and energy companies turn expertise like this into qualified pipeline.