Pod Retainer bracket pricing: Lite vs Standard vs Scale

PodFleet Pod Retainers come in three brackets: Lite, Standard, and Scale. Each one is optimized for a different operational shape, with different headcount, different scope coverage, and different pricing. Picking the right bracket is a sizing exercise, not a budget exercise.

Here is what each bracket includes, what each one fits, and how to figure out which one is right for your business.

What every Pod includes (regardless of bracket)

Before the bracket differences: every Pod, at every size, includes the same foundational structure.

• 1 Pod Operations Lead (POL) as your single point of contact
• 1 AI automation specialist (standard layer, not an upsell tier)
• Full SOP library, owned by you forever
• Metrics dashboard configured against your data
• 10-business-day replacement guarantee
• Daily async updates + weekly review
• Month-to-month commitment after 90-day initial period

What changes between brackets: the number of specialists, the scope they cover, and the AI specialist allocation.

Lite Pod

Composition: POL + 2-3 specialists + shared AI specialist.

Scope coverage: 1-2 deep functions OR 2-3 lighter functions.

Typical specialist mix:

• 1 customer support specialist
• 1 community manager OR 1 content operations specialist
• 1 data/admin specialist (often part-time within the Pod)

Throughput capacity: roughly equivalent to 3-4 full-time employees' operational work.

Fits:

• $1M-$3M ARR operator-led businesses
• Operations focused on 1-2 high-volume functions (e.g., a creator with massive support volume + a community)
• Smaller eCommerce brands (under 10K orders/month)
• Early-stage SaaS (under 5K tickets/month)
• GHL whitelabel agencies under 40 end-clients

Doesn't fit:

• Businesses needing full operational coverage across 4+ functions
• Businesses needing specialized roles (marketplace ops, sales ops, RevOps)
• Operations with 50K+ orders/month or 10K+ tickets/month

Common Lite Pod scope pattern:

• CX desk (Helpscout, Gorgias, Zendesk)
• Community moderation (Skool, Circle, Discord)
• AI automation layer
• Basic admin (CRM hygiene, weekly reporting)

Standard Pod

Composition: POL + 3-4 specialists + shared AI specialist.

Scope coverage: 3-4 operational functions, mid-depth.

Typical specialist mix:

• 1 customer support specialist
• 1 community manager
• 1 content operations specialist
• 1 data/admin specialist (full-time within the Pod)

Throughput capacity: roughly equivalent to 5-7 full-time employees' operational work.

Fits:

• $3M-$10M ARR operator-led businesses
• Operations spanning CX, community, content, and admin
• Mid-size eCommerce (10K-50K orders/month)
• Growing SaaS (5K-20K tickets/month)
• GHL whitelabel agencies between 40 and 120 end-clients
• Multi-product creators with both course + membership + newsletter

Doesn't fit:

• Very specialized operations needing 6-7+ specialists
• Businesses with very high single-function volume (e.g., 100K+ tickets/month support-only)
• Operations needing dedicated functions outside the standard layer (sales ops, RevOps, marketplace ops at deep level)

Common Standard Pod scope pattern:

• Full CX desk with AI-assisted drafting
• Community moderation + member lifecycle management
• Newsletter, podcast, YouTube content ops
• CRM hygiene, weekly KPI reporting, board prep support
• 6 daily automations running

This is the bracket most PodFleet clients land in. Most 7-figure operator-led businesses fit Standard cleanly.

Scale Pod

Composition: POL + 5-7 specialists + dedicated AI specialist (not shared).

Scope coverage: Full operational layer + specialized functions.

Typical specialist mix:

• 1-2 customer support specialists (tiered)
• 1 community manager
• 1 content operations specialist
• 1 data/RevOps specialist
• 1 sales ops or marketplace ops specialist (depending on business)
• 1 dedicated AI specialist

Throughput capacity: roughly equivalent to 8-12 full-time employees' operational work.

Fits:

• $10M-$20M ARR operator-led businesses
• Operations with deep specialization needs (multi-channel CX, sales ops, marketplace ops)
• Larger eCommerce (50K-200K orders/month)
• SaaS at 20K+ tickets/month or with complex customer success motion
• GHL whitelabel agencies at 120+ end-clients
• Multi-brand or multi-region operations

Doesn't fit:

• Businesses under $10M ARR (over-staffed for the volume)
• Businesses at $20M+ ARR (usually better served by multi-Pod arrangement or hybrid in-house + Pod)

Common Scale Pod scope pattern:

• Tier 1 + Tier 2 + Tier 3 CX (with explicit escalation paths)
• Community + member success ops
• Multi-channel content ops (newsletter, podcast, YouTube, social)
• Sales ops support (lead routing, demo scheduling, CRM hygiene)
• Marketplace ops (Amazon, Walmart, etc.)
• Dedicated AI specialist with custom workflow buildouts

How to pick the right bracket

Three signals to weigh.

Signal 1: revenue range.

• Under $3M ARR → Lite
• $3M-$10M ARR → Standard
• $10M-$20M ARR → Scale

This is the starting heuristic. Most businesses land in the bracket their revenue suggests. Override the heuristic only if the next two signals strongly point elsewhere.

Signal 2: function count + depth. Count the operational functions you need the Pod to cover. Estimate depth (how many specialist-hours per week each one needs).

• 1-2 functions, deep: Lite
• 3-4 functions, mid-depth: Standard
• 4+ functions OR specialized depth (sales ops, marketplace ops, RevOps): Scale

Signal 3: founder time recovery target. How many hours/week do you want to recover from operational work?

• Recovering 10-15 hours/week: Lite usually sufficient
• Recovering 15-25 hours/week: Standard
• Recovering 25+ hours/week or supporting a multi-team operation: Scale

The right bracket is usually the one that satisfies all three signals. If they conflict (e.g., revenue says Lite but function count says Standard), the function count signal usually wins because that's the actual operational shape.

Bracket up if your operation needs the headcount. Don't bracket up just because you can afford it. Over-bracketed Pods are operationally wasteful and the cost shows up in your monthly invoice.

Bracket switching after engagement starts

The retainer is month-to-month after 90 days. Bracket changes are possible:

Up (Lite → Standard or Standard → Scale):

• 30 days notice to trigger
• 4-6 weeks to onboard new specialists into the Pod
• New cost effective the first full month after onboarding completes

Down (Standard → Lite or Scale → Standard):

• 30 days notice to trigger
• Pod specialists who rotate off return to the PodFleet bench (no severance issue on your side)
• New cost effective the first full month after the transition

The month-6 conversation is the natural moment most clients re-evaluate bracket fit. The month-12 conversation typically re-evaluates strategic alignment, not bracket.

Why the brackets exist (instead of fully custom Pod sizing)

Three structural reasons.

Reason 1: brackets price predictably. Custom-sized Pods would mean custom pricing for every engagement. Brackets let us publish a predictable cost structure (within the ranges in the cost breakdown post) and let founders plan budgets.

Reason 2: brackets staff predictably. We hire and train against bracket-sized teams. A Standard Pod gets composed from our existing specialist bench in 2-4 weeks. A fully custom Pod would require custom recruitment per engagement, which would push onboarding from 4 weeks to 10-12.

Reason 3: brackets fit clean operational thresholds. The transitions between Lite, Standard, and Scale correspond to real operational inflection points in business growth. Businesses at the boundaries naturally re-evaluate bracket fit. The structure matches how operations actually grow.