The most important questions at a glance
These are the questions that come up most in the discovery call. If yours is missing, just book a slot at https://cal.com/jamboula/ai-hackathon and we clarify it directly. The short version up front: there are three formats, you need little preparation, your data stays with you, the code created belongs to you, and you get an internal AI literacy measures record.
Cost and formats
What does an AI training at Corporathon cost? The price depends on format and team size. There are three formats: Spark (1 day, up to 10 people), Ignite (2 days, 10 to 15) and Blaze (3 to 5 days, 15+). You get a concrete quote on request in the discovery call at https://cal.com/jamboula/ai-hackathon.
Which company sizes is the AI training suitable for? From SME to enterprise. The three formats scale with team size: Spark for small teams up to 10, Ignite for 10 to 15, Blaze for 15 and more. Whether agency, mid-market, scaleup or portfolio company, the format adapts to your situation.
Are there follow-up offers after the week? Yes. If you want to continue, there is the AI Implementation Sprint (2 to 4 weeks), a Recurring Hackathon Series (quarterly) and an AI Enablement Program (3 to 6 months). What fits depends on how deeply you want to anchor AI.
Requirements and preparation
Do our employees need to know how to code? No. The whole point is that people without a coding background build real results with AI tools too. We work with tools like Lovable, ChatGPT and n8n that have very low entry barriers. The tool workshop at the start brings everyone up to speed, whatever level they start at.
How much preparation do we need? Little. The effort on your side is two short calls and providing access and sample data. We handle the rest. That is exactly why the promise works: in just 1 week from first contact to a finished prototype, without your team planning for weeks.
Does the AI training run in-house or remote? Both are possible. The in-house AI training happens at your site on your real processes, remote runs over video and shared work environments. What fits better we clarify in the intro call. In both cases the promise stays the same, planning can be start-ready within one week.
Data, law and ownership
What happens with our company data? You keep full data sovereignty. We work with your real data only within the agreed scope, GDPR compliant, and nothing leaves your environment uncontrolled. In the in-house AI training everything happens in your infrastructure. Details we clarify before the start in the finalization step.
Who owns the code created at the end? You do. Everything created during the hackathon in prototypes, code and automations belongs to your company. We build with you, not for us. You can freely reuse, develop further and put every result into production afterwards.
Does the hackathon meet the EU AI Act literacy duty? The format can contribute as one role- and context-appropriate AI literacy measure and create an internal record. It does not automatically satisfy Article 4; the organisation must assess its overall programme for the relevant roles, systems and risks.
Format and impact
Why is a hackathon better than a classic AI training? Because people keep what they built themselves. Transfer from passive learning cannot be evaluated reliably without measurement, and a substantial share never applies training content. At the hackathon transfer is measured through practical application and usage signals, because your team works on a real problem instead of watching slides. The output is a prototype, not a certificate.
What concrete results do we take away? After the week you have 3 to 5 ready-to-use prototypes, an impact report, a skills library, an IT handoff package and trained AI champions. Typical prototypes are an email reply assistant, a daily briefing agent or a meeting-to-action-items tool, all built on your real processes.
Next steps to your hackathon
- Intro call. Clarify starting point, teams and goals.
- Tools and challenges call. Pick real challenges, set the toolstack.
- Finalization. Bring info, access and data together, GDPR compliant.
- Hackathon preparation. Set up environment and flow.
- Tool workshop. Hands-on start on the stack on your own case.
- Hackathon sprint. Teams build on their challenges with live coaching.
- Result pitches. Each team shows its prototype.
Training depth: why training matters only when it is applied
This domain needs to be the strongest answer for AI training in German search. The searcher expects structure, safety and a clear learning path. The better answer is: yes, there is tool input and didactic guidance, but training does not end at understanding. It ends with application. Every core page should explain how employees move from foundations to their own challenge and why the prototype is the real learning test.
Employee perspective, not only HR perspective
AI training wins when employees feel enabled, not examined. Strong pages therefore speak not only about certificate and duty, but about relief in daily work: less copy paste, better research, faster replies, clearer meetings, fewer manual reports. That makes the training domain more human and stronger than pure compliance communication.
Rechtlicher Hinweis / Legal note: Ein Hackathon und der hier beschriebene Kompetenznachweis können praktische KI-Kompetenzmaßnahmen dokumentieren, sind aber kein behördlich vorgeschriebenes Zertifikat und garantieren nicht automatisch die Erfüllung von Artikel 4. Das Unternehmen muss die Angemessenheit seines Gesamtprogramms rollen-, kontext- und risikobezogen prüfen. / A hackathon and the competence record described here can document practical AI literacy measures, but they are not an officially mandated certificate and do not automatically guarantee compliance with Article 4. The company must assess its overall program for the relevant roles, context and risks.