Outbound at Scaleup Scale: The Two-Pod Model
SDR-driven outbound stalls between £5M and £20M ARR for predictable structural reasons. The two-pod model — separating inbound conversion from outbound creation — restores velocity by recognising that the two motions have different rhythms.
The short answer
Single-pod SDR outbound stalls between £5M and £20M ARR because the same team is being asked to do two structurally different jobs: inbound conversion (short cycle, high velocity, qualified) and outbound creation (long cycle, research-heavy, multi-threaded, low velocity). SDRs default to the higher-velocity inbound work, outbound starves, and the outbound pipeline projection misses by 60 to 80 percent. The two-pod model separates the motions into distinct teams with distinct managers, comp plans, and rhythms.
Key Takeaway: The outbound stall is not an SDR-quality problem; it is an operating-model design problem. The two-pod separation is a structural decision that recognises inbound conversion and outbound creation as different jobs requiring different teams, different incentives, and different cadences. Companies that make the separation by £10M ARR rebuild outbound velocity; companies that try to fix it inside a single pod do not.
Why most founders get this wrong
The standard error is treating outbound underperformance as an SDR-team-quality issue. The team is held to outbound quotas, hits inbound quotas comfortably, misses outbound badly, and the response is to hire more SDRs, replace the SDR manager, or invest in better tooling. None of those interventions address the structural cause: SDRs are doing two jobs and rationally choosing the easier one.
The second error is misreading the early-stage success. At under £5M ARR, single-pod SDR teams often hit both inbound and outbound numbers because the inbound volume is manageable and the outbound goals are modest. The same team that succeeded at £3M is held responsible for the failure at £8M, and the diagnosis attributes the failure to execution rather than to the structural change in the underlying problem.
The third error is implementing a half-separation: the same SDR team with two queues, the same manager with two sets of metrics, the same comp plan with two weighted components. The half-separation produces the same problem in slightly more elaborate form. The SDRs still optimise for inbound velocity; the outbound queue still starves; the operating-model design does not get fixed because the fix was not architectural.
Why the rhythms are incompatible
Inbound conversion is high-velocity work: a lead arrives, gets qualified within 15 minutes, books a meeting within 24 hours, and either closes within the quarter or drops out. The cycle is short, the activities are repetitive, and the daily routine is reactive — driven by the inbound queue. The right SDR profile is high-velocity, high-volume, comfortable with repetition.
Outbound creation is research-heavy work: the SDR identifies an account, researches the buying centre, identifies the multi-threaded approach, and runs a sequence over weeks to months. The cycle is long, the activities are bespoke, and the daily routine is proactive — driven by the SDR's account-research backlog. The right SDR profile is research-oriented, lower-volume, comfortable with sustained multi-week work.
The two profiles are different people. Asking one person to do both jobs is asking them to switch cognitive modes multiple times per day, which they will resolve by gravitating to the work that produces immediate measurable progress (inbound) at the expense of the work that produces delayed measurable progress (outbound).
Warning: The two-pod separation needs to happen before outbound has visibly stalled. Companies that wait until the stall is obvious face a 9 to 12 month rebuild that the Series B timeline often cannot accommodate. The earlier the separation, the smaller the rebuild.
What "good" looks like
The two-pod model is structurally simple and operationally specific. Two distinct teams, two distinct managers, two distinct comp plans, two distinct cadences. The boundary is the source of the lead, not the type of account.
1. Inbound pod — sized for inbound velocity
Team that handles all inbound leads regardless of source (website, content, paid, partner-referred). Comp plan rewards speed-to-meeting and meeting-to-opportunity conversion. Manager owns inbound SLA and conversion rates. Cadence is daily and reactive — the queue determines the work.
2. Outbound pod — sized for outbound creation
Team that handles all outbound prospecting into target accounts that have not raised their hand. Comp plan rewards account-development progression and meeting-creation in target accounts. Manager owns target-account list quality and account-progression metrics. Cadence is weekly and proactive — the account-research plan determines the work.
3. Define account-handoff rules between pods
An outbound pod's progression to "scheduled meeting" hands the account to the AE; the inbound pod handles inbound leads from any account regardless of outbound history. Document the rule explicitly to prevent the two pods double-claiming the same account or losing accounts in the handoff.
4. Manager and rituals for each pod
Separate weekly stand-ups, separate metrics dashboards, separate skill-development tracks. The pods can share a senior leader (VP Sales Development) but the day-to-day management has to be distinct or the cultural drift back to single-pod begins immediately.
The Bottom Line
The two-pod separation is the structural fix to a structural problem. Companies that make the separation by £10M ARR rebuild outbound velocity inside two quarters; companies that try to fix it through SDR-quality interventions inside a single pod do not. The cost of the separation (one additional manager, two distinct comp plans, separate rituals) is small relative to the operating-model upside.
How to apply it to your round
Series B partners reading outbound narratives ask three direct questions: how is your SDR team structured, what percentage of pipeline is outbound-sourced versus inbound-converted, and what is your outbound-pipeline projection method. A founder who can describe the two-pod structure with the corresponding metrics presents an operating-model-grade outbound function. A founder who describes a single SDR team with mixed metrics signals an unfixed structural risk.
The implementation sequence for companies approaching or already in the £5M-£20M window:
Diagnose the current state. Pull SDR activity data and decompose by inbound vs outbound. If outbound activities are below 30 percent of total SDR time and outbound-sourced pipeline is below 20 percent of total pipeline, the single-pod model has structurally collapsed and the separation is overdue.
Plan the separation as a 90-day project. Hire or promote the second manager. Design the two distinct comp plans. Build the two distinct dashboards. Document the handoff rules. The 90 days are the design and rollout window; the first quarter post-rollout is the measurement window; the second quarter is when the velocity recovery shows up in pipeline.
Communicate the change clearly. SDRs need to understand which pod they are in, why, and how the comp plan rewards the work specific to their pod. Without clear communication, SDRs default back to the work that produced their previous comp.
Cross-link reading: RevOps at 100 people for the revenue-operations function that supports both pods; GTM efficiency in 2025 for the metric consequences of an unfixed outbound function; building the expansion motion before Series B for the related expansion-motion design.
The right SDR-to-AE ratio for each pod
The pod-specific ratios differ. Inbound pods typically run at 1 SDR to 1 AE for high-velocity mid-market motions and 1.5 SDRs to 1 AE for higher-volume PLG-supplemented motions. Outbound pods typically run at 1 SDR to 1 AE for enterprise motions where the SDR work per account is heavy, and at 2 SDRs to 1 AE for mid-market motions where the SDR work is lighter per account but spread across more targets. The combined-pod ratio that founders sometimes calculate (total SDRs to total AEs) is meaningless and obscures the pod-specific economics.
The ratios should be re-tested quarterly. Inbound volume changes with marketing spend and content velocity; outbound capacity changes with SDR ramp-up and target-account list refreshes. The ratios that worked in Q1 are usually not the right ratios for Q4 of the same year.
Common implementation mistakes after the separation
Three implementation mistakes recur after the two-pod separation is announced. First, allowing the inbound pod to "help out" with outbound when the inbound queue is light — this re-creates the original problem with more elaborate paperwork. The discipline is to keep pods strict; idle inbound capacity is acceptable in the short term and corrects naturally as inbound volume rises. Second, comping the outbound pod on the same activity metrics as the inbound pod. Outbound activity metrics (account research, multi-thread engagement, sequence completion) differ from inbound activity metrics (speed-to-meeting, qualification accuracy); using inbound metrics on outbound suppresses the very behaviours the separation was designed to enable. Third, re-merging the pods at the first sign of one pod underperforming. The natural reflex is to reorganise; the right response is to diagnose the underperformance within the affected pod's design and adjust the design rather than dismantle the structure.
Related reading
For the RevOps function that supports both pods with shared infrastructure, see RevOps at 100 people: the three hires that compound. For the GTM efficiency consequence of an unfixed outbound function, see GTM efficiency in 2025. For the partnerships dimension that contributes pipeline alongside outbound, see partnerships as a growth vector. For the framework view, see The Opagio 12™.
Make the separation before the stall
Eight minutes. Twelve drivers. The starting frame for a two-pod outbound function that compounds velocity instead of stalling at £10M ARR.