This is an example scenario, not a customer deployment. It shows how x101 capabilities apply to this kind of work. There are no customer-attributed figures on this page; outcome numbers are published only once they are measured in a live deployment. For deployments running today, see the production case studies.

01

The challenge

Deciding where to build next means combining data that lives in different places and different formats. The analysis is expensive enough that it happens quarterly, which means the answer is often built on assumptions that have already moved.

  • The analysis is a project, not a question

    Bringing grid, traffic, demographic, planning and cost data together takes weeks of specialist effort, so it happens on a fixed cycle rather than when a decision is needed.

  • Assumptions age before the decision lands

    By the time a study is finished, grid upgrade schedules, competitor sites and demand patterns have shifted, and re-running the work is not practical.

  • Reasoning is hard to interrogate

    An investment committee sees a ranked list, but tracing why one site outranks another means going back to the analyst who built the model.

  • Local rules are easy to miss

    Planning constraints, grid connection limits and site-specific restrictions live in documents that no spreadsheet reads.

02

What x101 does

The same platform capabilities that run in production elsewhere, applied to this work. Each step below is standard platform behaviour, not custom development.

Step 01

Every input in one place

Grid capacity, traffic and demand data, demographics, existing and competitor sites, planning records and cost data are read together rather than merged by hand.

Step 02

Asked in plain language

A planner asks the actual question, such as which five locations in a region give the best return within the current grid constraints, and x101 works out what to gather.

Step 03

Candidates ranked, with reasons

Locations come back ranked, each with the factors that drove its position, the forecast utilisation behind it, and the constraints that would need resolving.

Step 04

Local rules read, not assumed

Planning documents, connection policies and site restrictions are read as source material, and any blocking clause is surfaced with the passage that says so.

Step 05

Re-run when anything moves

A changed grid upgrade date or a new competitor site is a follow-up question, not a new study, and the ranking updates with the reasoning refreshed.

Step 06

Ready for the committee

The output is an investment-grade summary with its sources cited, so the decision and its evidence travel together.

Governance runs across every step. Each request carries the permissions of the person asking, actions follow the policies you set, high-impact steps wait for human approval, and every decision is written to a signed, replayable record.

03

What gets measured

These are the measures a deployment of this scenario is held to. Figures are published on this page once a live deployment has produced them.

Baseline and target

Agreed before the first week

  • Elapsed time from question asked to ranked recommendation
  • Number of scenarios evaluated per investment decision
  • Utilisation of new sites against the forecast that justified them
  • Analyst effort per site evaluated
How rollout works

A first use case live in weeks

  • Inside your perimeter. Your cloud, your access controls and your data, from day one.
  • Works with what you run. x101 reads the systems you already have, as they are today.
  • Paired with a solutions engineer. Someone who has deployed this before works alongside your team.
  • Measured against your baseline. The numbers that matter are agreed up front and reported against.