Peleven AG
of
Marc Grether
Member of the Executive Board & Platform Lead Business Development

From folder monster to AI knowledge hub: How Peleven is rethinking its quality management with Ariadne
About Peleven
Peleven delivers complex investment projects in the process and life science industries, from initial inquiry to operational readiness. To achieve this, the Swiss engineering and consulting firm combines technical expertise with clear project management and a focus on long-term operations. Headquartered in Basel with a total of seven locations across Switzerland and Germany, Peleven supports its clients in successfully implementing their projects.
The challenge: Letting knowledge grow with the company
When Peleven started in 2020 with a handful of employees, we were a small, tight-knit team. Everyone knew who to ask for help, and most things could be resolved directly and easily.
As the company grew, our requirements changed. Templates, guidelines, and instructions existed, but they were scattered across different locations on our file server and became increasingly difficult to keep up to date centrally. At the same time, the number of interfaces in our decentralized organization increased. It became increasingly challenging, especially for new employees, to find information quickly and understand how things were connected.
The typical effects of a growing organization became increasingly apparent in our daily work: content was sometimes saved in duplicate, templates were not updated everywhere at the same time, or knowledge remained tied to individual people.
For us, this was the right time to further develop our knowledge and process management. The existing knowledge needed to be better structured, more transparently accessible, and serve as a foundation for efficient collaboration and Peleven's continued growth.
The turnaround: From skeptic to pioneer
When we were faced with the decision to introduce a quality management system, I was initially the biggest skeptic myself. A year earlier, I had even stopped the project. At the time, my idea of a QMS was heavily influenced by classic audit scenarios: lots of documentation, dusty folders, and significant administrative effort—primarily with the goal of obtaining a certificate.
The purpose of quality management itself was never in question for us. Rather, it was unclear to me what added value a formal QMS would create for Peleven and our daily work. At the same time, we knew that ISO 9001 certification is an important prerequisite for certain clients and projects to even be considered as a service provider.
During our second attempt, we therefore focused on the tangible benefits for our company. The more intensively we looked into the topic, the clearer it became that a modern QMS can do much more than just prepare for an audit: it can make our processes transparent, make knowledge accessible, and clarify responsibilities.
We wanted to build a system that reflects how we actually work and supports Peleven in everyday life. Our existing, functional processes formed the foundation for this. The ISO requirements helped us to structure them consistently, identify gaps, and supplement content in a meaningful way. In this way, a formal requirement evolved into a management system that creates real added value for Peleven and our clients.
Documenting processes with the right level of detail
The next question was therefore very practical: How do you describe the working methods of an engineering company whose projects are so diverse?
No two projects at Peleven are the same. Scope, requirements, client organization, and technical tasks differ from case to case. Our goal, therefore, could not be to dictate every possible variation in detail.
We decided on a sensible level of abstraction: we describe common processes, responsibilities, and guardrails as concretely as necessary, while leaving room where our projects need it. The system is supplemented whenever new requirements or useful best practices emerge from our daily work.
This keeps our QMS close to reality: it creates orientation and accountability without restricting the necessary flexibility in our project business. That is exactly where the practical value of a good management system lies for us.
Implementation: Building a robust QMS in just a few months
When we received the green light from management in March 2026, we had already established a solid foundation. We had defined which processes belonged to each department, identified the respective process owners, and clarified the associated tasks and responsibilities. In some cases, initial process descriptions were already in place.
This groundwork paid off: we were able to build the majority of our new quality management system in just four months. We also leveraged generative AI to structure existing knowledge more quickly and create initial drafts. The technical review, adjustment, and approval of the content always remained the responsibility of the designated process owners.
Our experience in project business also helped us. Understanding requirements, structuring content, clarifying responsibilities, and implementing solutions step-by-step is part of our daily routine. We applied this exact approach to the introduction of our own QMS.
Involving employees early on
We consciously approached the introduction of the Ariadne system as a change process. In addition to management, we specifically involved employees who work with these processes every day and bring practical knowledge to the table.
Even during the development phase, we provided regular project updates and created ongoing touchpoints with the new system, facilitated by Microsoft Teams updates, personal presentations in all seven hubs, training sessions, and QMS ambassadors who served as local points of contact for questions and feedback.
The naming process was also part of this journey. All employees were invited to submit suggestions and vote on the system's internal name. More than a third of the workforce participated with over 140 ideas. That is how a software solution became our Qeleven – a name from within the organization for a system intended to be anchored in the employees' everyday lives.
Our goal remained the same throughout: Qeleven should not just be understood, but adopted and used step by step. That is why we combined factual information with concrete application examples, personal interaction, and a communication style that fits Peleven – pragmatic, positive, interactive, and with a pinch of humor.
DORIS: Our AI for corporate knowledge
At Peleven, we developed DORIS, an AI-powered gateway to our corporate knowledge. DORIS stands for "Document Research and Information System" and is designed to help our engineers find information in extensive project archives more quickly.
Today, DORIS is integrated with Qeleven, among other things, and accesses our entire structured corporate knowledge base. Questions like "Do I get a day of special leave if my brother-in-law gets married?" or "My daughter is sick. How long can I stay home?" used to be directed to our business support team. Today, DORIS provides these answers, as well as information on regulations or templates.
For us, the decisive advantage lies in traceability. DORIS synthesizes its answers based on the stored content while simultaneously displaying the sources and relevant text passages used. This allows employees to see exactly what an answer is based on and verify it in the source document if necessary. If DORIS does not find sufficient information, the system indicates this accordingly.
Identifying knowledge gaps with the help of AI
DORIS does more than just make existing knowledge accessible faster. Its usage also shows us where our knowledge base still has gaps or where content could be better structured.
To do this, we anonymously analyze which questions are asked and which topics cannot be answered sufficiently. This allows us to identify recurring information needs and further develop Qeleven in a targeted manner.
One example of this was the marketing department: recurring search queries showed us that certain documents were not yet sufficiently available centrally. As a result, we built a dedicated marketing knowledge area in Qeleven, where presentation templates and other marketing materials are now centrally accessible.
Our conclusion: A management system must serve the people
Looking back at the introduction of Ariadne today, the key for us was to consistently focus on the concrete benefits for Peleven and our employees. I would recommend this to other companies as well. Ask yourselves first: "What’s in it for me?" and what should a management system improve in our daily work for employees, for the organization, and ultimately for our customers? This creates a reliable compass for implementation and further development.
For us, ISO 9001 certification was important because it is a procurement criterion for certain projects. However, we see the real value of Qeleven in the fact that knowledge is now more accessible, responsibilities are more transparent, and our processes can be described and further developed on a common foundation.
This has confirmed our belief: A QMS is effective when it authentically reflects the organization as it is lived and evolves alongside it. When the people who work with it are involved and recognize its tangible benefits, it becomes more than just a certified management system. It becomes a robust knowledge base that is actively used in daily work while simultaneously opening up new possibilities—for us, for example, with DORIS as an AI-powered gateway to our corporate knowledge.