Inbound qualification team structure in UK SaaS in 2026

Inbound qualification team structure in UK SaaS in 2026 has converged on three patterns at 50-300 person scale. None is universally correct; the right pattern depends on inbound volume and AE seniority.

Pattern 1: Inbound SDR pod, separate from outbound SDR pod. Inbound SDRs run BANT-lite, book meetings to AEs, sit on a shorter response-time SLA than outbound (typically under 10 minutes for a high-intent inbound). Works when inbound volume justifies dedicated headcount (typically 50+ inbound leads per week per inbound SDR).

Pattern 2: AE direct-to-lead at high intent, SDR at lower intent. The highest-intent inbound (demo requests, contact sales) routes straight to an AE on a round-robin or territory basis; lower-intent (content downloads, webinar registrations) routes to SDR. Common at smaller scale where dedicated inbound headcount isn't justified. AEs prefer this because they own the lead from first touch; the cost is response-time variance.

Pattern 3: Marketing-ops triage, then routing. Marketing operations applies a scoring model and routes accordingly. Common at larger scale. The tradeoff is added latency: a lead might wait 1-2 hours in the scoring queue before reaching the SDR or AE.

The hire pattern: inbound SDRs typically come from junior CS or BDR backgrounds; they must be comfortable on the phone within 10 minutes of a self-serve form completion. Comp pattern is similar to outbound SDR (80/20 or 75/25 base/variable) but with the variable usually tied to AE-accepted-pipeline rather than meetings-booked, to avoid the SDR optimising for booked-but-low-quality inbound.

The trap: confusing inbound volume for inbound quality. Marketing teams report 'lead volume up 30 percent quarter-on-quarter'; sales teams report 'AE-accepted-pipeline flat'. The metric to watch is AE-accepted-pipeline per inbound SDR per week, not inbound volume.