Week 2 of the Pod Trial is when the engagement stops being preparation and starts being production. The Pod takes ownership of real customer-facing work using the SOPs documented in week 1.
The target for week 2 is for the Pod to be handling 50-70% of the operational load by Friday. The progression is gradual on purpose: low-risk workflows first, standard workflows mid-week, stretch workflows by end of week if the quality holds.
Here is the day-by-day breakdown.
Monday: low-risk workflow transfer
The Pod takes ownership of the easiest, lowest-risk workflows first.
Typical week-2 Monday handoffs:
- Standard refund processing (within policy, under $X amount)
- Order status questions
- Password reset requests
- Routine subscription pause/resume
- New-member welcome messages
These are workflows where:
- The SOP is unambiguous
- The customer-facing risk of getting it wrong is low
- Volume is high enough that the Pod can validate the SOP against real cases quickly
By end of Monday, the Pod has touched 100-300 real tickets. The POL reviews each one for quality before the day ends.
The existing team continues running the higher-risk workflows.
The handoff is incremental, not flip-the-switch. Your existing team is still handling the workflows that haven't transferred yet. Nothing breaks because nothing got dropped.
Quality review (end-of-day Monday).
The POL pulls a sample of 20-30 Pod-handled tickets and reviews them against the SOP. Looks for: tone match with the brand, accuracy of information given, adherence to policy. Any drift gets corrected immediately, and the SOP gets updated if the original draft missed a case.
Tuesday-Wednesday: standard workflow addition
Add the standard-complexity workflows.
Typical mid-week handoffs:
- Community moderation (responding to member posts within SLA)
- Routine CRM updates (lead enrichment, contact verification)
- Content scheduling tasks (loading newsletter into ESP, scheduling social posts)
- Standard customer-success check-ins
- A2P 10DLC renewal preparation (for GHL whitelabel agencies)
These are workflows that require more judgment than Monday's batch but still fit within documented SOPs. Volume per workflow is moderate.
The Pod is now handling 40-60% of total operational load by Wednesday afternoon. The existing team's daily volume has dropped noticeably.
Daily quality review continues.
The POL is reviewing samples every end-of-day, looking for drift. Sample size is large enough to be statistically meaningful (typically 50-100 items per day across workflows).
Founder visibility.
The founder gets a daily async update (Loom or Slack) from the POL covering:
- Volume handled by the Pod that day
- Quality observations
- Any issues that surfaced
- What's transferring next
This is the founder's heaviest visibility week of the entire engagement. They're seeing the operation move from their team to the Pod in real time.
Thursday: stretch workflow attempts
Try the harder workflows.
By Thursday, the Pod has validated the easier workflows for 3 days. Now we try the harder ones:
- Edge-case refund handling (out-of-policy requests requiring judgment)
- Escalated customer-support interactions (complaints, churn-risk conversations)
- Custom workflow modifications for individual clients (in GHL agency context)
- Complex CRM data work (deduplication decisions, list segmentation)
These are workflows where SOPs are necessary but not sufficient. The Pod specialists have to apply judgment within the SOP framework. The POL is closely supervising and approving every borderline case.
This is where the trial reveals fit.
If the Pod handles the stretch workflows well by end of Thursday, we're on track for the 70% target by Friday. If the Pod struggles, we pause and either:
- Adjust the SOP to be more prescriptive
- Reassign the workflow to a more experienced Pod member
- Defer the workflow to week 3 with additional preparation
Most engagements hit the 70% target. Some hit 50-60% because we deliberately defer something. Neither is a failure; both are real-time calibration.
Friday: weekly review + week-3 plan
60-minute weekly review (founder + POL).
The POL walks through:
- Actual workflows transferred this week
- Volume handled (Pod vs existing team breakdown)
- Quality metrics (CSAT, response time, error rates)
- Issues that surfaced and how they were resolved
- The plan for week 3 (the remaining 30-50% of operational load)
- Any SOP updates made during the week
The founder reviews, approves, asks questions, requests adjustments.
Mid-trial KPI baseline.
The metrics dashboard isn't fully live yet (that happens in week 3), but the POL shares the initial KPI snapshot. Comparing pre-trial baseline to end-of-week-2 numbers:
- Response time: usually already improved 20-40%
- Founder time on ops: usually down 50%+
- Backlog: usually cleared or significantly reduced
These are early signals. The full impact shows up in weeks 3-4.
I knew rationally that the Pod was taking over. The moment I emotionally felt it was Wednesday afternoon when I realized I hadn't been pulled into a single customer ticket all day.
What the existing team experiences
For most existing teams, week 2 is a relief. They're handing off work they were drowning in. The reactions we typically see:
- Day 1: cautious ("are they going to do it right?")
- Day 3: relieved ("oh, the tickets are getting answered")
- Day 5: collaborative ("here are some edge cases I forgot to mention in week 1")
The existing team usually stays in their role. The Pod is taking over the operational work that was overwhelming them, but the team members themselves are often retained for higher-leverage work (customer relationship management, strategic projects, founder support). The handoff is rarely a replacement; it's usually a re-allocation.
What the founder sees from their seat
The honest founder time investment in week 2:
- Daily: 15 minutes (reading async updates)
- Friday: 60 minutes (weekly review)
Total: 2.5-3 hours. About half of week 1.
What the founder gets in return: a functioning Pod handling 50-70% of operational load, real-time visibility into quality, and a path to 100% in week 3.
Why the 70% target matters structurally
We aim for 70% by end of week 2, not 100%, on purpose.
The remaining 30% is intentionally held back because:
- Some workflows benefit from one more week of validation
- Some require additional SOP refinement based on week-2 observations
- Some are high-judgment workflows where the Pod needs more reps under POL supervision before owning them solo
Pushing for 100% in week 2 would compromise quality. The 70-then-100 progression is what makes the handoff durable.
Week 3 is when we hit 100% of in-scope work. Week 4 is the decision point.