Question 1

Do our employees need to know how to code?

Accepted Answer

No. Modern AI tools let non-technical people build real, working things. We coach every team through the process.

Question 2

What happens to our company data?

Accepted Answer

Your data stays yours. We agree on handling and access before the event and work inside your environment wherever possible.

Question 3

How fast can we run a hackathon?

Accepted Answer

From our first call to a prototype your team built with AI: one week. The event itself runs for one to five days.

Question 4

What does a team walk away with?

Accepted Answer

Working prototypes on your real data, an impact report, a skills library and a clean handover package for IT.

Question 5

Does this support EU AI Act literacy?

Accepted Answer

The format builds and documents practical, context-specific competence. Your company remains responsible for assessing its overall Article 4 program.

Question 6

How many people can take part?

Accepted Answer

Formats run from a single team of six up to company-wide groups split into parallel teams, each with its own challenge and coach.

Question 7

Which tools do you work with?

Accepted Answer

The stack is chosen around your setup: ChatGPT, Claude, Gemini, Copilot, n8n, Make, Zapier, Lovable and your existing CRM or data tools.

Question 8

Do we need to prepare use cases in advance?

Accepted Answer

We collect and sharpen the challenges together in the tools and challenges call, so day one starts with building instead of brainstorming.

Question 9

What happens after the hackathon?

Accepted Answer

You get a handover package, internal champions who can train their own sub-teams, and an optional follow-up sprint to harden the best prototypes.

Question 10

Can you run it remotely or on site?

Accepted Answer

Both. On site works best for energy and momentum; remote and hybrid setups run with the same structure, coaching and pitch format.

lemlist review

What is lemlist?