Should an SDR Learn how to be a GTM Engineer?

Sales development is becoming dramatically more technical.

An SDR team today can be surrounded by CRM systems, data providers, enrichment platforms, intent signals, AI research, automated sequencing, call recording, lead scoring and workflow automation. In the last year, a new discipline, GTM engineering, has emerged specifically to connect these technologies and turn them into scalable revenue systems. Clay, one of the companies closely associated with the term, describes GTM engineering as building automated revenue systems using AI, data enrichment and workflow automation.

As one of the biggest SDR training programs, we are thinking about the question: How much of this technology should an SDR actually be responsible for?

Our view at Salesclass is that there is a danger in confusing two different developments. SDR teams should absolutely continue to be technologically savvy. But, that does not mean every SDR needs to become a GTM engineer.

In fact, we believe better GTM engineering should allow SDRs to spend more of their time doing the thing for which great SDRs are ultimately hired: having effective conversations with customers.

What Is GTM Engineering Changing About Sales Development?

Think about how much work traditionally sat with an SDR.

A rep might identify accounts, find the right people, research them, verify contact information, enter data into a CRM, decide who to contact, personalize a message, add prospects to sequences, make calls, update records and manage follow-up.

Only part of that work actually involves interacting with a potential customer.

Modern GTM technology is increasingly capable of handling much of the work surrounding the interaction. Systems can source and enrich prospects, identify buying signals, research companies, prioritize accounts, route leads, prepare information for calls and automatically update CRM records.

Clay makes the distinction particularly clearly. It describes the primary output of an SDR or BDR as booked meetings, while the GTM engineer builds workflows that perform research and preparation so that each rep can cover a larger book of accounts.

That distinction matters because it suggests a very different future for sales development from one in which every SDR becomes a part-time systems engineer.

There Are Really Three Jobs Here

The easiest way to think about the modern SDR organization is to separate three responsibilities that increasingly get mixed together.

RevOps and GTM engineering build and maintain the machine. There is a distinction between the two. RevOps typically owns foundational systems, CRM integrity, processes, routing and reporting, while GTM engineering is increasingly focused on building and experimenting with automated revenue plays on top of that infrastructure. Even Clay, which has pushed particularly hard toward GTM engineering, describes the two functions as complementary rather than interchangeable.

The SDR manager owns the sales motion. The manager needs to determine whether the right people are being targeted, whether the value proposition is resonating, what objections are appearing, whether conversations are effective and whether the resulting meetings are genuinely valuable.

The SDR owns the interaction. When the phone connects or a prospect responds, someone needs to turn that opportunity into a real conversation. That requires listening, questioning, communication, judgment, product understanding, objection handling and the ability to establish relevance quickly.

There will always be overlap between these jobs. An SDR should understand the systems they use. A manager should understand how the technology works. A GTM engineer needs enough commercial understanding to know what is worth automating.

But overlap does not mean everyone should have the same job.

Should an SDR Know How the GTM Engineering Works?

Absolutely.

A modern SDR who is frightened of technology is going to struggle. SDRs should understand their CRM, know how sequences work, understand where their prospects came from and recognize how AI and automation are being used in their sales process.

They should also be able to recognize when the technology gets something wrong.

If an AI-generated account summary misunderstands the company, the SDR should notice. If an enrichment system gives them the wrong person, they should question it. If the targeting produces a stream of prospects who clearly do not have the problem they are supposed to be solving, they should raise it.

That requires technological fluency and commercial judgment.

It does not necessarily require the SDR to build the enrichment waterfall, connect the APIs or design the automation that put the prospect in front of them.

What Should GTM Engineering Take Away From the SDR?

GTM engineering can be exciting for sales development success.

Consider the amount of SDR time that can disappear into manual research, list preparation, data cleaning, CRM administration, contact enrichment, repetitive personalization and moving information between systems. These tasks may be necessary, but they are generally not why somebody hired a talented communicator.

GTM engineering gives companies an opportunity to move much of that work elsewhere.

Clay describes GTM engineering workflows that automate seller research, update CRMs from call transcripts and provide sellers with account signals and call preparation. Its GTM engineering methodology explicitly looks for repetitive work that can be systematized rather than repeatedly performed by a person.

The interesting question is what we do with the time that automation gives back.

We think the answer should be more customer interaction.

More calls. Better preparation for important conversations. More listening. Better questions. More thoughtful follow-up. More time learning why prospects are interested, why they are not interested and what would have to change.

The purpose of GTM engineering should not simply be to allow an SDR to send more activity. It should help create more opportunities for meaningful human interaction.

The SDR Manager Becomes the Bridge

This also makes the SDR manager more important, not less.

Imagine that GTM engineering creates a sophisticated signal identifying companies that appear ready for your product. The system enriches those accounts, finds the relevant stakeholders, prepares research and delivers those prospects to the SDR.

