Give your team the time and space to build agents on the use cases relevant to their day-to-day.

A marketing hackathon is an event, anything between a few hours and a few days, where marketers build an agent for a real use case and then show it.
Marketers acquire agentic skills by building on their own work and by seeing what their peers build.
The success factors are a clear brief, the right people in the room, access and connectors sorted beforehand, real context, coaches on hand and the showcase.
Some hackathons are competitive with judges and a prize; others are collaborative, and building is the win.
We ran our first Agentic Marketing Hackathon in November 2026: teams of 3 or 4, a briefing kick-off on Monday, two days to plan and a build evening on Thursday.
A marketing hackathon gives marketers what they rarely get at work: protected time to build agents on the use cases that eat their week. Everyone brings one task they repeat, builds an agent that automates it and shows the result to the room.
What is a marketing hackathon?
A marketing hackathon is an event where marketers build an agent for a real use case, test it on real inputs and present what they built.
Each participant brings a use case that currently takes too much of their time: the weekly performance report, turning one webinar into a week of LinkedIn posts, the monthly competitor round-up, the creative brief for the next batch of Meta ads. They build an agent that does the work, run it on real inputs and show the room what works and what doesn’t yet.
The word comes from software teams: hack (build fast) plus marathon (keep going until it works). Marketing hackathons borrow the format and point it at marketing work. People build alone or in small teams, in person or virtually, over an evening, a full day or several days. Some hackathons have judges and a prize. Others have no ranking at all, and every build gets shown.
Why run a hackathon for your marketing team?
A hackathon gives marketers protected time and a safe space to build agents and acquire agentic skills on their own work, alongside their peers.
It reinforces the time and space to build. Most marketers already know which tasks they’d hand to an agent. What they don’t have is 2 or 3 uninterrupted hours to build one. A hackathon puts that time in the calendar, away from the inbox, with clear permission to experiment.
Marketers learn by building. Building an agent on your own use case teaches context, connectors, skills and quality control in a way no slide deck can. The blockers come up in the room, and they get solved in the room with the help of experienced coaches or colleagues.
Peer learning is the best learning. Seeing what other marketers build shows what’s possible in your own work. Plus, it’s a great opportunity for more experienced colleagues to informally coach their peers.
The agent goes back to work. Every participant leaves with a first version of an agent on a real use case, tested on real inputs and ready to improve the next day.
What do you need to decide before a marketing hackathon?
Before a hackathon, decide the format: who builds, for how long, in person or virtual, on which tools and whether there’s a prize.
Decision | Options | What to consider |
|---|---|---|
Who builds | Individuals, or teams of 2 to 4 from the same company | Teams share the work and take the agent back to the same workflow; individuals go deeper on their own use case |
How long | An evening, a full day or several days | An evening is enough for a first working agent; a full day adds use case identification and workflow mapping |
Where | In person or virtual | In person brings energy and faster peer learning; virtual opens the room to more marketers |
Which tools | The tools each company has approved, or one shared tool | Approved tools mean the agent survives the next day; one shared tool makes coaching simpler |
Prize or no prize | Competitive with judges, or collaborative with no ranking | A prize drives pace; no ranking makes people share what went wrong as well as what worked |
What are the success factors of a marketing hackathon?
The success factors of a marketing hackathon are a clear brief, the right people, access sorted beforehand, real context, support in the room and time to show the work.
1. Set a clear brief
A clear brief names the output in one sentence, for example: build an agent that automates one process you run every week.
A simple test: if you do it more than three times, it’s worth an agent.
It’s impactful to share a list of use cases that other marketing teams have built, for inspiration.
2. Curate the room and invite the right people
Who is in the room decides what gets built. Mix disciplines (content, performance, brand, CRM), job levels and agentic AI experience.
Invite marketing leaders to build, not to observe. When a CMO builds alongside the team, the permission to experiment is obvious to everyone. Inside each team, make sure the most confident builder doesn’t take over the keyboard.
3. Run a kick-off a few days before
Run a one-hour kick-off call a few days before the hackathon. Discuss the logistics and inspire your team: a talk from a company already running agents in production shows what good looks like, or colleagues can share what they’ve already built.
4. Sort tool access and connectors beforehand
Check that every participant has the approved tools, the right licences and the connectors switched on before the day. Waiting for access on the day can cost an hour of building. Where connectors aren’t approved, manual uploads, scripts and publicly available information keep content use cases moving.
Connectors decide which use cases are possible. A performance reporting agent needs GA4 or the ad platforms. A content agent needs Google Drive, SharePoint or Notion, where the briefs and brand guidelines live. A competitor monitoring agent needs a scraping tool such as Apify.
5. Bring the context
AI is as powerful as the data you feed it. Ask every participant to bring their brand guidelines, tone of voice, current briefs and templates and high-quality past outputs for their use case. During the build, the model dissects what makes them work, down to lexicon and syntax, and the skill is built from that.
Keep anything confidential out of the showcase.
6. Have support in the room
Put AI Coaches in the room who know both the tools and marketing. Coaches guide; they don’t build for the participants. They clear blockers, pull builds that have grown too wide back to one use case and check the quality of the output.
Good coaches can be external, or your internal AI champions can play the role of AI Coaches on the day.
The role of the AI Coach is to guide the build with questions:
What problem are you solving, and for whom?
Walk me through how this works today, step by step.
Which 2 or 3 steps could you build today?
What does a good output look like? Do you have 3 examples?
Where should a human check the output?
7. Make it safe to be a beginner
Some marketers will be building their first agent; others will be redesigning their full agentic system. Welcome basic questions and unfinished builds. A first agent that half works is a real result, and the beginner who shows it often teaches the room the most.
8. Showcase for peer learning
Leave proper time for the showcase. Each build gets a few minutes: the use case, a live run of the agent, what broke and what comes next. This is where peer learning happens, so protect it even when the build runs late.
See what marketing teams built at our Agentic Marketing Hackathon.
9. Plan the week after
What happens after the hackathon decides whether the agents survive. Ask every participant to record a short video of what they built and why within a week, share it in one place and pick the next use case to build.
Capture what you learned as organisers too. Ask your coaches to record the day (a meeting notetaker such as Granola on a phone works in a noisy room) and share their notes, so the next hackathon is better designed than this one.
How we run the Agentic Marketing Hackathon
We run the Agentic Marketing Hackathon over one week, in teams of 3 or 4 marketers from the same company: a one-hour kick-off on Monday, two days to plan and a 3-hour build evening on Thursday.
Teams of 3 or 4 from the same company. Each company brings 3 or 4 marketers who share a workflow, so the agent goes back to work with the whole team. CMOs, VPs and Marketing Directors are welcome to lead and build alongside their team.
Monday: a kick-off with inspiration and clear steps. The kick-off opens with inspiration: a team already running content production with agents shows what good looks like, or a talk on building high-quality content agents shows how to get there. Then come the clear steps: the brief, the rules, the run of show and the plan every team agrees before Thursday. Everyone gets the recording in our Hackathon space.
The brief. Build a content agent that automates one process your team runs every week. We share agent ideas for inspiration: email production, landing pages, an SEO blog pipeline, LinkedIn content from webinars, competitor monitoring, weekly performance reporting and Meta Ads creatives. Each participant picks the use case that currently takes the most of their time.
The rules. Use the agentic tools your company already uses and has approved, with connectors switched on for everyone in the team before the day. We don’t provide tools or licences.
Tuesday and Wednesday: plan the build. Each team agrees on the use case they want to build an agent for.
Three roles in every team. We advise every team to have three roles:
The architect designs the workflow, step by step.
The context engineer gathers the brand guidelines, past outputs and data the agent needs.
The builder builds and tests the skills.
Thursday: build and showcase. The build is supported and guided by AI Coaches. The best use cases are showcased to everyone.
The week after. Within a week, every team records a short message or recording about what they built and why, and shares it with the group in the Hackathon space.
Join our next hackathon
We plan to run more hackathons in London and virtually. Want to join our next Agentic Marketing Hackathon? Register your interest →
FAQ
How long should a marketing hackathon be?
A marketing hackathon can be an evening, a full day or several days. An evening of about 2 hours of building is enough for a first working agent on one use case. A full day leaves room for use case identification and workflow mapping before the build.
Do marketers need technical skills for a hackathon?
No. Marketers build agents in the AI tools they already use, with skills, projects and connectors, not code. What matters is a clear use case, the right context and a coach on hand when the build gets stuck.
Should a marketing hackathon have a prize?
It can. A prize and judges add pace and competition. A collaborative format with no ranking makes people share what went wrong as well as what worked, which is where the learning is. We run ours without a prize.
How many people should join a hackathon?
It depends on the coaching you have. On 12 November 2026 we ran an Agentic Marketing Hackathon with 40 marketers in 11 teams, with AI Coaches in the room throughout.
Can you run a marketing hackathon virtually?
Yes. A virtual hackathon works when access is sorted beforehand, coaches can join breakout rooms and the showcase is protected. In person brings more energy; virtual opens the room to marketers in more locations.
Which tools do you need for a marketing hackathon?
Use the agentic tools each company has already approved, such as Claude, ChatGPT or Microsoft Copilot, with connectors switched on before the day. Approved tools mean the agent keeps working after the hackathon.


