Team prep guide · Paris 2026

You're coming to Paris.

Your team is confirmed. Here is what to know before July 9: venue, timing, what to bring, and who to ask when questions land.

Logistics at a glance

Date: July 9 & 10, 2026
Venue: Google Paris
Kickoff: Thursday, 5 to 7 PM
Team size: Four to six people

What your team brings

Three things to come ready with on the day.

A team of four to six people across engineering, product, and the business.
A real problem your team is already trying to solve, agreed in advance with leadership.
Twenty-four hours of focused, uninterrupted time.

What we handle

Everything else, so your team can focus on the build.

Venue, food, tools, mentors, and the program structure around the build.
Google Cloud credits and on-site engineer access for every team.
Judging, awards, and the post-event check-in to keep the work moving.

Team onboarding pack

Full logistics and pre-event check-ins.

A single PDF your team lead shares with the four to six people coming. Sent the week of May 22, once participating teams are confirmed.

Event FAQ

Common questions, answered.

The questions portfolio companies ask most. If something is missing, the contact link below reaches the Eurazeo team directly.

When does the event start and end?: Thursday, July 9: kickoff session 5:00 to 7:00 PM. Friday, July 10: Google staff on-site from 7 AM. Final demos and judging wrap by approximately 5 PM.
How many people per team?: Four to six people per team. A flexible mix: engineering, product, design, business, or any combination that fits your project. The problem your team works on is agreed in advance with leadership, so the team arrives knowing the work is backed.
Does my team need engineers?: Plenty of teams will come without a single engineer. Modern AI builders, tools like Loveable, Base44, Bolt, and v0, let non-technical teams turn ideas into working prototypes in a day. What matters most is having people who know the problem deeply: the business owner, the team that lives with the workflow, the person closest to it day to day.
What should we wear?: Comfortable but professional. You will be on your feet, presenting, and meeting peers from across the portfolio. Aim for the middle ground, comfortable enough to build for a full day, polished enough to demo and meet new people.
What should we bring on the day?: Your laptop and charger, a phone charger, and headphones if you want quiet focus time. WiFi, power, screens, food, and drinks are all on us. Most teams also bring a small notebook for the kickoff and the first hour of scoping.
Can teams work overnight at the venue?: No. The venue closes Thursday around 9 PM and reopens Friday 7 AM, per Google security policy linked to the building's proximity to the data center. Plan your team's rest and any heavy build work around that window.
What is provided on-site?: Catering (lunch and coffee) by Google. Mentors and Google Cloud engineers in the room. AV, screens, microphones, and event support. Teams bring their own laptops.
What cloud and AI tools can we use?: All technology your team already uses is welcome: GitHub, Claude Code, Cursor, Loveable, Base44, and the dev tools that fit your stack. Google Cloud and Gemini are our exclusive cloud and AI-model partners, with on-site engineers and credits supporting your build. Avoid AWS, Azure, and OpenAI as primary cloud or model platforms.
Will we have Google Cloud credits and pre-configured environments?: Yes. Each team gets temporary credentials, pre-configured billing, and high quotas on-site. Resources are torn down after the event. A pre-event orientation session in mid-June walks teams through the Gemini APIs and getting-started guides.
How do we work with the mentors?: Mentors rotate through team tables throughout the day. Flag one over when you need help, no booking required. They will sit with you for as long as you need, then move on.
What does success look like by Friday afternoon?: A working slice of your idea, real enough to take forward. Not a finished product, not a polished launch, a credible build that proves the idea is worth pursuing. Most teams underestimate how much they can do in a day and overestimate how much they should try. Pick a small, sharp slice and finish it.
How are demos judged?: A joint Eurazeo and Google panel scores each team equally on three things. First, a working build: by Friday afternoon there is something that runs end to end, not slides. Second, a problem worth solving: the use case matters to your company beyond the room. Third, AI doing real work: AI is the engine, not a wrapper around something static.
What are the prizes?: There are prizes worth winning. Categories and details ship in the team pack on May 22, ahead of the event.
What happens to our work after the hackathon? Can we move it off Google Cloud?: Yes. Anything your team builds is yours, and you can keep running it on Google Cloud, move to another provider, or do both. Google Cloud also supports Anthropic Claude and other model providers through Vertex AI Model Garden, so you can switch models without switching cloud providers.
Where do we send questions or RSVPs?: The Eurazeo team handles RSVPs and program questions. Use the contact link at the bottom of this page to reach them directly.

The full arc

Dates your team should keep on the calendar.

May 15, 2026
RSVP deadline
Your team's confirmation is due. Reply directly to the Eurazeo team.
Confirmed
May 22, 2026
Participating teams locked
Eurazeo confirms the participating portfolio companies.
Confirmed
Mid-June 2026
Pre-event Tech Prep
60 to 90-minute virtual session with the Google team covering Google Cloud, Gemini, credentials, and on-site support. Mid-June; exact date confirmed in mid-May.
Finalizing
July 10, 2026
Hackathon
24-hour build at Google Paris. Demos and judging in the final hours.
Confirmed
August 31, 2026
30-day readout
Your team's outcomes call with the Eurazeo team.
Confirmed
November 15, 2026
Program close
Final case material capture and program wrap.
Confirmed

Questions

Reach the Eurazeo team anytime.

Contact Eurazeo