Ask a founder to draw their sales org and you get boxes with titles. Ask a rep who killed their deal and you get a story about the seams between those boxes — the SDR who booked a meeting the AE would never have taken, the solutions engineer pulled in two days before the demo, the CSM who learned about the expansion opportunity from the customer's cancellation email. The seven roles of the modern B2B revenue org are now stable enough to benchmark — what each owns, what each costs, and where each boundary leaks — and 2026's compensation data finally makes the picture quantitative. This piece walks the org from first hire to hundred-rep company through all seven roles.
The seven roles at a glance
The modern revenue org runs on seven roles: the Sales Development Representative who converts inbound interest into qualified conversations, the Business Development Representative who manufactures outbound conversations from cold accounts, the Account Executive who owns deals to close, the Solutions Engineer who owns technical truth, the Customer Success Manager who owns the post-sale relationship, the RevOps lead who owns the machine's instrumentation, and the VP of Sales or CRO who owns the number. Each role exists because its boundary with the neighbors was once a full-time job hiding inside somebody else's week. The comp data says the market agrees: these are seven distinct careers with distinct pay bands, not seven flavors of "salesperson."
SDR and BDR: the top of funnel, split in two
The SDR qualifies inbound: a lead arrives from content, advertising, or events, and the SDR's job is speed and diagnosis — responding fast enough to matter and qualifying hard enough to protect AE calendars. The BDR hunts outbound: no lead arrives, so the BDR manufactures one from a target account list, sequences, and signal work. The 2026 economics: a US B2B SaaS SDR runs $70-90K on-target earnings at mid-level on a standard 70/30 base-variable split, with variable paid per qualified meeting ($75-200) or per accepted opportunity ($150-500) (ev-sr1-003). The role's structural truth is a career lattice rather than a destination: the standard promotion to AE lands at 18 to 24 months with a 50-80% compensation lift, which is why the best SDRs treat the role as a two-year apprenticeship in the customer's world (ev-sr1-003).
Account Executive: the deal owner
The AE owns revenue. Everything upstream is preparation; the AE converts it into contracts, and the market prices the role accordingly: median SaaS AE on-target earnings sit around $195-200K on a 50/50 split, carrying roughly $800K in quota at a 4.2x quota-to-OTE ratio, with mid-market at $160-220K and enterprise at $230K-plus (ev-sr1-001). The attainment data is the role's sobering footnote: 40.6% of AEs hit quota, and the number falls as segments move upmarket — strategic AEs run 42% attainment on $300K OTE (ev-sr1-002). Read honestly, these are high-variance careers: more money, longer cycles, fewer shots, lower hit rates — the enterprise AE trade is a different financial proposition than the SMB trade, not a promotion version of it.
Solutions Engineer: the technical truth-teller
The solutions engineer — sales engineer, in older vocabularies — owns the technical validation layer: the demo that answers the buyer's actual architecture, the security questionnaire, the proof-of-concept that de-risks the purchase. The role earned its seat at the table as buying committees grew to eleven-plus stakeholders, because the committee's engineers get a vote, and the AE alone cannot win it. The SE's comp typically runs just below AE OTE with a lighter variable, and the role's failure mode is being booked as demo furniture: an SE pulled in for hour nine of the sales cycle, reading the discovery notes for the first time on the call. The high-performing pattern pairs AE and SE from qualification onward, with the SE owning the technical close plan in parallel to the AE's commercial one.
Customer Success Manager: the revenue after the revenue
The CSM owns the second sale — adoption, renewal, and expansion — and the org design question is whether the role carries a number. The 2026 market data suggests it increasingly does: account managers run median OTE around $180K with 47.8% quota attainment (ev-sr1-002), and the CSM-to-AM convergence is the decade's quiet rebranding of post-sale from cost center to revenue line. The boundary that leaks most is the handoff: the AE closes, the kickoff happens, and the CSM inherits a relationship whose promised outcomes live in the AE's head rather than the account plan. The repair is the documented success plan — the mutual close plan's post-sale twin — signed by AE, CSM, and customer before the ink dries.
RevOps: the instrument maker
RevOps owns the machine's instrumentation: the CRM architecture, the pipeline definitions, the forecast math, the comp plan mechanics, and the integrity of the seven numbers leadership reads. The role grew from administrator to owner as the data layer became the difference between managing and guessing — median pipeline coverage runs about 3.4x quota (ev-sr1-004), and whether a team's coverage is real or cosmetic is a RevOps verdict, not a vibe. The role's boundary discipline matters most with finance and IT: RevOps owns revenue data truth, negotiates its systems with IT, and answers to the CFO's audit. In the hundred-rep company, RevOps is a team; in the five-rep company, it is a fractional hire or a very organized operator — but the function exists either way, because the numbers exist either way.
VP Sales and CRO: the system owner
The VP Sales owns the revenue system for a stage; the CRO owns it across the whole motion, marketing included. The distinction is scope, not seniority — a VP Sales at a scale-up runs a bigger machine than most CROs ever will. The role's 2026 reality is a portfolio job: hiring the seven roles in the right order, setting the quota math so 3.4x coverage is achievable before demanding attainment, and defending definitions against the quarterly drift that corrupts every number downstream (ev-sr1-004). The failure mode at this layer is the hero rep promoted into a systems job — the best closer becomes the worst VP because the skills are different: forecasting is not closing, and coaching a seven-role org is not running a personal pipeline.
The seams where deals die
Every role boundary is a handoff, and handoffs are where information dies. The SDR-to-AE seam leaks qualification truth — the meeting notes say "budget confirmed" and the AE's first call discovers a steering committee. The AE-to-SE seam leaks technical debt — the demo answers last quarter's objections because the SE was booked late. The AE-to-CSM seam leaks promised outcomes. The RevOps-to-everyone seam leaks definition integrity, and the VP-to-board seam leaks forecast honesty. The org design answer is not more roles; it is documented handoff artifacts — qualification checklists, technical close plans, success plans, definition dictionaries — each owned by a named role, audited quarterly.
AI across the seven roles
The 2026 layer over the whole chart is AI augmentation, and it lands differently on each seat. On SDR and BDR desks, AI agents compress research and list construction — the hybrid deployments that pair agents with human judgment report pipeline gains up to 41%, while the fully autonomous sequences train buyers to filter machine voice on sight. On the AE seat, AI handles meeting prep and next-step drafting, but the close remains a human sport because trust is the product being purchased. The SE's workload shrinks on questionnaires — pattern-matched answers, human-verified — and expands on architecture conversations, which AI cannot own. CSMs get churn-signal instrumentation; RevOps gets definition-integrity automation; VPs get forecast scaffolding they must still have the judgment to overrule. The pattern across all seven: AI takes the preparation layer and leaves the relationship layer, which raises, not lowers, the value of the human who sits inside each role.
Building the org in the right order
The five-rep company needs three of the seven roles done well: an AE who can prospect, a fractional RevOps instrument, and a founder doing VP duty. The twenty-rep company splits SDR from AE, adds the SE as a shared resource, and hires the first CSM when renewal revenue matters more than a logo. The hundred-rep company runs all seven as teams, and its challenge inverts: the seams multiply faster than the headcount, and the definition dictionary becomes a governed artifact with an owner and a version number. The 2026 comp data prices each step of that build — and the org that respects the seams builds a machine where the seven roles compound instead of colliding (ev-sr1-001, ev-sr1-002). A final calibration on titles, because the market's vocabulary lags its structure. Job boards still advertise "sales rep" for SDR seats and "account manager" for CSM seats, and candidates price themselves against the wrong benchmark half the time. The seven-role model is not pedantry; it is the difference between hiring for a seam you know leaks and hoping a generic "salesperson" absorbs it. Founders who post the actual role — with its KPI, its comp band from the 2026 data, and its two promotion paths — fill seats faster and lose them less. The org chart is a hiring document before it is an org chart, and precision at the job-description layer is the cheapest org design intervention available.