AI Hackathon
from €15,000 · 2 build days · closing day
An AI Hackathon is a programme of two build days and a closing day in which your own people build working AI tools for their own work. Cost: from €15,000.
Your own people build working AI tools for their own work in two days. We facilitate and build alongside them. Not a training that fades in a fortnight, but tools that run the next day.
1+
working automation per team, at least
2-3
per team, business and IT together
Hackathons run at
Six working prototypes in two days, three went to production
Five management teams each built their own digital competitor in a dayIs this for you?
Yes, if...
- You want AI to land in working tools, not in awareness
- You do not believe in another training, but in building it yourselves
- You want proof and momentum before committing to a longer programme
No, if...
- You already know exactly what to automate and want it in production nowStraight to the Kickstart→
- Your team has no technical affinity yet and needs the basics firstSee Working with agents→
Why building beats training
Working tools instead of knowledge that fades
After a training your team knows something. After a hackathon something runs, in your own environment.
Building it yourself gives understanding and ownership
People who built it keep using it, and can explain it to the rest.
Business and IT in the same team
Two to three people per use case, with the owner of the problem in the room, not only builders.
Safe within your constraints
Human in the loop, real or synthetic data. In regulated environments we set that up beforehand.
We only run it when there is a next step
A hackathon that leads nowhere is an expensive marketing cost. At intake we decide together whether that path exists.
What you get out of it
Two build days on site
A SPAIK facilitator and a builder are both there on both days. Teams of two to three, with the owner of the problem in the team.
Your own use cases, your own data
No generic examples. We build in your environment and tooling, whether that is Copilot and Azure or something else. What gets built is yours.
Around three working tools
By the end of day two they are 80 to 90 percent done, with documentation per tool: manual, prompts, templates.
A closing day and a plan for what follows
Between the build days and the closing day teams apply the tools to real work, with remote support. On the closing day you show what runs and which department is next.
How it works
Intake
Which processes, which people, which constraints. In a regulated environment we arrange dev laptops and synthetic data up front.
Build day 1
A short AI intro with demos, then picking opportunities and forming teams. The rest of the day is spent building.
Build day 2 and the weeks after
Building until the tools work. After that teams apply them to real work, with remote support from SPAIK.
Closing day
Demos of what runs, what it delivered, and the choice of which department or use case comes next.
What it costs
- Facilitator and builder, every dayUp to four teams a pair is enough. Above that a builder joins per two extra teams, and the price moves with it.
- Documentation per tool builtManual, prompts and templates, so your team can carry on without us.
- Support between the build days and the closing dayTeams apply the tools to real work and can reach us during that period.
A single day with just the leadership team also works: build your own competitor, €9,500 including a return day after two weeks.
What participants built
Measured results at clients we are allowed to name.
From idea to working tool
Not a single prototype
6 working prototypes in two days
Three went to production
Read the case→Our promise
at least 1 working automation per team, built on your own work
“Our developers built in hours what would normally take weeks. Even the skeptics became enthusiastic. No theory, just building. Two days later: 6 working prototypes.”
Vincent Bekker
CTO, Euphoria Mobility
Next step
A hackathon gives you proof and momentum. If you then want one process in production with a business case underneath it, the Kickstart is the next step.
Frequently asked questions about the AI Hackathon
What does an AI Hackathon cost?
From €15,000. That includes two on-site build days with a facilitator and a builder from SPAIK, remote support in between, and a closing day.
Who takes part?
Teams of two to three people per use case, business and IT together, with the owner of the problem on the team. Technical affinity helps, but what matters is people who want to improve their own work.
What if we work in a regulated environment?
Then we set that up in advance: dev laptops, synthetic data and a human in the loop. We build within your guardrails and in your own tooling, whether that is Copilot and Azure or something else.
What happens after the closing day?
On the closing day you choose which department or use case goes next. If you then want to take one process into production with a business case behind it, the Kickstart is the next step. We only run a hackathon when that path exists.
Which process should you start with?
We know that after a half-hour call. Then you also know whether we are the right partner.