At most startups, the founder is the first, best, and only sales rep for longer than anyone planned. They know the product, they know the objections, and they can improvise a good answer to almost anything a prospect throws at them. That works, right up until the pipeline gets too big for one person, and the company has to figure out, usually under time pressure, who does what next.
The default move is to hire "a salesperson," see how it goes, and hire another one the same way if the first one works out. There is no defined role, no reporting line, and no comp plan more sophisticated than a commission percentage picked because it sounded fair. Six months later, the company has three reps with three different interpretations of the job, no clear escalation path when a deal gets stuck, and a founder who is still fielding every hard question personally, just with more people now also asking them questions.
None of this is a hiring failure. It is a structure failure. The company added headcount before it decided what the headcount was for, and structure gaps do not announce themselves. They show up, as inconsistent close rates, reps stepping on each other's accounts, and a founder whose calendar has more sales calls on it a year after the first hire than it did before.
A team that scales past the founder needs three things defined before the fourth or fifth hire, not after: clear roles with real boundaries, a reporting line that can coach, not just check in, and a comp plan that rewards the behavior the business needs at its current stage, not a generic template borrowed from a company five times its size.
Why Generic Org Chart Advice Fails Startups
Most advice on structuring a sales team is written by, or for, companies that already have thirty or more reps and a mature revenue operations function to support them. Applied to a ten-person startup, it produces a structure with more specialized roles than the pipeline can feed.
1. It assumes a pipeline that doesn't exist yet
A dedicated SDR only makes sense once there is enough top-of-funnel volume to keep them fully occupied qualifying leads. Hire one too early, without that volume, and you have a person with idle hours between calls and an AE who is annoyed at the quality of the handoff, because there simply weren't enough good leads to hand off in the first place.
2. It borrows comp plans without borrowing the context behind them
A comp plan with five KPIs and three accelerator tiers might make sense at a company with a data team tracking all of it. At a ten-person startup, it is usually just confusing, and confused reps optimize for whichever metric is easiest to hit, not the one that matters most to the business.
3. It skips straight to titles and skips the actual handoffs
An org chart with boxes labeled SDR, AE, and CS looks complete on a slide. It says nothing about what happens at the moment a deal moves from one box to the next: what information transfers, who is accountable if it gets dropped, and what a rep does when a deal doesn't fit neatly into either box.
What a Structure That Scales Looks Like
A sales structure that scales isn't the most sophisticated org chart available. It's the simplest one that matches the volume, complexity, and stage of the business today, with a clear next step for when it outgrows that.
It defines exactly what each role is accountable for, in language specific enough to settle a disagreement: an SDR owns qualified meetings booked, not closed revenue; an AE owns everything from a qualified meeting to a signed contract; a CS or account manager owns everything after that. When two reps argue about who owns an account mid-deal, the answer should already be written down somewhere, not decided by whoever raises it first in a meeting.
It also defines who coaches whom, and on what cadence. A rep without a real manager, someone who reviews their calls and pipeline on a fixed schedule, ramps slower and plateaus earlier than one who has that structure, no matter how talented they are individually. And it ties compensation to the one or two outcomes that matter most at the current stage, rather than to every metric someone thought might be worth tracking.
A Step-by-Step Framework for Structuring the Team
1. Map the roles the business needs today, not the roles it will eventually need
Start from your actual pipeline volume and deal complexity, not from a template. Below a certain volume, a combined SDR/AE role, sometimes called a full-cycle rep, usually beats a premature split, because splitting too early creates idle capacity on one side of the handoff and a bottleneck on the other.
2. Define handoffs as explicitly as the roles themselves
For every point where a deal moves between roles, write down what information has to transfer and who is accountable if it doesn't. A qualified meeting handed from SDR to AE should come with a defined minimum: budget signal, timeline, and the specific problem the prospect described, not just a calendar invite and a name.
3. Build comp plans around the one or two behaviors that matter now
Early on, that is usually new logo revenue or qualified pipeline generated, not a blend of five weighted metrics. A simple base-to-variable split, commonly 60/40 or 70/30 depending on deal cycle length, with accelerators for exceeding target, is easier for a small team to run and easier for reps to understand without a spreadsheet.
4. Write hiring profiles and interview scorecards before you post the job
Define the specific competencies the role requires, based on what your best-performing rep already does well, and score candidates against that consistently. Hiring on instinct alone, without a shared standard, is how three reps end up with three different definitions of the job by month two.
5. Install a 90-day onboarding path, not an open-ended shadowing period
A new rep should know, on day one, what they need to demonstrate by day thirty, sixty, and ninety to be considered ramped. Without that, ramp time stretches indefinitely, and nobody can say with confidence whether a slow start is a training problem or a hiring mistake.
When to Split SDR and AE, and When Not To
This is the single most common structural question early-stage founders ask, and the honest answer depends on volume, not ambition. A dedicated SDR role is justified once there is enough consistent top-of-funnel activity, inbound or outbound, to keep a prospector fully booked without an AE's help. Below that threshold, splitting the role just means paying two salaries to do the work one full-cycle rep could handle, with a handoff in the middle that adds friction and no real capacity.
Above that threshold, keeping the roles combined starts to cost more than it saves. Prospecting and closing require different skills and different daily rhythms, and asking one person to context-switch between cold outreach and a late-stage negotiation call, all day, every day, tends to make them worse at both. The split earns its keep once there is enough opportunity volume on each side to justify specialization.
There is no universal headcount number where this switch should happen, because it depends on deal cycle length, average deal size, and how much of your pipeline is inbound versus outbound. What matters is making the decision deliberately, based on actual pipeline data, rather than defaulting to a split because it is what a hiring template or a well-known scaleup happened to do at a very different stage of growth.
A useful test before making the switch: track how many hours a week your current full-cycle reps spend prospecting versus running late-stage calls. If prospecting is consistently squeezed to evenings and Fridays because closing work keeps taking priority, that is a signal the pipeline volume already justifies a dedicated SDR, even if the calendar math technically still fits in one role for now. Waiting for a perfectly obvious signal usually means waiting until pipeline has already started to suffer.
Common Mistakes That Trap the Founder in Sales
A few patterns show up again and again in teams that can't get the founder out of day-to-day selling.
- Hiring "a salesperson" with no written role definition, then hiring the next one the same way
- Splitting SDR and AE roles before there's enough pipeline volume to justify it
- Promoting the top individual performer into management with no training or support
- Running comp plans with so many metrics that reps can't tell what matters most
- Letting every deal escalate to the founder instead of defining what a manager can decide alone
Each of these looks like a hiring or people problem from the inside. Underneath, all of them are structure problems, and structure is the thing to fix first.
How Growth Frontier Implements Team Structure
We start with an audit, not a template. That means looking at your actual pipeline volume, deal cycle, and current headcount, and interviewing whoever is closing deals today, founder included, to understand what is genuinely working before we change anything. A structure built without that step tends to solve for problems the business doesn't have yet.
From there we design the roles, reporting lines, and handoff protocols your stage requires, calibrated specifically to your deal size and sales cycle rather than a headcount benchmark pulled from a different industry. Compensation gets built alongside the structure, not after it, so the incentives and the org chart are pulling in the same direction from day one.
The engagement includes hiring profiles, interview scorecards, and a 90-day onboarding program, so the next hire ramps against a defined standard instead of shadowing whoever happens to be free that week. We stay through the first thirty days of rollout to calibrate against real ramp data, because a structure that looks right on paper sometimes needs a small adjustment once actual people are working inside it.
If the structure problem traces back further, to an undefined ICP, positioning, or pricing that the team is supposed to be executing, that is worth solving first. We cover that in Sales Strategy & Planning, the layer underneath team structure that determines what your reps should be doing in the first place, before you decide how many of them you need.
“Hiring a salesperson doesn't remove the founder from sales. A defined structure does.”
Where This Lands in a Six-Month Build
Months 3 - 5 of the project outline, after a month of analysis has decided it is worth doing.
Nothing described above gets proposed on day one. Every engagement opens with a month of analysis that scores ten areas of the organisation, followed by an evaluation and a custom scope priced against what it found. Only then does the build start, and the sequence it runs in is fixed: technology, then the sales organization, then marketing, then tracking, then handover.
Organizational changes are the longest workstream in the outline, and the one most likely to be underestimated. Roles, job descriptions and compensation are changes to people's working lives, so they are scheduled with room either side: after the technology is in place, and long enough before handover that the structure has been observed running.
See the full six-month outline, or read what we build in this discipline.
Common Questions
When should a founder hire their first sales rep instead of selling personally?
When the founder can describe, in writing, how they win a deal today, and it's repeatable across more than a handful of accounts. Hiring before that point just means a new rep learns confusion faster; hiring after it means they inherit a real process instead of a blank page.
What's the right SDR to AE ratio for an early-stage team?
There often isn't one yet. Below roughly five or six reps, a combined SDR/AE role usually makes more sense than splitting, because the pipeline isn't large enough to keep a dedicated prospector fully occupied. The split earns its keep once qualified opportunity volume is large enough to specialize around.
How should we structure comp plans for our first sales hires?
Simple, and tied to outcomes the rep controls directly. A common starting point is a 60/40 or 70/30 base-to-variable split with one primary metric, not five competing ones. Overcomplicating comp before you have data on what predicts a good rep is a common early mistake.
What org structure works before we can afford a full SDR/AE split?
A small number of full-cycle reps who own a deal from first call to close, reporting directly to the founder or a working sales lead. This is less efficient per deal than a specialized structure, but it's far easier to manage with a small team and limited pipeline volume.
Who should manage the sales team once the founder can't anymore?
Usually a dedicated sales manager hired specifically for that role, not the strongest individual rep promoted by default. Selling and managing are different skills, and promoting a top performer into management without support is one of the most common ways to lose both a good rep and a good manager at once.
Ready to Build a Team That Scales?
We'll design the roles, comp plans, and onboarding your team needs to grow past you.