Built for leaders designing the sales org

Sales team structure is the org chart plus the handoffs. Both have to live in the CRM for the structure to actually run.

Sales team structure covers the role model (SDR, AE, SE, CSM), the segment split (SMB, mid-market, enterprise), the territory model (geo, named-account, round-robin), the pod model (hunter plus farmer plus overlay), and the handoffs between every pair. The structure fails when the CRM holds the names but not the handoffs. Strkr encodes the handoffs as routing rules.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

The hardest part of sales team structure is not the org chart; it is the handoffs. SDR to AE on qualified lead. AE to SE on technical demo. AE to CSM on close plus seven days. AE to AE on account change. Reps to coverage on PTO. Any team past 10 reps has 20-plus handoff rules. Most CRMs hold the org chart as data but encode zero of the handoffs. The result is that structure lives in a Google Doc that nobody updates and reps negotiate handoffs ad hoc. The six pain points below are the ones that come up when teams try to run structure through a CRM that does not encode it.

Handoffs happen on Slack

The SDR DMs the AE and hopes for the best.

When an SDR qualifies a lead, the handoff to an AE typically happens on Slack. The SDR sends a DM with the account name, the AE acknowledges, and the lead changes hands. The CRM record often does not reflect the handoff for hours or days. The lead stays assigned to the SDR until someone updates it. Strkr encodes the SDR to AE handoff as a routing rule triggered on stage change with the record update instantaneous.

Territory models drift

The named-account list from Q1 is stale by Q3.

Teams running named-account models maintain the list in a Google Sheet. The list updates slowly. Accounts that should have moved to another territory stay in the original. Prospecting conflicts (two reps working the same account) happen because the ground truth has drifted from the sheet. Strkr maintains the named-account list as data with routing rules that enforce the territory model in real time.

Role scope blurs under pressure

The AE runs the renewal because the CSM is swamped.

Role boundaries blur under pressure. An AE picks up a renewal because the CSM is swamped. An SE joins a Stage 2 call because the AE needs technical support early. The scope creep is usually benign in the moment but accretes until nobody knows what each role actually owns. Strkr encodes role scope as rules that fire on specific triggers, which creates a reference point for role conversations.

Pod models fragment

The pod structure exists in a slide, not the CRM.

Teams running pod models (AE plus SE plus CSM working as a unit on a book) encode the pod in a slide deck. The CRM assigns deals to individual reps. The pod coordination happens on Slack and in weekly pod meetings. When a new pod spins up or a pod member changes, the structure takes weeks to settle. Strkr encodes pods as a first-class concept with deal ownership, reporting, and routing attached.

Segment splits bleed

A mid-market account grows into enterprise but the rep stays.

Teams split segments by employee count, revenue, or named-account tier. Accounts grow. A mid-market account that crosses into enterprise territory should move to an enterprise AE. The move often does not happen because the rep protects the book. Strkr runs rules that flag segment-crossing accounts for review and routes on the move so the segment split holds.

Compensation misalignment

The pay plan assumes the structure that no longer exists.

The pay plan encodes the structure (SDR pay plan, AE pay plan, enterprise AE pay plan, pod structure, overlay structure). When the structure changes mid-year the pay plan often does not. Reps get paid against the wrong assumption. Finance disputes compound. Strkr versions the pay plan to the structure so a structure change triggers the pay plan update as a related change rather than an orphan.

The role models that work

Four role patterns teams actually use.

The role model is the first structural decision for a sales team past the single-founder-selling phase. The four cards below describe the most common patterns, when they work, and what each encodes in the system.

Pattern 1 · AE only

Single-role motion for small teams or complex deals.

An AE-only model works for teams under 8 reps or for sales motions where every deal needs the senior relationship (large enterprise, specialized vertical). The AE owns prospecting through close. The downside is that AEs spend 30 to 40 percent of time on prospecting rather than deal advancement. The model is often an early-stage default that evolves to AE-plus-SDR as the team scales.

Pattern 2 · SDR plus AE

The classic split for growth stage.

