Structured infrastructure consultation, booked under the right category.
Four consultation categories — platform architecture, marketplace onboarding, government pilot deployment, enterprise relocation programme setup. Five-step intake with timezone-aware scheduling. Each booking is logged into the engagement-desk register with a category-specific preparation brief.
Pick the category that matches your programme. The desk routes from there.
- CT.01Platform Architecture Session
- Used by
- Enterprises · universities · mobility operators · relocation companies
- Purpose
- System design · deployment posture · integration scope
- CT.02Marketplace Provider Onboarding Session
- Used by
- Moving companies · drivers · packing teams · storage partners
- Purpose
- Platform onboarding · compliance · service integration
- CT.03Government Pilot Deployment Session
- Used by
- Ministries · municipalities · transport authorities · education systems
- Purpose
- Pilot rollout · deployment mode · data governance
- CT.04Enterprise Relocation Programme Setup
- Used by
- Corporate HR teams · universities · NGOs · mobility coordinators
- Purpose
- Tenant setup · workflow configuration · provider routing
- 1
- 2
- 3
- 4
- 5
What kind of organisation is booking?
The engagement desk routes the request based on your organisation type.
Category routing
The consultation purpose drives the category — Marketplace onboarding routes to CT.02, pilot discussion routes to CT.03, enterprise rollout to CT.04; everything else routes to CT.01 Platform Architecture.
Architecture tier suggestion
The organisation type seeds an architecture tier suggestion (a ministry → L.05, an enterprise → L.04, a relocation company → L.03). Visitors override before submitting if their programme calls for a different tier.
Preparation brief
Each category surfaces its own preparation brief on the confirmation panel — the materials the desk asks visitors to bring to the session. Mirrors the engagement-preparation discipline of Big-4 advisory practices.