.svg)
.svg)
.svg)
Your sales organisation structure should be designed around the work it takes to win and serve your customers. Most teams build that work around one of three models: an island, where each rep runs the full deal alone; an assembly line, where specialists own separate stages such as prospecting, closing, and retention; or a pod, where a small cross-functional group owns a set of accounts together. These are design choices rather than a fixed ladder. Buyer complexity decides how much coverage a deal needs, and deal volume and economics decide whether that coverage comes from generalists, specialists, or a dedicated team. If you sell into very different segments at once, such as self-serve SMB and enterprise, split by segment first and choose a model for each. Change the structure only when your own operating numbers say the current one has stopped working.
What a Sales Organisation Structure Actually Decides
A sales organisation structure is the way you divide selling work among people and define how they hand it off. Underneath the labels, every structure answers four practical questions.
Who owns which stage of the deal? One person can carry a lead from first touch to signature, or that journey can be split so a prospector books the meeting and a closer runs it.
How does work pass between people? If stages are split, the handoff has to be defined in writing and built into your CRM, or leads stall in the gap between two roles.
How is the market divided? Accounts can be split by geography, by product line, by customer size, or by industry. This layers on top of the workflow model.
Who manages whom, and who gets paid for what? Every structure implies a reporting line from the front-line rep up to the person who owns the revenue number, and a compensation plan that credits the right people for each stage.
Get these four right for your current stage and the team runs with less friction. Copy a structure built for a company at a different stage and you inherit its overhead without its benefits. The rest of this guide covers the three core models, gives you a way to choose between them, works a hard case end to end, and shows how to tell whether the structure you pick is actually working.
The Three Core Models
Most sales teams, from a two-person startup to a global enterprise, build around one of three workflow models, and many blend them. The specialised version was popularised by Aaron Ross in Predictable Revenue, and teams such as Close openly run a mix. Treat the models as design alternatives rather than stages you must pass through: a company can run one for years, combine two, or move between them as its needs change. They differ in one variable: how much a single deal is split across people.
The Island Model
In the island model, each rep owns the entire sales cycle. They prospect their own leads, qualify them, run the demos, negotiate, close, and often handle the early account relationship afterward. Each rep operates as a self-sufficient island.
This is the default for new and small teams because it needs little coordination between roles. You hire capable generalists, give them a target, and let them sell. It rewards hustle and produces well-rounded reps who understand the full cycle, which makes it a strong training ground. Compensation is simple too, since one person owns the deal and earns the commission on it. Even here, the team still needs basic operating agreements: how accounts are assigned, what the pipeline stages mean, who qualifies a deal, and who holds pricing authority. What the island model avoids is the handoffs between specialists, while still needing a shared way of working.
The island model has a known ceiling. Because every rep does everything, output depends heavily on individual talent, and performance varies widely from one person to the next. It is hard to coach a single stage when everyone owns all of them, and it gets expensive to scale, since every new hire has to be good at prospecting and closing and account management at once.
Best for: early-stage teams, small businesses, and products with a short, transactional sales cycle where one capable rep can reasonably carry a deal end to end.
The Assembly Line Model
The assembly line model, sometimes called the functional or specialised model, splits the sales cycle into stages and gives each stage to a dedicated role. A common version runs four roles in sequence:
- Lead generation builds the top of the pipeline from marketing and research.
- SDRs or BDRs qualify those leads and book meetings for closers.
- Account Executives run the demos, negotiate, and close.
- Account managers and customer success own the relationship after the sale, with account managers carrying an expansion and renewal quota and customer success focused on adoption and retention.
Each rep specialises in one stage. Leads move down the line like a product through a factory, which is where the name comes from.
Specialisation is the main gain. A closer who only closes gets sharper at closing, an SDR who only prospects books more meetings, and you can hire and coach for one skill at a time, which is easier to recruit for at scale. It also lets each stage be managed and improved on its own, because each has its own owner and its own conversion rate, so you can see where deals slow down and fix that stage without disturbing the others. That gain holds only while handoff quality holds; done badly, specialisation loses context and conversion drops.
The cost is coordination. Handoffs between stages are where this model breaks: a lead an SDR qualifies loosely wastes an AE's time, and an AE who closes a poor-fit deal hands customer success a problem. Running it well needs three things in place: written criteria for what qualifies a lead to move to the next stage, those criteria built into the CRM as routing rules and stage definitions with response-time SLAs, and a comp plan that credits both the SDR who sourced the deal and the AE who closed it.
It also needs enough volume to keep every specialist busy. As a staffing reference, the Bridge Group's 2025 study of 351 B2B companies puts the ratio at about one SDR for every 2.4 Account Executives, with one SDR to two AEs the most common split. Size your own from meeting supply and AE capacity: how many qualified meetings one SDR can book a month, and how many active opportunities one AE can run well. Run the model with thin pipeline and your specialists sit idle.
Best for: teams with enough lead volume to keep specialists busy, repeatable sales motions, and SaaS or mid-market models where the cycle has clear, separable stages.
The Pod Model
The pod model, sometimes called a cluster, groups a few specialists into a small self-contained unit that owns a defined set of accounts or a segment together. A typical pod might pair an SDR, one or two AEs, and a customer success manager who all work the same accounts. It is, in effect, a small assembly line wrapped around a shared book.
Because the pod owns its accounts end to end, the handoff problem shrinks: the SDR, AE, and CSM talk to each other daily about the same customers, so context carries across stages instead of being lost in a queue. Pods tend to produce tight collaboration, faster problem-solving, and strong account ownership, and they often carry a shared pod goal alongside individual targets, which rewards the coordination.
The trade-offs are flexibility and resourcing. Pods can be harder to staff, since each one needs a balanced mix of roles, and a pod that loses a member feels it immediately. They can also compete with each other when territory or account assignment is unclear. Pods work best once a company is large enough to run several of them and has enough accounts of the right kind to keep each specialist fully loaded.
Best for: larger or scaling teams, complex or high-value deals, and account-based models where a customer needs coordinated attention from several roles at once.
How to Choose: A Decision Framework
The three models are a fit question rather than a ranking, and the fit depends on your buyer and your economics. Four signals decide most of the answer. They often correlate, but they do not always move together, so read each one on its own: a deal can be high-value yet short and simple, or modest in value yet long and technical.
Pipeline volume, and whether splitting it pays. Steady, high lead flow is what makes specialists usable. On its own it does not make them worth hiring. The real test is whether dividing the work improves the economics: weigh the cost of the new role against the selling time it frees, the extra qualified pipeline it creates, and the coordination it adds. Steady leads with low incremental value from a specialist are a reason to wait. Note that this is about lead flow, so a large team with thin pipeline still should not specialise.
Deal value and cycle length. These set how much time and money each deal can justify. Short, low-value deals favour a single owner who moves fast. Long, high-value deals can carry the cost of more people and more coordination.
Deal complexity. How many moving parts a deal has, and how much technical or security validation it needs, decides how many kinds of expertise have to touch it. A simple product sale needs one person; a deal that needs a security review and a proof of concept needs specialist support.
Buying group. A deal with one decision-maker can be carried by one rep. A deal sold to a committee needs several conversations at once. That does not automatically require a pod. A strong Account Executive can stay accountable for the whole deal while coordinating finance, procurement, security, and the business, pulling in a solutions engineer or an executive sponsor as needed. The real question is whether those extra participants can be shared informally across deals, or whether you have enough such accounts to justify standing pods. Keep accountability with one owner, and treat specialist participation as separate from it.
Read the four together and a default usually emerges. The harder case is when they disagree, and the most common disagreement is a small team selling complex, high-value deals: volume says island, deal shape and buying group say the buyer needs more coverage. The resolution is to let deal shape set the coverage you owe the buyer, and let volume set how formally you can resource it. Keep full-cycle reps because you lack the volume to run true specialists, and assign each strategic account an informal group of the people already touching it, such as the rep, a technical lead, and an executive sponsor. The next section works that case out in full.
One cut comes before the model. If different parts of your book look nothing alike, split by segment first, then choose a model inside each. Be precise about SMB. A genuinely self-service motion, where customers find, buy, and adopt the product with little or no rep contact, may not need a sales assembly line at all. It needs product-led acquisition with sales assistance where a deal warrants it. A sales-assisted SMB motion, with higher-velocity commercial deals, is where a light assembly line pays off. Enterprise is where coverage follows account and buying complexity. The table below assumes a single, reasonably consistent motion. Treat it as a starting point to confirm against your own numbers.
| If this describes you | Start with | Why |
|---|---|---|
| Under ~5 reps, still finding product-market fit, variable deals | Island | No handoffs to coordinate, builds full-cycle reps, lets you learn the motion |
| Steady lead volume, single decision-maker, repeatable mid-market deals | Assembly line | Lets each stage be managed and improved on its own, with clear per-stage metrics |
| Complex, high-value, multi-stakeholder deals, enough of them to staff specialists | Pod | Coordinated coverage without losing context in handoffs |
| Small team but complex, high-value deals | Island plus informal specialist coverage on key accounts | Not enough volume to specialise; still give big accounts team coverage |
| Scaling fast, hiring in volume, cycle has clear stages | Assembly line, then pods as account depth grows | Easier to recruit for one skill; pods add coordination later |
| A book that spans very different segments | Segment first, then a model per segment | One structure cannot fit a self-serve deal and an enterprise deal |
A Worked Example: Small Team, Complex Deals
Take the hardest row from that table and resource it properly. Picture a seven-person team selling six-figure deals into enterprise buying committees, holding maybe fifteen to twenty live opportunities at a time. (The numbers here are illustrative, to show the method.) Volume says island, because there is not enough pipeline to keep dedicated SDRs or CSMs busy. Deal complexity and the buying group say the buyer needs more than one voice in the room. The resolution is full-cycle Account Executives with specialists shared informally around the accounts that matter. A workable design looks like this.
| Responsibility | Who owns it (illustrative) |
|---|---|
| Account strategy and forecast | The Account Executive on the deal |
| Prospecting into the account | The same AE, supported by marketing |
| Technical validation and security review | A shared solutions engineer, pulled in per deal |
| Executive alignment with the buyer | The founder or VP of Sales |
| Commercial negotiation | The AE, within set approval limits |
| Handoff to delivery at close | A named implementation owner |
Why not simply hire SDRs and CSMs? At fifteen to twenty opportunities, a dedicated SDR would not have enough target accounts to fill a calendar, and a dedicated CSM would carry too few accounts to justify the role. Sharing one solutions engineer across deals keeps that specialist busy and keeps the AE accountable for the whole deal. When the number of these accounts grows enough to load a specialist full-time, that is the signal to make the group a formal pod. This is the conflict rule in practice: deal shape set the coverage the buyer needed, and volume set how formally the team could resource it.
How Structures Evolve as You Scale
A common path runs island, then assembly line, then pods, and it is worth knowing because it matches how many teams grow. It is not a law. Plenty of companies keep full-cycle reps at real scale, add specialist overlays without forming pods, reorganise by segment without touching the workflow, or pull pods back into a central team. Close, for one, runs a deliberate blend of island and assembly line rather than a single model. Treat the sequence as the most common route and your own numbers as the thing that decides.
A team usually starts on the island model because it has to sell before it can afford to design a process. As lead volume becomes steady and the motion becomes repeatable, the island model can cap output: top reps spend time prospecting that a cheaper SDR could do, and coaching is hard because no one specialises. That is often the point to move toward an assembly line and let people focus.
As the company grows and deals get larger or more account-based, the long assembly line can feel impersonal and handoffs multiply. Breaking the line into pods keeps the specialisation while restoring ownership and context for each set of accounts.
The signals that prompt a review are worth naming, because they tell you to look rather than to act automatically.
- Your best closers spend a large share of their week prospecting, while lead volume is steady enough to keep a dedicated SDR busy. A practical test is whether you can hand a new SDR enough accounts to book a full calendar of qualified meetings each month.
- Leads stall or get dropped between stages.
- Large accounts complain about being passed around.
- Specialists are idle, which means you specialised ahead of your volume.
Before you restructure, confirm the structure is the problem. Leads stalling between an SDR and an AE can be a structural mismatch, or it can be a process defect: loose qualification, no lead-acceptance rule, slow routing, or no shared owner. Fix the process first and reorganise only once you have ruled it out, because reorganising people to solve a process problem adds cost and solves nothing.
When the structure genuinely is the problem, budget for the switch. A restructure usually resets territories, quotas, comp, and reporting lines, and that disruption can dent attainment while reps ramp into new roles. How much, and for how long, depends on your cycle length and how cleanly you manage the change, so track pipeline and attainment before and after rather than assuming a fixed recovery time.
How to Tell If Your Structure Is Working
A structure is working when it holds up on five fronts. Run this check before a reorg to find the real problem, and after one to confirm it worked. A structure that scores well on all five is doing its job, whatever model it happens to be.
| Lens | Question to ask | Warning sign |
|---|---|---|
| Capacity | Are people fully and productively used? | Specialists idle, or closers buried in work a specialist should do |
| Conversion | Do deals move through qualification and close? | Stage conversion drops right after a handoff |
| Customer experience | Does context survive the handoffs? | Buyers repeat themselves or feel passed around |
| Economics | Does the cost to acquire and serve justify the deal? | A new role costs more than the selling time it frees |
| Accountability | Does every stage and account have one clear owner? | Deals stall with no one who owns the next step |
The Organising Dimensions
Once you have a workflow model, you still have to divide the market among the people in it. For many scaling companies, segmentation is the first cut, made before the model is even chosen, because a 10-seat deal and a 10,000-seat deal need different motions. The dimensions below layer on top of the island, assembly line, or pod.
By customer segment or size. Separate teams handle enterprise, mid-market, and small business, because the deals move at different speeds and need different pacing. Most scaling SaaS companies split this way at some point, and it often drives every other structural choice.
By geography or territory. Reps or pods own a region. This is simple to administer and cuts travel and time-zone friction, which still matters for field sales. It can create uneven territories when some regions are richer than others.
By product or product line. Reps specialise in one product and its buyers. This helps when products are technical or very different from each other, at the cost of a customer who buys several products dealing with several reps.
By industry or vertical. Reps or pods specialise in one industry so they can speak its language and cite relevant customers. This suits companies selling into regulated or specialised markets where domain credibility wins deals.
These dimensions combine. A large organisation commonly runs a segment split at the top, a geographic split inside enterprise, and pods inside each region. The workflow model decides how a deal is run; the dimensions decide how the market is divided among the people running it.
The Leadership Ladder
Whatever model and dimensions you choose, a growing sales organisation tends to form the same reporting layers, though titles and boundaries vary.
At the top sits the revenue owner. A VP of Sales owns the sales number; a Chief Revenue Officer usually owns a wider remit, often spanning sales, marketing, and customer success. Below them are directors or regional leaders who own a segment, region, or product line, then front-line managers who run a team of reps or a cluster of pods and do most of the coaching, and at the base the individual contributors who close, prospect, and support accounts. Read this as a sales reporting line, and keep in mind that customer success often sits in its own function reporting to a Chief Customer Officer or the CRO, working alongside sales without sharing its hierarchy.
Span of control is role-specific. The Bridge Group's 2025 study puts SDR managers at an average of 6.4 SDRs each, ranging from about 3.6 at companies under $5M in revenue to 8.1 at $500M and above. Front-line managers of Account Executives, who coach longer and more complex deals, usually carry fewer. Use these as planning benchmarks that shift with how much coaching the role demands, and add a management layer rather than stretching one manager past what they can coach.
Common Mistakes
A few errors show up repeatedly, independent of which model a team picks, and they cost more than choosing the "wrong" model.
Changing structure without changing comp. Splitting a full-cycle role into SDR and AE changes who gets credit for pipeline and for bookings. If the comp plan does not follow, reps fight over attribution and the new structure stalls. Redesign the plan as part of the reorg.
Splitting roles without building the handoff. The moment you divide the cycle, you need written qualification criteria and the routing rules, stage definitions, and response-time SLAs to enforce them in your CRM. Without that plumbing, deals leak between roles and each team blames the other.
Restructuring ahead of your volume. Adding SDRs, pods, and handoffs before you have the lead flow to feed them leaves specialists idle and adds coordination cost with no payoff.
Copying a later-stage company. Borrow the ideas behind a bigger company's org chart and design your own for your stage, because the overhead that pays off at their scale is dead weight at yours.
Treating the structure as permanent. A structure fits a moment. Teams that keep last year's org chart past its signals keep paying for a shape they have outgrown.
Frequently Asked Questions
What is the most common sales organisation structure?
There is no single answer across all companies. Very small teams default to the island model. Scaling B2B and SaaS companies often move to an assembly line, because it fits repeatable deals with clear stages, and large account-based teams frequently run pods or a blend. The right one depends on your volume, deal shape, and buyer.
Should we hire an SDR or another AE?
Hire an SDR when your AEs are losing real selling time to prospecting and you have enough target accounts to keep a dedicated prospector's calendar full. Hire another AE when the bottleneck is closing capacity: qualified pipeline is waiting and your current AEs cannot work it all. Add an SDR to create pipeline and an AE to convert it, and check which one is actually the constraint before adding either.
What is a good SDR to AE ratio?
The Bridge Group's 2025 benchmark of 351 B2B companies is about one SDR for every 2.4 Account Executives, with one SDR to two AEs the most common split. Treat that as a reference point and size your own against it. The right ratio depends on how much of your pipeline is inbound versus outbound and how many qualified meetings one SDR can book, so tune it against your own conversion data.
When should we move off the island model?
The clearest signal is your best closers spending a large share of their time on prospecting a cheaper specialised role could handle, combined with steady enough lead volume to keep a new SDR busy. A practical test is whether you can hand a new SDR enough accounts to book a full calendar of qualified meetings each month. When both are true, an assembly line usually lifts output, provided the handoffs are built properly.
Can we combine these structures?
Yes, and large organisations usually do. The workflow model and the market dimension are separate choices, so a company can run pods inside a regional split inside a segment split. The models themselves also stack, since a pod is a small assembly line, and many companies run a deliberate blend. Segmenting first and then running a different model in each segment is common.
