Hackathon / Paris build days, 9–10 July 2026
100 people, 24 hours in Paris
About 100 people from across Europe and the US came together at Google’s Paris office for 24 hours of building. The work started months earlier, when teams chose a business problem and gathered data. After the demos, they explored what it would take to put their prototypes to work.
By Adam Mazik, Rydoo’s hackathon team lead.
I used AI-generated illustrations to honor the NDA and protect client privacy.

Choosing the problem
Where does the work slow down?
The winning team reviewed a month of customer conversations. In roughly one in three of the 412 calls, someone had to follow up with an answer. Before anyone wrote code, the team knew which part of the job to test.
Watch the organizer’s recap
The winning demo
Could it answer a customer live?
Two teammates played out a customer call in front of the jury. Their assistant found an answer and its source during the conversation. The demo won the Grand Prix. After Paris, the team began preparing the tool for a broader test with customer success.
Read the winning team’s account
The business case
What would make a pilot worth it?
The team asked customer success managers how much time they spent researching and following up. Their estimate gave the pilot a benchmark. The next test is whether managers recover that time and customers get answers they can trust.
See how the team estimated the savings4.5 hours in potential savings per customer success manager each week.
Estimated before rollout · July 2026
Which workflow would you put to the test?
Michael Duncan co-created the Paris hackathon. Bring him a workflow that slowed your team down last week. Together you can decide what to measure before the build, what to demonstrate, and what would justify a pilot afterward.