Clients often ask what they should prepare before working with us. The honest answer: the engagements that fly are the ones where the following arrive early. None of it requires technical skill to gather — it requires a decision that the project matters.
The onboarding checklist
- An executive sponsor and a decision-maker. One named person who owns the outcome and can say yes within days, not committees.
- A technical contact. Someone who knows (or can find) how your environment actually works today.
- Tenant and subscription details. Your Microsoft 365 tenant, Azure subscriptions, and current licensing — so we design for what you own.
- Scoped access, granted properly. We work through role-based, least-privilege access with your approval on every role — never shared passwords. Expect us to ask for read-level access first.
- A data inventory, even a rough one. What data you hold, where it lives, and what you consider sensitive. A spreadsheet is fine; honesty matters more than polish.
- Your regulatory position. Existing CNDP declarations or authorizations, sector obligations (banking, insurance, health, public), and whether you may qualify as an infrastructure of vital importance — this changes the architecture.
- Existing policies and past audits. Security policies, incident history, previous assessments — the map of what has already been tried.
- Your definition of success. The two or three outcomes that make this project worth it, in business language.
- Constraints we should respect. Budget ceiling, deadlines, freeze periods, languages your teams work in (we deliver in French, Arabic, and English).
- Thirty minutes a week. A standing slot with your sponsor. Small, non-negotiable, and the single best predictor of on-time delivery.
If gathering items 5 and 6 feels daunting, that is itself a finding — and a good reason to start with our free Governance Readiness Assessment, which turns “we’re not sure” into a scored, prioritized starting point. Then book a discovery call and bring the list.