- Half Day · one team
- Full Day · several teams
In-company buildathon
One day where your teams build with AI on their own processes. In the afternoon there are live demos and everyone takes home what they built.
What a buildathon looks like →
Your team works on the company's real problems, with expert AI mentors by their side, and ends the day with something functional and scalable.
// builders, not consultants









One day where your teams build with AI on their own processes. In the afternoon there are live demos and everyone takes home what they built.
What a buildathon looks like →After the day, we join your team and build what comes next with your people, week by week.
How we join in →Hit pause. Give your team
a day to build what they've been putting off.
Half DayOne team, half a day, one problem in depth.
Full DaySeveral teams in parallel, a full day, demos at the end.

Full Day · Friday, July 3, 2026
Seven areas of the same company building at the same time, with live demos at the end.

One morning · Saturday, June 20, 2026
Six teams from different companies, in the same room, turned problems from their work into working flows in one morning.

Full Day · Friday, October 9, 2026
Agents for sales reports, automated invoicing and digging into metric drops.
You have more opportunities than hands to execute them. We join your team and build them together.
Three fronts. Start with the most urgent one.
Teams
We raise the AI level team by team, until they build on their own.
If your team is already stretched thin and growing means hiring.
Growth and operations
We define which processes change, which growth opportunities open up and what we build first.
If the opportunity is now and the roadmap is already full.
Company brain
You ask the AI you already use and it answers with context, telling you where it got it from.
If you've grown and now there are tools everywhere, manual processes and questions nobody can answer.
So growing doesn't depend only on how many people you can hire.
See how we work month to month →A build is something we make and leave working, published with what it does and how.


Mercado Libre
Building each seller's status by hand, every monthYou ask in plain language and get a dashboard that says where to push


TurismoCity × Despegar
Checking campaign spreadsheets by handThe report lands in Slack, summarized, every morning


Skipit
Setting up every new merchant by handAn agent does the setup on its own, inside Skipit Pay


PedidosYa · PeYa Wallet
Reading every piece of competitor newsOnly what matters arrives, already analyzed


Team UdeSA · Corte
Looking for new clients by handFinds the company and the decision maker, and writes the message


Team UdeSA
Twenty open tabs to understand a marketTop 5, insights, actions and sources, by email

Calm
Calm's first Buildathon: +30 challenges proposed by the teams, +15 solutions working, +20 hours a week freed from operational tasks.

Fardo
A 14-person company brought its problems and left with three agents running.



Fima · Banco Galicia
Three stuck marketing processesAll three unblocked in one afternoon

deRentas
Logo, palette and campaigns, but no systemA brand system an agent can use

The scenes on this page: the request, the work and the product running, built with the pieces of the Design System.
Theory and other people's cases.
Leaves judgment, not lasting capability.A diagnosis and a plan.
Expensive, slow, and leaves little in your people.Hiring AI profiles.
Takes months to put together.We don't hand you an AI roadmap to execute: we execute it with you.
Lasting capability, without the fixed cost.
Pato IturraspeFounder · Mate & Build 🧉
Mate & Build is a team of senior builders, and in every company we train the people who keep building inside. That's what lets us run a buildathon with every area at once and stay afterwards.
Mate & Build was founded by Pato Iturraspe, who comes from marketing and growth at LATAM unicorns and builds with AI every week, in public. Pato has always been the one who understands the problem before the solution, and with AI that turns out to be exactly what's needed.
Every week Pato documents the builds on @patoiturraspe_ and on LinkedIn: AI experiments, mistakes and the systems that come out of them.
No. Teams build with AI on their own work, with someone by their side. What you need is a real problem that eats time every week.
Almost always with a buildathon: in one day you see what your people can build and where the value is. If you want to go slower, Arranque is two sessions so the team starts using AI with judgment. We figure it out together on a 15-minute call.
The team that learned to build, every flow written in five steps, and the access in your name. If it can't be explained in five steps, it doesn't get automated.
At a buildathon, the same day: every team closes the afternoon with its demo working. Working month to month, we first define the scope and the quick wins: within the first weeks something is already running.
We build on secure services like AWS, Supabase and Vercel, and the data stays protected with per-user access. Control always stays on your side: you keep using what we built after we're done.
A 15-minute call to see where you stand and where to start.
Pato replies, not a bot.