The decision at a glance
- Turn the territory list into investigate, monitor or qualify decisions.
- Separate an account relationship from an evidenced package purchasing route.
- Keep the original milestone date, unresolved question and next responsible person visible.
Use this guide to turn a territory list into a defensible next-conversation shortlist. Separate an account worth researching from a project worth forecasting; record the specific evidence question that would move it forward.
Choose the next conversation before assigning pipeline value
| Shortlist entry | Reason it belongs | Next action |
|---|---|---|
| Research an account | Your service territory and a supported role relevant to your offer | Assign one question for a useful discussion |
| Monitor a development | A named phase or decision that could change fit or timing | Specify the original record to check next |
| Qualify a pursuit | A defined package and evidenced purchasing route | Confirm scope with the responsible party before forecasting |
Work through the two Abilene records
The existing Stargate Abilene preview and the separate Microsoft-campus preview share a city and developer. Their public sources describe different campus and phase claims. Use the Texas comparison linked below to keep their evidence separate. T1, T2
For BD, keep the development and the account relationship on separate lines. A named developer is a research starting point; it does not establish who buys your package. Ask which campus and phase the conversation concerns before applying another record’s timing.
Keep a useful next-conversation record
| Field | Record before the next review |
|---|---|
| Account fit | Territory, work package and reason the account is relevant |
| Evidence | Named site/phase, supporting public source and its original date |
| Unresolved question | The role, decision or buying route you still need to establish |
| Next action | Responsible person and your follow-up task date, separate from any project forecast |
Use the existing free evidence worksheet to retain source references and unknowns. Membership adds available participant research, supporting source collections, project history and tracker CSV export; depth varies by record. Export is a working input for your own shortlist, not proof that a project is procurable. R6, R2
Choose a resource for the account question
| Account task | Resource to evaluate |
|---|---|
| Qualify individual U.S. developments | Data Center Radar |
| Analyze supplier relationships | DC Byte Supplier Analytics D1 |
| Compare international markets | datacenterHawk H2 |
| Find facility and company context | Baxtel B2 |
Use supplier-relationship analytics or broader market intelligence when that is the actual account question. Use Radar for the evidence and unresolved questions behind individual U.S. developments. The resource comparison is an editorial assessment, not a verified feature ranking.
Take the next step with your own territory
Open the Texas and Illinois worked examples, then select an existing public preview in your territory. Bring one unresolved question into the next review. The membership page explains current plans and links a real public research example; the free digest requires email confirmation. R6, R2, R5
Put the research into practice
- A Data Center Ally alternative for construction teams: Evaluate discovery and qualification needs before changing the research tools behind an account plan.
- Project research for recruiters: See how a workforce-focused team can qualify the same account signal without assuming hiring demand.
- Open the existing Stargate Abilene preview: Keep this campus and its initial-operation scope distinct.
- Open the separate Microsoft-campus preview: Read the named campus and recorded site-preparation evidence before choosing your package question.
- Compare the real Texas phase claims: Use the bounded sample and source dates to distinguish separate Abilene campuses and the El Paso construction report.
- Apply the Troy regulatory gate: Keep preparation, an adopted restriction and an extension recommendation separate.
- Build your territory shortlist: Record the decision, missing evidence and next responsible person using the existing worksheet.
- Keep approval evidence separate: Match each decision, condition or withdrawal to its authority, site and work scope before updating an account plan.
- Establish the purchasing route: Separate a reported participant from buying authority, a current invitation and your next useful conversation.
These workflows help frame the next evidence check. Project and source review dates keep their separate meaning.
Your next project review
See the research before choosing.
Use the member research example to assess one account question. Keep unsupported roles and procurement claims unresolved.
Get the free weekly digest. Confirm your email to subscribe.
Sources and research method
Vendor statements describe advertised capabilities. Fit recommendations are our analysis of the reader’s task. A public-preview check establishes what Radar displayed on the review date; project event dates retain their separate meaning. Compare current access, licensing and relevant records before subscribing.
- DC Byte Supplier Analytics, opens in a new tabVendor description of project filters, company profiles, supplier relationships and benchmarking.
- datacenterHawk company profile, opens in a new tabCompany description of international market coverage, supply, demand and pricing research.
- Baxtel homepage, opens in a new tabPublic facility research, industry news and data center real estate services.
- Radar current membership and real public research example, opens in a new tabLive membership destination and real public example checked October 26, 2026. Current pricing/terms govern; no customer outcome is inferred.
- Radar research methodology, opens in a new tabLive explanation of public previews, member research, dates and verification boundaries, checked October 3, 2026.
- Radar free weekly digest, opens in a new tabLive signup promise and confirmation requirement, checked October 3, 2026.
- Crusoe: initial Abilene phase live, September 30, 2025, opens in a new tabAlready-public source reopened October 26, 2026 for campus/phase comparison; not a new present-status certification.
- Crusoe: separate Microsoft Abilene campus, March 27, 2026, opens in a new tabAlready-public announcement used to distinguish the new campus from existing operations; later work and procurement remain separate checks.
New evidence or a correction? Contact Data Center Radar with the page and supporting source.