Walk into ten managed service providers and you'll find ten different sales team structures — except none of them were actually designed. They were assembled, piece by piece, in response to whatever fire was burning that quarter. The owner closed the first hundred customers personally. A senior engineer who "could talk to clients" was moved into a quasi-sales role. A few years later, somebody got hired off LinkedIn with "BDR" in their title because a peer MSP said it worked for them.
The outcome is predictable. New logo growth stalls. Account managers don't know whether to upsell or just keep clients happy. The owner is still the top closer at $4M ARR. Compensation plans are a patchwork of percentages that nobody trusts. And every quarterly business review starts with the same question: "Why isn't pipeline working?"
Pipeline isn't working because the team isn't structured to produce it. Sales results in an MSP are a downstream effect of three things: who owns what, who reports to whom, and who gets paid for which outcome. If those three are wrong, no amount of CRM hygiene, marketing investment, or sales training will fix the numbers.
This guide lays out how MSPs should structure their sales teams in 2026 — the core roles, when to hire them, how to organize them by company size, how to separate hunters from farmers, what to pay them, and the structural mistakes we see most often. It's written for MSP owners and revenue leaders who are tired of growth being a personality-driven sport.
An MSP sales team should be structured around distinct roles with non-overlapping responsibilities, reporting cleanly into a single revenue leader, and compensated on the specific outcomes each role controls. Most MSPs do the opposite: they staff sales by accident, blur the lines between roles, and pay everyone roughly the same percentage regardless of what they actually influence. That's why pipeline feels broken.
The pattern is so common it has a name internally at QBS: the accidental sales org. Year one, the founder is the entire sales team — they close every deal, sign every contract, hand off every kickoff. Year three, the founder is exhausted and promotes Marcus, the senior network engineer who's "great with clients," into a hybrid sales/technical role. Year five, MRR has plateaued, and an outside BDR gets hired to "fix the top of funnel." Year seven, there's an Account Manager whose job description was written in twenty minutes and includes the phrase "and other duties as assigned."
At each step, the response to a sales problem was a hire — not a structural redesign. Nobody ever stopped and asked: what jobs do we actually need someone to own, and who's accountable for each one? That question is the foundation of sales team design, and it's the one MSPs skip the most often.
The underlying issue is that MSPs are technical businesses sold by technical founders. Founders are excellent at the discovery and trust-building parts of sales because they speak fluent infrastructure, security, and compliance. They are usually terrible at the operational parts — territory definition, quota carrying, pipeline math, comp design, sales rhythm. So when they hire, they hire people who feel like them (technical, relationship-driven) and avoid the operational discipline they personally never needed.
The second issue is that the MSP business model creates an inherent tension between new business and retention. Every dollar of MRR you sign today still has to be delivered tomorrow, every month, forever. Unlike a SaaS company where the product is the same for everyone, an MSP delivers a custom service to each client. That makes account management a much heavier lift, and it tempts MSPs to load up their sales reps with post-sale responsibilities so the technical team doesn't have to deal with client politics. That decision — letting AEs own ongoing accounts — is the structural mistake that quietly caps growth at every MSP we've ever worked with.
The third issue is that MSP comp plans are usually copied from a peer-group conversation. "Joe over at the competition pays 10%." Joe pays 10% on something — but you don't know what, on what base, with what claw-back, against what quota. Comp models are not transferable between MSPs because the underlying service mix, contract length, and project-to-MRR ratio are different. A copied comp plan is almost always a wrong comp plan.
The fourth issue is reporting lines. In small MSPs, "sales" often reports to the owner, who is themselves the lead seller. That means the manager of the sales function is also the top individual contributor, the case study source, and the deal escalation point. There is no one above them who can audit pipeline health, coach call execution, or build a forecast. The sales function is structurally un-managed.
Getting any of this right requires designing the sales org rather than letting it accumulate. The good news is that MSPs don't have to reinvent anything — the role definitions, team compositions, and comp structures that work have been validated across thousands of B2B services businesses. They just need to be adapted to the MSP-specific mix of recurring services, professional services, and high-touch account management. That's what the rest of this guide is for.
A complete MSP sales team is built from five core roles. Not every MSP needs all five immediately, but every MSP that crosses roughly $10M ARR has all five, in some form, on the org chart. Knowing the roles in advance lets you sequence the hires deliberately rather than reactively.
The five core roles are: Sales Development Representative (SDR), Account Executive (AE), Sales Engineer (SE), Account Manager or virtual Customer Success Manager (vCSM), and Sales Operations. Each owns a distinct part of the revenue motion, each carries different metrics, and each is paid differently.
The SDR owns the top of the funnel. Their job is to source meetings with qualified prospects — through outbound prospecting, inbound lead follow-up, list research, and event follow-up — and book them onto an AE's calendar. They do not own closing. They do not own demos. They book meetings, qualify lightly, and hand off.
Hire an SDR when you have a defined ideal customer profile, a repeatable outbound motion, and an AE (or owner acting as AE) who has the calendar capacity to take new meetings. Hiring an SDR before you have a closer is one of the most expensive mistakes in MSP sales — you'll generate meetings nobody can run. The right SDR-to-AE ratio is typically 1:1 or 2:1, depending on average deal cycle.
Common SDR metrics: meetings booked per month (typically 12–20 for MSP outbound), meetings held, qualified opportunities created, and SQL-to-meeting conversion rate. SDRs should not carry revenue quota — they carry activity and meeting quotas, full stop.
The AE owns the middle of the funnel — discovery through signed contract. They run the deal: qualification, technical scoping (with the SE), proposal generation, negotiation, and close. In a healthy MSP, the AE owns the prospect from first meeting to contract signature, then hands off to the account manager for delivery and ongoing relationship.
Hire your first AE when the owner is no longer the bottleneck — meaning, you have more qualified meetings than the owner can run, OR the owner needs to step out of selling to focus on the business. Most MSPs hire their first AE around $1.5–2M ARR. Hiring earlier than that creates a rep who has nothing to do; hiring later than that means the owner is the choke point.
AE quota for an MSP varies wildly depending on deal size, but a useful benchmark is $600K–$1.2M in new ARR per AE per year, with 8–14 new logos closed in that range. AE comp is typically 50/50 base-to-variable, with the variable component weighted heavily toward first-year MRR.
The SE is the technical credibility in the room. They join discovery calls and demos, scope solutions, write the technical sections of proposals, and translate between the prospect's environment and the MSP's service catalog. Without an SE, AEs end up pulling senior engineers off billable work to support sales calls — which kills both delivery margin and sales velocity.
For MSPs, the SE is arguably the highest-leverage role on the team. A good SE can support 2–3 AEs, dramatically improves close rates on complex deals (especially compliance-driven sales), and reduces the post-sale scoping rework that creates margin erosion. Hire an SE as soon as you have a second full-time AE, or when the senior engineering team is being pulled into pre-sales more than four hours per week.
The SE is sometimes paid a small variable component tied to deal close, but should primarily be on salary plus a team-based bonus. You don't want your SE optimizing for closed deals at the expense of accurate scoping — that's how MSPs end up with unprofitable contracts.
The AM (or vCSM, depending on how you brand the role) owns the post-sale relationship: quarterly business reviews, strategic roadmapping, renewal, expansion, and serving as the client's executive sponsor inside the MSP. They are the human face of the contract for the next three years.
Account management is a different job from new logo sales. It requires deeper technical fluency, longer time horizons, and a fundamentally different communication style. We will return to this in the hunters-vs-farmers section, but the short version is: do not ask your AEs to also be your AMs. Hire your first dedicated AM as soon as you have 20–30 accounts that justify quarterly business reviews and you can no longer keep up with renewal motions by hand.
AM metrics: net revenue retention (NRR), gross revenue retention (GRR), expansion ARR, QBR cadence completion, and reference-ability. AM comp is typically heavier on base with a smaller variable tied to NRR and expansion bookings.
Sales Ops is the role MSPs add last and need first. Sales Ops owns the CRM, the reporting, the territory and quota math, the comp calculations, the forecasting rhythm, and the integration between sales and the rest of the business (marketing, delivery, finance). Without sales ops, your revenue leader is doing all of this in a spreadsheet at 9pm on Sunday.
You don't need a dedicated Sales Ops hire until you have 4–6 sellers and meaningful complexity in your comp plan and forecast. Before that, sales ops responsibilities sit with the revenue leader or an embedded HubSpot administrator. We've helped many MSPs run sales ops as a fractional function before bringing it in-house — this is part of how we work with MSPs through turning a CRM into a real revenue engine.
Marketing is not a sales role, but it lives adjacent to the sales team and feeds the SDR/AE pipeline. In MSPs under $5M ARR, marketing is usually a single hire (or a fractional engagement) and reports into the revenue leader along with sales. For more on how marketing should be structured to feed an MSP sales team, see our breakdown of MSP marketing strategies for 2026.
The right MSP sales team structure is the smallest one that can produce your next stage of growth — not the one a $50M MSP has. Structuring too far ahead of revenue is just as harmful as structuring too far behind it. Below are the four tiers we see most often, with the team composition that works at each.
| ARR Tier | Typical Headcount | Sales Org | Reporting Line |
|---|---|---|---|
| Under $1M ARR | 2–10 total | Owner-as-AE + 1 SDR (or fractional) | SDR reports to owner |
| $1M–$5M ARR | 10–30 total | 1 AE + 1 SDR + 1 part-time SE + 1 AM | All sales report to owner or first VP Sales |
| $5M–$15M ARR | 30–80 total | 2–4 AEs, 2–3 SDRs, 1–2 SEs, 2–4 AMs, fractional Sales Ops | VP Sales over hunters; VP CS or Director of AM over farmers |
| $15M+ ARR | 80+ total | Pods: 1 AE + 1 SDR + .5 SE per pod, dedicated AM team, in-house Sales Ops, RevOps function | CRO over all GTM functions |
At this stage, the founder is the entire closing function. That is not a bug, it's a feature. Nobody else can sell the company's services with the same credibility, technical depth, or personal investment. The structural goal at this stage is not to replace the founder, it's to give the founder leverage so they spend more time in front of qualified prospects and less time generating their own leads.
The right hire here is an SDR (or a fractional sales development function). The SDR books meetings, the owner runs them. Everything else — proposals, scoping, kickoff — the owner still does. Resist the urge to hire a full AE at this stage; you'll spend 6 months ramping them and they'll close less than half what you would have closed yourself.
Sales ops at this stage is the owner with a HubSpot login. Account management at this stage is the owner remembering everyone's name and showing up for the important QBRs. That's fine — for now.
This is the stage where most MSPs break. The owner has hit the ceiling of personal selling capacity, the SDR motion is producing more meetings than the owner can run, and the first AE hire becomes urgent. This is also the stage where the owner has to make a hard decision: do I stay in sales as a player-coach, or do I exit selling and hire a VP Sales?
The right structure at this stage is: 1 dedicated AE, 1 SDR, a part-time or shared Sales Engineer (often a senior solutions architect from the delivery team who allocates 25–40% of their time), and the first dedicated Account Manager. The owner stays involved in the top 5 strategic deals and is the executive sponsor on the largest accounts, but is no longer carrying a quota.
This is also the stage where comp plans get formalized. The handshake-and-commission model that worked when there were two of you doesn't survive five sellers. We strongly recommend writing the comp plan down, having it reviewed by someone outside the company, and making sure every variable has a definition. (More on comp models in the next section.)
At this stage, the structural mandate is to fully separate new logo acquisition from account management. Hunters report to the VP of Sales. Farmers (AMs/vCSMs) report to a VP of Customer Success or a Director of Account Management. Each function has its own metrics, its own comp plan, and its own meeting cadence.
This is also the stage where you'll likely add a second AE, a second SDR, a dedicated Sales Engineer, and start building out the AM bench. Sales Ops becomes its own function — often fractional first, then in-house once headcount justifies it. Forecasting moves from gut feel to a defined pipeline-stage methodology with weighted projections.
Marketing also professionalizes here. You'll have a dedicated demand gen role or agency relationship producing inbound leads. The SDR team handles both inbound qualification and outbound prospecting, often with sub-specialization between the two.
Above $15M ARR, the most common structural pattern is the sales pod: a small unit consisting of an AE, an SDR, and a shared Sales Engineer that operates as a mini-business within the company. Pods are often organized by vertical (healthcare, manufacturing, professional services), geography, or deal size (mid-market vs. enterprise). Pod-based structures dramatically improve focus, ramp times, and ICP alignment.
At this stage, you have a CRO (or equivalent) over the entire GTM motion, with VPs of Sales, Customer Success, and Marketing reporting up. Sales Ops becomes RevOps and owns the systems, data, and process for the entire revenue function. You'll also have specialization within roles — for example, a renewals AM vs. an expansion AM, or an outbound SDR vs. an inbound SDR.
This level of structure is where the right RevOps framework becomes load-bearing. We've written more about that in our RevOps framework guide, which lays out how the GTM functions interlock at this scale.
Yes. The single highest-leverage structural decision an MSP can make is to separate new logo sales (hunters) from account management (farmers) — and to do it earlier than feels comfortable. The longer you delay this split, the more revenue you leave on the table at both ends of the funnel.
Here's why. Hunters and farmers do fundamentally different jobs. A hunter spends their time in the discomfort of cold conversations, untrusted relationships, and short time horizons. They optimize for getting to "yes" on a new contract in 30–120 days. A farmer spends their time inside known accounts, building trust over years, optimizing for retention and expansion. The skills overlap a little. The personality types overlap less. The daily rhythms overlap almost not at all.
When you ask one person to be both, two things happen. First, the urgent always crowds out the important — and in this case, the urgent is the existing account that's irritated about a help desk SLA breach, and the important is the prospecting block that fills next quarter's pipeline. Within a quarter, your "hunter-farmer" rep is doing 90% farming. New logos die.
Second, the comp plan can't cleanly reward both behaviors. If you pay heavy on new logo, your rep neglects existing accounts and you bleed NRR. If you pay heavy on retention, your rep stops prospecting and you bleed new ARR. There is no comp plan that solves this for a single rep — only a structural split solves it.
The objection we hear most often is: "But our clients want one relationship throughout their lifecycle." That's a true preference, and it has to be honored — but it doesn't require one sales rep throughout the lifecycle. What clients actually want is to feel known, to have someone who understands their environment, and to have a single point of escalation. All of that is the account manager's job. The AE who closed them six months ago does not need to be involved in QBRs in year three.
The clean handoff is the key. We coach MSPs on a deliberate transition that includes a three-way kickoff (AE, AM, client), a documented account brief, and a 30-day overlap where the AE remains copied but the AM leads. After 30 days, the AE is out of the day-to-day. Clients adapt to this faster than MSPs expect — usually within two interactions.
The right timing for the split varies. Below $1M ARR, the owner is doing both jobs and that's fine. Between $1M and $3M, you'll start to feel the strain — typically when one rep is managing more than 15–20 active accounts AND carrying a new logo quota. Above $3M ARR, the split is essentially mandatory. We've seen MSPs try to push to $5M with combined roles, and the result is always the same: a stalled pipeline, an exhausted rep, and a slow erosion of NRR.
One nuance: the right answer for some MSPs is not a binary hunter/farmer split, but a three-role model — hunter (AE), farmer/strategic AM (high-touch, top 20% of accounts), and a customer success generalist (long-tail accounts, lighter touch). This works particularly well for MSPs with a wide spread in client size, where a $300K MRR client clearly needs different attention than a $4K MRR client.
If your team is currently structured with combined roles and you're trying to figure out when to split, here are the signs you're already past the right moment: rep complaining they can't prospect because clients keep interrupting; NRR sliding below 100%; new logo bookings stagnant for 2+ quarters despite stable lead flow; and reps consistently missing quota even though "they had a good year on retention." Any two of those are a signal to act.
MSP sales comp is its own discipline because the underlying revenue is its own beast. You're selling a mix of recurring services (high LTV, low first-year value), professional services (high first-year value, no recurrence), and hardware or licensing (often pass-through with thin margin). One comp plan has to balance all three without distorting rep behavior.
The framework we use with MSP clients is built around five principles, then translated into a role-by-role plan.
The numbers below are benchmarks we see most often across MSPs in the $1M–$20M ARR range. Adjust to your specific market, deal size, and average contract length.
Account Executive (AE): 50/50 base-to-variable split. OTE typically $120K–$180K for mid-market MSPs, higher in major metros. Commission structure: 8–12% on first-year MRR, 1–3% recurring residual for life of contract (often capped at 3 years), 3–5% on professional services revenue, 0.5–1% on hardware pass-through. Quota: $600K–$1.2M new ARR/year.
Sales Development Rep (SDR): 70/30 or 75/25 base-to-variable. OTE $55K–$80K. Variable tied to meetings booked AND meetings that convert to qualified opportunities (don't pay only on meetings — that incentivizes garbage meetings). Typical structure: $50–$100 per qualified meeting plus a quarterly bonus on SQL conversion rate above a threshold.
Sales Engineer (SE): 80/20 or 85/15 base-to-variable. OTE $130K–$180K. Variable tied to a team-level bonus on closed-won deals they supported, not individual deal comp. Some MSPs add a small spiff for accurate scoping (no margin write-down post-implementation).
Account Manager / vCSM: 70/30 or 75/25 base-to-variable. OTE $90K–$140K. Variable structure: 60% tied to net revenue retention (NRR) above a threshold, 40% tied to expansion bookings (cross-sell, upsell, new project revenue from existing accounts). Some MSPs add a small QBR completion bonus to enforce cadence.
Sales Operations: Typically salary-based with a small company-wide performance bonus (5–15% of base). Sales Ops is an operational role, not a quota-carrying role.
Three patterns we see repeatedly that destroy comp plans:
Mistake 1: Paying recurring residual forever with no cap. Sounds rep-friendly, becomes a P&L problem. After a few years, you have reps making more on their book of legacy accounts than on new business — so they stop hunting. Cap residuals at 2–3 years.
Mistake 2: Letting reps "double-dip" on AE and AM comp. If your AE closes a deal AND owns the ongoing account, they get hunting comp AND farming comp on the same revenue, often forever. This is the most expensive structural mistake we see — and it's only solvable by splitting the roles.
Mistake 3: Vague quota definitions. "Hit $1M in new business this year." Does that include hardware? Pass-through licensing? One-time projects? Renewals that the AE wasn't actually involved in? Every term in the comp plan needs a written definition, signed at hire, reviewed annually.
If you want to go deeper on the operational side of comp — how to actually calculate it, track it, and pay it in HubSpot — our companion piece on turning CRM into a revenue engine goes into the systems side.
Across the MSPs we work with, the same handful of structural mistakes show up over and over. Here are the seven most common, and what to do about each.
Why it happens: The owner is good at it, hasn't made the leadership transition, and hires AEs who can't ramp because the owner keeps taking the best deals.
Fix: Set a hard deadline for the owner to exit individual selling. Reroute all new inbound leads to the AE, with the owner only joining as executive sponsor on deals above a certain ARR threshold. Coach the owner into a Chief Revenue Officer role, or hire one above them. The owner's job is to make the team capable of selling without them — not to be the best seller.
Why it happens: They know the services cold, the team trusts them, and a sales hire feels risky. So you "promote" them into sales.
Fix: This works exactly once in a hundred. The skills are different, the motivation profile is different, and the rhythms are different. If the person genuinely wants to sell, give them 18 months with explicit ramp targets and outside sales coaching. If they don't hit, move them back into a Sales Engineer role where their technical depth is the asset — they'll usually be happier there anyway.
Why it happens: A peer MSP raves about outbound, or a sales coach pitches an SDR motion. You hire one, expecting magic.
Fix: Don't hire an SDR until there's an AE (or owner with calendar capacity) ready to run the meetings. SDRs without closers produce meetings nobody can convert, which discourages the SDR, who then churns. Sequence: closer first, then top-of-funnel.
Why it happens: Headcount is tight and clients "want continuity."
Fix: Covered in the hunters-vs-farmers section. Split the roles. The earliest version of this is one full-time AM with a small book, with the owner or a second AE handling overflow accounts.
Why it happens: The owner is the de facto manager, but they're also still selling. Coaching, pipeline review, and forecasting fall through the cracks.
Fix: Once you have 3+ sellers, you need a non-selling sales manager — even if it's a 60/40 player-coach to start. Their job is pipeline review, deal coaching, forecast accuracy, and ramp. If your owner can't make this transition, hire a VP Sales who can.
Why it happens: "We pay 10% on new MRR." Done. Until somebody closes a deal with 18 months of MRR upfront and nobody knows how to comp it.
Fix: Every comp plan needs a written document covering: revenue types and rates, quota definition and timing, accelerator structure, clawback conditions, what counts vs. doesn't count, and dispute resolution. Reviewed annually, signed at hire.
Why it happens: The structure of the sales team doesn't define what the AE owes the delivery team at close.
Fix: Build a sales-to-delivery handoff checklist that's a required step in your CRM before a deal can be marked closed-won. It should include the SOW, scoping notes, decision-maker map, technical environment summary, and any commitments made during the sales cycle. No handoff doc, no closed-won status. This is also where good lead scoring and qualification practices earlier in the funnel pay off — better-qualified deals hand off cleaner.
Designing the structure is half the work. Operationalizing it — making the org chart live inside your day-to-day systems, comp calculations, pipeline reviews, and forecasting — is the other half. This is where we focus our work at Quantum Business Solutions.
QBS is a HubSpot solutions partner serving B2B revenue teams, with deep focus on managed service providers. We work with MSP owners and revenue leaders to design the sales org, then build the operating system underneath it. Our work for MSPs falls into three areas:
1. Sales org design. We help you map the right roles for your current and next ARR tier, design the comp plan, define quotas and territories, and write the role-by-role expectations. This is the strategic work — done over a few weeks of focused engagement with your leadership team. It's where the structural decisions get made.
2. HubSpot as the system of record. Once the structure is set, we configure HubSpot to enforce it. That means deal pipelines that match your actual sales process, custom properties that capture the data your forecasts need, automation that handles the SDR-to-AE handoff, and reporting that gives your sales leader real-time pipeline health. We're opinionated about why HubSpot is the right CRM for MSPs — we've written the comparison in MSP CRM: Why HubSpot Wins for Managed Service Providers, including why Dynamics 365 falls short for this segment.
3. The Q2 framework for ongoing execution. Our Q2 framework is how we structure the ongoing partnership: Quarter-by-quarter execution sprints that connect the strategic priorities from your sales leadership to operational outcomes in your CRM, marketing, and customer success motions. Each quarter we identify the 2–3 highest-leverage initiatives, build the systems to support them, and measure the result before moving on. The framework keeps structure and execution aligned without drifting into vague "consulting" engagements.
Most MSPs come to us at one of three inflection points. The first is the transition from owner-led selling to a real sales team — usually around $1.5–3M ARR. The second is the hunters-and-farmers split, usually around $4–6M ARR. The third is the move from a single-rep model to pods, usually past $10M ARR. At each of these points, the structural decisions you make set the next three years of growth.
What we don't do: we don't sell you software you don't need, we don't write decks and disappear, and we don't have a single template we apply to every MSP. Sales org design has to be specific to your service mix, your market, and your leadership team. The structures in this guide are the starting points — the right answer for you sits inside a conversation about your specific business.
For MSPs further along the journey, we also help build out the broader revenue stack. That includes the sales enablement technology stack that supports your team, the marketing-to-sales handoff that fills your top of funnel, and the customer success operations that protect NRR. Each piece reinforces the structure underneath.
If you've read this far and recognized your own MSP in two or three of the mistakes above — that's normal. Most MSPs are in the middle of one structural transition or another. The work is to name it, design what comes next, and execute deliberately. We'd be glad to help.
An MSP should structure their sales team around five core roles with non-overlapping responsibilities: a Sales Development Rep (SDR) for top-of-funnel meeting generation, an Account Executive (AE) for new logo closing, a Sales Engineer (SE) for technical scoping, an Account Manager (AM) or virtual CSM for post-sale retention and expansion, and Sales Operations for CRM, reporting, and comp. Not every MSP needs all five immediately, but the roles should be hired in this sequence as ARR grows. Each role reports cleanly into a single revenue leader, carries its own metrics, and is compensated on the specific outcomes it controls.
A complete MSP sales team needs five roles: SDR (sources qualified meetings), AE (owns deals from discovery to close), Sales Engineer (handles technical scoping and proposal support), Account Manager or vCSM (owns post-sale retention and expansion), and Sales Operations (owns systems, reporting, and comp calculations). Below $1M ARR, the owner typically plays the AE role and only the SDR is hired. Between $1M–$5M ARR, the AE, AM, and part-time SE are added. Above $5M ARR, all five roles exist as standalone functions, with hunters reporting to a VP of Sales and farmers reporting to a VP of Customer Success.
The right size for an MSP sales team scales with ARR. Under $1M ARR, the team is typically the owner plus 1 SDR. Between $1M–$5M ARR, expect 4–6 sales-related headcount: 1 AE, 1 SDR, a part-time SE, an AM, and a fractional sales ops function. Between $5M–$15M ARR, the team grows to 8–14 people across hunters and farmers. Above $15M ARR, MSPs typically organize into pods of 1 AE + 1 SDR + 0.5 SE each, with a dedicated AM team and in-house RevOps. A useful benchmark is one AE per $600K–$1.2M of new ARR target, plus one AM per $2–3M of book under management.
An MSP should always hire a closer before hiring an SDR. Hiring an SDR before there's an AE (or owner with calendar capacity) to run the meetings is one of the most expensive mistakes in MSP sales — the SDR generates meetings nobody can convert, gets discouraged, and churns within months. The correct sequence is: owner as AE first, then SDR to extend the owner's capacity, then a dedicated AE once meetings exceed what the owner can run, then a second SDR to support the AE. The right SDR-to-AE ratio is typically 1:1 or 2:1 depending on average deal cycle length.
MSP sales reps should be compensated differently based on role and revenue type. For Account Executives, the typical structure is a 50/50 base-to-variable split with OTE of $120K–$180K, paying 8–12% on first-year MRR, 1–3% recurring residual (capped at 2–3 years), 3–5% on professional services revenue, and 0.5–1% on hardware pass-through. SDRs are paid 70/30 base-to-variable with comp tied to qualified meetings and SQL conversion, not raw meeting count. Account Managers are paid 70/30 with the variable component split 60/40 between net revenue retention and expansion bookings. Sales Engineers are mostly salary with a team-based bonus on closed-won deals they supported. Comp plans should always be written down with definitions for every term.
An MSP should separate sales (hunters) from account management (farmers) as soon as a single rep is managing more than 15–20 active accounts while also carrying a new logo quota, or once total ARR exceeds $3M. Below $1M ARR, the owner typically handles both roles. Between $1M–$3M ARR, the strain becomes visible — new logo bookings stagnate while existing accounts demand more time. Above $3M ARR, the split is essentially mandatory. The signs you've waited too long: reps complaining they can't prospect because clients keep interrupting, NRR sliding below 100%, and consistent quota misses despite "a good year on retention." The clean handoff between AE and AM should include a documented account brief, a three-way kickoff with the client, and a 30-day overlap period.