Engagement

From first call to cutover counsel — the stages of a System Amberpoint advisory engagement.

Advisory work follows a predictable path so your team knows what happens between the first call and the final memo. This page is the companion to our Cloud Migration Advisory offer.

Stages

  1. Inquiry and fit

    You describe drivers, estate size, and dates. We confirm whether advisory—not implementation staffing—is the right purchase. If we are a poor fit, we say so early.

  2. Paid discovery

    A short discovery locks scope, access, and the fixed fee for the main engagement. You receive a written statement of work before workshops begin.

  3. Working sessions

    Planning workshops and interviews with owners. Diagrams and decision logs stay shared; nothing important lives only in a private notebook.

  4. Artefacts and rehearsal

    Wave plans, cutover criteria, and rehearsal agendas. Where the engagement includes it, we observe a dry run and amend the runbook.

  5. Cutover counsel and close

    Optional presence during the first production move, then a close-out memo listing residual risks and owners on your side.

What you prepare

Named contacts, inventory of systems in scope, known hard deadlines, and permission for advisors to speak with the people who actually run releases. Incomplete inventories slow discovery more than any tooling gap.

What we will not do during an engagement

Replace your change-advisory board, approve production changes on your behalf, or keep working indefinitely under an open retainer without a fresh statement of work.

Primary action

If you already know you need migration counsel, open the flagship advisory page. If you are still shaping the ask, request a call and we will suggest assessment, workshop, or full advisory.