Back to Learn
The SDR/AE split can make economic sense when deal size, sales complexity, and buyer expectations justify the handoff.
My general decision bar is around $50,000 in annual contract value.
Not because $50K is a magic number. It is not.
But once a deal gets into that range, the economics usually start to support deeper research, stronger signal work, and more specialized roles. Below that, especially in transactional deals, the model is often overused and quietly unprofitable.
The better build for many teams is a full-cycle seller supported by an evolved SDR role that owns data, signal, research, and tooling.
You split the roles because that is what sales orgs were supposed to do.
SDRs book meetings. AEs close deals. Everyone knows their lane.
Nobody stops to ask whether the deal size can actually pay for the handoff.
Now your cost of sale is climbing. Your reps are stuck below quota. Buyers are repeating the same context twice. And the model you copied from another company is working against you.
That is the naked emperor of B2B sales.
A structure everyone can see is broken in certain motions, but very few leaders are willing to question.
Key Takeaways
- The SDR/AE split usually earns its cost when deal size, complexity, and buyer expectations justify a handoff.
- My general decision bar is around $50K ACV, not as a universal rule, but as a practical threshold for when specialization starts to make more sense.
- Below that, especially near transactional price points, a separate SDR layer can make the math harder and the buying experience worse.
- The model spread because it fit the growth-at-all-costs era, not because it always served the buyer.
- A handoff is not free. It costs money, time, context, and buyer trust.
- The SDR role should evolve into a GTM engineer or sales assistant function that owns data, signal, and AI-assisted workflows that make great sellers better.
- You cannot scale a broken system. Fix the model before you add more reps to it.
Who this is for
This is for founders and VPs of Sales deciding how to structure a go-to-market team.
It is also for RevOps leaders weighing whether to add or keep a dedicated SDR layer.
If you are about to hire your first SDR, or you already run a split and your unit economics feel off, this is the decision you actually need to make.
Quick definitions before we get into the math
An SDR, or Sales Development Representative, is usually responsible for prospecting, outbound activity, qualification, and booking meetings.
An AE, or Account Executive, usually owns discovery, sales conversations, deal progression, negotiation, and closing.
The SDR/AE split is the sales model where one role creates or qualifies the opportunity and another role runs the sales cycle.
ACV means annual contract value. It is the annual revenue a customer is worth to your business.
CAC means customer acquisition cost. It is what you spend to acquire a customer, including people, tools, marketing, and sales costs.
A full-cycle seller owns the sales process from prospecting through close.
A GTM engineer is an evolved support role that sits between sales and RevOps. Instead of only booking meetings, this person owns data quality, list building, signal interpretation, enrichment workflows, and the tools that help sellers show up with relevance.
These definitions matter because the question is not, “Should we hire SDRs?”
The better question is, “Has this sales motion earned the right to add another role, another handoff, and another layer of cost?”
Why is the SDR/AE split quietly failing so many teams?
Because most teams adopted it as a default, not as a decision tied to deal size, sales complexity, or buyer experience.
They copied the org chart before they checked the math.
From training thousands of sellers across nearly two decades, I have watched this play out again and again. A company splits the roles, adds headcount, and assumes growth will follow.
What follows instead is friction.
The SDR asks discovery-adjacent questions. The buyer gives context. The meeting gets booked. Then the AE joins the next call and asks the buyer to explain the same problem again.
That is not a small thing.
Every handoff adds cognitive load. Every repeated explanation costs the buyer attention. Every seam in your process gives the buyer another reason to wonder whether your team is actually listening.
You pay for the model twice.
You pay for it in cost of sale.
Then you pay for it again when the buyer has to carry your internal complexity.
At what deal size does an SDR/AE handoff actually make sense?
My general decision bar is around $50,000 ACV and up.
That does not mean every $49K deal should be full-cycle or every $51K deal needs an SDR. Please do not turn this into fake math.
The point is simpler than that.
Once a deal is large enough, complex enough, and research-heavy enough, specialization can start to earn its place. The deal may require deeper account research, stronger signal interpretation, multiple stakeholders, and more thoughtful outreach. In those motions, an SDR or GTM support role can create real leverage.
A $5,000 transactional product usually does not earn that same level of contact-by-contact research or a two-person sales motion.
That does not mean you abandon relevance.
It means you stop pretending a transactional motion is an enterprise one.
The work has to match the deal. The cost has to match the price point. And the buyer experience has to be better because of the structure, not worse.
This is the question most founders skip.
They ask how to make the SDR-to-AE handoff smoother.
The better question is whether their deal size earns a handoff at all.
Why does the math break at lower deal sizes?
Because labor is not free.
That sounds obvious, but this is the math teams skip.
When you run a sales-led process where the first touch is a cold call or email from an SDR, your customer acquisition cost is not just ad spend. It is the SDR’s salary and commission. It is the AE’s salary and commission. It is the sales tools, enrichment tools, dialers, data providers, and management layer underneath them.
Then you have to ask whether the deal can carry all of that.
In a higher-ACV motion, it might.
In a lower-ACV motion, the math can get ugly fast.
John Barrows shared a useful example during the Make It Happen Mondays episode “Owning the Pipeline Like a CEO” that illustrates the problem. Referencing data from a Pavilion presentation he delivered, Barrows estimated that the SDR resources required to land a single $10,000 ACV customer could cost roughly $6,000. That figure does not include the Account Executive, sales engineer, or supporting technology costs.
The exact number will vary by company. The point is not whether your cost is $5,000, $6,000, or $7,000. The point is that low-ACV deals can become expensive very quickly when multiple layers of headcount are involved.
Teams calculate CAC like headcount does not count.
It does.
At a $10K deal size, a separate SDR layer can make you unprofitable in year one. Not because SDRs are bad. Because the price point may not cover the people required to acquire the customer.
Make it make sense.
If you are selling a lower-ACV product and paying two sellers plus a tech stack to create one customer, the math needs to be very clear.
Most of the time, it is not.
Why did this model spread if it does not work for everyone?
Because it suited a specific era.
The SDR/AE split became especially popular in SaaS and venture-backed sales environments where money was cheaper, growth expectations were aggressive, and specialization looked like maturity.
Hire more SDRs. Book more meetings. Add more AEs. Show more activity.
That worked well enough for long enough that a lot of teams stopped questioning it.
But “we can afford this for now” is not the same as “this is a durable business model.”
During the growth-at-all-costs years, companies could throw more bodies at the revenue gap. If productivity was low, they hired more reps. If reps were missing quota, they widened the team. If pipeline was thin, they added more activity.
The buyer paid the price.
The silos built in the last decade often served the company’s reporting structure more than the buying process. They created more internal specialization, but not always more buyer clarity.
And buyers feel that.
They feel it when they explain their world to one person and then have to do it again.
They feel it when the SDR does not have enough context to answer real questions.
They feel it when the AE starts discovery from scratch because the handoff notes are thin.
They feel it when your internal process becomes their unpaid labor.
That is the part too many teams ignore.
A handoff is an ask. You are asking the buyer to trust that the next person will understand them better, move them forward faster, and make the conversation more useful.
If the handoff does not do that, you have not earned it.
What should the SDR role become?
It should evolve.
Not disappear.
I respect the people in the SDR seat. It is hard work. It requires resilience, curiosity, and a willingness to start conversations with people who were not expecting to hear from you.
The problem is not the person.
The problem is the way many companies designed the role.
I love using an SDR-type employee for prospecting and intelligence work. I do not want a high-cost AE whose core skill is running the middle and bottom of the funnel spending all day cleaning lists, enriching data, and manually sorting signals.
That work matters.
It should be owned by the right role.
For many teams, the smarter version of the SDR role looks more like a GTM engineer or sales assistant function.
This person bridges sales and RevOps. They use tools like Clay, ZoomInfo, CRM data, enrichment platforms, and AI-assisted workflows to bring in better intelligence. They help identify the right accounts, surface useful signals, clean the data, and build workflows that make outreach more relevant.
The support role owns the intelligence layer.
The AE owns the buyer conversation that intelligence makes possible.
That is a better division of labor.
Not “SDRs book meetings and throw them over the fence.”
Not “AEs waste hours doing manual list work.”
A strong GTM support role should help a seller show up more prepared, more relevant, and more useful to the buyer.
That is the job.
When is keeping SDRs and AEs separate the right call?
When the deal is large enough and complex enough to pay for the structure.
The SDR-to-AE model still works in the right environment. It can create leverage. It can protect senior sellers’ time. It can support deeper research and stronger account strategy.
But it has to earn its place.
Keep the split when:
- ACV is high enough to absorb the cost.
- Sales cycles are long enough to justify specialization.
- Buying committees are complex.
- Account research materially improves the odds of winning.
- The SDR can make the AE more effective instead of creating more buyer friction.
- The handoff improves the buyer experience instead of slowing it down.
The mistake is applying an enterprise structure to a transactional business and assuming volume will rescue the margins.
It usually will not.
You cannot scale a broken system.
Before you add another SDR, decide whether your deal size earns the one you already have.
The decision rule
Use an SDR/AE split when the deal is large enough, complex enough, and research-heavy enough to justify a handoff.
Use a full-cycle seller when the deal is lower ACV, more transactional, and the handoff adds more cost than value.
Use a GTM engineer or sales assistant when your AE needs better data, cleaner lists, stronger signal work, and support from tools, but the buyer does not need another person in the process.
The decision is not about copying the org chart from a company you admire.
It is about asking whether the structure earns its cost.
Does it improve the buyer experience?
Does it reduce friction?
Does it help the seller show up with more relevance?
Does the price point support the people involved?
If the answer is no, the model is not strategic.
It is just expensive.
FAQ
At what ACV does an SDR/AE split stop being profitable?
There is no universal cutoff, but my general decision bar is around $50,000 ACV.
Below that, the split gets harder to justify. Near transactional price points, especially around $10K or lower, it can become unprofitable quickly because the deal has to absorb both SDR and AE headcount, plus the tools and management layer underneath them.
The question is not just, “Can this model create meetings?”
The question is, “Can this deal size pay for the way we are acquiring customers?”
What should replace the SDR role at smaller deal sizes?
For many teams under that threshold, a full-cycle seller makes more sense.
That means one seller owns prospecting through close, which keeps cost of sale aligned with the deal size and removes unnecessary handoffs from the buyer experience.
If you keep a support role, evolve it into a GTM engineer or sales assistant function. That person owns data, signal, list-building, enrichment, and tooling so the closer can stay focused on buyer conversations and deal progression.
The point is not fewer people.
The point is matching the work to the role, the cost, and the buyer experience.
What is a GTM engineer?
A GTM engineer is the evolution of the traditional SDR support function. Instead of being measured only on dials and meetings booked, a GTM engineer bridges sales and RevOps. They use tools like Clay, ZoomInfo, CRM data, enrichment platforms, and AI-assisted workflows to surface better intelligence and improve seller efficiency.
The goal is not to replace the seller.
The goal is to feed a strong seller better data, better signals, and better context so they can show up with more relevance.
Is the full-cycle AE model better for small deals?
Usually, yes.
For transactional and lower-ACV products, a full-cycle seller often makes more economic sense because there is no costly handoff to absorb.
One rep owns the relationship from prospecting through close. That keeps the cost of sale lower and reduces the amount of context the buyer has to repeat.
It is not always perfect. But for smaller deals, it often fits the economics and the buyer experience better than a split SDR/AE model.
Why does the SDR/AE split frustrate buyers?
Because each handoff is a seam the buyer has to cross.
A buyer explains their problem to the SDR. Then they join a call with the AE and have to explain it again. If the handoff is weak, the buyer starts wondering whether anyone actually listened.
That adds cognitive load.
It also erodes trust.
A good handoff should make the next conversation better. If the AE starts from zero, the handoff did not earn its place.
What framework can I use to decide whether to split SDR and AE roles?
There is no branded acronym for this one.
Use a simple decision lens:
- What is the ACV?
- How complex is the buying process?
- How much research is required to earn relevance?
- How much buyer friction does the handoff create?
- Does the handoff improve the buyer experience?
- Can the deal size absorb the full CAC, including people and tools?
My general decision bar is around $50K ACV. Above that, a split can make sense if the motion is complex enough. Below that, especially near transactional price points, start with a full-cycle seller and add support only when the math and buyer experience both support it.
Can you recommend books that will help me learn more?
Yes. Read Profit Generating Pipeline: A Proven Formula to Earn Trust and Drive Revenue by Leslie Venetz, available at www.salesledgtm.com/book.
The book outlines a 9-step formula for prospecting and revenue generation adapted to the modern buyer.
How can I learn more about hiring Leslie as a speaker or working with her team?
Visit www.salesledgtm.com to learn more about services and schedule time to connect.
Closing
The org chart you copied was built for a different era. Cheaper money. Less scrutiny. More tolerance for bloated sales motions. You do not have to keep defending it.
Look at your deal size. Run the real cost of your headcount. Watch where buyers are carrying the weight of your internal handoffs. Then ask the question most teams skip:
Has this model earned the right to exist in this sales motion?
That answer will tell you more about how to build your team than any borrowed org chart ever will.