A complex energy deal is not mature simply because the customer wants it. The organization expected to deliver the project also has to reach its own conclusion that the opportunity is technically sound, commercially workable, operationally supportable, and worth committing resources to.
A complex deal has two decision systems moving at once. The customer must decide whether the project meets its operating needs and can pass its budget and approval process. The developer or utility must decide whether it can finance, deliver, and operate what it proposes. Both sides can favor the idea and still lack an agreement that works.
Commercial development sits between them. The work is not merely to persuade one organization to buy. It is to help both organizations develop enough confidence in the same project to make commitments that can actually be executed.
WORKING PRINCIPLE
The customer case and the internal case have to converge.
A project cannot survive on customer enthusiasm alone, and internal approval is meaningless without a credible customer decision. The opportunity becomes real when both sides can explain why the commitments make sense.
One opportunity, two approval systems
The customer may be asking whether the project improves cost, reliability, resilience, staffing, sustainability, capital efficiency, or operating flexibility. The supplier may be asking whether the project meets return requirements, fits existing assets, can be engineered and constructed, allocates risk appropriately, and can be operated for the promised term.
Those questions overlap, but they are not identical. A customer can prefer an option that creates unacceptable delivery risk for the supplier. A technically elegant solution can fail the customer's capital constraints. A commercially attractive transaction can create operating obligations that neither side has examined closely enough.
The commercial developer therefore has to understand both approval systems early. Waiting until the end to discover an internal capital hurdle, customer procurement barrier, engineering constraint, or contract requirement is one of the fastest ways to lose months of work.
The customer case must be strong enough to travel internally
The person who first engages the supplier is rarely the only person who will decide. The project may need to move from facilities to finance, from engineering to procurement, from a sustainability team to executive leadership, or from a local operator to a corporate capital committee.
That means the customer case has to be understandable beyond the initial champion. The rationale should survive when it is retold by someone who was not present for every technical discussion.
A mature opportunity can answer basic institutional questions: What problem are we solving? Why now? Compared with what alternative? What value matters most? What new obligations would this create? Who owns the risk? What happens if we do nothing? What approvals remain?
The internal case has its own stakeholders
Commercial teams can make the opposite mistake internally. They may assume that a promising customer opportunity will naturally attract support from engineering, finance, operations, legal, and senior management.
Those functions are not obstacles to the sale. They are responsible for different dimensions of whether the organization can responsibly make the commitment. Engineering needs to understand feasibility and design risk. Operations needs to understand maintainability and service obligations. Finance needs to understand returns, capital exposure, and downside cases. Legal needs to understand how obligations and remedies are allocated. Leadership needs to understand strategic fit and resource priority.
A commercial leader who understands those questions can bring the right functions into the opportunity at the right time rather than treating internal review as a late-stage gate to push through.
THE INTEGRATION TEST
Can each function see its concerns reflected in the project?
Alignment does not mean everyone evaluates the project the same way. It means the opportunity has been developed far enough that engineering, operations, finance, legal, commercial, and customer considerations fit into one coherent decision.
Translation is a commercial leadership skill
Different functions often use different language for the same underlying issue. A customer may describe reliability as peace of mind. Engineering may describe it as redundancy and failure modes. Finance may see avoided downtime or capital risk. Operations may see staffing, maintenance, and recovery time.
The commercial leader's job is not to replace those specialists. It is to connect their perspectives so that a concern raised in one part of the project is understood in the others.
That requires enough technical fluency to understand what changes the solution, enough financial literacy to understand what changes the economics, enough customer knowledge to understand what changes the decision, and enough organizational awareness to know who needs to be involved next.
Disagreement is useful when it appears early
Complex opportunities often become weaker when the commercial process suppresses disagreement. Teams want momentum, so inconvenient questions are deferred: Is the schedule realistic? Does the customer actually value this benefit? Can operations support the proposed commitment? Is the capital assumption defensible? What happens if load changes?
Those questions are not evidence that the project is failing. They are how the project becomes more robust. An engineering objection can reveal a better design. An operating concern can expose an unrealistic service promise. A financial challenge can force the team to improve the baseline. A customer's hesitation can reveal that the real decision criterion was misunderstood.
The expensive version of disagreement is the one that arrives after pricing has been promised, executives have been briefed, or contract language has been drafted around assumptions no one fully tested.
Internal sponsorship cannot substitute for customer evidence
A senior executive can decide that a market, customer, or technology is strategically important. That may justify attention, but it does not make an individual opportunity mature.
The customer still needs a consequential problem, a credible decision path, stakeholders willing to engage, and enough institutional commitment to continue the work. Without that evidence, internal enthusiasm can turn into repeated technical studies, proposals, and management attention that never converge on a transaction.
Strategic importance should influence how an opportunity is evaluated. It should not eliminate the need for qualification.
Customer momentum cannot substitute for internal readiness
The reverse is equally dangerous. A customer may be ready to move while the supplier has not resolved its own critical issues.
Perhaps the technical scope is still changing. Perhaps the organization has not allocated capital. Perhaps legal and commercial positions are not aligned. Perhaps a delivery team does not yet exist. Perhaps operating responsibility is unclear. Advancing externally faster than the organization can support internally creates promises that later have to be renegotiated.
Good commercial leadership manages pace on both sides. It keeps the customer moving without manufacturing commitments that the delivery organization cannot yet make.
The two decision paths need deliberate coordination
This is where matrix leadership becomes practical. The commercial leader may not directly manage the engineers, operators, lawyers, finance team, or customer stakeholders involved in the opportunity. Progress depends on influence, clarity, sequencing, and shared understanding rather than formal authority alone.
That means making dependencies explicit. What needs to be learned before pricing is credible? What customer commitment justifies deeper engineering? What internal approval is required before a term sheet is offered? Which contract issue could change economics materially? What decision has to happen first so that other work is not wasted?
The opportunity becomes more manageable when the team can see those dependencies as one development path rather than as separate workstreams.
A real deal is one both organizations can execute
The phrase “sold twice” can sound transactional, but the deeper point is about institutional alignment. Both organizations are deciding whether to accept a long-lived set of commitments.
The customer needs confidence that the project improves its position and can survive its internal decision process. The supplier needs confidence that it can deliver what is being promised on acceptable technical, financial, operational, and contractual terms.
Commercial development creates value when it helps those two judgments converge. The goal is not simply a signed agreement. It is an agreement that both organizations understood well enough to approve and are prepared to implement.