Skip to content
← Back to blog

AI sales roles in 2030: the return of the full-cycle seller

Summarise this article with
AI sales roles in 2030: the return of the full-cycle seller

AI doesn't replace the seller. It replaces the machinery around them: research, preparation, documentation, CRM upkeep, routine follow-up. What remains is an AI-native full-cycle seller who owns the customer relationship from the first signal to the renewal. The lasting advantage isn't the agent but customer memory: every signal connected and retrievable when a human or an agent needs it.

The only sales role that may survive AI is the salesperson.

Not the SDR, not the account executive, not the customer success manager, not the account manager. A full-cycle seller who owns the customer relationship from first signal to renewal, backed by agents that do the invisible part of the work.

That is the paradox in a recent episode of The Science of Scaling with Day AI founder Christopher O'Donnell. AI clears out many specialised sales roles and brings the salesperson back at the same time. I listened to the episode twice. The paradox holds.

An illustrative example you probably recognise: an account executive at a 60-person SaaS company is preparing a renewal call for a key account. The CSM who owned the account left last month. The notes live in the CRM, in three Slack channels and in a former colleague's inbox. The last CRM entry says "all good, follow up Q3". She walks into the call unaware of an open support escalation. The customer asks why nobody mentioned it. The deal survives. The trust does not fully.

That is not an AI problem. It is a relay-race problem, and AI makes it faster and louder.

Sales did not start as a relay race. One person found the customer, understood the problem, won the deal and kept the relationship. Growth then split that job into SDR, AE, CSM, AM, support and RevOps. Each function got more efficient on its own. The customer experienced more handovers, and context leaked at every one.

Product development went the same way. A generalist builder became a chain of product managers, designers, front-end, back-end, data, QA and ops. AI changes the economics that made both chains sensible. A capable generalist covers more ground again, without pretending to hold every specialist skill.

What you'll learn

  • Which metric replaces the AI adoption rate, and why "our team uses AI" says nothing about your sales system
  • How to split an AE's role into jobs an agent can take, and which ones stay with the human
  • Where the SDR-to-AE-to-CSM relay collapses, and where specialists stay
  • Why customer memory is the moat and the agent is not

My thesis: AI does not replace the seller, it replaces the machinery around them

Research, preparation, documentation, system updates, analysis and routine follow-up move to agents. What stays with the human and gets scarcer: trust, judgement, taste, curiosity, relationships and accountability.

This is not a claim that one model can run a revenue organisation alone. It is an organisation design argument. When coordination and routine execution get cheap, the case for slicing one customer relationship across six people gets weaker.

I'll show it in four steps: metric, delegation, org chart, memory. The last one is the strongest, so it comes last.

What should replace the AI adoption metric?

Work product. Counting licences, prompts or weekly active users tells you that people touched AI. It does not tell you whether your sales system got better. The better question is: what leaves the system differently than before?

In the episode, Mark Roberge and Christopher O'Donnell propose harder hypotheses. Could a seller move from roughly 25% of the week in customer-facing selling to 75%? Could one manager support 14 sellers instead of seven? Could output per rep double? These are not benchmarks. They are testable operating questions from a conversation, and that is how you should treat them.

The difference is not academic. "Our team adopted AI" is an activity statement. "Our sellers spend two more days a week with customers and forecast quality holds" is a work-product statement. Only the second one belongs in a board deck.

A useful scorecard starts with what leaves the system:

  • Customer-facing time per seller
  • Time from meeting to accurate follow-up
  • Completeness and freshness of account context
  • Qualified opportunities created per seller
  • Manager span without a drop in coaching quality
  • Retention and expansion after the signature

The same discipline applies to any AI programme in sales: one measurable bottleneck, not a broad adoption campaign. What that looks like in practice is in how to get started with AI in B2B sales.

Why do agents need jobs rather than prompts?

A prompt asks for an output. A job defines an ongoing responsibility: the context it needs, the constraints, the review point and the result. Agents given prompts produce volume. Agents given jobs produce work someone can check and own.

