1 day · up to 10 participants

Spark Hackathon

One day, one team, two real challenges – by the evening the first prototype is running.

Duration
1 day
Participants
up to 10
Result
1 prototype
Lead time
from 2 weeks

References

Companies from our projects

Names and logos of companies we have worked with.

Insight Consulting Berlin Logo
Adobe Logo
NavVis Logo
Onventis Logo
Ecoza Institute Logo
Ecoza Logo
YOYABA Logo
Insight Consulting Berlin Logo
Adobe Logo
NavVis Logo
Onventis Logo
Ecoza Institute Logo
Ecoza Logo
YOYABA Logo
Adobe Logo
Ecoza Institute Logo
Onventis Logo
Ecoza Logo
NavVis Logo
Insight Consulting Berlin Logo
YOYABA Logo
Adobe Logo
Ecoza Institute Logo
Onventis Logo
Ecoza Logo
NavVis Logo
Insight Consulting Berlin Logo
YOYABA Logo

01 – Key facts

Why teams book Spark

Spark is the compact starting point: a full day in which your team gets hands-on with the most important AI tools, tackles two real challenges from everyday work, and pitches a working prototype by the evening.

Immediately measurable time savings

Everyone leaves with at least one automation that takes work off their plate starting the next day.

No risk, no project

One day of effort instead of month-long programs – ideal for testing AI enablement first.

Everything stays with you

Prototypes, prompts, and access remain yours, including AI literacy fundamentals that can support documentation under Art. 4 EU AI Act.

02 – Outcomes

What you have afterwards

Spark doesn't end with a slide deck. It ends with concrete outcomes your team keeps using the next day.

A first automation of their own

Every participant leaves the day with at least one automation that immediately saves time in their own work.

A shared vocabulary

Prompting, context, agents, and model limitations – explained through your own use case instead of abstract examples.

A solid basis for decisions

Afterwards you know which processes are ready for AI and where a bigger program would pay off.

03 – Process

How Spark runs

From the first alignment call to handover: every step is prepared so the time on site goes entirely into building.

  1. 01Discovery call20 minutes to clarify goals, participants, and possible challenges.
  2. 02Challenge preparationWe sharpen two challenges and prepare tools, access, and credits.
  3. 03Hackathon dayKickoff, tool showcase, build phase with coaching, pitches, and awards.
  4. 04Follow-upSummary, prototype handover, and recommendations for next steps.

04 – Scope

Everything included in Spark

Included services, a good starting fit, and the team on site – at a glance.

Included

  • Tool credits and access for all participants
  • Challenge design created together with you
  • Tim Jamboula as hackathon lead on site
  • All prototypes and prompts remain with you
  • AI literacy fundamentals that can support documentation under Art. 4 EU AI Act

A good fit if

  • Teams of up to 10 people going beyond chatbots for the first time
  • Companies that want to test AI enablement before scaling
  • Departments with clearly defined routine tasks

Your contact on site

  • Tim Jamboula, hackathon lead and facilitator

Voices from the hackathon

Hackathon posts on LinkedIn

Public posts by Tim Rath (Founder YOYABA) and participants from YOYABA and NavVis after the AI hackathons, in the original.

LinkedIn

Post by Tim Rath. It is loaded from LinkedIn when shown, which needs your consent to external content.

Tim Rath, Founder YOYABAOriginal on LinkedIn

LinkedIn

Post by Marie Klamer. It is loaded from LinkedIn when shown, which needs your consent to external content.

Marie Klamer, YOYABAOriginal on LinkedIn

LinkedIn

Post by Tim Rath. It is loaded from LinkedIn when shown, which needs your consent to external content.

Tim Rath, Founder YOYABAOriginal on LinkedIn

What other customers say

Voices from real Corporathons.

Verbatim excerpts from public LinkedIn posts by participants.

„24 hours in our office. Pizza everywhere. 5 teams racing to build something real with AI."

Marie Klamer

YOYABA · LinkedIn-Beitrag

„Turns out that's all it takes to go from "I should really learn AI" to actually shipping a working product. No coding experience needed."

Marie Klamer

YOYABA · LinkedIn-Beitrag

„By the end of day one, people who had never touched a terminal were working in Claude Code and building solutions of their own."

Okechukwu Ukaigwe

NavVis · LinkedIn-Beitrag

„You don't need months of preparation. Just a team, a bit of chaos, and the willingness to start."

Lisa Kral

YOYABA · LinkedIn-Beitrag

„24 hours in our office. Pizza everywhere. 5 teams racing to build something real with AI."

Marie Klamer

YOYABA · LinkedIn-Beitrag

„Turns out that's all it takes to go from "I should really learn AI" to actually shipping a working product. No coding experience needed."

Marie Klamer

YOYABA · LinkedIn-Beitrag

„By the end of day one, people who had never touched a terminal were working in Claude Code and building solutions of their own."

Okechukwu Ukaigwe

NavVis · LinkedIn-Beitrag

„You don't need months of preparation. Just a team, a bit of chaos, and the willingness to start."

Lisa Kral

YOYABA · LinkedIn-Beitrag

06 – Get started

Spark for your team?
Let's talk.

Book a discovery call

The calendar is loaded via Cal.com. This requires your consent to external content.

07 – FAQ

Frequently asked questions

The questions that come up most often about Spark in the discovery call.

08 – Other services

A different format might fit better

The three services differ in duration, group size, and depth – here are the alternatives.