Pod Trial Week 4: decision (retainer or clean exit, both work)

Week 4 of the Pod Trial is the formal decision point. By now, both sides know whether the engagement is going to convert to a retainer. The week-4 ceremony exists to make the decision official, transfer deliverables (regardless of outcome), and either continue cleanly or exit cleanly.

Three real outcomes happen at the end of week 4. Each one is structured so neither side has reason to delay. Here is what each looks like.

Monday-Thursday: continued steady-state operation

Most of week 4 is operationally indistinguishable from week 3. The Pod continues running at 100% load. The POL continues weekly KPI reporting. The metrics dashboard continues updating.

What's different: the Pod is also preparing deliverables for end-of-week handoff, regardless of which outcome happens.

Deliverable preparation work happening behind the scenes:

• Final SOP library cleanup (proofreading, formatting, indexing)
• Dashboard structure finalized (so the founder can continue reading it weekly with or without us)
• Automation documentation (clear instructions for any AI/Zapier/n8n workflows the Pod configured)
• Per-client config docs finalized (for GHL whitelabel agency engagements)
• Pod composition write-up (who was on the Pod, what each person owned)

If the outcome is retainer, the deliverables transition into the ongoing engagement. If the outcome is clean exit, the deliverables are the final transfer.

Wednesday: retainer proposal sent

The POL sends the retainer proposal as a written document (typically Wednesday of week 4).

The proposal contains:

• Pod composition (final roles + headcount)
• Monthly retainer cost (varies by Pod size bracket: Lite, Standard, or Scale)
• Scope (specific workflows in vs out)
• KPIs the Pod will track and report on weekly
• Escalation protocol (when the POL escalates to the founder)
• Replacement guarantee terms (10 business days, absorbed by PodFleet)
• Commitment terms (month-to-month after 90-day initial commitment)
• Termination terms (30 days notice, all SOPs and dashboards delivered to founder)

The founder gets 48 hours to review before the decision meeting Friday.

Friday: decision meeting

60-minute meeting (founder + POL).

The POL walks through the proposal. The founder asks questions. The decision happens.

Three real outcomes:

Outcome A: sign the retainer

Most common outcome (typically 75-85% of Pod Trials we run).

What happens immediately:

• Founder signs the retainer agreement
• Trial fee credits against month one of the retainer
• Pod continues operating seamlessly into the retainer (no re-onboarding, no handoff break)
• Friday weekly reviews continue
• Daily Loom updates continue
• Metrics dashboard continues

The transition from Trial to Retainer is functionally invisible from the operational side. The founder sees no change in service, just a different invoice line item starting month 2.

Outcome B: clean exit

Less common but real outcome (typically 10-20% of Trials).

The clean exit happens when:

• The fit wasn't right (Pod composition didn't match operation, or scope was wrong)
• The founder's circumstances changed (business pivot, funding round mid-trial, etc.)
• The economics don't work for the founder right now (most common: business is earlier-stage than the Pod model fits)

What happens immediately:

• Pod stops operating end-of-week
• All deliverables transferred to founder's workspace by Friday:
  • Full SOP library
  • Metrics dashboard
  • Automation documentation
  • Per-client config docs (if applicable)
  • Pod composition write-up
• No clawback. No IP retention. No non-compete on the SOPs.
• We provide a 30-minute handoff call to walk through the deliverables

The founder walks away with an operational audit and infrastructure that has standalone value. We've had clients use the deliverables as the foundation for hiring an internal ops manager who continues the work.

This outcome is genuinely fine. We built the Trial structure expecting it would happen sometimes. The pricing model accommodates it.

Outcome C: scope adjustment + retainer

Third real outcome (typically 5-10% of Trials).

The founder wants to continue but at a different scope than originally proposed. Common variations:

• Smaller Pod (cost-driven)
• Different specialist mix (workflow priorities shifted during the Trial)
• Narrower workflow coverage (founder wants to keep certain functions in-house)
• Phased ramp (full retainer scope, but starting with a subset and expanding over 2-3 months)

The POL adjusts the proposal during or after the decision meeting. Founder signs the modified retainer. Engagement continues.

Both outcomes work. Sign produces an ongoing operation. Clean exit produces standalone infrastructure. The Trial was designed so neither side is incentivized to drag out a bad fit.

What gets delivered regardless of outcome

The full delivery package, given to the founder regardless of whether they sign:

1. SOP library.

• 30-50 documented standard operating procedures
• Indexed and structured in your Notion or Drive workspace
• Includes purpose, trigger, steps, tools, owner, and escalation path for each

2. Metrics dashboard.

• 3-metric structure (throughput, quality, outlier)
• Configured against your data in your tool
• Includes the secondary detail page with breakdowns

3. Automation documentation.

• Every AI configuration we built
• Every Zapier/n8n/Make workflow we configured
• Includes maintenance instructions for whoever runs it next (you, an internal hire, or a different provider)

4. Per-client config docs (GHL agency engagements).

• One-page configuration sheet per end-client
• Updated through the end of the Trial
• Indexed by version

5. Pod composition write-up.

• Who was on the Pod
• What each person owned
• Performance notes
• Recommendation on which specialists you'd want on the retainer Pod (if applicable)

All of this is yours. No clawback. No NDA on the materials.

The Trial fee logic

Quick reminder on how the Trial fee works:

• Paid upfront at the start of week 1
• Flat fee (varies by Pod size and complexity)
• If you sign the retainer, the Trial fee credits against month one
• If you don't sign, you've paid for the Trial and you keep all deliverables

The economics: the Trial fee is intentionally priced so it pays back for us only if a meaningful percentage of Trials convert. We're betting on the Pod proving itself in 4 weeks. If it doesn't, we eat the cost differential. That risk is what makes the Trial structure trustworthy on your side.

Why we end the week with a clean transfer either way

The deliverable transfer is structured the same regardless of outcome because we want both outcomes to feel clean.

If we made the clean exit messy (slow delivery, NDA on SOPs, lock-in on dashboards), we'd be incentivizing ourselves to push for retainer sign even when the fit isn't right. That would corrupt the entire Trial structure.

Instead, we make clean exit easy. This means our incentive during week 1-4 is to actually deliver value, not to manufacture lock-in. If we earned the retainer, we earned it. If we didn't, the founder walks with everything and we both move on.

This is what makes the Trial a real test, not a sales motion.