VDC engagements run on a recognizable curve. The first 90 days have three distinct phases, each with different signals, different metrics, and different risks. Treating all three phases the same way produces engagements that look fine on paper but quietly underperform.
This piece breaks down what each phase looks like operationally — what the pod is doing, what the customer should be doing, what to measure, and what to worry about. If you're inside an active VDC engagement, use this as a calibration guide. If you're scoping a new one, it sets the realistic expectation.
Day 1: setup and baseline
What it looks like. Contract signed, pod composed, tooling provisioned, kickoff session done. The pod has access to your codebase, your project management tooling, your communication channels. The first commit may not have landed yet but is days away.
What the pod is doing. Reading. Mapping the codebase. Understanding the conventions. Getting unblocked on tooling. Asking the buyer's senior engineers questions that should have been answered in the codebase walkthrough but weren't quite covered.
What the customer should be doing. Being available. Day-1 unblockers are the most-impactful ones in the engagement — a 4-hour delay on day 1 (your security team can't approve a tool, your product owner is unreachable for a clarification) costs proportionally more than the same delay at day 60.
What to measure. Time-to-first-commit. Should be 5–10 business days from contract signing. If it's drifting toward day 15+, something's wrong with the onboarding sequence — see the 14-day onboarding guide for the day-by-day breakdown.
What to worry about. Tooling delays. Senior-engineer unavailability. Vague scope (the kickoff happened but the first milestone isn't well-defined). Each of these compounds — fix them at day 1, not day 14.
Day 30: calibration
What it looks like. The pod has shipped its first 1–2 milestones. Sprint cadence is established. Code-review patterns have started to converge. Some friction has surfaced and (ideally) been resolved. The customer's engineering leadership has had at least one milestone-acceptance conversation and learned what "done" means for this pod.
What the pod is doing. Settling into the codebase. Building velocity from the lower-output ramp. Surfacing risks the customer hadn't anticipated ("the auth library you're using has a known issue with our integration target"). Proposing scope adjustments based on implementation reality.
What the customer should be doing. Refining acceptance criteria. The first milestone taught both sides what acceptance feels like for this pod; subsequent milestones get sharper. Calendar-blocking time for the milestone-acceptance flow so it doesn't bottleneck.
What to measure.
- Velocity gradient: is shipped-output increasing vs. flat? Increasing = healthy ramp; flat = pod has plateaued early, structural issue.
- Code-review turnaround: should be trending down from days to hours.
- Milestone-acceptance lag: time between pod-says-done and customer-says-accepted. Should be same-sprint by day 30, not multi-sprint.
What to worry about. The pod operating like staff augmentation (your EM running standups, code reviews going through your team rather than the pod's tech lead). This is the most common anti-pattern and it's hardest to fix the longer it runs.
Day 60: stabilization
What it looks like. The pod is in steady state. Velocity is no longer ramping rapidly but is climbing on a flatter gradient. Most of the operational friction has been resolved. The pod knows your codebase well enough that they're suggesting architectural moves, not just executing tickets.
What the pod is doing. Production work at near-full velocity. Code review of each other's work without your engineers needing to gate every PR. Identifying technical debt and proposing cleanup that fits within the milestone schedule. Becoming an engineering partner, not just a delivery vendor.
What the customer should be doing. Stepping back from operational involvement. Your EM should be down to 1–2 hours per week of pod oversight by day 60, not the 8–10 hours/week from day 1. If they're not, governance is duplicated and needs to shift.
What to measure.
- EM time spent on pod oversight: trending down significantly.
- Pod-originated suggestions: 5–10% of incoming work by day 60 (will rise to 15–25% by day 180).
- Escalation count: should be roughly zero per month at this point.
What to worry about. Plateau. If velocity stops climbing and stays flat, something structural is capping the pod. Common causes: scope is too granular (decomposed below the pod's natural unit of work), wrong specialist mix, or the customer's acceptance is becoming the bottleneck.
Day 90: first real fit measure
What it looks like. The first quarter of delivery is complete. There's enough data to know whether the engagement is working. The first quarterly business review with the platform's engagement architect happens around now.
The fit signals at day 90. An engagement that's working at day 90 shows:
- Velocity stable + climbing. Not flat. Not bouncing. On a sustainable upward gradient.
- Governance fully transitioned. Pod's delivery manager is running operations end-to-end; your EM is reviewing outcomes only.
- Pod proactivity emerging. Pod members are suggesting architectural improvements, surfacing risks early, proposing scope adjustments.
- Acceptance lag near zero. Same-day or next-day milestone sign-offs.
- Composition stable. The pod hasn't needed major rotations; if rotations happened, they were platform-managed without disruption.
The misfit signals at day 90. An engagement that isn't working at day 90 shows:
- Velocity flat since day 30. Pod is shipping but not accelerating.
- Your EM still in standups. Governance hasn't transitioned.
- Pod still purely order-taking. No proactive suggestions.
- Acceptance still taking weeks. Bottleneck on the customer side.
- Multiple unplanned rotations. Pod composition isn't fitting.
If you see misfit signals at day 90, don't terminate yet — diagnose. Most are fixable. The corresponding fixes are in the seven anti-patterns post. If after a 30-day correction cycle (day 120) the signals haven't moved, then termination is on the table.
What changes between day 90 and day 180
For engagements that pass the day-90 fit check, the next 90 days are about deepening the partnership:
- Pod's institutional knowledge of your codebase reaches near-parity with mid-tenure employees.
- Velocity continues climbing on a flatter gradient — typically 1.5–2.5× initial baseline by day 180.
- Pod begins shaping 15–25% of incoming work, not just executing.
- Composition may rotate as work shifts — adding specialists for emerging needs, retiring ones whose work is complete.
- Pod becomes an engineering partner — invited into architecture reviews, consulted on platform decisions, not just product roadmap work.
For more on what month 6 looks like, see the healthy-VDC-at-month-6 post.
Frequently asked questions
What if our engagement skips a phase or runs them in different order?
Some engagements compress because they're smaller (2–3 specialists vs 6–8). Some stretch because the codebase is unusually complex. The phases describe the typical curve; deviations are fine if you understand why they're happening. What's not fine: skipping the calibration phase entirely (jumping from setup directly to "expecting steady-state output").
How do we run the day-90 review?
90-minute session with the pod's delivery manager, the platform's engagement architect, and your engineering leadership. Walk through the fit signals above. Document any corrections needed. Set a 30-day re-check.
Should we do a day-30 review too?
Lighter version, yes. 30-minute check at day 30 covering velocity gradient, governance transition status, and any operational friction. Can be informal — not as structured as the day-90 quarterly review.
What's the most common reason engagements fail at day 90?
Governance never transitioned. The customer kept running standups, code reviews, and milestone acceptance like staff augmentation. The pod's delivery manager never got operational ownership. By day 90, both sides are doing the same work and the engagement is structurally broken.
Where to start
If you're inside an engagement and want a structured calibration session at day 30, day 60, or day 90, schedule a 30-minute call. We'll walk through the fit signals against your engagement and surface any patterns to correct.
For the day-by-day onboarding context (days 1–14), see onboarding a VDC: the first 14 days. For the longer-term steady-state context (month 6+), see healthy VDC at month 6.