CASE STUDY · CO-DEVELOPMENT
Regaining process control over grown customer systems
An organically grown system landscape was developed towards a customer-facing platform with customer profiles and first cross-selling capabilities. In co-development, a verifiable system state emerged — and an internal team able to solve similar process problems more independently and more structured.
The situation
A travel company operated several customer-facing systems: product catalogues, booking flows and service touchpoints. The systems worked in day-to-day operations, but did not represent an end-to-end customer process.
Customers could book products, but could not build a reliable profile. Information about behaviour, preferences and recurring interactions therefore stayed hard to use.
This left the company missing an important part of its process control: recognition, profile building, follow-up offers and cross-selling were only partly possible in the grown system landscape.
The real obstacle lay less in a single technical weakness than in the grown structure. The system touched several areas without any single department being clearly responsible.
This created a typical blockage: the need was known, but the topic was too distributed, too coordination-intensive and too hard to grasp to be started pragmatically.
From a grown system to an editable platform state
Kernity did not start with a general AI training, but with a concrete process problem from the company. Together with the internal team, the large legacy complex was translated into a workable implementation slice.
The implementation slice was defined along the customer process: which information has to be captured? Where does a customer profile emerge? How can booking and service contacts be connected with follow-up offers?
Before building, core requirements, system boundaries and technical guardrails were clarified. This created a frame in which two people could work in a focused way, without having to move the entire organisation at the same time.
The team worked with an AI-assisted development environment and a specification-driven approach. Kernity supported the methodical setup, the architecture decisions and the practical application of good development and governance principles in everyday work.
- Co-development on the real customer process
- a clear implementation slice instead of an open-ended mega-project
- customer-profile and cross-selling logic as a verifiable platform state
- business requirements expressed as a technical specification
- technical guardrails for review, further development and later hardening
The result was a working system state that represented central requirements and could serve as a basis for review, further development and a possible move to production.
Business value
The most important benefit was regained process control. A previously hard-to-grasp customer system was turned into a concrete, verifiable platform state.
This gave the company a basis to review customer profiles, follow-up offers and cross-selling capabilities on the business side, and to develop them further technically.
At the same time, the knowledge stayed in the company. The internal team had not watched, but built it themselves, and could reuse the resulting way of working for further iterations.
- a verifiable platform state for customer-profile and cross-selling capabilities
- better control over customer-facing processes
- know-how built up in the internal team instead of full outsourcing
- a clearer view of which steps are needed for hardening and production
- less dependence on long upfront clarifications and large coordination loops
Why this matters
Grown systems are not automatically a problem. They become critical when they start to limit business logic: customer relationships stay transactional, follow-up offers depend on manual workarounds, and new digital functions fail on unclear responsibilities.
In such situations, simply introducing yet another tool is rarely enough. First the process has to become tangible again: which data is created where? Which decisions should be supported? Which system logic is needed so the company can actively steer the customer process?
Co-development creates a robust way of working for this. The organisation does not just buy a result, but builds its own software and AI capabilities on a real use case.
Transferable relevance
The transferable relevance does not lie only in this one customer system. It lies in a structural shift: with AI tools, business teams can now build first software solutions much faster, because technical implementation moves closer to the people who understand the business problem best.
This creates new speed, but also new risks. A working prototype is not yet a secure, maintainable or production-ready system. Especially when real customer data, operational processes or business-critical decisions are involved, it needs architecture, review, documentation, security assessment and a controlled path towards operation.
Kernity's role sits exactly at this interface: teams are enabled to build on real use cases themselves, without outsourcing or skipping professional engineering discipline. Early solutions emerge quickly — and, at the same time, a clear basis to decide what should be developed further, hardened or deliberately limited.
- business units that want to develop their own internal tools or process solutions with AI support
- product and engineering teams that want to use AI-assisted development productively, without losing quality and control
- organisations that need fast prototypes, but have to consider architecture, security and compliance early
- grown customer, booking, offer or service processes that should be modernised step by step by internal teams
- use cases where it has to be decided whether an initial system state is hardened, put into production or deliberately discarded
The pattern is clear: AI democratises the entry into software development. Kernity ensures that this new speed can turn into robust systems, clear decisions and sustainable internal capabilities.
KEY TAKEAWAY
AI makes getting started with software development faster and more accessible; Kernity provides the guardrails so that early solutions become secure, maintainable systems that can be developed further responsibly.
NEXT STEP
A similar initiative?
In the free initial call we clarify whether Kernity is the right partner for your situation – and which entry point would make sense. The goal is not to sell a solution on the spot.
30 minutes · video or on-site · no preparation needed