Part 4: Sales automation does not belong in the IT department.
The first three parts of this series focused on problems, concepts and use cases. This article addresses a more fundamental question: Who in the company is actually responsible for automating sales processes?
In many mid-sized companies, the answer is automatic: IT. Workflow automation platforms are classified as technical tools that require technical expertise, so the topic is delegated. This reflex is understandable, but it is also the main reason why sales automation never really takes off
Why delegating to IT usually fails.
In most companies, the IT department already has its hands full. ERP migrations, security issues, infrastructure, support for other departments. Sales workflows end up somewhere around item twenty-five on the priority list.
Even if IT had the time, it usually lacks the domain knowledge. How exactly does follow-up after a trade show work? Which fields need to be added at which point? When should a lead be routed to which team member? Only sales can answer these questions. IT can at best implement what it is told.
The result is a back-and-forth a back-and-forth where sales and IT are constantly talking past each other. Requirements are misunderstood, iterations drag on and the outcome is something that leaves both sides only partly satisfied. Or there is no outcome at all because the project quietly dies along the way.
What needs to change.
Sales automation has to sit where the expertise is: within sales itself. Sales leaders need to be able to build, test and adapt workflows on their own, ideally without having to raise an IT ticket every time and without hiring an external agency.
For that to work, platforms must be designed for sales leaders, not for developers. This is where the real issue lies. Most workflow platforms on the market are the opposite: technical tools with a high degree of flexibility, but with an operating logic that is almost impenetrable without a developer background.
Four dimensions that make the difference.
What exactly distinguishes a sales-specific platform from a generic workflow platform? In practice, four dimensions are decisive.
1. The language the tool speaks
Generic platforms speak the language of developers. They revolve around webhooks, JSON payloads, trigger endpoints and authentication flows. Anyone who does not understand these concepts is left staring at the interface without a clue.
Sales-specific platforms speak the language of sales. They revolve around leads, contacts, enrichment, duplicate checks, pipeline stages and account owners. The salesperson immediately understands what is going on and can start working without first translating everything into their own terms.
2. The data sources that come built in
In theory, generic platforms can be connected to almost anything. In practice, this often means: connecting to a CRM is possible, but someone has to configure it. Enriching company data is possible, but someone has to integrate and pay for an external data source. Duplicate checks are possible, but someone has to build the logic from scratch.
Sales-specific platforms come with what sales teams constantly need. CRM connectors for the most common systems. Company data enrichment as a built-in component. Duplicate checking as a ready-made function. Email validation as default. This not only lowers the barrier to entry, it also reduces ongoing costs because fewer additional services need to be purchased.
DataAgents goes one step further here. Our own sales products are directly integrated as data sources and triggers. A trade show contact captured with VisitReport starts a workflow, a business card scanned via BusinessCards flows straight into the workflow, enrichments via LeadResearch are available without detours. This depth of integration into an end-to-end sales ecosystem is not available with purely generic platforms.
3. The templates available as a starting point
Generic platforms either provide no templates at all or templates that are so generic they contribute almost nothing to a concrete sales process. Users face a blank interface and have to start from scratch.
Sales-specific platforms provide workflows that address the typical problems of day-to-day sales work. Lead enrichment after a Web form submission, trade show contact processing, duplicate checks during CRM import. These templates are not just a starting aid, they are also a way to learn. Anyone who studies what a well-designed sales workflow looks like learns how to set up further workflows themselves.
4. The ownership that stays within the department
In practice, generic platforms almost always require technical support. Either from the internal IT team, from external consultants or from a specialized agency. Not only does this cost money, it also creates dependencies and slows down every desire for change.
Sales-specific platforms are designed so that ownership can stay within sales. Adjustments are made in-house. New workflows arise directly from operational day-to-day work. When requirements change, the workflow is adjusted in the afternoon and runs differently the next morning. This speed is not only more efficient, it also changes how sales teams think about and manage their own processes.
What this means in practice.
Anyone selecting a workflow platform for sales should not just ask what is technically possible. Almost every platform on the market can do almost everything. The crucial question is: Who will actually be sitting in front of this interface?
If the answer is that the IT department will take care of it, then a generic platform might be suitable. With all the consequences already mentioned: long iteration cycles, high Dependencies, slow adjustments.
If the answer is that sales should take ownership of its own processes, then you need a platform built precisely for that purpose. One that does not first have to be learned, but is immediately understood. One that comes with what sales teams need. One that offers ready-made templates as a springboard while still allowing the depth required for individual customization.
That is the kind of platform with which sales Automation truly gains traction. Not as an IT project that might get off the ground at some point, but as a tool that delivers value from day one.
In the fifth and final part of this series, we show what this looks like in practice. We follow a typical mid-sized company as it builds a concrete workflow and describe, step by step, what happens, who is involved and what outcome is achieved.
Next part: What modern sales automation looks like in practice.