Take a mid-market account executive. The role contains many jobs that do not need the AE:

  • Prepare an account brief before the meeting
  • Pull the relevant product usage and support history
  • Draft the follow-up and list unresolved decisions
  • Update the CRM and forecast fields
  • Compare what changed since the last conversation
  • Flag risk, buying signals and missing stakeholders

Those are better agent jobs than "help me sell this account". Each has inputs, a repeatable process and a moment when a human checks the result.

The seller's job then gets clearer, not smaller: hold the conversation, listen for what is not said, earn trust, make a judgement and own the decision. An agent can prepare a point of view. It cannot carry accountability for the relationship.

This is why bad automation disappoints so often. The team buys a tool, writes a clever prompt and leaves the job undefined. The agent has no stable objective, no source hierarchy and no definition of done. A practical delegation system starts by splitting the role into job descriptions, the way an agent-ready GTM ticket turns vague work into an executable brief. And before you delegate, you map the process, the way a forward deployed engineer would.

What happens when the org chart starts melting?

The SDR-to-AE-to-CSM-to-AM relay collapses towards a full-cycle seller. Not everywhere and not overnight. But the line between "before the deal" and "after the deal" gets hard to defend once one human can retrieve the full customer history and delegate the work around it.

I take the strongest counterargument seriously: specialisation had reasons. SDRs exist because volume and ramp time had to be cheap. Enterprise deals need teams with solutions architects and procurement experience. Generalists can get shallow. That stays true. What changes is not that expertise disappears. It takes fewer handovers to apply it.

You can see the same recombination in product and engineering. Designers build working prototypes. Engineers look at customer evidence themselves. Product people query data directly. O'Donnell describes an "agent engineer" at Day AI as one example of a hybrid role, commercial and technical at once. The title matters less than the shape: close enough to the customer to understand the job, technical enough to make agents useful against it.

That creates an Innovator's Dilemma for organisation design. A startup hires five people with the new profile. An incumbent may have five hundred people whose careers, incentives and systems depend on the old specialisation. The startup does not have better models. It can redesign the work faster.

The answer for incumbents is not to delete functions in a spreadsheet. In Germany, the works council sits at the table for changes like this anyway. The answer is to test where continuity improves the customer experience, then retrain around broader ownership. The State of Go-to-Market 2026 already shows smaller AI-enabled teams: 45 instead of 65 FTEs in the 25 to 100 million revenue band. But team size is an outcome. The design question is: who owns the customer when the machinery gets cheap?

Why is customer memory the real moat?

Because agents are becoming commodities. Models improve, agent frameworks converge, useful skills get copied fast. The same research, drafting and workflow capabilities will be available to every competitor. What stays different is what the agent knows about this customer, this company and this moment.

I led the sale of a CRM to Swisscom. So I don't think CRM is dead. But the CRM is one input, not the whole truth. The customer also exists in meeting transcripts, email, Slack, support cases, product usage, contracts, implementation notes, call recordings and decisions that never made it into a field. The relational system does not disappear. It becomes part of a wider memory layer.

That layer needs three properties:

  1. Coverage. It connects the relevant customer signals across systems instead of treating one database as complete.
  2. Permissioning. People and agents only retrieve what they are allowed to see. Sensitive material is handled deliberately.
  3. Retrieval. It brings the right fragment to the point of work, rather than dumping the entire archive into every prompt.

This is the strongest argument because it explains why so much AI sales output is poor. A generic AI SDR may have a capable model and a polished sequence. It still sends irrelevant messages because it does not know that the prospect raised a security concern last month, used a competing product in a previous role, attended a webinar yesterday and has an open support ticket.

That is a context failure before it is a model failure. Fragmented context, customer knowledge scattered across heads, tools and chats, is not fixed by AI. AI makes it faster and louder.

The durable capability is not generating more words. It is retrieving the right piece of organisational memory when a seller or an agent needs it. A useful customer data system for B2B sales therefore has to preserve meaning across the whole relationship, not merely fill more fields.

