Frameworks
The reasoning behind the recommendation.
Each framework below is the structure we actually use in engagements. Published in full, with the trade-offs they impose, so a leadership team can apply them without us.
Operating beliefs
Six Working Principles
How we frame any product, pricing, AI or infrastructure question before proposing an answer.
Methodology
Strategizes Infrastructure Decision Framework
Whether, where and when to commit capital to a data center program.
Diligence structure
How We Evaluate Infrastructure Investments
What evidence has to exist before an infrastructure commitment is defensible.
Operating beliefs
Six Working Principles
Decision it serves
How we frame any product, pricing, AI or infrastructure question before proposing an answer.
Where it is applied
These are not values. They are the assumptions we test first, because most poor decisions we are asked to unwind trace back to one of them being ignored.
Pricing is a product decision
Packaging, entitlements and value metric are design choices. Handing pricing to sales alone converts a product problem into a discount problem.
Technical debt is a business decision
Debt is a financing choice with an interest rate. The question is not whether to carry it, but which debt you are willing to service and for how long.
Roadmaps are expressions of trade-offs
A roadmap that offends nobody has not chosen anything. The useful artefact is the list of things deliberately not being done and why.
Infrastructure decisions compound over time
Power, site, topology and vendor commitments set the cost floor for a decade. Reversibility is worth paying for early and almost unbuyable later.
Metrics influence behaviour
Teams optimise what is measured, including the parts you did not intend. Choose the metric that survives being gamed.
Strategy is resource allocation
Intent expressed without moving people, capital or attention is a statement, not a strategy.
Trade-offs we accept
- Applying these principles usually narrows optionality on purpose — fewer initiatives, funded properly.
- They tend to surface organisational disagreement early, which is uncomfortable but cheaper than discovering it after commitment.
Methodology
Strategizes Infrastructure Decision Framework
Decision it serves
Whether, where and when to commit capital to a data center program.
Where it is applied
A six-phase sequence used on owner-side infrastructure work. Each phase exists to make a specific commitment reversible for as long as possible, and to make the point of no return explicit when it arrives.
1. Understand demand
Load shape, growth assumptions, density and tenancy. Demand stated in MW is usually a placeholder until it is stated as a ramp.
2. Validate infrastructure
Power availability and timing, land, water, connectivity and grid interaction tested against the deployment date, not the brochure.
3. Assess technical risk
Topology, resilience, cooling strategy and constructability reviewed independently of the parties selling them.
4. Evaluate commercial viability
Capex and opex bounds, energization risk, contract structure and the cost of delay quantified as a range, not a point.
5. Support the investment decision
A defensible recommendation with the conditions under which it stops being correct.
6. Govern delivery
Owner-side controls through design, procurement, construction and commissioning so decisions survive execution.
Trade-offs we accept
- Phases two and three often slow a program by weeks and remove far more expensive rework later.
- The framework will sometimes conclude that the right decision is not to proceed on the current site or timeline.
Diligence structure
How We Evaluate Infrastructure Investments
Decision it serves
What evidence has to exist before an infrastructure commitment is defensible.
Where it is applied
Six evaluation areas we work through on hyperscale and enterprise diligence. Each is judged on evidence and timing, not on assurances.
Power & utilities
Capacity, firm dates, redundancy path and tariff structure. Timing risk is usually larger than price risk.
Land & site
Title, zoning, environmental constraint, expansion envelope and constructability.
Connectivity
Route diversity, carrier presence, latency to the served demand and long-term fiber economics.
Infrastructure readiness
Cooling strategy against local climate and density, water position, and equipment lead times.
Commercial viability
Cost per MW, ramp economics, contract exposure and sensitivity to delay.
Governance
Decision rights, stage gates and reporting that make the program auditable while it is still running.
Trade-offs we accept
- No site scores well on every area; the work is deciding which weaknesses are financeable and which are structural.
- Evidence-based diligence takes longer than vendor-supplied packs and is the only version that holds under investment committee scrutiny.
Next step
Before committing capital, changing pricing, or restructuring product teams — let's talk.
We will be direct about whether an engagement is the right answer, and what scope would make it useful.