Frequently asked questions about the AI workshop and Corporathon hackathon

Pricing depends on format, team size and preparation. Spark, the AI workshop, runs one day, Ignite and Blaze as the hackathon run two to five days. We give you a clear number for your case in the discovery call, no package puzzles. Book a slot at

Three. Spark, the AI workshop, runs one day onsite with up to 10 participants and delivers a first prototype. Ignite builds on that with two days for 10 to 15 people, Blaze with three to five days for 15 plus. Which one fits depends on your goal and the number of teams. We recommend the right setup in the discovery call.

Yes. On request we support implementation with an AI Implementation Sprint over two to four weeks, a quarterly Recurring Hackathon Series or an AI Enablement Program over three to six months.

Little. The preparation sits with us and fits into the same week as the workshop day or the hackathon. From you we need two short calls, access to sample data and the choice of problems you want to solve. We build the rest.

Usually within a few days of the discovery call. Two short prep calls clarify goal and access, then a date is set for the workshop day or the hackathon days.

No. The hackathon is built for business teams, not just developers. You work with tools like Lovable, n8n, Gamma and Custom GPTs that need no classic coding. The opening tool workshop gets everyone to the same level.

Cursor, Lovable, n8n, Gamma, Figma Make, Claude Code, Custom GPTs, Codex, ElevenLabs, Claude Cowork and NotebookLM. Which ones you use depends on your task. The tool workshop makes your team familiar with the right stack.

You decide which data enters the hackathon. We work to your rules, handle data protection and access in the prep phase and use anonymized or synthetic data where needed. After the hackathon your data stays with you. Nothing leaves your frame without approval.

You do. Everything built during the hackathon belongs to your company. Prototypes, automations and code are yours to keep and put into production. We keep nothing back and lock you into no license.

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.

For most goals, yes. If you want AI adoption and real results, a hackathon takes you further than lectures. Retention is higher and the team ends with something finished. Pure documentation duties are covered through the internal AI literacy measures record.

A classic hackathon is a contest for developers. The hackathon is aimed at your business workday, for expert teams without a coding requirement, with your real data and problems. The goal is not a prize but AI adoption and solutions that keep running after the last day. The entry often starts with the 1-day AI workshop, before a team moves on to the multi-day hackathon.

Agencies, tech scaleups, digital natives, mid-market and enterprise. We work with twelve industries from marketing to mechanical engineering to pharma. Whether five or fifty participants, we adapt format and challenges to your size and goal.