The SDR-plus-AE split separates prospecting from closing. SDRs own outbound and inbound qualification. AEs own Stage 2 through close. The handoff happens on qualification criteria (meeting booked, discovery completed). The model scales well from 8 to 50 reps. Common variant: BDR for inbound, SDR for outbound. The handoff rule is where this pattern lives or dies.

Pattern 3 · SDR plus AE plus SE plus CSM

The product-led technical motion.

For technical products the four-role model adds an SE (sales engineer) for technical demos and a CSM for post-close retention. The SE joins on Stage 3 technical demos. The CSM takes over at close plus 7 days. The pod version groups these four roles into a unit assigned to a book. The role count scales well to 100-plus reps for product-led motions.

Pattern 4 · Hunter plus farmer

Separate new-logo and expansion motions.

The hunter-plus-farmer model separates new-logo acquisition (hunter AE) from existing-account expansion (farmer AE or AM). The farmer owns renewals, upsell, and cross-sell on existing accounts. The hunter owns new logos only. The model fits teams where expansion revenue is a majority of ARR. Common complication: the handoff from hunter to farmer on first close needs clear rules so nobody double-covers.

Territory and segment models

How to split the book without the handoffs breaking.

The territory and segment model (how accounts assign to reps) is the second structural decision. The six cards below describe the common patterns and where each one leaks under scale.

Geo territory

By region, state, or country.

Geo territory assigns accounts by location (US-West, US-East, EMEA, APAC). Works well for field-heavy motions and account-manager models. Leaks when a buyer HQ moves or when a global account spans multiple reps. The rules need an explicit tiebreaker for cross-geo accounts.

Named-account

Each rep owns a list.

The named-account model assigns a fixed list of accounts per rep. Common for enterprise motions where the account relationship is the asset. Leaks when the list drifts from reality (new accounts form, old accounts become dormant). The CRM needs the named-account list as data with routing rules enforcing it.

Segment split

By employee count, revenue, or industry.

The segment split assigns by account size (SMB, mid-market, enterprise) or industry (SaaS, services, retail). Works well for role specialization. Leaks when accounts cross segment boundaries. The rules need a segment-crossing review trigger so accounts move cleanly.

Round-robin

By rotation on inbound.

Round-robin assigns inbound leads by rotation. Common for high-volume inbound motions and SMB books. Works well when every lead is roughly comparable. Leaks when leads are not comparable (a well-qualified enterprise lead gets routed to an SMB-focused rep). The rules need segment-first routing with round-robin as the fallback.

Industry vertical

By specialization in a vertical.

Industry vertical assigns by rep specialization in a vertical (healthcare, fintech, manufacturing). Works well where domain knowledge is a buying signal. Leaks when accounts cross verticals (fintech that also serves healthcare). The rules need primary-vertical with cross-vertical review.

Hybrid

Named-account plus segment-fallback.

The hybrid model combines named-account for top-tier accounts with segment-fallback for the rest. The top 100 to 500 named accounts assign to specific reps; the long tail routes by segment. Works well for teams past 30 reps where named-only is impractical but pure-segment loses the strategic-account focus.

The handoffs that make the structure run

Eight handoffs every team past 10 reps needs to encode.

The structure that is written on a slide is not the structure that runs; the structure that runs is the one encoded as handoff rules in the system. The eight cards below are the handoffs every team past 10 reps needs to encode explicitly.

Handoff 1 · SDR to AE

On qualified lead stage change.

The SDR-to-AE handoff fires on stage change from Qualified to Working. The rule routes the lead to the AE whose territory, segment, or named-account list matches. The SDR gets credit through the pay plan. The AE sees the handoff on their home screen within seconds. The common failure mode (Slack DM then wait for CRM update) disappears.

Handoff 2 · AE to SE

On technical-demo request.

The AE-to-SE handoff fires on technical-demo scheduled. The rule routes to the SE pool with capacity and expertise matching (industry, product area). The SE sees the request with the deal context, buyer stakeholders, and prior calls attached. The handoff eliminates the Slack-ping-and-hope pattern common with specialist roles.

