Green Tomato Media × 2026
GTM AI Build Day
One day. Claude Code. Small teams. Real tools.
$ claude "solve my problem"
Format
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.
Judging
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?
15%
Team collaboration
Did non-tech members shape the problem and solution?
PASS
Working demo
Must run live during demo. No working demo = not eligible for prizes.
Prizes
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
Timeline
4-week plan
Guides pinned from day one: Claude Code, GitHub, Cloudflare, Skills. Self-serve — no session needed.
1 — Announce & Get Started
Week 1 · T−4 weeks
Launch announcement, open sign-ups, pin all the getting-started guides. People set up on their own time.
- Post announcement in #general — CEO-level signal
- Create #ai-hackathon channel, open team sign-up form
- Pin guides: Claude Code app download, GitHub basics, Skills
- Present the Cloudflare platform — what’s available, how deploy works
- Tech anchors available in channel to unblock setup
2 — Showcase 1: What We Built
Week 2 · T−3 weeks
Team members who’ve already built with Claude Code show real problems they solved. Before/after, what surprised them, what they’d do differently. Proof it works — from people who aren’t engineers.
- 3 short demos: the problem, the build, the result
- Intro to Skills — what they are, how to use and create them
- Q&A — what was hard, what was easy, how long did it take
3 — Onboarding: MCP Connectors & Deploy
Week 3 · T−2 weeks
Hands-on sessions. MCP connectors, GitHub, Cloudflare deploy. Hands on keyboard, not watching.
- MCP connectors: Slack, Sheets, Notion, APIs — live, everyone follows along
- Deploy: push a project to Cloudflare, end to end
- By end of week: every participant has shipped at least one thing
4 — Showcase 2: Everyone Builds
Week 4 · T−1 week
Technical showcase then hands on keyboard — everyone builds something together. Teams lock their problem and prep for build day.
- Technical deep-dive: advanced workflows, what the infra gives you
- Everyone builds: hands on keyboard, 30 min, tech anchors floating
- Teams lock problem statements by Friday
- Day-before reminder with schedule
🟢 Build Day
The Day
One afternoon-to-evening session. Build, demo, celebrate.
- MC the day — kickoff, mid-session check-in, demos
- Tech support roving between teams
- Demos + prizes
Build Day
Day-of schedule
Anchored on Chiang Mai afternoon for maximum timezone overlap.
🇹🇭 ICT 14:00–22:00
🇪🇺 CEST 08:00–16:00
🇬🇧 BST 07:00–15:00
🇵🇭 PHT 15:00–23:00
14:00
Kickoff callRules, schedule, tips. CEO: why this matters. 20 min.
14: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.
20:30
Code freezePush final commits. Record a backup video of your demo in case of tech issues.
21:00
Demo session5 min per team: show it working, explain the problem, take questions.
21:45
Voting & winnersPeer vote + judge panel. Prizes announced.
22:00
Wrap-upCelebrate. Every team has infra to ship — deploy what you built.
Prerequisites
Every participant needs
- ☐ GitHub account (free) — for committing and sharing code
- ☐ Claude Code app installed — download from
claude.ai/download - ☐ Claude Team account access (provided by your org admin)
- ☐ Watched the onboarding recording (if you missed the live session)
Communications
Ready-to-send messages
Click each to expand. Copy and adapt.
▸ Announcement — CEO kick-off #general
Week 1🟢 Announcing GTM's First AI Build Day Team, We're running an internal AI hackathon and everyone is invited — technical or not. 📅 Date: [DATE] ⏰ Full day (14:00–22:00 ICT / 08:00–16:00 CEST) 🛠️ Tool: Claude Code 👥 Teams of 2–3 people The idea is simple: form a small team, pick a real problem from your daily work, and use Claude Code to build a tool that solves it. In one day. You don't need to be a developer. You need to be curious and willing to try. We'll run an onboarding session beforehand to get everyone comfortable with the tools. Why are we doing this? Because AI isn't just for the tech team. Every department has repetitive tasks, manual processes, and ideas that never get built. This is your chance to build them. 🏆 Every project can ship to production — infra is provided for all teams. More details coming soon in #ai-hackathon. Start thinking about what annoys you most in your workflow — that's your project idea. — CEO
▸ Team sign-up prompt #ai-hackathon
Week 2👋 Team sign-ups are open! Form your team (2–3 people) and fill out this form: [LINK] What we need: • Team name (have fun with it) • Members (name + department) • Problem idea — one sentence on what you want to build Tips: → Mix it up. Best teams have someone who knows the problem + someone who can drive Claude Code. → Don't overthink the idea. "I waste 2 hours a week doing X manually" = perfect project. → Solo? Post here and we'll match you. Need inspiration? Here are some example ideas: • A script that checks all our YouTube thumbnails against best practices • A tool that generates weekly SEO status reports from a CSV export • A Slack-ready summary bot for long meeting transcripts • A bulk content quality scorer for our affiliate pages • An internal FAQ chatbot trained on our company docs Deadline to sign up: [DATE]
▸ Onboarding session invite #ai-hackathon
Week 2🎓 AI Build Day — Onboarding Session This is the session that'll make your hackathon 10x better. Don't skip it. 📅 [DATE] at [TIME] ICT 📍 [ZOOM/MEET LINK] ⏰ 90 minutes What we'll cover: 1. Claude Code from zero — what it is, how to talk to it (15 min) 2. GitHub essentials — clone, commit, push. That's all you need. (20 min) 3. Live build — I'll build a working tool from scratch while you watch (30 min) 4. Q&A + fix your setup (25 min) ⚠️ Before the session, please: ✅ Create a GitHub account (github.com) ✅ Install the Claude Code app from claude.ai/download ✅ Open the app and sign in with your Claude Team account Can't make it live? We'll record it and pin the video here. This is genuinely the most important 90 minutes for non-technical folks. You'll go from "I've never used a terminal" to "I can build things." I've seen it happen.
▸ Day-before reminder #ai-hackathon + #general
Week 3🟢 AI Build Day is TOMORROW Quick checklist: ☐ Claude Code app installed (claude.ai/download) ☐ GitHub account ready ☐ Claude Team account logged in ☐ You know your team and your project idea Schedule (all times ICT / CEST): 14:00 / 08:00 — Kickoff call 14:30 / 08:30 — Build starts 17:00 / 11:00 — Mid-session check-in (optional) 20:30 / 14:30 — Code freeze 21:00 / 15:00 — Demos (5 min per team) 21:45 / 15:45 — Voting & prizes 🏆 Pro tips for tomorrow: → Start with "claude, help me build [simple description of your tool]" → Don't try to build everything. Build one thing that works. → Commit to GitHub often. Don't lose your work. → Ask for help early in #ai-hackathon-help See you at 14:00 ICT. Let's build something cool. 🚀
▸ Post-event recap #general
Day after🏆 AI Build Day Recap What a day. Here's what [X] teams across [X] departments built in one day: 🥇 [Team Name] — [Project description] 🥈 [Team Name] — [Project description] 🥉 [Team Name] — [Project description] Other standout projects: • [Team] built [tool] — [one-line description] • [Team] built [tool] — [one-line description] The numbers: • [X] teams participated • [X] working tools built • [X] departments represented • [X] people used Claude Code for the first time What happens next: → All projects can ship — infra is provided, deploy on day one → All project repos are in [GitHub org link] — explore, fork, improve → Demo recordings: [link] Huge thanks to everyone who participated, and especially to those who stepped outside their comfort zone. This is how we build an AI-native company — one useful tool at a time. — The AI Build Day team