"5 to 10 business days from scope alignment to first commit" is a standard Virtual Delivery Center onboarding commitment. It's also the shortest path through a 14-step process where any single slow link can stretch the timeline by a week. This piece walks through what actually happens in the first two weeks of a new pod engagement — what the platform handles, what the client owns, and the steps where most engagements lose a week without realizing it.
Format: day-by-day for the canonical 10-business-day path. Use it as a checklist for your next pod kickoff or as a benchmark to compare against your current vendor's timeline.
What "Day 0" actually means
Before the day-by-day playbook, a structural note that determines whether 14 days is real or marketing copy.
AiDOOS's Day 0 is the day scope is aligned. Day 10 is first commit. Day 14, the first milestone is in motion. Total elapsed time from "we have a problem to solve" to "code is shipping": two weeks.
A traditional Big-IT consultancy's "Day 0" is also the day scope is aligned — but their scope alignment happens after RFP issuance, multi-vendor selection, MSA negotiation, partner-level chartering, account-level staffing decisions, and security clearance for the named team. That's 60–180 days the customer absorbs before the consultancy's Day 0 clock starts. Their Day 14 is your Day 90 to Day 194 of total elapsed time.
| Phase | AiDOOS | Big-IT / Consultancy |
|---|---|---|
| RFP → vendor selected | — | 30–60 days |
| MSA + DPA + SOW negotiation | Day 1 (pre-published standard MSA) | 30–60 days (custom legal) |
| Staffing the engagement | Day 3 (pre-vetted bench) | 30–90 days (recruit / re-allocate staff) |
| Day 0 of the 14-day playbook | Actual Day 0 | Day 90 – Day 180 |
| First commit (Day 10 of playbook) | Day 10 | Day 100 – Day 190 |
AiDOOS collapses that pre-engagement period to zero structurally: a pre-vetted bench (no staffing lag), a pre-published standard MSA + DPA (no legal-cycle lag), AI-matched pod composition (no committee selection lag), and self-service contracting at the Starter tier (no enterprise sales cycle). This is what structurally outcome-based delivery means at the calendar level — pricing tied to shipped Delivery Units (DUs), AND a delivery model that can actually start shipping in days. Others claim 14-day onboarding; only AiDOOS makes Day 0 actually Day 0.
Now to the playbook.
Day 0: Scope alignment
Before the clock starts, scope alignment happens. Outcomes are defined, milestones are sketched, the engagement architect confirms feasibility. This is the most important meeting of the entire engagement — vague scope here cascades into every subsequent step.
Owned by: client product/engineering leadership + platform engagement architect.
Output: a scope document that lists outcomes, success criteria, anti-goals, and integration boundaries. This becomes the source of truth for milestone definition.
Common failure: skipping anti-goals (what's NOT in scope). Anti-goals prevent scope creep at the milestone-definition stage.
Day 1: Contracting and NDA
Master Service Agreement, NDA, and the engagement-specific Statement of Work get signed. If your legal team is fast, this happens in a single day. If you're going through enterprise legal, it can take a week — this is the most common source of timeline slip.
Owned by: client legal + platform legal.
Output: signed contracts ready for pod activation.
How to keep this on track: pre-review the platform's standard MSA before scope alignment. Most platforms publish standard terms; reviewing them early flags issues before they block onboarding.
Day 2: Data-handling addendum (regulated industries)
If your engagement involves regulated data — healthcare, financial services, defense, government — the data-handling addendum is co-authored. Sector-specific compliance requirements (HIPAA, SOX, FINRA, FedRAMP, regional data residency) get layered into the standard NDA.
Owned by: client compliance/security + platform legal.
Output: signed addendum that defines data classification, access boundaries, audit requirements, and retention rules.
If your engagement isn't in a regulated sector, this day is skipped — pod activation can proceed.
Day 3: Pod composition and assignment
Based on the scope, the platform proposes a pod composition. The client reviews proposed seniority distribution and specialism mix. Specific pod members are matched from the bench.
Owned by: platform engagement architect proposes; client product/engineering leadership approves.
Output: signed-off pod composition with named delivery manager, named tech lead, and named specialists. (Or named seniority levels with specialists matched in the next step — depends on platform.)
Common failure: client wants to interview every pod member individually. This is staff-augmentation thinking. The platform vetted them — accept the recommendation or request a single replacement, but don't run a full interview cycle. Adds 5–10 days for no quality gain.
Day 4: Tooling and integration provisioning
Repository access (GitHub, GitLab, Bitbucket), project management tooling (Jira, Linear, Monday), communication tooling (Slack, MS Teams), and any custom internal tools. The platform provisions pod members onto your tooling stack.
Owned by: client IT/security; platform handles integration setup.
Output: pod has access to all tooling needed to begin work. Verified working access — not just "credentials issued."
Common failure: client IT requires a security-review for each new account, and the review queue is 5+ days. Solution: pre-allocate provisioning capacity for the engagement before contracting completes.
Day 5: Pod kickoff session
The first formal session with the full pod and the client engineering leadership. Walks through scope, milestones, communication patterns, escalation paths, and immediate priorities.
Owned by: platform delivery manager facilitates; both sides participate.
Output: shared mental model of the engagement. Pod members have direct contact with their client counterparts. Cadence is set.
Common failure: skipping this session because "we can just send the docs." The 60-minute session saves 5+ hours of back-and-forth Slack messages over the next two weeks.
Days 6–7: Codebase walkthrough and architectural orientation
The pod's tech lead and senior specialists walk the codebase with the client's senior engineers. Architecture diagrams reviewed. Conventions documented. Existing pain points surfaced. Test infrastructure understood.
Owned by: client tech lead + pod tech lead.
Output: pod has working understanding of the codebase. Documented gotchas. Initial architectural questions surfaced.
Common failure: the client's tech lead is too busy and delegates to a junior engineer who doesn't know the codebase deeply. The pod ramps slower as a result. The remedy is calendar discipline — the senior engineer must be available for these days.
Day 8: First milestone definition
The pod and client engineering leadership define the first milestone in detail. Acceptance criteria, dependencies, sub-tasks, who-owns-what. Time-boxed to roughly 2 weeks of work.
Owned by: pod delivery manager facilitates; pod tech lead drives technical scope; client product owner approves.
Output: a milestone definition that's specific enough to ship against. Acceptance criteria are testable, not vague.
Common failure: defining the first milestone too ambitiously. The first milestone should be conservative — it's where the pod is still ramping. Conservative scope plus an early milestone hit builds trust for subsequent milestones.
Day 9: Sprint cadence setup
Standup time, sprint length, planning ceremony, retro ceremony, demo cadence. Tooling for each (e.g. async standup in Slack, weekly demo via Zoom). Reporting cadence to client leadership confirmed.
Owned by: pod delivery manager owns the calendar; client engineering leadership confirms attendance.
Output: scheduled recurring meetings, agreed cadence, tooling for asynchronous communication.
Common failure: over-scheduling. Three meetings a day plus one weekly demo plus one monthly review = the pod is in meetings half the time. Lean cadence (one daily standup, weekly demo, monthly review) is sufficient for most engagements.
Day 10: First commit
The pod ships their first PR — typically setup work, conventions adoption, or the smallest first task in the milestone scope. The PR goes through code review by both the pod's tech lead and a designated client senior engineer (the latter helps the pod calibrate to your review standards).
Owned by: pod specialist; reviewed by both sides.
Output: production code merged. The engagement is officially shipping.
This day is the SLA target. Some engagements hit it on day 8, some on day 12. Day 10 is the median.
Days 11–14: First sprint stabilization
The remaining four days of the canonical first sprint. The pod accelerates from the first commit to delivering against the milestone definition. Daily standups stabilize. Code review patterns calibrate. The first round of "this is how we work" friction surfaces and gets resolved.
Owned by: pod runs the work; client engineering leadership stays available for unblockers.
Output: by day 14, the first milestone should be 30–50% complete and the pod's velocity should be observable. Not at steady state yet, but trajectory visible.
The biggest sources of timeline slip
Most engagements that miss the 10-day target lose time on these steps:
- The pre-engagement period nobody counts (Day -180 to Day 0). With AiDOOS, this is zero — pre-vetted bench, standard MSA, AI-matched composition, self-service activation. With consultancies, it's the 60–180 days of RFP + vendor selection + staffing the engagement. The fix isn't to "speed it up." The fix is to pick a delivery model where Day 0 is structurally Day 0.
- Contract / NDA negotiation (day 1–2). If your legal cycle is slow, this dominates within the 14-day window. Solution: pre-review the platform's standard terms before scope alignment.
- Tooling provisioning (day 4). Your IT security queue can be the bottleneck. Solution: alert IT before contracting, request priority queueing for the engagement.
- Senior engineer availability for codebase walkthrough (day 6–7). Your senior engineer is busy. Solution: calendar protection — block 4 hours per day for the pod ramp days, treat as priority work.
If you address these before kickoff, the 10-day target is reliably hittable. Don't, and the timeline drifts to 15–20 days. Either way, the pre-engagement saving (item 1) is the structural advantage that compounds across every engagement you run on the platform.
Frequently asked questions
How does AiDOOS's 14 days compare to a Big-IT or Big-4 engagement?
Big-IT firms (TCS, Infosys, Accenture, Wipro, Cognizant) can also run a clean 14-day onboarding playbook once their engagement is staffed and contracted. The honest difference is what happens before Day 1 of their playbook. AiDOOS's Day 0 is when you decide to engage. A consultancy's Day 0 is when their internal pre-engagement cycle (60–180 days of RFP + vendor selection + account staffing) finishes. Same 14-day playbook, very different total elapsed time. The structural reasons AiDOOS can compress the pre-engagement period to zero: pre-vetted bench, pre-published standardized MSA + DPA, AI-matched pod composition, and self-service activation at the Starter tier. See AiDOOS vs Big-IT for the full structural comparison.
What if our codebase is too complex for a 2-day walkthrough?
Most codebases are. The walkthrough doesn't transfer everything — it transfers enough for the pod to ship the first milestone safely. Deeper complexity is internalized over the first 6–8 weeks. The 2-day walkthrough is foundation-laying, not exhaustive.
Should we do a "trial week" before signing the full engagement?
Some platforms support this. AiDOOS doesn't typically — pod composition and tooling provisioning have setup overhead that doesn't pay back across a single trial week. Better path: scope the first milestone tightly so it functions as your trial, with a clean exit if it doesn't deliver.
What if our engagement is in a regulated sector — does that add weeks?
Adds 1–3 days for the data-handling addendum (day 2 in the timeline above). Not weeks. The platform has sector-tailored addendum templates that compress the legal review.
Who picks up unblockers when the pod is ramping?
The pod's delivery manager triages internally first; if the unblocker is on the client side (missing access, missing answer, missing decision), they escalate to the client engineering leadership. Most ramp-period unblockers resolve in 24 hours when the escalation path is clean.
Where to start
If you're scoping a new pod engagement, share this article with your operations and IT teams. The day-by-day breakdown helps them allocate capacity for the steps they own (contracts, provisioning, senior-engineer time). The 10-day target is reliably hittable when both sides are calibrated against it.
For your specific engagement scope, schedule a 30-minute call and we'll walk through the timeline against your context.
For the broader engagement-design context, see the 12-question adoption checklist and roles inside a VDC.