Spark
The AI workshop · 1 day · up to 10 people
The entry point, one focused problem and a first working result on the same day onsite.
- Morning AI foundations
- One challenge sprint
- Handoff notes for IT
AI Workshop
Your team builds a working prototype from real company data in a facilitated sprint, instead of talking about AI in a seminar. The entry point is often the AI workshop, one day onsite on one focused problem. Need more, you scale straight up into this multi-day Corporathon hackathon. We plan scope, challenges, roles, data, tool access and the run of show so your hackathon can be ready to start within one week. What ships and when depends on the agreed scope.


Built for
The market is shifting from chatbots to agents. Teams need application, not another slide deck.
Starting point
Lectures and slide decks create knowledge on paper. A hundred employees who actually run AI in daily work move a company further than a thousand where only ten do. That is exactly what the AI workshop is built for, one day where teams build real work output with the tools they will keep using.
<20%
With passive learning, less than 20% of content sticks. Lectures and webinars fizzle out because participants never get hands-on.
~70%
Around 70% of training participants never apply what they learned in their daily work. The gap between theory and practice is too wide.
0×
Classic training delivers no measurable return. No prototype, no tool, no workflow, just a certificate of attendance. For CFOs and budget owners a nightmare, because they approve budget for something whose impact can't be proven.
Comparison
Classic training
Corporathon hackathon
Output
Format
Retention
Adoption
ROI evidence
Role of IT
From workshop to hackathon
The entry point is Spark, the one day AI workshop. Need more, move on to the multi-day Corporathon hackathon with Ignite or Blaze. Every format is all-inclusive, we prepare, facilitate and document. Pricing on request.
The AI workshop · 1 day · up to 10 people
The entry point, one focused problem and a first working result on the same day onsite.
2 days · 10 to 15 people
More depth for parallel teams, real challenge design and solid prototypes.
Teams
Build
3 to 5 days · 15+ people
The large format for several challenges, production-near results and a rollout plan.
Roadmap
Report
Champions
Voices
We did not want a training format, we wanted real output. Five teams started with our own data and tools and shipped prototypes in 24 hours that went straight into daily work. The effect was immediate because every team solved a problem that had been stuck for weeks.
Tim Rath
Founder, YOYABA
Challenges
Results
5 Prototypen
built in 24 hours
1 Tag
from problem to result
Handoff
documented for further use
Social proof
Original posts from real Corporathon hackathons, embedded straight from LinkedIn.
View on LinkedIn
Challenges
Three starting points we see in almost every company. The AI workshop starts exactly there, the hackathon takes it further.
Antwort-Assistent
Triage
The challenge
80% of the team only uses ChatGPT, Claude or Gemini as a chatbot. The age of agents is here, but nothing of it lands in daily work.
What happens in the hackathon
In the hackathon the team builds its first real agent: with tools, data access and a workflow that runs without prompt copy-paste.
Board Update
autoZeit
-2 Tage
Quellen
6
The challenge
Licenses bought, trainings done, pilots ending in slides. What's missing is something that actually runs in operations.
What happens in the hackathon
One week, one scope: the biggest time sink becomes a working prototype with an owner, a metric and an IT handoff.
The challenge
A few enthusiasts push AI, everyone else waits. Knowledge stays with individuals and adoption stalls after the kickoff.
What happens in the hackathon
Teams build themselves, document their solution and become internal champions who start the next use case without us.
Free Resources
Part of our hackathon toolkit is free: ready-made AI skills for your agents, tools and canvases for the prep phase, plus a curated directory of the tools our teams actually build with. No login, just use it and share it in your team.
Ready-made, reusable skills for your AI agents. One command to install, usable in your team right away.
ViewROI calculator, readiness check and canvases for the prep phase. Usable directly, no sign-up.
ViewProven prompts and MCP setups from real hackathons. Copy, adapt and put them to work.
ViewCurated directory of the tools our teams build with. Including use case and pricing.
ViewTools we build with
Benefits
We work with your processes, data and tools instead of generic course examples.
Kontext-Mapping
Every team leaves the sprint with something that runs and has been tested.
Prototyp v1
liveTests
Docs
Handoff
From kickoff to a working prototype in five working days.
Sprintwoche
Mo
Di
Mi
Do
Fr
Participants train their own sub-teams afterwards and keep adoption high.
01
Pre-scoping with per-team challenge design, a curated tool stack per challenge including access, a facilitated build sprint with support throughout, at least one working prototype per team, a handoff document per prototype with owner, access, open risks, acceptance criterion and next step, and documentation of the AI literacy measure for participants.
Our process
We clarify what leadership wants to achieve, which teams take part and where the AI journey goes.
We check existing licences and handle the rest: access, environments and test accounts.
We align agenda, tech stack and concrete challenges together with your team leads.
Full prep on our side: logistics, participant list and challenge briefs are final.
Your team builds, we facilitate table by table. By the end of the day the first prototype runs.
Presentation, documentation and setup instructions so IT can integrate and the team can own it. If the problem runs deeper, next comes the Corporathon hackathon.
Output, not slides
A Corporathon is not a seminar. It is a facilitated sprint where teams rebuild real work with AI.
0 week
from scope to ready-to-run sprint
0 formats
Spark, Ignite and Blaze
0 steps
from call to documented handoff

Next step
Book a discovery call directly, we clarify goal, format and date in the call.
The calendar loads external content from Cal.com. Click to load it, or accept "functionality" in the cookie settings so it loads automatically next time.
FAQ
The Corporathon AI hackathon, with the AI workshop (Spark, one day onsite) as the entry point. Hands on, real data, a working prototype.
For agencies, tech scaleups, digital natives, mid-market and enterprise. Business teams without coding skills are explicitly included. We tailor challenges and format to size and goal, from five to over fifty participants.
One day to five days depending on format. Spark is the AI workshop and runs one day onsite, Ignite two days, Blaze three to five. The run-up with intro call, tools call, data approval and prep fits into the same week, so you can be ready to start within one week.
At least one working prototype per team, a handoff document and a documented AI literacy measure.
No. Business teams build with AI tools without traditional coding. We pick the stack so the challenge is solvable without prior knowledge.
The hackathon can document a practical AI literacy measure and support Article 4, but it is not an official certificate and does not guarantee automatic compliance. The company must assess the overall program by role and risk.
Most companies no longer have a knowledge problem. They have an execution problem. People have heard of ChatGPT, some attended a seminar, and daily work barely changes. That is rarely about motivation. It comes down to four concrete points a lecture cannot fix: the transfer to the real, often sensitive work case breaks; no one owns AI; real data is locked until IT and privacy are involved; and …
A Corporathon is not a developer competition. It is a guided work sprint for business teams who cannot and do not need to code. Participants work with Cursor, Lovable, n8n, Gamma, Figma Make, Claude Code and Custom GPTs on their own data. Facilitation keeps the focus on one tightly framed problem so something usable exists at the end. A typical sprint has four interlocking parts: challenge …
The goal is not a good feeling on Friday afternoon. The goal is that your team visibly works differently after the sprint: a working artifact you own and keep running, practical AI skill that formed on a real case and therefore sticks, a documented AI literacy measure toward EU AI Act Article 4, and a realistic picture of where AI actually carries in your process and where it does not.
Pre-scoping with per-team challenge design, a curated tool stack per challenge including access, a facilitated build sprint with support throughout, at least one working prototype per team, a handoff document per prototype with owner, access, open risks, acceptance criterion and next step, and documentation of the AI literacy measure for participants.
Pricing on request for now. The right shape depends on team size, number of challenges and how deep the handoff needs to be.