Seven-step workflow
From a vague GPU requirement to a defensible cloud decision
Start with the workload, then preserve the evidence and assumptions behind the choice. Use the steps that fit your decision; you can request an independent review without completing the tools. Imported files and edits stay in the local tool tab. Export what you need before closing it and retain the matching JSON files. Inspect every export before sharing; use a redacted human-readable copy for discussion and keep machine-readable JSON intact for the validated handoffs.
Step 01
Define the workload and hard requirements
Record the workload, budget, region, memory, topology, interruption tolerance, and evidence requirements in the Decision Room. Use measured throughput where available; a benchmark for another workload is not a performance guarantee.
Define a workload brief →
Step 02
Build and retain an evidence-backed shortlist
Run the Decision Room against comparable published offers. Inspect sources, exclusions, unknowns, and revalidation triggers, then download the decision JSON for later imports. Published price and deployment eligibility do not prove live capacity.
Build a decision dossier →
Step 03
Challenge the workload economics
Use inference, training, batch, or cloud-vs-owned calculators to test throughput, utilization, scaling, and interruption assumptions. Keep storage, egress, support, taxes, and operational costs explicit; the normalized GPU rate is only part of total cost.
Choose a workload calculator →
Step 04
Ask for evidence tied to one candidate
After building a shortlist and completing the workload brief, select a candidate and export its provider evidence request. Retain the exact request JSON and inspect it before deciding to share it with that provider. If the brief includes details you cannot disclose, revise it and regenerate a matching request; keep the generated JSON intact. The site does not send requests. Guided response authoring needs this exact JSON, not only the Markdown or response template.
Create a scoped evidence request →
Open guided provider response →
Step 05
Review returned evidence against the original request
Import the retained request JSON and completed response JSON into the Decision Room buyer review. Inspect scope mismatches, expiry, unanswered questions, and commercial gaps. Export the reviewed Assurance handoff when useful; a ready result does not authenticate the provider or approve the purchase.
Review a returned response →
Step 06
Resolve total cost, risk, and human sign-offs
Import the decision JSON into the Assurance Room, then optionally import the reviewed provider handoff. Inspect proposals before applying them, document costs and evidence, resolve risk gates, and record the responsible human sign-offs. Export the matching Assurance JSON; contract, security, and procurement authority remain with your team.
Complete decision assurance →
Step 07
Revalidate the dated decision
Import the matching Decision Room and Assurance JSON dossiers into the Decision Monitor and replay them against the current public catalog. Inspect material changes, expired evidence, and sign-offs needing review. This is a local check when you run it: it does not schedule private monitoring or send alerts.
Revalidate a decision →