01
01
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
Use Case
Scope
Build
Transfer
AI Workshop
AI Hackathon for Companies
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.
- Real prototypes instead of slides
- Facilitated by AI practitioners
- Ready to run within a week
- Documented handoff included
Built for
The market is shifting from chatbots to agents. Teams need application, not another slide deck.
Starting point
What goes wrong with training in the AI era
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.
Little
Knowledge retention
With passive learning, often little of the content sticks. Lectures and webinars fizzle out because participants never get hands-on.
Often
No application
Many training participants do not apply what they learned in their daily work. The gap between theory and practice is too wide.
Open
Hard-to-see value
Classic training often delivers no directly visible output. No prototype, no tool, no workflow, just a proof of participation. For CFOs and budget owners a nightmare, because they approve budget for something whose impact can't be proven.
Comparison
In the age of AI only a hands-on learning approach counts
Classic training
Corporathon hackathon
Output
Proof of participation and documentation
A working prototype
Format
Slides and lectures
Hands-on with real data
Retention
unclear without transfer measurement
measurable via usage and handoff
Adoption
fades within days
champions train their sub-teams
ROI evidence
hard to show
tangible projects on your own stack
Role of IT
not involved
documented handoff included
From workshop to hackathon
Three formats, one principle, build instead of listen.
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.
02
02
Ignite
2 days · 10 to 15 people
More depth for parallel teams, real challenge design and solid prototypes.
- Challenge design upfront
- Parallel teams
- Pitches with handoff package
Teams
Build
Sprints
Scores
Launch
03
03
Blaze
3 to 5 days · 15+ people
The large format for several challenges, production-near results and a rollout plan.
- Multi-day sprint
- Post-event report
- Rollout roadmap
Roadmap
Report
Champions
Plan
Impact
Rollout
Challenges
The challenges the AI workshop solves.
Three starting points we see in almost every company. The AI workshop starts exactly there, the hackathon takes it further.
Reply assistant
Triage
Quote follow-uphigh
Reschedule meetingmedium
Newsletterlater
12 replies prepared
From chatbots to agents
The challenge
Many teams only use 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
autoTime
-2 days
Sources
6
From tool tests to prototypes
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.
How does our onboarding work?
Playbook.pdfPolicy v3Notion
From lone champions to a team
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
Free AI 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.
AI Skills
Free AI skills
Ready-made, reusable skills for your AI agents. One command to install, usable in your team right away.
ViewTools
Free tools
ROI calculator, readiness check and canvases for the prep phase. Usable directly, no sign-up.
ViewLibrary
AI prompt & MCP library
Proven prompts and MCP setups from real hackathons. Copy, adapt and put them to work.
ViewDirectory
AI tool directory
Curated directory of the tools our teams build with. Including use case and pricing.
ViewTools we build with
Benefits
How it feels when AI finally lands in daily work.
Your context, our expertise
We work with your processes, data and tools instead of generic course examples.
Kontext-Mapping
Prozesse
Daten
Tools
Rollen
Guardrails
Focus on output, not slides
Every team leaves the sprint with something that runs and has been tested.
Prototyp v1
liveTests
Docs
Handoff
Results within one week
From kickoff to a working prototype in five working days.
Sprintwoche
Mo
Di
Mi
Do
Fr
Champions who carry it on
Participants train their own sub-teams afterwards and keep adoption high.
AL
MK
SB
JD
TR
LP
01
Deliverables
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
Next steps to your AI workshop.
Day 0 · Discovery Call
We clarify what leadership wants to achieve, which teams take part and where the AI journey goes.
Day 0 · Tool Setup
We check existing licences and handle the rest: access, environments and test accounts.
Day 0 · Challenge Design
We align agenda, tech stack and concrete challenges together with your team leads.
Day 0 · Preparation
Full prep on our side: logistics, participant list and challenge briefs are final.
Day 1 · AI Workshop
Your team builds, we facilitate table by table. By the end of the day the first prototype runs.
Afterward · Handoff
Presentation, documentation and setup instructions so IT can integrate and the team can own it. If the problem runs deeper, next comes the hackathon.
Output, not slides
A hackathon 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
Ready for your hackathon?
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
Questions that should be clear before the first call.
The hackathon 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 attestation and does not guarantee automatic compliance. The company must assess the overall program by role and risk.
There is no proof of participation at the end, there is a working result: built workflows that keep running in daily operations.
Usually one week: scoping call, use-case selection, access and tool setup. After that the sprint is ready to run.
You decide which data enters the sprint. Access, privacy and boundaries are agreed upfront and we only work with approved material.
You do. Prototypes, automations, workflows, prompts and generated code belong to your company after the sprint.
We work with the stack that fits you: LLM APIs, automation and data platforms, and your existing systems.