Process
Four steps, timed,
with the dependencies stated.
A desk that trades on accuracy should be exact about its own process. Response times below are published as targets with their dependencies, not contractual SLAs, and the boundary between our work and the downstream party’s is stated at every step.
The enquiry arrives structured
Most enquiries start in the Path Check, which asks the seven questions a provider’s enterprise team would ask and prefills the form with your answers. A direct enquiry works the same way — the form collects the same structure.
You receive: A reply that tells you whether there is a fit, and what is missing if not.
Timing
Reply target: 4 business hours
Dependency
Business hours: Sunday–Thursday, Riyadh time (AST, UTC+3). Depends on a complete enquiry — buyer, workload, blocker.
The Path Note
The Path Note is the working document. Your CTO reads the infrastructure facts; your counsel reads the regulatory frame; your deal desk reads the sequencing. It states what is provisional and who confirms each step.
You receive: A written, forwardable note: the route, the facts behind it with sources and dates, and the order of operations.
Timing
Target: about 48 hours, where there is a fit
Dependency
Depends on the enquiry being complete and the route being determinable from public rules.
The introduction
The receiving team gets the buyer context, workload class, residency expectation, timeline, and budget band — so the first call starts at the real questions rather than a qualification checklist.
You receive: A named conversation with the CST-registered provider or specialist that fits, framed by a readiness pack.
Timing
Follows the Path Note
Dependency
Depends on your go-ahead and the receiving team’s availability.
The downstream engagement
This boundary is deliberate and stated everywhere: Cloudi Arabia is the introduction and preparation layer. Nothing downstream is claimed, represented, or marked up.
You receive: A direct commercial relationship. Scope, delivery, SLA, pricing, and legal terms sit with the downstream party.
Timing
On the downstream party’s paper
Dependency
Entirely between you and the provider or specialist.
What we do not do
The boundary, in one list.
Counsel, procurement, and providers all ask; the answer is the same for each:
- Host, operate, or resell cloud capacity
- Issue compliance opinions, audits, or certifications
- Give legal advice or draft contracts
- Represent any provider’s SLA or pricing
- Take a percentage of the provider bill
The full statement lives in the terms.
The Path Note, outlined
What the written note contains.
This is the template outline — an actual Path Note is specific to one deal. Labelled template until the first published example exists.
Path Note · template outline
1 · The route
One sentence: the provisional path and why.
2 · The facts
Regions, provider classes, regulatory frame — each sourced and dated.
3 · Standing
Contracting standing as it applies to your deal: Etimad, CR/MISA, RHQ, local content.
4 · Order of operations
What happens first, what can run in parallel, what waits.
5 · The first conversation
Who it is with and what they will ask for.
6 · Boundaries
What is provisional, and who confirms each step.