Sales development team structure

Build the team around the work it must do, the buyers it must cover, and the handoff it must produce. Decide the mission, then write the customer definition and coverage rules before drawing reporting lines. The expensive mistake is letting early replies define the market. An SDR without a written ICP creates one from whoever replies.¹ That profile can harden into a target list that sends the team after the wrong market.² A clean org chart cannot repair that sequence.

Set the mission before the org chart

Give the team one outcome to optimize before deciding who reports to whom. The mission should tell each person what work belongs to the team and what handoff counts as success.

A poorly defined mandate creates confusion and reduces the effectiveness of the role.³ Decide the objective before you hire or assign coverage.⁴ Two main operating models are setting introductory meetings and generating qualified opportunities.⁵ With introductory meetings, prospects understand the broad value proposition while their readiness or ability to move forward remains unqualified.⁶

Use the objective to settle the first design choice. Ask, "Is your aim to better qualify leads and free up rep time for calls and meetings?".⁷ Or ask, "Or are you looking to get more meetings for reps in their assigned territories, or perhaps in their assigned account list?"⁸

Write the answer in one sentence. Then define what the next team owns, what the receiving team owns, and what must be true before a handoff happens. Move on when the team can explain its job without adding a second mission.

Write the customer definition before assigning coverage

Coverage works when the team knows which accounts belong in it. Put the customer definition on paper before using it to divide territories, segments, or account lists.

The absence of a written ICP is easy to miss because people can believe they agree on the customer until they write their definitions separately and discover disagreement.⁹ Include disqualifiers alongside fit criteria.¹⁰ Fix the definition before the first hire.¹¹

Include the conditions that make an account worth pursuing and the conditions that remove it from coverage. Test the definition against accounts the team already wants to pursue, then resolve disagreements before assigning ownership.

Choose the coverage axis from the work

Choose one primary ownership rule for each account. The work may call for market segmentation, geographic coverage, or another division that matches how prospects are reached and qualified.

The appropriate sales process structure depends on the segment and the work involved.¹² New sales representatives are typically assigned a geographic territory or leads from a particular market segment.¹³ After the first two or three reps, leaders will probably begin drawing segmentation lines.¹⁴

Start with the division that makes account ownership easiest to understand. If geography drives the work, assign territory. If buyer type drives it, assign segment. If both matter, choose which rule decides ownership when they conflict and document the exception.

Check the support available to each segment before finalizing the design. A sales organization can place representatives in a segment without product support.¹⁵ Ask what help the team needs to qualify and progress accounts, then make the gap visible before the first assignment.

Set the reporting line around the handoff

The reporting line should help the team improve at the work it owns. Place management where coaching, prioritization, and handoff quality can be inspected consistently.

SDR teams should report to Sales.¹⁶ One operating model places inbound sales development within Marketing and outbound sales development within Sales as separate functions.¹⁷

Use a split when inbound and outbound have different missions, inputs, and performance measures. Keep ownership of each motion explicit. A reporting line that changes the team’s mission from one quarter to the next makes performance harder to interpret.

Ask who owns the definition of a qualified handoff, who coaches the work, and who resolves disputes over account ownership. That person should have enough authority to change the process when the handoff fails.

Match coverage to deal complexity and team size

1

SMB

2

Mid-market

3

Enterprise

1. SMB
2. Mid-market
3. Enterprise

The support each person needs changes with the market served. Build progression into the structure so the team can take on more complex work as its judgment improves.

One progression runs from SMB to mid-market to enterprise, with mid-market and enterprise SDRs paired individually with AEs.¹⁸ Smaller companies tend to have a higher ratio of SDRs to AEs, so one SDR supports fewer AEs.¹⁹

An SDR is typically an early career professional who builds consistent pipeline for AEs by acquiring or qualifying leads.²⁰ The team can also serve as the organization’s talent pipeline while driving sales pipeline.²¹

Use complexity to decide when an account needs dedicated attention. Ask whether the person covering the account can qualify it, explain the next step, and maintain the handoff standard without constant intervention. When that changes, adjust the pairing, segment, or management support.

Connect structure to measurement

A structure earns its place when its results can be inspected. Tie the team’s measures to the mission chosen at the start.

Set up the team around a specific business goal, challenge, or growth opportunity.²² That choice creates an ROI hypothesis and clarifies the performance metrics needed to test it.²³

If the mission is lead acquisition and qualification, inspect whether the leads fit the ICP through the later stages of the funnel. Conversion rates from SDR generated leads to qualified opportunities to won deals hold as pipeline increases when the leads fit the company’s ideal customer profile.²⁴ Stronger and more consistent pipeline produces greater and more predictable revenue.²⁵

Choose measures that expose handoff quality as well as the activity used to create it. When the downstream result weakens, check the customer definition, coverage rule, qualification standard, and receiving team in that order. Move on when the measure tells you which part of the structure needs attention.

Revisit the design as the team changes

Treat structure as a working decision that needs review when the market, mission, or team changes. Review the sequence of problems instead of waiting for a missed target to reveal every flaw at once.

Teams building sales development for the first time encounter the same problems in roughly the same order.²⁶ Knowing that order matters because prevention costs less than repair.²⁷ When a sales team misses expectations, evaluate its structure and whether the right people are in the right positions.²⁸

Use a review to ask what has changed in the work, which accounts now need different coverage, and whether the handoff still matches the mission. Make one structural change at a time when possible, then inspect the result against the measure tied to that change.

What not to do

Keep these failures out of the design before they become management problems.

• Do not choose every objective at once, because the objectives involve different activities and require different skill sets.²⁹
• Do not put a VP of Sales in charge of two SDRs and expect consistent coaching, because quota pressure pulls attention toward the forecast and coaching stops when it is needed most.³⁰
• Do not assign every motion to one role, because sales teams should be specialized into different sales roles.³¹