Skip to content

Switching delivery Changement de livraison

A client should not learn about a delivery change by having a bad week.

Most practices considering this are not starting from zero. They already deliver in-house or already use another vendor, and the real question is whether a transition can happen without the client feeling it.

Starting point

In-house today

Your own team currently handles this work directly. The usual trigger is a capacity ceiling, a language gap, or a service line — like Microsoft 365 stewardship — that keeps losing to more urgent tickets.

Starting point

Another vendor today

A different delivery arrangement is already in place. The usual trigger is language coverage, reliability, cost structure, or a contract term coming up for renewal.

What a careful transition actually requires

  1. Inventory the current state

    Name what is actually being delivered today, to which accounts, in which language, and by whom — before comparing it to anything new.

  2. Choose a defined slice

    Pick one account, one service line, or one time window rather than moving the whole book at once.

  3. Run it in parallel

    The new path handles the chosen slice while the existing one continues everywhere else, so nothing depends on a single cutover date working perfectly.

  4. Compare the returned work

    Read the notes that come back against your own quality bar before deciding the slice is ready to grow.

  5. Confirm client-visible continuity

    Check that anything the client sees — tone, response pattern, language — held steady through the test, not only that the technical work was correct.

  6. Expand or retire

    Widen the slice on a schedule you set, or stop the test cleanly if it did not hold up — both are legitimate outcomes of a real parallel run.

Probably not the right week to start

  • A client is mid-incident or mid-escalation right now.
  • An existing vendor arrangement has exit terms that are not yet resolved.
  • Nobody inside your practice has actually agreed to own the decision.
  • The goal is to avoid a difficult conversation with your current team rather than to test a real capacity gap.
See the checkpoint calendar

Straight answers on switching

Will our existing vendor know we are testing something else?

That is your call to make, not something this page decides for you — plenty of practices run a bounded parallel test quietly before deciding anything final.

How long does a parallel run usually take?

No universal number is promised here — length depends on the slice you choose and what your own quality bar requires before you trust it.