The SDR starts calling. Then something incredibly valuable happens that cannot be seen from the database alone: customers start talking back.

Perhaps the supposed buying signal isn't actually important. Maybe one job title responds far better than another. Perhaps prospects consistently misunderstand the value proposition. Maybe an objection appears repeatedly that nobody anticipated when the campaign was designed.

The manager's responsibility is to turn individual conversations into organizational learning. They should listen to calls, coach SDRs, identify patterns and bring those insights back to the people responsible for targeting, messaging and GTM systems.

That creates a feedback loop:

GTM system → SDR → customer conversation → SDR manager → insight → improved GTM system.

The machine gets better because humans are talking to customers.

Should Some SDRs Become GTM Engineers?

Definitely. But this is a different career path.

There will be SDRs who discover that they love the systems side of the job. They may find themselves experimenting with Clay, building workflows, working with AI, connecting data sources and thinking constantly about how to automate repetitive processes.

GTM engineering could be a fantastic career path for those people.

The role itself is still evolving. Clay has even experimented with a much more radical model in which traditional SDR, AE and sales engineering responsibilities are collapsed into a highly technical GTM engineering function. In its model, people combine automation and systems building with customer conversations and selling.

That is an interesting model, particularly for companies selling highly technical GTM products. It does not necessarily follow that every company needs its SDR organization to look like that.

Clay itself acknowledges how unusual the required combination is. Its description of strong GTM engineering candidates combines technical fluency and systems thinking with being highly effective with people and customer calls.

Those people exist. But they represent a particular talent profile. Someone else may be exceptional at opening conversations, making people comfortable, listening carefully, thinking on their feet, understanding business problems and handling objections without having any desire to build a data pipeline.

That person can still be an exceptional salesperson.

As Sales Technology Improves, Human Skills Matter More

There is an interesting paradox at the center of all this. The more work technology can do before a conversation, the greater the opportunity to concentrate human effort on the conversation itself.

AI can provide an SDR with information about a company. It can suggest why a particular prospect might care about the product. It can summarize previous interactions and propose questions to ask.

Then the prospect answers the phone. The conversation immediately becomes unpredictable. The prospect misunderstands what you do. They interrupt. They give you an objection you weren't expecting. They mention a problem that wasn't in your research. Their tone changes. Something you say creates curiosity and suddenly the conversation goes somewhere completely different.

This is where strong salespeople differentiate themselves.

They listen rather than simply waiting for their turn to speak. They ask the next question based on what somebody actually said. They understand when to push and when to stop. They communicate complicated ideas simply. They recognize when the problem they expected to discuss isn't actually the customer's problem.

Those skills include curiosity, communication, confidence, empathy, commercial judgment, problem solving and the ability to establish trust quickly.

Better technology doesn't make those abilities obsolete. It can make them more valuable because technology allows us to concentrate human talent where it has the greatest impact.

So What Should We Train Future SDRs to Do?

This distinction matters enormously to us at Salesclass.

We believe SDRs entering today's technology companies need to understand the modern GTM environment. They should be comfortable with CRM systems, prospecting platforms, AI tools, sales engagement systems and the increasingly automated processes around them.

But Salesclass is fundamentally training people for customer interactions and conversations, not the technical wiring behind those conversations.

We want an SDR to understand a company's value proposition and translate it into something relevant to a particular stakeholder. We want them to know how to start a conversation, ask a good question, listen to the answer, recognize a business problem, communicate value, respond to objections and earn the right to continue the relationship.

Those abilities also have value well beyond the first SDR job.

An SDR who becomes exceptional at customer conversations can progress into account executive roles, account management, Customer Success, partnerships, sales leadership and other customer-facing positions. An SDR who becomes fascinated by the machinery behind those conversations may instead develop toward RevOps, sales operations or GTM engineering.

Both are legitimate and increasingly important careers.

They simply aren't the same career.

Build the Machine. Manage the Motion. Master the Conversation.

The rise of GTM engineering should force companies to reconsider what they actually want their SDRs doing all day.

If an SDR is spending hours cleaning data, copying information between systems or manually performing research that can reliably be automated, that may increasingly be a systems problem rather than an SDR responsibility.

Let RevOps create a dependable foundation. Let GTM engineering build and improve the systems that identify opportunities and eliminate repetitive work. Let SDR managers turn what the team learns from the market into better targeting, messaging and coaching.

And let SDRs become exceptionally good at the moment all of that infrastructure was built to create: a conversation with a potential customer.

The modern SDR doesn't need to know nothing about technology. Quite the opposite. They need to be comfortable operating in an increasingly sophisticated technology environment.

But we should be careful about assuming that because the sales organization is becoming more technical, every salesperson needs to become an engineer.

Let GTM engineering build the opportunity. Let management improve the motion. Let the SDR master the conversation. See you on the sales floor!

‍