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.
Switching delivery Changement de livraison
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.
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.
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.
Name what is actually being delivered today, to which accounts, in which language, and by whom — before comparing it to anything new.
Pick one account, one service line, or one time window rather than moving the whole book at once.
The new path handles the chosen slice while the existing one continues everywhere else, so nothing depends on a single cutover date working perfectly.
Read the notes that come back against your own quality bar before deciding the slice is ready to grow.
Check that anything the client sees — tone, response pattern, language — held steady through the test, not only that the technical work was correct.
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.
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.
No universal number is promised here — length depends on the slice you choose and what your own quality bar requires before you trust it.