The old way
When the operation is humming
- Workload at 70-85% of Pod capacity
- No major scope additions planned
- KPI trends stable or improving
The Pod way
When growth is straining the team
- Workload at 95%+ of Pod capacity
- New functions or volume coming online
- Founder time on ops creeping back up
Month 6 of a Pod Retainer is the first real strategic decision point after the initial commitment. The optimization pass at month 3 tuned the operation. By month 6, the question shifts from operational (is this running well?) to strategic (is this the right shape for what's coming?).
Three Pod bracket options. Three real decisions. Here is the framework for picking the right one for your next 6-12 months.
The 3 Pod brackets
PodFleet Pods come in three sizes, optimized for different operational shapes.
Lite Pod.
- 1 POL + 2-3 specialists + AI automation specialist
- Covers 1-2 operational functions deeply (e.g., customer support + community)
- Fits: $1M-$3M ARR operator-led businesses, or focused-scope engagements at larger sizes
- Throughput capacity: roughly the operational workload of 3-4 full-time employees
Standard Pod.
- 1 POL + 3-4 specialists + AI automation specialist
- Covers 3-4 operational functions (customer support, community, content ops, data/admin)
- Fits: $3M-$10M ARR operator-led businesses
- Throughput capacity: roughly the operational workload of 5-7 full-time employees
Scale Pod.
- 1 POL + 5-7 specialists + dedicated AI automation specialist (not shared)
- Covers full operational layer plus specialized functions (e.g., marketplace ops, advanced CRM, sales ops support)
- Fits: $10M-$20M ARR operator-led businesses, or smaller businesses with unusually complex operations
- Throughput capacity: roughly the operational workload of 8-12 full-time employees
Above the Scale Pod, the operation has typically grown to a point where multiple Pods or a hybrid (internal ops team + Pod) makes more sense than a single very-large Pod.
When to stay at current bracket
Three structural signals that staying is the right call.
Signal 1: workload at 70-85% of Pod capacity. This is the sweet spot. Pod has enough headroom to absorb spikes (launches, holidays, surprise volume) without quality degrading. Not so under-utilized that you're paying for capacity you're not using.
Signal 2: no major scope additions planned in the next 6 months. The roadmap doesn't include a new product line, a new region, a major new channel, or a new customer segment. The operational shape will look similar in month 12 to how it looks in month 6.
Signal 3: KPI trends stable or improving. The 3-metric dashboard (throughput / quality / outlier) shows healthy trends. No deteriorating metric needs more capacity to address.
If all three signals are true, stay. The Pod is operating where it should be.
When to scale up
Three structural signals that scaling up is the right call.
Signal 1: workload consistently at 95%+ capacity. The Pod is running hot. Specialists are working at peak throughput most weeks. Vacation coverage is fragile. SLAs are starting to slip on busy weeks. This is the operational signal that capacity is the binding constraint.
Signal 2: new functions or volume coming online. The business is launching a new product, expanding to a new region, opening a new channel, or growing volume in a way that's going to compound the operational load. The Pod needs to be sized for the coming load, not the current load.
Signal 3: founder time on ops is creeping back up. This is the most subtle signal. Founder time on ops dropped to ~1 hour/week post-Trial. If at month 6 it's drifted back to 4-6 hours/week, something is structural. Usually the Pod is over-capacity and escalations to founder are filling the gap.
If 2-3 signals are true, scale up. Don't wait. Scaling up takes 4-6 weeks (new specialists need onboarding). If you wait until you're already broken, you spend 6 weeks broken.
Pods scale better when you commit to the next bracket BEFORE you fully need it, not after. The 4-6 week onboarding window for new specialists means scaling reactively always lands late.
When to scale down
Real but rare. Three structural signals that scaling down or pausing fits.
Signal 1: business is contracting. Revenue is declining. Customer base is shrinking. The operational load that justified the bracket no longer exists. Scaling down preserves cash while keeping coverage on the workflows that still matter.
Signal 2: a major function moved in-house. You hired an in-house ops manager, or your team grew to absorb workflows that were Pod-handled. The Pod's scope can shrink to focus on the workflows that still benefit from external operation.
Signal 3: strategic pivot makes the current scope wrong. The business is pivoting (new model, new segment, new go-to-market). The current Pod scope doesn't fit the new direction. Scaling down to Lite while the new direction settles makes sense.
The mechanics: 30 days notice, bracket-resize discussion with the POL, transition plan for any specialists who would rotate off the Pod (some return to the bench, some get reassigned to other Pods).
The honest 6-month inventory
Whatever the decision, month 6 is a good moment to take inventory of what the engagement has actually produced. The questions worth answering honestly:
- What's working operationally? Which workflows are running better than they were pre-Pod?
- What's NOT working? Any function where you wish the result were different? Why?
- Where is the operation still founder-dependent? Any escalation pattern that's persistent?
- What's the financial impact? Hours saved, cost saved, revenue retained, NPS improved, etc.
- Would you re-sign if you were deciding fresh? This is the cleanest test of fit.
The honest answers shape both the bracket decision and the conversation with the POL about what to keep, what to change, and what to add.
Where month 6 conversations typically land
In our experience across engagements:
- ~60% stay at current bracket
- ~25% scale up
- ~10% restructure scope without changing bracket (different function mix at same size)
- ~5% scale down or pause
The 60% staying is the most common because the optimization pass at month 3 typically leaves the operation well-tuned. The 25% scaling up reflects business growth. The Pod that fit at month 1 fits less well at month 6 of a growing business.
What month 12 looks like (preview)
Month 12 is the renewal conversation. Less about brackets, more about strategic alignment: is the Pod the right long-term shape for the business, or has the business outgrown the model? Different framing than month 6.