Persistent memory also solves the handover problem from the opening. The AE in the example would have seen the open escalation before she joined the call. A customer should not have to retell their history because an SDR passed them to an AE, or because the AE left. The organisation should remember. The human owner can change without the relationship resetting to zero.

What do you do as a sales leader on Monday?

Do not start with the future org chart. Start with one customer journey and map the work around it.

  1. Choose one seller. Someone with strong judgement and enough range to own more of the cycle.
  2. List the jobs around the relationship. Separate conversation and decisions from preparation, documentation, retrieval and routine follow-up.
  3. Delegate three narrow jobs. Give each agent sources, constraints, a review gate and a work-product metric.
  4. Build memory as you go. Connect the minimum customer signals those jobs need, and define access before you scale.
  5. Measure continuity. Customer-facing time, follow-up quality, context completeness and post-sale outcomes.

The aim is not to prove that one person can do six old jobs. The aim is to find out which parts of those jobs were machinery, which were expertise and which need a trusted human owner.

Where this works, where it doesn't, and the trap

✅ What shines. Mid-market deals with clear product usage, where one seller backed by agents can hold the relationship from signal to renewal. Every handover you remove there removes a piece of context loss, and the customer notices.

❌ What doesn't shine. Enterprise deals with twelve stakeholders, a security review and procurement. The team stays, and the full-cycle seller is the owner, not the one-person show. And the numbers from the episode, 25 to 75% customer-facing time, 7 to 14 sellers per manager, are the two speakers' hypotheses, not benchmarks. Test them, don't quote them.

⚠️ Warning. The trap is buying the agent before the memory. An AI SDR on top of an empty CRM scales irrelevance. Connect the signals and define access first, then delegate.

Back to the start. The only sales role that may survive AI is the salesperson. One human owns the relationship end to end. Agents prepare the work, keep systems current, surface risks and recover the relevant history. I call that Get Multiplayer: humans set goals, decide and approve. Agents prepare and do the repeatable work. Shared goals and shared context keep them working together. The machines do not forget. The human still decides what matters.

As execution gets cheaper, trust, judgement and customer understanding get more valuable. The seller of 2030 looks less like the final station in a pipeline and more like the person sales was built around in the first place.

If you want one operator note a week on Product, GTM and AI: subscribe to The Science of GTM newsletter.

Frequently asked questions

Will AI replace salespeople by 2030?
In the Science of Scaling episode, Mark Roberge and Christopher O'Donnell argue that AI is more likely to replace the machinery around selling than the human who owns the relationship. Research, documentation, CRM updates, analysis and routine follow-up can move to agents. Judgement, trust and accountability remain human work.
What is an AI-native full-cycle seller?
An AI-native full-cycle seller owns the customer relationship from the first signal through the deal and into retention and expansion. Agents support that person with preparation, retrieval, documentation and recurring operational work. The human decides and carries the accountability. Fewer handovers mean less lost context.
Which sales roles converge as AI improves?
The boundaries between SDR, AE, CSM and AM weaken because one seller with agent support can cover more of the customer cycle. Specialists stay useful, especially in complex enterprise deals with security reviews and procurement. It just takes fewer handovers to apply their expertise.
Why is customer memory more important than the AI agent?
Agent capabilities are becoming commodities, every competitor gets the same models and frameworks. Useful output depends on retrieving the right customer context from meetings, email, support, product usage and CRM, with the right permissions, at the moment a human or an agent needs it. That is a context failure before it is a model failure.
How should a sales team measure AI value?
By work product, not adoption. Useful measures are customer-facing time per seller, follow-up speed and quality, completeness of account context, qualified opportunities per seller, manager span without a drop in coaching quality, and retention and expansion after the signature. How many people use a tool says little about its value.
Written by

Serial Entrepreneur, Author

Marc works at the intersection of Product × GTM × AI and builds B2B software companies with humans + agents. He started his first software company at 16 and has spent twenty years where software product management meets go-to-market. Co-founder of Teklens, the Company Brain for tech companies. Innosuisse expert and Springer Gabler author.