The four-week onboarding playbook
Discovery, selection, training, go-live. The exact sequence we use to put a dedicated operations team into production in twenty business days — and what each week is actually for.
Most outsourcing engagements lose six to ten weeks at the start — scoping that drags, credentialing delays, training built from scratch. We've compressed that into four weeks, and the compression isn't magic. It's sequence.
Here's what each of the four weeks is actually for, and why skipping or reordering them tends to add a quarter to time-to-value.
Week 1 — Discovery and alignment
The week most operators rush. Discovery is not requirements-gathering. It's the week where the operating model gets agreed in writing — the workflows that will be ours, the ones that stay with you, the hand-off points, the SLAs, the escalation matrix.
By end of week one, three artifacts exist:
- A workflow map with hand-off boundaries explicitly drawn.
- The metric set we'll be measured against, with thresholds.
- The team profile — roles, seniority, language, time zone.
Week 2 — Selection and setup
Candidates are drawn from the existing TrueNext bench, not recruited cold. This is the unglamorous reason four weeks works: we're not running a hiring process inside the onboarding. The team is interviewed and selected from people we already employ.
Week two also includes the part most clients underestimate — IT provisioning. VDI access, VPN, role-based permissions, MFA setup, endpoint compliance. Most of week two's time is spent in your IT's queue, not ours.
The fastest onboardings we've run had one thing in common: the client's IT lead was in the kickoff call. The slowest had IT looped in during week three.
Week 3 — Training and integration
The team learns your systems, your SOPs, and your judgment calls. Training is shadow-then-reverse-shadow: the team watches your operator run live work for two days, then runs it themselves with your operator watching. By Friday, mock tasks are graded and gaps are flagged.
This is also when the communication architecture goes live — the Slack channels, the standup cadence, the weekly review template. The rituals exist before production does.
Week 4 — Go-live with QA wrap
Production starts at reduced volume — typically 30% of target — with 100% QA on every output. As QA scores stabilize, volume ramps and QA coverage drops to a sampled rate. By end of week four, the team is at full target volume with sampled QA and a weekly review running.
Why this works
Three reasons, none of them clever:
- The bench is real. We're not hiring during the engagement. The team exists on day one.
- Discovery is a deliverable, not a meeting. Week one ends with signed artifacts, not notes.
- Production starts at 30%. Ramp protects quality. Trying to go live at 100% on day one is how operations fail publicly.
Where to go next
The phase-by-phase detail with deliverables and owners lives on the How it works page. To see the practice areas this playbook applies to, the Industries directory covers the four verticals.
For more on how we structure the engagement economics so the compressed timeline does not become a corner-cutting exercise, see why we don't sell hours.
Ready to map this against your operation? Book a discovery call and we'll walk you through week one.
