What a Mate & Build is
A Mate & Build is a practice.
You take an afternoon — or an hour, if the problem is well bounded — grab something concrete from your work, and build an MFP: a minimum functional product. Something basic, but working. Something you can use the next day, even if it's missing things.
You do it alone, with a teammate, with a peer from another team, or with someone who's already done a few. Then you document it so the rest of your company can replicate it.
It's not a course. It's not a consultancy. It's not content. It's real construction, inside the work, with AI alongside.
Why run a Mate & Build
It's learned by building with it. Every hour you spend consuming content about AI is an hour you didn't spend using it on something that's actually yours.
In-house courses give you generic knowledge you don't apply to anything. Your concrete problem forces you to make real decisions. That's where the learning happens.
When someone on your team sees you solve something in an afternoon with AI, they want to do their own. Then someone from another team shows up. That's how real change starts inside a company: from the inside out, one MFP at a time.
A workflow, a system of skills, a file system (in Spanish) — what you build keeps getting used the next day, and you can hand it off to the team. It doesn't evaporate like a four-hour module.
Another person at your company with the same problem saves months if they see how you solved it. Internal documentation multiplies the value of the session many times over.
Not when you have more time. Not when your company launches an AI initiative. When you have the problem in front of you and one free hour.
The principles
Solving "build a chatbot for any industry" teaches nothing. Solving "cut from three hours to thirty minutes the report I send every week" teaches everything.
The session ends with something you can actually use — even if it's basic, even if it's missing features. An MFP is the minimum unit of a Mate & Build. If it can't be used the next day, it's not a Mate & Build.
An AI with structured context next to it becomes a system. An AI with one long prompt trying to do everything is unstable magic. Build structure, not commands.
The prompts, the code, the exact times, the things that didn't work — all open, at least inside the walls of your company. Opacity is what keeps most people out. Transparency is what builds teams that learn together.
If it can't be started and finished in one afternoon — or one well-bounded hour — the problem is poorly framed. Cut it down until it fits. Speed isn't a compromise, it's a discipline.
What you built on your table has to be buildable on any other table at your company. If it depends on a secret tool or an impossible setup, it doesn't qualify.