Skip to main content

Marketing owns the Customer! Does it?


A Customer
Customer
The customer, the elusive entity that every business is about – or at least should be about.
The customer gets targeted, marketed to, sold to, serviced, analysed, shall have a positive customer experience, and sometimes even is made happy.
The ‘customer’ as an entity is owned by the marketing department, err, the service department, oops, sales … or is it IT? After all IT is likely to run the CRM system. If it is not a cloud system, that is.
In reality it is different in every company and probably rightfully so.
On the other hand every department has their own requirements and the ‘owner’ of an entity is likely the one who decides upon the relative priorities of these requirements. And the fulfillment of requirements regularly decides upon the effectiveness and efficiency a business unit can operate with.
Now the marketing department is heavily invested in collecting all data that a customer leaves behind in order to understand behaviours and be able to entice known and unknown customers into buying (in the case of a B2C business) or solidifying the lead to an extent that it can be handed over to the sales department (in case of a B2B business). They are interested in lots of attributes, segmentation, slicing and dicing towards various dimensions. Born were Data Management Platforms, and Customer Data Platforms, and overall a very thriving industry of Marketing Technology.
The sales department now is interested in opportunity management, CPQ (configure, price, quote), relationship with the buyers and their potential influencers, closing the deal as efficiently as possible. Born is a world of sales support software.
The service departments are mainly dealing with customers post sales, or when there are questions/issues coming up in the course of the buying journey, trying to resolve them as efficient as possible. This helped the creation of more classes of enterprise software.
These times it is easy to purchase and deploy them, with the help of the cloud and decentralized budgets.
All these types of software regularly have their own data store and, of course, different data models. And, as they are often implemented locally, they are also not integrated, with all the negative consequences this has.
As the ‘customer’ is one important piece of the enterprise data model an important consequence is that suddenly there is different customer information at different places. There is no single ‘truth’ anymore, not even different views on the same data, just different data with little chance of consolidation that is left.
But, in the context of their own jobs (to be done) the individual departments get closer to their optimal process.
Just that this optimal process is not likely to be close to a global optimum, which would be defined around the customer’s job to be done.

The Solution?

Given all this: Who should own the customer and the customer data? Someone needs to.
I would argue that it should not be a single business unit. They have their local objectives (which are not always directly inferred from global objectives) and tend to prioritise their own goals over other business units’ goals; and they surely do not have the skills necessary for proper data modeling.
I would also argue that it is neither a group. This normally leads to no one feeling accountable and thus will not yield results.
In conclusion this leaves a department that delivers a service to the other business units. As we are talking technology here the logical candidate is IT.
The precondition for this to work is that the CIO sees him-/herself as an enabler to the business, and conversely also is expected to be in this role.
Dilbert and Mordac; Source: Scott Adams
Dilbert and Mordac; Source: Scott Adams
A CIO these digital ages needs to be on the forefront of the business transformation that any digital transformation is.  And the enterprise data model as part of an enterprise architecture is part of this.
Am I dogmatic about this? No, as long as the enterprise architecture is part of a cross-business strategic unit – and has a cross-business governance body to ensure proper direction.
And it needs to stay nimble. This I am dogmatic about, because, in an adaptation of an SAP slogan: IT and business must run at the speed of the customer.
A tall order.

Comments

Last Year's Top 5 Popular Posts

You are only as good as your customer remembers

As you know, I am very interested in how organizations are using business applications, which problems they do address, and how they review their success. In a next instance of these customer interviews, I had the opportunity to talk with Melissa Gordon , Executive Vice President, Enterprise Solutions at Tidal Basin about their journey with Zoho. You can watch the full interview on YouTube. Tidal Basin is a government contractor that provides various services throughout the government space, including disaster response, technology and financial services, and contact centers. Tidal Basin started with Zoho CRM and was searching for a project management tool in 2019. This was prompted by mainly two drivers. First, employees were asking for tools to help them running their projects. Second, with a focus on organizational growth and bigger projects that involved more people, Tidal Basin wanted to reduce its risk exposure and increase the efficiency of project delivery. This way, the compa...

SAP Draws a Perimeter around Agentic AI and What That Means for the Rest of US

The most consequential enterprise AI governance document published this year arrived in late April with surprisingly little fanfare. SAP's updated API Policy, version 4/2026 , is a short document in plain English. The clause that is most interesting is Section 2.2.2. It restricts how autonomous and generative AI systems are permitted to interact with SAP APIs. Read literally, it has the potential to change the architecture of agentic AI projects across every SAP customer landscape. Read carefully, it is also more interesting than the lock-in headlines suggest. The policy targets a specific category of AI behavior, not AI as such. It connects to commercial mechanics that go well beyond API stability. And the literal text, in its current form, will probably not survive the next two policy revisions intact. There is a lot to unpack. I will walk through what the policy actually says, how the SAP-watching community is reading it, what the rest of the major enterprise vendors are doin...

The Illusion of Value: Why Salesforce’s Agentic Work Unit is the New "Bad Query" of the AI Era

The News On February. 25, 2026, Salesforce announced a pricing and metrics update . During the company’s Q4 FY2026 earnings call, CEO Marc Benio ff, together with CMO Patrick Stokes , unveiled the Agentic Work Unit (AWU). Positioned as a metric to quantify the labor performed by autonomous digital systems, Salesforce defines an AWU as one discrete task accomplished by an AI agent. According to Salesforce, this discrete task represents the exact moment " raw intelligence is converted into real work ". It is not a fixed unit but measured as a processed prompt, a completed reasoning chain, or an invoked tool. Salesforce explicitly designed the AWU to move the industry conversation away from the raw consumption of Large Language Model (LLM) tokens. As Benioff noted, tokens only measure "how much an AI talks," whereas the AWU is intended to measure actual business execution. The scale of this rollout is massive. Salesforce reported that its platform has already processe...

Data Wars: SAP Vs. Salesforce In The AI-Driven Enterprise Future

The past weeks certainly brought a lot of news, with SAP Sapphire and Salesforce's surely strategically timed announcement of acquiring Informatica , ranging at the top. I have covered both in recent articles. The enterprise software landscape is crackling with energy, and Artificial Intelligence (AI) is certainly the star of the show. It isn't anymore about AI as a mere feature; it's about AI as the strategic core of enterprise software. Two recent announcements underscored this shift: SAP's ambitious AI-centric vision that was unveiled at its Sapphire 2025 conference, and, arriving hot on its heels, Salesforce's agreement to acquire data management titan Informatica for $8 billion. Both signal an intensified battle for AI supremacy, where trusted, enterprise-wide data is the undisputed new monarch. Of course, SAP and Salesforce are not the only ones duking this one out. SAP's Sapphire Vision: An AI-Powered, Integrated Enterprise At its Sapphire 2025 event in ...

CPQ, Meet Price Optimization: Your Revenue Lifecycle Just Got Serious

The news On October 1, 2025, Conga announced its intent to acquire the B2B business of PROS , following PRO’s acquisition by Thomas Bravo . At the same time, ThomaBravo and PROS announced that PRO’s travel business segment will be run as a standalone business . The bigger picture Revenue operations, revenue management and revenue lifecycle management have become a thing in the past years, as evidenced by the number of specialized companies that solve parts of the overall problem of optimizing revenue. It also got abused to some extent (e.g., surge pricing models) when the users of the corresponding capabilities consider optimizing being the same as maximizing. Reality check: It is not. While optimizing involves a bit of identifying how much a customer is willing to pay, it also involves the thought of repeat business, or in other words customer loyalty, even without a formal loyalty program. And that involves the customer experience, part of which the speed of creating a quote with mat...