Pod Trial Week 1: onboarding (what gets mapped, documented, and aligned)

Week 1 of a PodFleet Pod Trial is the highest-leverage week of the entire engagement. Everything that happens in weeks 2, 3, and 4 depends on the quality of the week-1 documentation. If we miss a workflow in week 1, it shows up as a gap in week 3. If we misread the team dynamics in week 1, the handoff in week 2 gets bumpy.

So we treat week 1 with disproportionate care. Here is exactly what happens, day-by-day, including what the founder sees and what the Pod is doing behind the scenes.

Monday: kickoff

60-minute kickoff call (Monday morning, founder + POL).

The call covers:

• The operational outcomes you're hoping the Trial proves (e.g., "I want to stop personally answering refund tickets," "I want our community to feel active again," "I want a metrics dashboard I actually read")
• The team members the POL will shadow this week
• The tools we need access to (helpdesk, community platform, CRM, ESP, project management, etc.)
• The handful of known operational issues you want us aware of from day one

This call is the founder's heaviest involvement of the week. After this, the POL takes over and runs the rest of week 1 with minimal founder time.

Access provisioning (Monday afternoon).

The POL works with your designated access-owner (usually an existing team lead or the founder themselves) to get logged into every tool we need. Specifically:

• Helpdesk admin access (Gorgias, Helpscout, Zendesk, etc.)
• Community platform moderator access
• CRM read access (write access typically added in week 2)
• ESP read access for sequence audit
• Project management tool member access
• Loom + Slack provisioning

We provision against your existing access-management system; we don't ask you to create custom workarounds. This usually takes 2-3 hours of back-and-forth on Monday.

Introductions to your existing team (Monday end-of-day).

The POL introduces themselves to your existing team members via Slack DM or a short email. The framing is collaborative, not replacement: “I'm here to learn how you run the operation. Over the next few days I'll be shadowing you. The goal is to document so the work is reproducible, not to evaluate your performance.”

This framing matters. Existing team members are often nervous when a new ops person shows up. Most week-1 friction comes from existing-team anxiety, not from operational complexity.

Tuesday and Wednesday: shadowing

Shadow the existing team doing their actual work.

The POL spends Tuesday and Wednesday observing the existing team's recurring workflows. Specifically:

• Watches how tickets get answered in real time (which templates, which escalation paths, which judgment calls)
• Sits in on community-management work (how moderators handle disputes, how welcome messages get written)
• Observes the content workflow (how the newsletter actually ships on Tuesday, which steps depend on which people)
• Reviews recent CRM activity (what fields are actually used, what's neglected)
• Sits in on any team standups or recurring meetings

This is the most underrated phase of the engagement. We don't just take your word for how the operation runs. We watch it run. The documented version of an operation is almost always different from the actual version, and the differences are where the gaps live.

Document everything in real-time.

As the POL shadows, they're building a working SOP library in your Notion or Drive workspace. Not pretty docs yet, just structured notes. Each workflow gets:

• Trigger (what starts this workflow)
• Steps (what happens in order)
• Tools used
• Owner
• Edge cases observed
• Frequency

By end of Wednesday, the POL has notes on every recurring workflow in your operation. Usually 30-50 workflows for a $1M-$20M ARR business.

Every operation has 5-10 workflows that exist only in one person's head. Week 1 finds them and documents them. This alone is often worth the Trial cost.

Thursday: draft SOPs and build the operating plan

Draft formal SOPs from the shadowing notes.

The POL converts the working notes into proper SOP documents. Each SOP is structured the same way:

• Purpose
• Trigger
• Step-by-step procedure
• Tools required
• Owner
• Quality criteria
• Escalation path
• Frequency

The library typically covers 30-50 SOPs by end of Thursday. Some are 1-page (simple repetitive tasks). Some are 4-5 pages (complex workflows with multiple decision branches).

Build the operating plan for weeks 2, 3, and 4.

The POL drafts a plan that specifies:

• Which workflows the Pod will take over in week 2 (typically 50-70% of operational load)
• Which workflows the Pod will own in week 3 (typically 100% of in-scope load)
• Which 5-8 KPIs the Pod will track and report on
• Which Pod members will be assigned to which workflows
• The escalation protocol (which decisions require founder approval, which the POL handles)

This plan is what gets presented Friday.

Friday: operating plan presentation

60-minute presentation (Friday afternoon, founder + POL).

The POL walks through:

• The SOP library overview (how many SOPs, what's covered, what's not)
• The proposed week-2 handoff scope
• The KPI dashboard structure
• Pod composition (which specialists will work on which workflows)
• Any operational issues discovered during shadowing that need founder decisions

The founder reviews, approves, or adjusts. The most common adjustment: scope expansion ("I forgot to mention we also do X, can you add that?"). Less common: scope reduction ("Don't touch this workflow, I want to keep doing it myself for now").

By end of Friday, both sides have aligned on what week 2 looks like. The Pod is ready to start taking real operational load on Monday.

What the founder sees from their seat

The honest founder time investment in week 1:

• Monday: 90 minutes (kickoff + access provisioning back-and-forth)
• Tuesday: 30 minutes (responding to a handful of POL questions in Slack)
• Wednesday: 30 minutes (responding to questions)
• Thursday: 0-15 minutes (POL is mostly head-down on documentation)
• Friday: 60 minutes (operating plan review)

Total: 3-4 hours of founder time.

What the founder gets in return: a documented inventory of every workflow in their operation, an SOP library they own, a proposed operating plan, and a clear picture of what weeks 2-4 will look like.

What the existing team experiences

The existing team typically reports:

• Day 1-2: slight nervousness about being shadowed
• Day 3: realizing the POL is genuinely there to learn, not evaluate
• Day 4-5: appreciation that someone is finally documenting what they've been doing

The framing the POL maintains is consistent: “You've been holding this together. We're here to make it reproducible so you don't have to be the single point of failure.” This framing reduces existing-team anxiety to near-zero by mid-week.

Why week 1 is the highest-leverage week

The investment is asymmetric. Week 1 costs us roughly 40-50 hours of POL time on documentation. It generates an SOP library that drives the next 90+ days of operational work.

If we cut week 1 short (skip the shadowing, accept your existing documentation as-is, start operating immediately in week 2), the engagement breaks in week 3 when undocumented workflows surface as gaps. So we don't cut it short.

This is also why the Trial structure works. Week 1 produces deliverables (the SOP library) that have standalone value, regardless of whether you continue to the retainer. Even on a no-conversion outcome, you've gotten an operational audit.