Scale · Outbound at Volume

Build an Outbound Pod Structure (SDR + AE)

Design a repeatable SDR + AE pod that owns a slice of ICP, hits volume targets, and scales by cloning the pod — not by hiring chaos.

foundermanagerAdvanced⏱ 6-10 hours of org design
When to use
Use this when your single SDR is maxed and you are about to hire a second rep — or when you are spinning up your first formal sales org. The pod model gives you a cloneable unit so each new hire fits a slot, not invents one. Run before you write the next job description.
The prompt
You are a head of outbound at a digital marketing agency running 1,000+ touches/week without burning domains. You build pod structures the way franchises build store playbooks — repeatable, accountable, cloneable.
Agency: [AGENCY_NAME] — [SERVICES] | ICP: [ICP] | Weekly target: [WEEKLY_VOLUME_TARGET] | Team: [TEAM_SIZE] | Stack: [TECH_STACK] | Sending domains: [DOMAINS] | Avg deal size: [ACV] | Sales cycle: [SALES_CYCLE]
Design a pod structure pairing SDRs with AEs to cover [ICP]. Define pod composition, ratios, territory/ICP slicing, weekly activity quotas, handoff SLAs, comp structure, and the cloning trigger (when to spin up pod #2).

- Each pod must own a distinct ICP slice — no overlap, no lead fights.
- Quotas tied to [ACV] and [SALES_CYCLE], not vanity activity.
- Include explicit SDR-to-AE handoff SLA (response time, qualification bar).
- Comp structure must reward pod outcomes, not individual heroics.
- Define the metric trigger that authorizes hiring pod #2.
Output: (1) Pod org chart, (2) Role JD summaries, (3) ICP slice map, (4) Weekly quota dashboard mock, (5) Handoff SLA doc, (6) Comp plan table, (7) Pod-cloning trigger.
Variables
  • [AGENCY_NAME] — Your agency name
  • [SERVICES] — What you sell
  • [ICP] — Ideal customer profile
  • [WEEKLY_VOLUME_TARGET] — Cold touches per week per pod
  • [TEAM_SIZE] — Current sales headcount
  • [TECH_STACK] — CRM, sending tool, dialer
  • [DOMAINS] — Sending domains
  • [ACV] — Average contract value
  • [SALES_CYCLE] — Avg days from first touch to close
Example input
AGENCY_NAME: Halo Search | SERVICES: SEO + content for B2B SaaS | ICP: Series A-B SaaS, 50-300 employees | WEEKLY_VOLUME_TARGET: 1200 | TEAM_SIZE: 1 SDR + founder selling | TECH_STACK: Smartlead + Pipedrive + Aircall | DOMAINS: 3 alt domains | ACV: $48k/yr | SALES_CYCLE: 42 days
Example output
Pod composition: 2 SDR + 1 AE + 0.25 ops shared. Ratio justified by 42-day cycle and $48k ACV — 2 SDRs feed enough qualified meetings to keep 1 AE at 8 active opps. ICP slice: Pod 1 owns Series A-B SaaS in MarTech + DevTools verticals. SDRs split by vertical, no account overlap. Quotas: each SDR 600 touches/wk, 12 booked meetings/wk; AE 8 first-meetings/wk, 2 closed/mo, $96k MRR added/quarter. Handoff SLA: SDR books, AE confirms within 4 business hours, runs discovery within 5 business days, returns disqualified meetings to SDR within 24 hours with reason. Comp: SDR $55k base + $200/qualified meeting + 2% of pod closed revenue; AE $90k base + 8% of closed revenue + 2% pod kicker. Cloning trigger: when Pod 1 hits 90% of quota 2 quarters running AND a second ICP slice exists with >500 named accounts, spin up Pod 2 (clone, do not modify).
Pro tips
  • Resist hiring a 3rd SDR into one pod — clone the pod instead, it scales cleaner.
  • Comp the AE on pod revenue, not personal — it kills lead-fighting overnight.
  • Write the cloning trigger as a number, not a vibe, or you will hire too early.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts