Pod Retainer Month 1: scope expansion (what changes once you sign)

The first month of a Pod Retainer is operationally different from the Pod Trial in two important ways: the scope expands, and the cadence shifts from “build and validate” to “run and tune.”

Most founders we work with sign the retainer at end of week 4 of the Trial and then ask: “OK, what's different now?” The honest answer: not much in the first few days, then a noticeable shift starting week 5.

Here is what month 1 of the retainer actually looks like.

Day 1 of the retainer

The transition from Trial to Retainer is seamless on the operational side. The Pod keeps running. The POL keeps reporting. Your daily Loom updates and Friday weekly reviews continue without a pause.

What's different: the contract type. You're now on a 90-day initial commitment with month-to-month afterward. Pod size is committed at the bracket you signed (Lite, Standard, or Scale). The retainer scope (what's in vs out) is in writing.

Week 5: scope expansion meeting

Within the first week of the retainer, the POL schedules a 60-minute “scope expansion” meeting. This is where the workflows that were intentionally out of the Trial scope get evaluated for inclusion.

Typical Trial-scope exclusions that get added in month 1:

• Workflows you weren't ready to hand off in week 1
• Functions that were “coming soon” (e.g., a new product launch, a new community, a new ad channel)
• Workflows that depend on other teams (legal, finance, product) and needed coordination
• Edge-case workflows the Pod observed during the Trial but didn't formally take on

You and the POL prioritize which to add first, second, third. Most retainers add 3-5 new workflows in month 1.

The Trial scope is intentionally narrower than what the retainer will eventually cover. Month 1 is when the scope catches up to what your operation actually needs.

Week 6: net-new workflow onboarding

The new workflows go through their own mini-onboarding inside the existing Pod:

• POL shadows the team member or process currently owning the workflow
• SOPs get drafted
• Pod specialist (often the same one running similar Trial workflows) takes ownership
• Quality gets reviewed daily for the first week

This is faster than the Trial onboarding because the team relationships are established and the documentation infrastructure exists.

Typical net-new workflows added in week 6:

• Sales operations (inbound lead routing, demo scheduling, follow-up sequences)
• Partnership coordination (managing affiliate or referral programs)
• Vendor management (coordinating with external contractors, agencies)
• Reporting (board prep, investor updates, internal exec summaries)
• Recruiting support (job posting management, candidate scheduling, first-round screening)

The Pod's bandwidth has been validated during the Trial. Adding 3-5 new workflows in month 1 is typically well within capacity for a Standard-bracket Pod.

Week 7: full retainer scope live

By the end of week 7 (week 3 of the retainer), the Pod is running everything that's in retainer scope. The POL's weekly review now covers the full operational footprint, not just the Trial subset.

Typical operational state at end of week 7:

• 30-50 SOPs in the library, all current
• 5-8 KPIs on the dashboard, with 4 weeks of trend data
• Pod handling 100% of in-scope workflows
• Founder time on ops: 1-2 hours per week (versus 10-30 pre-Trial)

This is the operational shape that persists for the next 11+ months of the retainer.

Week 8: first retainer-only KPI review

The weekly Friday review continues, but the Friday at end of week 8 is the first “retainer-only” KPI review (the previous Fridays included Trial baseline comparison).

The review structure shifts subtly:

• Less “compared to before the Pod” framing
• More “trend within retainer” framing
• New KPIs added based on the full scope
• Outlier metric of the week gets more attention

The dashboard is now operating on a steady-state cadence. Friday becomes a 30-minute review (down from 60 minutes during the Trial).

What stays the same

A lot stays the same, on purpose:

• Same POL (no handoff to a new account manager)
• Same specialists (no team turnover at retainer signing)
• Same SOPs (the ones built during the Trial are still the foundation)
• Same dashboard (in your tool, owned by you)
• Same daily Loom + Friday review cadence

The retainer is a continuation, not a restart. This is structurally different from how most BPO contracts work, where signing a master agreement triggers a re-onboarding cycle. The Pod model avoids that.

What to watch for in month 1

Three things commonly come up in month 1 that don't show up during the Trial:

1. Scope creep. Founders sometimes try to add 8-10 net-new workflows in week 5. The Pod has capacity for 3-5 new workflows in month 1 without quality drift. Adding more compresses the onboarding window and degrades the work. The POL will push back if scope expansion exceeds capacity, but it helps if the founder knows this going in.

2. Existing team role transitions. If the existing team is being reallocated (rather than retained in their original roles), month 1 is when those transitions finalize. Some uncertainty during this period is normal. The POL helps document role changes if requested.

3. KPI definition refinement. Some KPIs you thought you wanted to track during the Trial turn out to be less useful once you've read them weekly for 4 weeks. Month 1 is when the dashboard gets tightened: drop the metrics that aren't actionable, add the ones the Trial revealed as important.

What month 2 looks like (preview)

Once month 1's scope expansion is complete, month 3 is when the operation enters the optimization phase. Different focus, different cadence. Month 2 is mostly steady-state operation with light tuning.

For most founders, month 1 is the last month with elevated involvement. From month 2 forward, the retainer becomes a background operational layer that surfaces only through Friday reviews and the rare escalation.