Handoff 3 · AE to CSM

On close plus 7 days.

The AE-to-CSM handoff fires on close plus 7 days (configurable). The rule routes to the CSM owning the segment or named-account list. The CSM gets the deal context, decision-maker map, and implementation notes. The 7-day buffer gives the AE time for the thank-you touch and the implementation kickoff.

Handoff 4 · AE to AE (account change)

On segment crossing or territory shift.

The AE-to-AE handoff fires on an account crossing segment or moving territory. The rule flags the account for manager review (to avoid gaming the trigger) and routes on approval. The source AE gets credit for in-flight pipeline through a defined window. The pattern eliminates territory disputes.

Handoff 5 · Rep to coverage (PTO)

On PTO date range.

The PTO handoff fires on a rep marking PTO. The rule reassigns next-touch owners for the window to a coverage rep. The reassignment reverts on return. Deals that moved stages during PTO notify the returning rep. The pattern eliminates the Slack-handoff-and-forget failure mode.

Handoff 6 · Rep to rep (deal transfer)

On explicit transfer with manager approval.

Rep-to-rep deal transfers (strategic reasons, workload rebalancing) fire on explicit transfer request. The rule routes to manager approval with the context: current pipeline value, time in cycle, strategic reason. On approval the deal transfers with full history and the pay plan logic adjusts.

Handoff 7 · SE to AE (back on close)

On technical-demo complete.

After the SE runs the technical demo and the deal progresses, the primary ownership stays with the AE. The SE handoff-back is implicit: the SE remains on the deal timeline but AE owns next steps. This handoff is where overlay roles often cause confusion if not encoded.

Handoff 8 · CSM to AE (expansion)

On expansion opportunity surfaced.

The CSM-to-AE handoff fires when a CSM identifies an expansion opportunity. The rule routes to the AE owning expansion for the account (sometimes the same AE who closed; sometimes a dedicated expansion AE). The pattern makes expansion a managed motion rather than a cultural one.

Head-to-head

Strkr versus the slide-deck sales team structure.

The head-to-head below is Strkr with structure encoded as rules against the common pattern of structure living in slide decks and Google Docs with the CRM holding only the org chart.

Feature Strkr Slide-deck structure plus CRM org chart
Role scope Encoded as rules that fire on triggers Lives in slides, drifts in practice
Handoffs Routing rules on stage change Slack DMs and tribal norms
Territory model Named-account list as data with enforcement Google Sheet maintained slowly
Segment splits Rules route on segment-crossing Manual reassignment on review
Pod structure First-class concept with ownership Slide deck plus weekly pod meeting
PTO coverage Reassign for window, revert on return Slack handoff, often forgotten
Pay plan alignment Versioned to structure, change together Structure changes, pay plan lags
Deal transfer Request to approval with context Email approval, context lost
New hire onboarding Role model readable in the system Tribal knowledge transfer
Structure changes Configuration change, propagates Weekend of manual reassignment
How teams use Strkr

Teams that redesigned structure around rules.

The four playbooks below are from sales teams who redesigned structure and encoded the handoffs as rules in Strkr. Each describes the structural change and the measurable impact.

B2B SaaS, 35 reps

Moved from AE-only to SDR plus AE plus SE.

A 35-rep B2B SaaS team was running an AE-only model with reps spending 35 percent of their time on outbound prospecting. The team restructured to SDR plus AE plus SE over 90 days. The new structure encoded in Strkr with handoff rules on stage change, SE routing on technical-demo request, and segment-crossing flags for account moves. Attainment improved from 72 percent to 88 percent in two quarters. The VP of Sales said the structural win was that the handoff rules eliminated the 2 to 3 day lag between SDR qualification and AE engagement that had been bleeding deals.

Enterprise B2B, 60 reps

Named-account enforcement eliminated prospecting conflicts.

A 60-rep enterprise B2B team ran a named-account model but the list lived in a Google Sheet. Prospecting conflicts (two reps working the same account) happened monthly. The team moved the named-account list to Strkr as data with routing rules enforcing the assignment. Conflicts dropped to zero in three months. The ops lead said the structural change was that the list became operational rather than aspirational.

