Klaudia Bednarczyk
Communications Expert, Raiffeisen Tech Poland
We have just wrapped up two days of intensive workshops in the form of an AI Hackathon, organized by Raiffeisen Tech Poland and the HO-based Group Risk Data & Regulatory Reporting team. The event brought together artificial intelligence, innovation, and collaboration across international teams, with the goal of building working AI applications that could meaningfully support the RBI Group in achieving its risk data objectives and making better use of data in a more modern, scalable way.
What truly defined the hackathon was not the element of competition, but its hands-on, workshop-driven nature. Participants went through the full lifecycle of building an AI product — from ideation, through design, all the way to a working demo — while strengthening collaboration, knowledge sharing, and a practical approach to fast-paced delivery.
Eighteen participants from Raiffeisen Tech Poland and the Vienna-based Group Risk Data & Regulatory Reporting team, split into six three-person teams, worked on real-world IT solutions. Along the way, they developed their AI capabilities and applied a modern, product-driven approach to building technology. The event encouraged collaboration and sharing knowledge and experience.
The Hackathon was the perfect opportunity not only to enable our engineers to engage with the rapidly evolving AI landscape and current industry trends, but also to provide a hands-on environment where they could experiment and apply these technologies in real use cases. Equally important was the collaboration aspect — bringing together teams from different locations and strengthening the way we work together as one organization. This combination of practical AI experience and cross-team collaboration is key to building the capabilities we need for the future
The hackathon was designed around two clear objectives — building AI capability across teams and delivering real, usable products.
Equip teams with hands-on experience in spec-driven AI development — making AI builds reproducible, scalable, and transferable across projects.
Go beyond prototypes — deliver standalone, localhost-ready IT products with mocked integrations that can be replaced by real connections later.
The hackathon kicked off with check-ins and team formation, but the real excitement began with the random assignment of both the business problem and the technological approach. Teams worked either with GitHub Spec-Kit or BMAD, taking on an end-to-end challenge — from concept, through technical design, all the way to a working demo.
Each solution had to meet functional requirements, maintain high code quality, and align with RBI’s technology standards, ensuring that ideas were not only innovative, but also production-minded from the very beginning.
The challenge was designed to reflect real-world complexity — teams had to quickly understand the problem space, align on the approach, and turn requirements into working, end-to-end solutions within a very limited time
The first use case focused on Data Quality and aimed to simplify the work of Data Stewards through a simple and more intuitive interface for managing Data Quality Indicators and their lifecycle, as well as the automation of key processes.
The second use case covered AI-powered license management — a platform designed to support contract analysis and license record management. The solution was intended to automatically extract key information from contracts via AI and enable users to ask questions against the beforehand extracted contracts, in natural language , supporting compliance and self-service capabilities.
600+ Data Quality Indicators live as YAML files in GitHub — hard to navigate, slow to validate, impossible for non-technical users to manage. The challenge: build a graphical interface that gives Data Stewards full control.
Vendor contracts are scattered, unstandardized and full of hidden obligations. The challenge: build a platform that uses AI to extract license data from contracts and lets users query it in natural language.
Teams operated within RBI’s real technology landscape — no sandbox shortcuts, real enterprise constraints.
Each team was randomly assigned either GitHub SpecKit or BMAD as their AI-driven development methodology.
All AI calls routed through RBI’s enterprise LLM Gateway — the same governed, secure infrastructure used in production.
UI built using the RBI Group Design System and Freya component library for consistent, accessible interfaces.
Docker-based packaging and deployment — solutions had to be production-ready and portable from day one.
Access to Atlassian, Playwright, and other MCP connectors — teams could tap into real RBI tooling.
Teams were encouraged to push boundaries — integrating IDM, ServiceNow, ORCA, or any RBI resource they could leverage.
Projects were assessed from multiple perspectives, capturing both the quality of the product itself and the way it was built and presented. The focus was on user experience, technical excellence, and the overall clarity of delivery. Judges looked at the functionality and usability of each solution, the quality of its architecture and code, and the effectiveness of the applied AI mechanisms. Security and the interpretability of results were also key factors, ensuring that solutions were not only innovative, but also reliable and transparent.
Equally important was the ability to clearly communicate business value within a short, 5-minute demo — a challenge itself in a fast-paced hackathon environment.
All of this took place under the watchful eye of the jury:
During the hackathon, teams showcased a broad spectrum of approaches to building systems around DQI challenges and document intelligence—ranging from lightweight MVPs and optimized workflows to advanced enterprise-grade architectures and AI-driven platforms.
Team D presented a solution tightly integrated with GitHub, leveraging pull request workflows to manage changes in DQI. They extended the core system with a dashboard layer, search capabilities, and a basic approval pipeline, creating a pragmatic, developer-centric change management loop.
Team E focused heavily on usability and data operations. Their system emphasized operational efficiency, delivering a robust set of features for filtering, editing, previewing, as well as Excel import and YAML generation—essentially enabling fast, structured data manipulation through a highly accessible UI layer.
Team F1 pushed furthest into governance and enterprise process design. They combined business-role modeling with automated PR generation, AI-driven risk analysis, and natural language–controlled bulk updates. The result was a highly comprehensive, end-to-end enterprise workflow model with strong emphasis on control, auditability, and automation.
In the contract intelligence track, Team B delivered a document extraction system for licensing contracts, enhanced with confidence scoring and a “talk to your data” assistant, enabling interactive exploration of extracted insights.
Team C evolved this direction into a production-grade platform, introducing OCR pipelines, PostgreSQL-based persistence, containerized deployment, versioning mechanisms, and a context-aware AI chat interface—bringing the concept closer to a fully operational enterprise system.
Finally, Team A contributed a critical process insight around the BMAD methodology. Their observation was that while this highly detailed, specification-heavy approach delivers strong value in longer, structured delivery cycles, it becomes overly heavy and inefficient in the compressed timeframe of a hackathon environment.
The score differences between the top teams were minimal (under 5%), clearly demonstrating an exceptionally balanced and high-level performance across all participants. Ultimately every team was a winner, with valuable lessons learned that will shape future projects.
Enterprise governance workflow with maker-checker roles, AI risk classification, and auto-generated pull requests for DQI changes.
Problem 1
Second place went to Team F1, who built a highly advanced governance workflow for DQI based on a GitHub pull request flow. Their system introduced a maker-checker role model, structured approval workflows, AI-powered change risk classification, and auto-generated pull requests—delivering strong role separation, control, and process security.
Production-grade license analysis platform combining OCR extraction, Multilevel AI Assistant, full versioning, audit trails, and full containerization. Built with distributed spec driven approach
Problem 2
Team C, who delivered the most complete, production-grade solution for licensing contract analysis. Their system combined OCR and data extraction from PDFs and images, supported over 49 contract attributes, and included full change versioning, an audit trail, and an AI assistant enabling users to query specific agreements. The solution was further strengthened with proper containerization, testing, PostgreSQL integration, and Docker-based deployment. Furthermore this team managed to parallelized the development to utilized the most of every team member.
Contract data extraction with 60+ field analysis, confidence scoring, editable outputs, and a "talk to your data" feature across all contracts.
Problem 2
Third place was awarded to Team B, who presented a solid contract data extraction solution. It included document upload, AI-driven analysis of over 60 fields, confidence scoring, editable outputs, change logs, and a “talk to your data” feature spanning all contracts.
Two days of intense work, a multitude of ideas, and even more inspiring conversations have demonstrated the immense potential within our teams. Innovation emerges where technology, the courage to experiment, and a well-defined business problem intersect.
The combination of AI, risk data considerations, strong engineering practices, and cross-team collaboration quickly translates into real, high-value solutions. The hackathon was also an opportunity to develop future-ready skills—from data literacy and secure design to building AI-ready products.
Teams that delivered working MVPs the fastest typically relied on a SpecKit-driven approach, which enabled rapid translation from specification to implementation and iterative product improvement through agent-based workflows. Agent-assisted testing and code review also proved highly effective, as did parallel work across branches—especially in cases where the specification was clearly defined and stable. The strongest results emerged when the problem was well described and did not require continuous clarification during implementation.
At the same time, several important limitations became apparent. The BMAD approach turned out to be too heavyweight for a two-day hackathon, leading to iterative loops in PRD refinement and validation, while also making it difficult for multiple contributors to collaborate without a shared single source of truth. In cases of weak documentation, AI-generated code exhibited hallucinations and inconsistencies, and debugging still required significant manual intervention.
The key takeaway from the entire hackathon was that the quality of the initial documentation and the precision of the specification had a direct and dominant impact on the quality and consistency of AI-generated code—far greater than the choice of tools or implementation frameworks themselves.
We would like to sincerely congratulate all teams for their impressive creativity, commitment, and highly mature approach to the problems they tackled. The presented projects demonstrated a broad spectrum of thinking—from improving data quality processes and building intuitive workflows, through the development of tools supporting data operations and integrations with systems such as GitHub, to advanced enterprise-grade solutions in the areas of governance and contract intelligence, leveraging AI, OCR, and process automation. We particularly appreciate the diversity of approaches—from fast, iterative MVPs to complex system architectures—as well as the strong product thinking that was evident across all teams. The hackathon also showed how important a well-prepared specification and carefully crafted initial documentation are, as they directly translate into the quality and consistency of the solutions being built
What we learned from two days of building with AI.
Spec Quality > Tool Choice The quality of initial documentation and the precision of the specification had a far greater impact on AI-generated code quality than the choice of tools or frameworks. Clear specs = faster shipping, fewer hallucinations, higher consistency. | |
Parallel Dev Works Parallelizing development in spec-driven frameworks is possible and gave teams a huge advantage — when the spec was clearly defined and stable. | Business + IT Together Business plays an essential role in defining the spec together with IT. Without that collaboration, specs stay vague and AI output suffers. |
Weak Specs = Hallucinations In cases of weak specifications, AI-generated code exhibited hallucinations and inconsistencies — debugging still required significant manual intervention. | Trust but Verify Teams’ trust in AI-produced code was very high — but a second verification step remains inevitable to catch edge cases and ensure reliability. |
BMAD: Heavy but Resilient BMAD was too heavyweight for a 2-day hackathon, but for real-world delivery cycles its rigorous specification approach will be an advantage for more resilient specs. | SpecKit: Speed to MVP Teams using SpecKit delivered working MVPs the fastest — enabling rapid spec-to-implementation translation, agent-assisted testing, and iterative improvement through agent-based workflows. |
A heartfelt thank you to the organizers, mentors, coaches, jury, and participants for creating a space to learn, experiment, and collaborate across international teams. It was this sense of collaboration, the exchange of perspectives, and the shared approach to problem-solving that truly became the greatest value of this hackathon.
Communications Expert, Raiffeisen Tech Poland