Most enterprise procurement software was built independently of ERP, despite the fact that those systems are backbones of any organisation. It was only once those products found customers that large SAP ERP users began asking for the two to be connected – and by then the connection was an afterthought rather than a design principle. Retrofitting an external system deep into an existing ERP architecture is never seamless, and two decades later the industry is still paying for that sequence in middleware, replicated data and integration projects that never quite end.
BeNeering was built the other way round.
“Our philosophy from day one was not to rebuild what already exists and works well,” says founder and CEO Christoph Moll. “I had worked at SAP. I knew how robust that system was for materials management, logistics, procurement, finance and controlling. Rather than reinventing that foundation, we built to use it – deeply and natively.”
A procurement execution layer, not a parallel system
BeNeering provides a unified procurement execution layer that extends SAP ERP with requester self-service, real-time compliance and AI-driven intake-to-order, delivered as software as a service. The platform is used by more than 400,000 users across 86 countries and 12 industries.
The architectural consequence is straightforward. BeNeering communicates with SAP in real time, working directly with live master data and transactional data – purchase requisitions, purchase orders, goods receipts, invoices. Those data and documents stay where they belong, in SAP. There is no replication layer to reconcile and no integration to maintain.
“That architectural choice is our real innovation, and it is what sets us apart from other procurement solution providers,” Moll says. “It also means we can grow faster, because we are not reinventing the wheel. And we avoid the integration headaches that affect bolt-on solutions, because BeNeering was built for SAP ERP from its first line of code.”
The competitive position that follows is an unusual one. “The market has established enterprise platforms on one side and ambitious startups trying to carve out a foothold on the other,” Moll says. “What distinguishes BeNeering is that it extends the ERP platform those suites typically sit beside, rather than setting out to replace it”.
What it produces in practice
The architecture is a means rather than an end, and the results show up in operational numbers rather than in feature lists. Among BeNeering’s customers, a chemicals company runs at a 90 percent no-touch purchase order rate. An automotive filtration manufacturer has brought maverick buying down to 1.5 percent of spend. A telecommunications provider operates a single entry point for all indirect requests, across a requester population that has no reason to know SAP exists.
That last point matters more than it first appears. The users of a procurement platform are rarely procurement professionals – they are engineers, plant managers, marketers and administrators buying something they need in order to do their actual job. A system that requires them to understand purchasing logic will be worked around.
BeNeering’s customers include companies from the chemicals, telecommunications, industrial filtration, defense and biotechnology sectors. “For a company of our size to earn the trust of corporations like these says something about what a smaller, focused organisation can achieve,” Moll says. “It is a source of genuine pride throughout the company.”
Where AI belongs, and where it does not
BeNeering is currently evolving into an AI-based business suite, with AI, security, intelligent agents and orchestration as central pillars. Moll is unusually precise, however, about what that does and does not mean.
“AI interprets and suggests. It does not execute,” he says. “Execution stays deterministic, against SAP data and SAP rules. That is a narrower claim than much of the market is currently making, and we think that is the point. An agent that can place an order is an agent that can place the wrong one.”
Applied to procurement, the division is a practical one. Understanding what a requester actually wants – from a free-text description, an email, a photograph of a broken part – is genuinely hard, and it is work that AI does well. Deciding whether the resulting order is compliant, correctly coded and within budget is not a judgement call. It is a rule, and rules should be applied by systems that cannot be creative about them.
Innovation as a habit – leading to a culture
At BeNeering, innovation is not directed from the top. Teams invest in their own development and attend industry conferences, which Moll describes as creating an organic drive within each department to work at the current state of the art.
“That mindset extends to how we treat our own software,” he says. The company continuously refactors and modernises its platform, and a substantial part of what has been built over the past decade is currently being restructured on new architectural models.
Many of the architects behind the technology have been with the company for twelve to fifteen years. Staff turnover sits well below the industry average, and the core product team has remained stable throughout. Moll regards that continuity as the reason the innovation engine keeps running.
Matching people to work
The persistent organisational challenge, Moll says, has been ensuring the right people are in the right roles. New joiners are told explicitly that they are not locked into the position they were hired for, and that if something else proves a better fit, the company will make it possible.
The reasoning is that people achieve more by building on their strengths than by correcting their weaknesses. “It means constantly and thoughtfully matching people to work where their strengths can genuinely shine, while keeping the broader team united,” he says. “It is a challenge I am proud to say we have met well.”
The structure is deliberately flat. Moll sees himself as part of the team rather than above it, and says colleagues tend to treat him accordingly – something he takes as a compliment rather than a lapse. “That commitment to working alongside people, rather than above them, is at the heart of how we operate.”
From electrical engineering to enterprise software
Moll wrote his first programs at twelve. Mathematics and physics were his subjects at school, and he went on to a Master’s in electrical engineering in Dortmund followed by a Master of Science in Information Engineering in London. Business featured nowhere in the plan.
“Mathematics and physics captivated me from my school days onward, and that analytical foundation has never left me,” he says.
He moved into management consulting after his studies – not from a sudden interest in commerce, but because he wanted to apply analytical method to problems outside his own technical field. “For me it was about the discipline of analytical thinking, the ability to break down and solve complex problems, regardless of the domain.”
That path led to SAP, where he spent six years from 2001 to 2007, managing customers, working with business stakeholders and programming inside the system. Supporting clients end to end – from requirements discussion through to technical implementation – made him an all-rounder, and the combination of technical depth with business fluency became the foundation BeNeering was built on.
“The product is a direct expression of that combination,” Moll says. “Technology and business come together at its core.” The company’s name says it plainly: “Business Engineering.”
Growing into the role
BeNeering began in 2007 as a one-person venture, with Moll working as a freelancer under a small GmbH. It now employs more than 80 SAP architects and procurement specialists across Germany and Poland, and remains privately owned with no external financing.
“What changed everything was meeting the right people at the right time, starting with a project in Switzerland working with Philip Morris,” he says. Those relationships led to the product, the cloud platform, the founding of BeNeering Poland and the growth of the German business. From there, growth compounded.
The CEO role was not something he sought. “It was the natural consequence of building something that outgrew its founder,” he says. “Even now, being a managing director is not where my heart lies first.” At his core, he remains a technologist.
His priorities as CEO reduce to three: keeping the team united and motivated, attracting and developing the right people, and advancing the product. “A strong product is non-negotiable, because without one we do not have the asset that ultimately serves our customers.”
Leadership formed by circumstance
Moll has never thought of himself as a leader in the conventional sense. “What I am today is the product of the path I have walked, one that began with technology and a technical education.”
The roots go back further than any job title. As a teenager he led a youth group, organised and supervised trips, and served as an altar boy – responsibilities that taught accountability early. He also performed music on stage, which he credits with the confidence to stand in front of people and grow through the discomfort of doing it. “I think that is where the roots of the leadership I bring to BeNeering today really began.”
He is candid that work and personal life blend more than he would like. “Finding the right balance is an ongoing effort. It is not something I have perfected.” What gives him confidence is watching the management team grow in capability and responsibility, allowing him to hand work over rather than remain involved in everything.
The road ahead
“A company that stops evolving in IT has no future,” Moll says. BeNeering’s roadmap extends the platform further into the procurement lifecycle, with strategic sourcing and supplier lifecycle management following the current AI and architecture work.
Customers shape that roadmap directly. “Our customers’ real-world challenges and needs are what we translate directly into our software and our roadmap,” he says – an arrangement the company treats as co-innovation rather than requirements gathering.
Asked what he wants to prove, Moll returns to scale. He believes an organisation of BeNeering’s size can match and in certain respects outperform far larger software houses, on agility and on the quality of the team. Independence is part of that. “We are not beholden to investors pulling us in directions that serve interests other than our customers’.”
Advice to those building something
Moll’s counsel to aspiring leaders is to lead by example. “I cannot reasonably expect more from my team than I am willing to give myself. In so many respects, effective leadership means working alongside your people at eye level and inspiring them toward a shared goal.”
He adds a caution: management should not become self-serving. Leadership, in his view, carries a broader, almost social responsibility, and is fundamentally about a team achieving something together.
“When a leader sees themselves as part of the team rather than above it, that is when you unlock better results and genuine satisfaction, for everyone involved.”
