EU AI Act Article 4: every training week produces a documented AI literacy record. Learn more →

Corporathon

Formats: Spark, Ignite, Blaze

Three formats for every team size: Spark (1 day), Ignite (2 days), Blaze (3 to 5 days). Plus follow-up offerings. Prices on request.

Three formats for every team size

An AI hackathon fits a small team as well as several departments. To make that work, Corporathon comes in three sizes. Spark, Ignite and Blaze differ in duration and number of participants, but share the same flow and the same promise, a running prototype at the end. Which format fits you depends on team size, goals and the depth you want to reach. We quote prices on request, because every engagement is tailored differently.

Spark, 1 day, up to 10 participants

Spark is the focused start. In one day a small team gets to know the stack and builds a clearly scoped challenge, such as an email reply assistant or a daily briefing agent. Spark fits when you seriously touch AI for the first time and want a tangible result fast. The day ends with a pitch and a first prototype.

Ignite, 2 days, 10 to 15 participants

AI training vs AI hackathon

Criterion Classic AI training / seminar Corporathon AI hackathon
Output certificate, attendance record working prototype
Knowledge retention unclear without transfer measurement measurable through prototype quality, usage and handoff
AI adoption after 30 days unclear without measurement measure through usage and handoff
ROI evidence hardly possible tangible projects and results
Format lecture, slides hands-on, real data and tools
Time to result weeks to months 1 week

The detailed comparison in prose is on /vergleich/ki-schulung-vs-ki-hackathon.

How a hackathon runs

Whatever the format, every Corporathon follows the same dramaturgy. Day 1 starts with AI foundations and a tool workshop where the team gets to know the stack, including Cursor, Lovable, n8n, Gamma, Claude Code and Custom GPTs. Then come team building and ideation, then the kickoff into the sprint, from here the building starts. On day 2 and the following days it continues to deployment, then come the pitches and the handoff to IT. The goal stays the same, after 24 hours a running prototype stands, not a concept on paper. Blaze deepens that over several days.

Services and packages

The three core formats are Spark, 1 day, up to 10 participants, Ignite, 2 days, 10 to 15 participants, and Blaze, 3 to 5 days, 15 and more. After that we keep the impact alive with follow-up offerings. The AI Implementation Sprint over 2 to 4 weeks moves a prototype toward production. The Recurring Hackathon Series on a quarterly rhythm anchors AI for good. The AI Enablement Program over 3 to 6 months accompanies a broad transformation. Prices on request, depending on format and team size.

What each format delivers

From every Corporathon you take away 3 to 5 ready-to-use prototypes, plus an impact report, a skills library, an IT handoff package and internal AI champions. You also get an internal AI literacy measures record under Article 4, the AI literacy obligation has applied since 2 February 2025. More on /en/eu-ai-act.

Next steps to the hackathon

  1. Intro call, we settle the goal, the team and the right format (https://cal.com/jamboula/ai-hackathon).
  2. Tools and challenges call, we collect your real use cases and the right stack.
  3. Finalization, we lock format, date and participants.
  4. Hackathon preparation, access, sample data and environments are set up.
  5. Tool workshop, the team learns the stack hands-on.
  6. Hackathon sprint, each team builds its own challenge on real data.
  7. Result pitches, the running prototypes are presented and handed to IT.

Challenges

Typical challenges that work in every format are an email reply assistant, a daily briefing agent, a meeting-to-action-items workflow, an executive reporting autopilot and an internal knowledge bot on your documents. A proposal generator from raw notes fits well, as does a support assistant for recurring requests. In Spark the focus is on one challenge, in Ignite and Blaze several teams work in parallel.

CTA

Time for your Corporathon? In just 1 week from first contact to a finished prototype. Book a discovery call, https://cal.com/jamboula/ai-hackathon. Includes an internal AI literacy measures record under Article 4.

FAQ

Which format fits my team size? Spark covers up to 10 people, Ignite 10 to 15, Blaze 15 and more. For larger workforces several teams work in parallel on their own challenges. We settle the right format in the discovery call based on goals and team size.

What is the difference between Spark and Ignite? Spark runs one day with a small team and one focused challenge. Ignite runs two days with more participants, several parallel teams and more time for deployment. Ignite is the most booked format because it combines depth and pace well.

What do the formats cost? The price depends on format and team size. We do not quote a flat figure on the page for now, because every engagement is tailored differently. You get a concrete quote on request in the discovery call at https://cal.com/jamboula/ai-hackathon.

What happens after the hackathon? On request it continues with follow-up offerings. The AI Implementation Sprint moves a prototype toward production, the Recurring Hackathon Series anchors AI quarterly, the AI Enablement Program accompanies over 3 to 6 months. That keeps the impact alive.

Are the formats also bookable remotely? Yes. Every format runs on-site with you or remote over video and shared working environments. Flow and result stay the same either way. We settle what fits in the intro call.

Can several teams work in parallel? Yes. In Ignite and Blaze several small teams work at the same time on their own challenges. That is intentional, because each group builds on its real problem and the results spread widely. In Spark the focus is on one challenge.

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.

Discovery Call

Termin direkt buchen

30 Minuten, in denen wir Ausgangslage, Teamgröße und passende Challenges klären. Danach weißt du, welches Format zu euch passt.

cal.com · Corporathon Discovery Call

Der Kalender wird von cal.com geladen und setzt dafür eigene Cookies. Wir laden ihn erst, wenn du zustimmst oder ihn hier direkt anforderst.

Alternativ direkt auf cal.com buchen