Enterprise AI Transformation: What My Conversation with Neptune Software CRO Bart Meursing Taught Me

When I sat down with Bart Meursing, Chief Revenue Officer at Neptune Software, for a recent Leaders Lounge conversation, I expected us to talk about AI, enterprise software and the changing role of the CRO. We did. But the idea I kept returning to afterwards was much simpler: most enterprises do not have an AI ambition problem. They have an AI execution problem.

Bart knows this challenge from both sides. He has helped scale enterprise software businesses beyond $100 million in revenue three times and now leads Neptune Software's global Revenue Office. Neptune works with organisations running mission-critical processes in complex SAP environments, where a promising proof of concept means little unless it can operate securely, reliably and at scale.

Our discussion helped me connect two questions that boards, investors and leadership teams often treat separately. How do we turn enterprise AI into measurable business value? And what kind of Chief Revenue Officer and executive team can lead that transformation? In my view, the answer to one increasingly depends on the other.

The enterprise AI execution gap is the distance between testing an AI use case and embedding it into a secure, governed workflow that produces a measurable business outcome. Many companies can build a compelling demo. Far fewer can connect that demo to legacy systems, trusted data, user permissions and day-to-day decisions.

This distinction matters in SAP enterprises because the processes involved are often critical to the business. Warehouse operations, asset maintenance, procurement, field service and supply chain decisions cannot depend on an isolated chatbot with no understanding of roles, authorisations or audit requirements.

Bart's perspective reinforced something I see in executive search: transformation stalls when ownership is fragmented. Technology leaders may understand the architecture. Commercial leaders may understand the customer outcome. The board may understand the strategic urgency. But unless someone connects these views and creates accountability for execution, the pilot remains a pilot.

Bart has built predictable growth engines at significant scale, so I was particularly interested in what he believes AI changes about the CRO playbook. His answer was not that the fundamentals disappear. Recurring revenue still comes from recurring customer impact. Strong teams still define the customer's problem, quantify value, build trusted relationships and qualify opportunities with discipline.

What has changed is the buyer journey. Enterprise buyers now conduct more research before speaking to a salesperson. They compare claims, consult peers and increasingly use AI tools to build shortlists or interpret complex offers. By the time a human conversation begins, it may be shorter but much more consequential.

That changes the job of the CRO. Revenue leaders must make their company's value clear to people and understandable to machines. They need precise positioning, useful expertise and evidence that can be discovered by search engines and generative AI systems. This is not only a marketing task. It is a revenue strategy for a market in which an AI agent may influence the shortlist before the buying team contacts a vendor.

Neptune Software describes itself as an AI execution platform built for SAP enterprises. Its Naia 3.0 release shows why agentic development can change the conversation between commercial teams, technology leaders and business users.

Instead of beginning with developer capacity or a long application backlog, leaders can begin with a business question: what should we build first and what outcome should it improve? Agentic development can translate user stories into applications that work within the customer's own environment, data structure and governance model.

I do not see this as removing the need for technical talent. I see it as raising the value of judgement. Developers and technology leaders spend less time on repetitive work and more time orchestrating agents, reviewing architecture, protecting the clean core and deciding which problems are worth solving. Faster development creates value only when it is paired with stronger prioritisation and governance.

One part of my conversation with Bart felt especially relevant to my work at Key Search. If AI gives every seller access to similar research, similar prompts and similar polished language, then human qualities become more valuable, not less.

I would look for revenue leaders who are authentic, curious and bold. I would also test for judgement, accountability, coachability, resilience and genuine customer obsession. An AI literate CRO should know where automation creates leverage but also recognise where a customer or colleague needs a thoughtful human response.

I would ask candidates to teach me something important about their last customer's industry in two minutes. I would ask them to explain a lost deal, what they misunderstood and what they changed afterwards. These questions reveal whether a leader can synthesise complexity, stay curious under pressure and turn experience into better decisions.

