AI hackathons for internal teams
Your team should leave with something they built.
I run working sessions where people use AI on the jobs they already do. They learn by building, find out where the tools break, and leave with a prototype they can explain because they made it themselves.
Why I run them this way
I have led people analytics, talent technology, and AI enablement from inside organizations. I have sat through the polished demos and watched teams struggle to connect them to Tuesday morning.
A useful hackathon starts with the team's own work. Recruiters might build around candidate follow-up, while an operations lead takes on intake and routing. Finance might test a reporting workflow. Each problem is familiar to the people solving it, even when the tool is new.
How the day gets built
- 01
I learn how the team works
Before the event, I talk with people across the team and find a short list of recurring problems they understand well enough to improve.
- 02
The team builds
Small groups choose one problem, learn the tools they need, and make a working first version. I teach, troubleshoot, and help each group keep the scope realistic.
- 03
We decide what happens next
Every group demonstrates its work. I document what was built, what it would take to keep using it, and who should own the next step.
A recent team build
An operations team built a working support workflow in three days.
During an AI enablement workshop for AC Brands, the team mapped its own use cases and built a workflow that triaged customer emails and routed the work into Asana. They left with a working automation and a pattern they could reuse elsewhere.
“I went from knowing very little about how AI tools could be leveraged in my day to day to actively thinking about different automations that could be used to save us time.”
Tool partners
I am a solutions partner for tools including Lovable, Lindy AI, and Emergent. That gives me another route for getting non-technical teams from an idea to working software during the session. I choose the build surface around the team and the problem.
- Lovable
- Lindy AI
- Emergent
Typical shape
Half-day, full-day, or multi-day depending on the scope. Sessions can be on-site or virtual, usually with 8 to 40 people. Preparation and a written debrief are part of the work.
Tell me who will be in the room and what they do.
I will suggest a format and tell you what needs to happen before the build day.
Plan a hackathon