One project, several buyers
A contact at the owner does not tell you who controls your package.
A data center sale rarely sits inside one company.
The owner may approve the site, budget, and technical standards. That does not mean the owner writes every specification or issues every purchase order.
The utility or power developer can affect whether the schedule is viable. The design team can set the accepted equipment. The GC or EPC can release packages. Trade contractors can control installation and field access. Commissioning and operations can decide whether the system is accepted and supported.
Your sales plan needs the project, package, phase, and decision owner.
invested in data centers worldwide during 2024
That spending is split across owners, utilities, designers, builders, equipment suppliers, and service firms.
IEA, 2025projected share of U.S. electricity use from data centers by 2028
Power availability can delay or stop a project before equipment packages are released.
U.S. Department of Energy, 2024of ERCOT's tracked large-load requests are from data centers
In Texas, utility and interconnection teams belong in the sales plan from day one.
ERCOT and PUCT, 2026
Power can decide the schedule
If the power plan slips, the campus slips.
A seller who maps only the owner and contractor can miss the utility, interconnection, generation, and transmission decisions that set the project schedule.
The practical rule
Build the sales plan around the project package, not the corporate org chart.
Who can affect the sale
The buyer changes with the work
A data center campus is delivered by several organizations. Each one can control a different part of the sale.
The National Institute of Building Sciences identifies owners, designers, engineers, contractors, suppliers, trades, and commissioning agents as participants in project information delivery through handover.[4]
That same structure appears in the buying process.
Owner and capital
Approves the site, budget, technical standards, and delivery model.
Power and site
Secures land, utility capacity, generation, permits, and interconnection.
Design
Writes the basis of design, equipment requirements, and approved makes.
Procurement and construction
Sets package strategy, bids, contracts, schedule, access, and change control.
Commissioning
Runs testing, closes deficiencies, and recommends system acceptance.
Operations
Owns reliability, service, spares, lifecycle cost, and expansion.
Specifications are written before the RFQ
By bid day, many technical choices are already fixed.
The basis of design, electrical topology, cooling approach, controls, resiliency requirements, and approved makes can narrow the field before procurement issues a package.
A strong owner relationship does not replace access to the engineer, EPC buyer, trade contractor, commissioning lead, or operator.
Who matters at each stage
Track the open decision, then find the person who controls it
Titles alone are not enough. The person who matters in design may not control procurement, installation, or acceptance.
Concept
Who mattersIs the site viable?
Land, power, capital, permits, and schedule.
Owner sponsor, development, utility, and energy teams.
Design
Who mattersWhat will be specified?
Topology, cooling, controls, resiliency, and approved makes.
Owner engineering, architect or engineer, and technical leads.
Procurement
Who mattersWho buys the package?
Bid list, commercial terms, long-lead release, and contracts.
EPC or GC procurement, project controls, and technical approvers.
Construction
Who mattersWho controls installation?
Site access, sequence, safety, quality, and changes.
Owner PM or CM, GC or EPC, trade leads, and package leads.
Commissioning
Who mattersWho accepts the system?
Test scripts, deficiencies, integrated testing, and turnover.
Commissioning authority, quality, and owner operations.
Operations
Who mattersWho owns service and expansion?
Reliability, maintenance, spares, response, and lifecycle cost.
Critical facilities, operations, sourcing, and portfolio leaders.
One contact is not coverage
Your first contact may not own the purchase.
An owner engineer may guide the specification. An EPC buyer may issue the order. A trade contractor may choose the installation method. Commissioning may control final acceptance.
Evidence rule
Do not put a person on a project chart without project evidence.
A relevant employer or title can start research. It does not prove that the person controls a decision on the project.
The RFQ is often late
The field can narrow before vendors see a bid
By the time an RFQ arrives, the site, power approach, basis of design, approved makes, package strategy, and long-lead priorities may already be set.
The best time to build coverage is while those decisions are still open.
ERCOT now studies qualified large-load projects of 75 MW or more in batches, with developers, utilities, generators, advocates, and other stakeholders involved. That is one example of how early the project takes shape before equipment packages reach the market.[3]
Start when the project becomes visible, not when procurement sends the package.
Keep the project history
Do not lose the pursuit when the lead changes
Data center projects pass from development to design, construction, commissioning, and operations.
NIBS recommends interim information deliveries at conceptual design, design development, construction documentation, and the in-use phase instead of waiting for one final handover.[5]
Sales teams often lose context at the same points. The new account owner gets contacts and notes but not why each person mattered, which decision was open, or who could make the next introduction.
A new lead should inherit the phase, package, named roles, evidence, warm paths, gaps, and next actions.
Most CRM handoffs preserve
- Company and contact records
- Meetings, notes, quotes, and opportunities
- Pipeline stage and account owner
A project handoff must also preserve
- The current phase and package
- The roles that control each open decision
- Confirmed evidence, assumptions, and gaps
- Warm paths, next actions, and owners
The four facts every pursuit needs
For every target contact, answer four questions
Project. Phase. Authority. Path. Without all four, the contact is only a name.
Project
Which campus and package?
Name the exact site, building, system, or work package.
Phase
What decision is open now?
Design, bid, construction, commissioning, service, or expansion.
Authority
Who can specify, buy, install, or accept it?
Tie the person to a specific role in the package.
Path
Who can make the introduction?
Name the introducer, reason to engage, and next action.
A relevant title is not enough. Tie the person to the project and package.
Company-level relevance can start research, but it should not be presented as confirmed project involvement.
What ExecGraph does
Build the pursuit around the project
ExecGraph builds project-specific pursuit charts for data center vendors. It combines project evidence, company roles, contact history, and warm paths, then shows where the team has coverage and where it does not.
Start with the exact project
Select the campus, phase, category, owner, and known contractors before adding contacts.
Map the roles that control the package
Identify who can specify, approve, buy, install, accept, or support the work.
Separate evidence from relevance
Show confirmed project evidence separately from broader company and industry experience.
Keep missing roles visible
Do not force a weak match into the chart. Show the gap and assign the next research action.
The output is a working list of who to reach, why they matter, how to get there, and what still needs to be verified.
Keep one project record
NIBS frames owner requirements across planning, design, construction, and operations. The pursuit should keep the same project context across those handoffs.[6]
The sales advantage
Enter before the specification, bidder list, and delivery plan are fixed
The data center market is growing, but growth alone does not create access.
Vendors still need to know which project is real, what package is forming, who controls the open decision, and how to reach that person before the window closes.
That is the purpose of a project-first pursuit.
Track the exact project. Find the open decision. Reach the role that controls it.
Common questions
Data center project coverage
Why is the project the account in data center sales?
Because one project can spread decisions across the owner, utility, design firm, general contractor, trade contractors, commissioning team, and operator. The company paying for the project may not control every specification, bid, installation decision, or acceptance test.
Which companies can influence a data center package?
The mix depends on the phase and package. It can include the owner, developer, utility, architect or engineer, EPC or general contractor, specialty trades, equipment suppliers, commissioning authority, and critical-facilities operator.
Why should power teams be in the pursuit map?
Power availability, interconnection timing, transmission needs, and generation strategy can determine whether the site and schedule are viable. Those decisions can be made before equipment packages reach the market.
When should a vendor start mapping the project?
Start when the site, power plan, design team, contractor team, or delivery schedule becomes visible. Waiting for the RFQ can mean entering after the specification, bidder list, and package strategy are already set.
How does ExecGraph handle uncertain contacts?
ExecGraph separates confirmed project evidence from general company relevance. A relevant title can trigger research, but it is not shown as confirmed project authority without supporting evidence. Missing roles remain visible as gaps.
Map one live project
Bring the campus, phase, and package. We will show the likely roles and missing coverage.
ExecGraph organizes the known companies, decision roles, project evidence, warm paths, and open gaps into one pursuit chart your team can review and correct.