---
title: "About Matisse Chenavas"
description: "A software engineer and the founder of MC Studio, I connect a leadership team’s vision to the realities on the ground and help teams adopt AI."
url: "https://mc-stud.io/en/about"
lang: "en"
updated: "2026-10-12"
---

About

# Matisse Chenavas

- AI Adoption Lead
- software engineer
- founder of MC Studio

I connect a leadership team’s vision to the realities on the ground, then build what is missing between the two. These days it is mostly AI: getting it adopted, properly, by teams that already have a lot on their plate.

- [LinkedIn](https://www.linkedin.com/in/matisse-chenavas)
- [GitHub](https://github.com/ZEDIUM-Off)
- [contact@mc-stud.io](mailto:contact@mc-stud.io)

![Portrait of Matisse Chenavas.](https://mc-stud.io/_astro/01-hero-portrait.CTqtA5AW_1wswFE.jpg)

Background

## My path

1. 2021
   ### A year of computer science at IUT Lyon 1
   The starting point, before choosing project-based learning.
2. 2022 to 2025
   ### Trained at 42 Lyon
   The piscine, then the common core: learning from peers and from projects.
3. 2022
   ### First developer contract
   A fixed-term API developer role in October and November: my first paid assignment.
4. Since 2023
   ### Independent software and AI engineer
   Business applications, automation, document reading, developer environments and agentic engineering training, mostly from inside my clients' teams. As a sole trader until 2025, then through MC Studio.
5. 2024 to 2026
   ### Founder of HIGHFINITY
   A first company, from November 2024 to May 2026.
6. Since 2026
   ### MC Studio
   My studio, founded in January 2026 to carry operational AI and agentic engineering under my own name.

## Right now

- I am preparing an eight-session programme to train developers in agentic engineering.
- I am building Zedflow, an engine for typed agent flows, and I use it for my own operations.
- I publish the code of the tools I use to code with agents.

How I work

## Inside your team, or a small team around the project

Most of my projects ran inside teams I had not assembled, alongside their developers. That is the setting I know best: I join your rituals, bring scoping, architecture and AI, and equip the team with agentic working methods it keeps after I leave.

Either way, you have one point of contact who says what is proven, what is not yet, and who answers for what he ships.

1. ### Embedded in your team
   I join the project team, its tools and its rituals, and ship with it. That has been the setting of most of my engagements since 2023.
2. ### Agentic methods set up in-house
   Rules written for humans and agents, skills, workflows with human approval, systematic verification: I set up what serves the team, and I train it to use them.
3. ### A small team, if the project needs it
   For a larger project, I can bring together a few independents chosen for their speciality, with a written scope and deliverables. I set the architecture, review what goes to production and stay your point of contact.

Principles

## What guides my work

1. ### Accuracy over effect
   I prefer a simple, verified solution to an impressive demo.
2. ### Open about limits
   I say what is demonstrated, what is assumed and what still needs checking.
3. ### Humans in the loop
   Systems prepare and speed things up. Binding decisions stay human.
4. ### Handover
   I document decisions and train teams so they stay autonomous.

## Let’s talk about what AI could change for you

A 30-minute discovery call, by video and with no commitment, to talk about your project, your constraints and the best next step.

[Book a call](https://calendar.app.google/VQTPrCgNvQSNwdA7A)

[contact@mc-stud.io](mailto:contact@mc-stud.io?subject=First%20call)