Sales development team structure

The order matters. If a team is built before its mission and ideal customer profile are settled, it will make up its own definition of a good account. An SDR without a written ideal customer profile creates one from whoever replies.¹ That profile can harden into a target list that sends the team after the wrong market later.² Decide the output and boundaries before headcount, territories, or reporting lines. This keeps the structure tied to revenue work.

Set the mission

Start with the work the team must own. The mission should name an output someone can inspect once the work is complete.

The team builds consistent pipeline for account executives by acquiring or qualifying leads.³ Before setting it up, tie the team to a specific business goal, challenge, or growth opportunity.⁴ That gives you an ROI hypothesis and the performance measures needed to test it.⁵

Ask which job you are assigning:

• "Is your aim to better qualify leads and free up rep time for calls and meetings?"⁶
• "Or are you looking to get more meetings for reps in their assigned territories, or perhaps in their assigned account list?"⁷

Proceed once the objective is an observable output. If the team needs to do both jobs, decide which output will shape hiring, coverage, coaching, and measurement first.

Choose the output

Choose the handoff before dividing the market. It sets the skills the team needs and what the receiving team can reasonably expect.

There are two main models: setting introductory meetings and generating qualified opportunities.⁸ With an introductory meeting, the prospect understands the overall value proposition while readiness and ability to move forward remain unqualified.⁹ A qualified opportunity requires the rep to move the prospect from curiosity into interest and verify that the prospect meets or exceeds a minimum threshold.¹⁰

Use the introductory meeting model when the market for the product is immature or account executives need more at-bats.¹¹ For a qualified opportunity model, write the minimum threshold into the acceptance rule. Include the problem to confirm, the level of interest required, and the conditions that allow the next conversation to proceed.

Listen for whether people use "meeting" and "opportunity" as if they mean the same thing. They describe different handoffs. The receiving team should be able to accept or reject the output using a rule the sending team can apply consistently.

Choose the coverage boundary

Coverage gives each person a clear place to work and gives you a way to spot gaps. Pick the boundary that matches how your buyers are grouped.

SDRs can focus on a territory or market vertical where they canvass and qualify prospects.¹² New sales reps are typically assigned a geographic territory or leads from a particular market segment.¹³ Use one primary boundary for each assignment and write what happens when an account fits more than one boundary.

Write the ideal customer profile with disqualifiers as well as fit criteria.¹⁴ That keeps territory, segment, and vertical decisions from turning into a list of accounts that happened to reply. If coverage is expanding across regions, document where ownership changes and how accounts move between regions. A sales development team may be expanding into a multi-region operating model.¹⁵

Ask which territory or market vertical this person owns and which accounts fall outside the ideal customer profile. Also decide who keeps the account when a region or segment changes. Every assignment needs an owner and an exclusion rule.

Set reporting and management

Reporting determines where coaching time comes from and which work stays protected when forecasts become urgent. Choose the reporting line after the mission and handoff are clear.

SDR teams should report to Sales.¹⁶ Since 2012, 68 percent of groups have sat within the Sales organization.¹⁷ A split model can place inbound sales development under Marketing and outbound sales development under Sales as separate functions.¹⁸ Use that arrangement when the two motions have different work, measures, and handoffs that need separate attention.

Capacity changes with company size. Smaller companies tend to have a higher ratio of SDRs to account executives, so one SDR supports fewer account executives.¹⁹

Keep development in the design as well. SDRs can serve as the organization's talent pipeline while driving sales pipeline.²⁰ Give the role a path to stronger responsibility through the work itself, with coaching tied to the skills the next role requires.

Inspect the structure

Review conversion and fit alongside activity totals. The question is whether the assigned market produces the handoff the business chose.

Conversion rates from SDR-generated leads to qualified opportunities to won deals can hold as pipeline increases when the leads fit the ideal customer profile.²¹ Stronger and more consistent pipeline produces greater and more predictable revenue.²² Review those transitions by territory, vertical, or segment, then trace weak movement back to the boundary, the acceptance rule, or the quality of the accounts assigned.

Look for a pattern before changing the org chart. If activity rises while accepted opportunities fall, inspect the target definition and handoff first. If accepted opportunities convert well in one coverage unit and poorly in another, compare the assigned market and qualification rule before changing people.

What not to do

Check these failure modes before approving the structure. Each one points to a different repair.

• Do not leave the mandate vague. A poorly defined SDR or LDR mandate can create confusion and reduce effectiveness.²³
• Do not choose every possible objective without deciding which work the team will be built around. The activities require different skill sets.²⁴
• Do not measure introductory-meeting quantity while requiring qualified-opportunity quality. That mismatch can end in failure.²⁵
• Do not put a VP of Sales over two SDRs and expect consistent coaching. The VP has a quota, attention follows the forecast, and coaching can stop when it is most needed.²⁶
• Do not wait until after the first hire to write the ideal customer profile. The omission should be fixed before the first hire.²⁷
• Do not treat activity volume as proof of a sound structure. SDRs sent more than 200 emails per day and worked 600 to 700 accounts per month without consistently hitting quota.²⁸

Before approving the org chart, make the mission, output, coverage rule, reporting line, and acceptance test visible in the same operating document. Then review accepted work against the ideal customer profile and its disqualifiers before expanding coverage. You can change headcount or assignments with a reason attached to the change.