The best AI era leaders will not simply add tools to the old revenue process. They will redesign how the team works and protect the trust that holds a high-performance culture together.

Traditional enterprise buyers are not persuaded by AI theatre. They need confidence that a solution can improve a specific operational measure without introducing unacceptable risk.

That measure might be inventory accuracy, equipment downtime, first-time fix rates, compliance or the speed of a supply chain process. The strongest enterprise AI case therefore begins with the operational problem and its baseline, not with the novelty of the model.

Neptune's SAP native approach is relevant because it places applications and AI agents inside existing business workflows while respecting enterprise governance. For a buyer responsible for warehouse operations, inspections, field service, procurement or supplier collaboration, that practical context matters more than an impressive standalone demonstration.

Bart's message to me was clear: the proof of concept should not need a separate story about future value. It should be designed around the business case from the beginning.

My practical takeaway for revenue teams is to automate the motion but not the meaning. AI can reduce the mechanical work involved in account research, meeting preparation, first drafts, pipeline hygiene and forecast consolidation. That gives people more time for the work that requires judgement and trust.

Discovery, coaching, difficult deal reviews and meaningful customer relationships still need human attention. So does the work of building shared accountability across sales, marketing, solution consulting, customer success, partnerships and revenue operations.

AI can make a global Revenue Office faster. It cannot decide what kind of culture that organisation should have. Leaders must model the collaboration, creativity and trust they want the technology to amplify.

The most memorable advice from our conversation was also the most contrarian: stop trying to impress people with AI and start with something boring.

Another chatbot or dashboard may create excitement but it does not necessarily change the P&L. A less glamorous workflow such as invoice matching, order exceptions or maintenance scheduling may produce much clearer value.

I would advise an executive team to choose three to five use cases tied to measurable revenue growth, cost reduction or risk mitigation. Put governance in place before scaling. Embed AI into the workflow where the decision already happens. Measure the outcome against a real baseline and let the business result make the case.

For enterprise AI transformation, boring can be a sign of maturity. It means the company has moved beyond experimentation and started solving the operational problems that matter.

After speaking with Bart, I believe boards and investors should ask five direct questions about enterprise AI transformation:

Which business workflow are we improving?
A use case needs an operational owner and a measurable baseline.

Can the solution move from a demo into our real environment?
Integration, permissions, governance and auditability must be part of the design.

Who is accountable for adoption and value?
Technical delivery and commercial outcomes cannot remain in separate conversations.

Does our leadership team understand AI well enough to redesign work?
AI literacy at the top is now a transformation capability.

Are we protecting the human qualities that create trust?
Authenticity, curiosity, judgement and courage become more important as automated content becomes common.

The enterprise AI winners will not necessarily be the companies with the most pilots or the most sophisticated model. I believe they will be the companies with leaders who can connect technology, customer value and organisational change. Leadership architecture is not something to address after the transformation. It is one of the conditions that makes transformation possible.

What is enterprise AI transformation?
Enterprise AI transformation is the process of embedding artificial intelligence into governed business workflows so that it improves measurable outcomes across operations, customers or revenue.

Why do enterprise AI pilots fail to scale?
Pilots often fail because they are disconnected from legacy systems, trusted data, permissions, governance, user adoption or a clearly owned business outcome.

How is AI changing the Chief Revenue Officer role?
AI is changing buyer research, sales productivity and revenue operations. Modern CROs need to make value discoverable to human buyers and AI agents while leading teams that combine automation with judgement and trust.

What should companies look for when hiring an AI era CRO?
Companies should look for AI literacy, enterprise selling experience, commercial judgement, curiosity, authenticity, accountability, resilience and the ability to redesign how a revenue organisation works.

How should an SAP enterprise start with agentic AI?
Start with a specific workflow and measurable baseline. Choose use cases connected to revenue, cost or risk then design integration, governance and user permissions before scaling.