There is no correct answer, which is why the debate never ends. There are two known failure modes, and you are choosing which one to manage.
Under sales
What it produces: tight alignment with what actually closes. SDRs hear deal feedback quickly, and AEs treat their meetings as their own pipeline.
The failure mode: short-termism. A sales leader under quota pressure will pull SDRs toward whatever books this month, which means working the easiest accounts and de-prioritising the slower, larger ones. Coaching is also the first thing cut at quarter end, exactly when it matters.
Best when: the motion is proven and the constraint is execution.
Under marketing
What it produces: better connection to campaign, content, and signal. Inbound follow-up is faster, and messaging tests are more disciplined because marketing runs tests for a living.
The failure mode: drift from sellability. Measured on volume, the team produces meetings that sales does not want, and the argument becomes a lead quality dispute that neither side can resolve because they are measured differently.
Best when: demand generation is the constraint, or the ICP is still moving.
Standalone, reporting to revenue
What it produces: the function gets its own voice, its own career path, and protection from both quarterly pressure and volume targets.
The failure mode: isolation. A standalone team can optimise its own numbers while serving neither side, and it needs a leader senior enough to hold that line.
Best when: the team is large enough to justify it, usually above ten to fifteen reps, and there is a credible leader.
The question that settles it
Not which structure is better. Which failure can you least afford this year?
- If your problem is that meetings do not convert, the sales line reduces the
distance to what closes.
- If your problem is not enough qualified conversations at all, the marketing
line brings demand generation closer.
- If your problem is that the SDR function keeps getting raided for headcount
or attention, standalone protects it.
What matters more than the line
The shared number at the handoff. A team reporting anywhere will behave well if both sides of the seam carry meeting-held rate and next-step rate, and badly if each side carries its own volume metric.
That is the argument in why GTM alignment matters and the SDR to AE handoff: structure sets the default, measurement sets the behaviour, and measurement wins.
Where this sits
Reporting structure is Motion in the Tenbound Pipeline Architecture Standard, with consequences in Mastery. The line decides who coaches, and coaching is the input that decays fastest under pressure. See SDR coaching.