Green Tomato Media × 2026

GTM AI Build Day

One day. Claude Code. Small teams. Real tools.
$ claude "solve my problem"

How it works

👥 Teams of 2–3

Mixed technical + non-technical. Everyone contributes. Non-tech members own the problem & the pitch.

🛠️ One tool: Claude Code

Terminal + Claude. No infra, no frameworks, no setup. Just describe what you want to build and iterate.

🎯 Real GTM problems

Build something you'd actually use Monday morning. Content tools, ops scripts, dashboards, automations.

🧠 No coding needed

Claude Code writes the code. You bring the problem, the idea, and the feedback. If you can describe it, you can build it.

🏆 5-min demos

Every team gets 5 minutes to show what they built and why it matters. Judged on usefulness, not complexity.

🚀 Ship to production

Every project can ship. Infra is provided for all teams — if you build it, you can deploy it.

How projects are scored

35%
Business impact
How much time or money does this save if deployed?
30%
Usefulness
Would the team actually use this Monday morning?
20%
Creativity
Is this a clever or unexpected approach to the problem?
25%
Team collaboration
Did non-tech members shape the problem and solution?

Incentives

Cash prizes per team · funded via training/formation budget

💎
2,500€
Grand Prize

High business impact (revenue) + used every day

🥇
1,000€
1st place
🥈
500€
2nd place
🥉
250€
3rd place

8-week plan · Build Day Friday June 5

Weekly content drops and internal showcases. Onboarding session in week 6 unlocks everything.

1 — Get Started with Claude
Apr 13–17 · T−8
Foundational content drop. No live session — people consume on their own time.
  • “Get Started with Claude” materials & videos released
  • Content drop: connectors & projects — how to wire Claude into your tools and organize your work
2 — Claude Environments & GTM Plugins
Apr 20–24 · T−7
Presentation on the GTM Claude environment — what’s available, what plugins we’ve built, how to use them.
  • Live presentation: Claude environments & GTM plugins
  • Showcase #1 — internal project presentation
3 — Skills
Apr 27–May 1 · T−6
Learn how Claude skills work and see how a colleague is using them in production.
  • Content drop: Claude skills (videos + guides)
  • Showcase #2 — internal project presentation
4 — Cloudflare Infrastructure
May 4–8 · T−5
How GTM’s Cloudflare setup enables secure access and team sharing.
  • Presentation: Cloudflare access & infrastructure — what we provide, how we secure it, how we share it
  • Showcase #3 — internal project presentation
5 — MCP & Connectors Deep Dive
May 11–15 · T−4
Going deeper on connectors — how MCP works, which connectors we use at GTM, how to wire Claude into the tools you use every day.
  • Content drop: MCP & connectors — the GTM stack
  • Showcase #4 — internal project presentation
6 — Deep Dive
May 18–22 · T−3
A longer-format technical session on a real production system built with Claude.
  • Deep dive workshop: Andrim presents his projects — approach, architecture, lessons learned
  • Team sign-ups open
7 — Final Prep
May 25–29 · T−2
Last week before the event — teams and projects locked in, setup verified.
  • Setup guide published: GitHub, Claude Desktop, Claude Team access
  • Warm-up challenge — a small solo task to try before the event
  • Final team list and project ideas announced
  • Build Day logistics shared: schedule, tools, channels, what to expect
8 — 🟢 Build Day
Jun 1–5 · The Week
Onboarding earlier in the week, then build, demo, celebrate.
  • Live onboarding (early in the week): Claude Code (20 min) → GitHub workflow: clone, commit, push (20 min) → live build demo (30 min) → Q&A (20 min)
  • Day-before reminder with full schedule
  • 🟢 Friday June 5 — Build Day (13:00–23:00 ICT / 08:00–18:00 CEST)

Day-of schedule

Anchored on Chiang Mai afternoon for maximum timezone overlap.

🇹🇭 ICT 13:00–23:00
🇪🇺 CEST 08:00–18:00
🇬🇧 BST 07:00–17:00
🇵🇭 PHT 14:00–00:00
13:00
Kickoff callRules, schedule, tips, and why this matters. 20 min.
13:30
Build startsTeams go heads-down. Tech + Innovation leads available in #ai-hackathon-help.
17:00
Mid-session check-inOptional 10-min standup. Each team: what are you building, what’s blocking you?
17:15
Build continuesFinal push. Commit code to GitHub. Start prepping your demo.
21:30
Code freezePush final commits. Record a backup video of your demo in case of tech issues.
22:00
Demo session5 min per team: show it working, explain the problem, take questions.
22:45
Voting & winnersPeer vote + judge panel. Prizes announced.
23:00
Wrap-upCelebrate. Every team has infra to ship — deploy what you built.

Every participant needs