Mid-market, 22 reps

Pod structure encoded as first-class concept.

A 22-rep mid-market team wanted to try pods (AE plus SE plus CSM working a shared book of 40 accounts). The incumbent CRM had no pod concept, so the team ran pods in slides with weekly pod meetings. Coordination overhead was high. The team moved to Strkr with pods as a first-class concept. Deal ownership, reporting, and routing attached to the pod. Pod attainment averaged 94 percent versus 81 percent for the non-pod half of the team. The VP of Sales said encoding pods changed them from a coordination burden to a leverage structure.

Growth stage, 12 reps

Started with structure encoded from day one.

A 12-rep growth stage team made the deliberate choice to encode structure from day one. SDR plus AE handoff on stage change. Segment splits with crossing flags. PTO coverage. Pay plan versioned to the structure. The setup took three weeks with a partner. The VP of Sales said the counterfactual (encoding structure after 18 months of accretion) would have been a six-month project. The team scaled to 30 reps on the original structure with incremental refinements.

Encode the structure instead of writing it in slides.

Start a 14-day trial on Strkr with structure encoded: handoff rules, territory routing, segment crossings, pod ownership, PTO coverage, pay plan versioning. See what structure feels like when it actually runs rather than describes.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

What is sales team structure?

Sales team structure is the full set of structural decisions for a sales org: the role model (SDR, AE, SE, CSM), the territory and segment model (geo, named-account, segment, round-robin, vertical, hybrid), the pod model (hunter plus farmer, team pods), and the handoffs between every pair of roles. The structure is the org chart plus the rules. Most teams design the org chart and leave the handoffs to tribal norms. The structure that actually runs is the one encoded in the CRM as routing rules.

What role model should we start with?

For teams under 8 reps, AE-only often works. For teams 8 to 50 reps, SDR-plus-AE is the standard. For technical product-led motions past 20 reps, SDR-plus-AE-plus-SE-plus-CSM covers specialization and retention. For teams where expansion is a majority of ARR, hunter-plus-farmer separates new-logo and existing-account motions. The right starting point depends on the sales motion complexity more than the team size. The common mistake is jumping to a four-role model before the volume justifies the specialization.

When should we move from round-robin to named-account?

Round-robin works when leads are roughly comparable and the volume is high. Named-account works when strategic account relationships are the asset. Most teams move from round-robin to named-account when top accounts start representing a majority of pipeline value or when enterprise motion begins. A hybrid model (named-account for top 100 to 500 accounts, round-robin for the rest) often fits teams in transition. Strkr runs both models and the hybrid.

How do we handle segment crossings?

Segment crossings (a mid-market account grows into enterprise, an SMB account scales up) happen in every team past 15 reps. The structural solution is a crossing trigger that flags the account for manager review before the move happens. On approval the account routes to the receiving-segment AE. The source AE gets credit for in-flight pipeline through a defined window (commonly 90 days). Strkr runs this trigger as a rule with manager approval queue.

How does the pay plan align to the structure?

The pay plan should version to the structure so changes propagate together. When the structure changes (new segment split, pod reorganization, SDR to AE handoff change), the pay plan should update as a related change rather than an orphan. Strkr versions the pay plan to the structure with effective dates. Deals calculate commission against the plan version that was active at close. Structural changes mid-year do not retroactively affect historical deals.

How often should we review the structure?

Most teams review structure quarterly for small adjustments (territory list refresh, named-account updates) and annually for larger decisions (role model changes, pod reorganization, segment split revision). The quarterly review runs off the pipeline and attainment data to catch structural issues (segment overlap, under-covered territory, pod imbalance). The annual review runs off the compensation data, hiring plan, and strategic plan. Strkr ships structure analytics (coverage, overlap, handoff timing) to support both cadences.

Also built for

Related audiences.

Sales System Sales Team Management Software Sales Team Software Sales Tracking CRM For RevOps For Sales Managers

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing