CASE STUDIES
What we built, and what it did.
Phillipe, the AI video editor One1 Studio builds, is our lead case study. The earlier projects below come from the studio’s AI implementation work. Each entry says what was built, what was reported, what was not measured, and why the same result should not be assumed elsewhere.
Phillipe, the AI video editor for creators.
One1 Studio builds Phillipe, co-founded by Max Ferrer and Sebastian Gonzalez Capdevielle, a professional video editor who has edited for brands and creators like Whop and Clix. Max couldn’t find an AI video editor that made videos look good, so he built one. It worked, but it lacked an editor’s touch, so Max and Sebastian taught it the way Sebastian teaches his students and iterated until it produced a decent edit. Together they built an AI editor that doesn’t just edit videos. It edits them with taste.
A person uploads footage of themselves talking and optional supporting footage, picks a style and starts the edit with one click. Phillipe cuts pauses, filler and repeated takes, places supporting footage on spoken moments, and returns a rough cut for review before adding word-timed captions and music. Changes are requested in chat.
The edits are built to look designed rather than simply captioned: word-by-word kinetic typography, text set behind the speaker and B-roll on the spoken beat.
This is the studio’s own product rather than a client engagement, and no user, revenue, or time-saved figures are claimed for it. It applies the same method as the client work below: one narrow job, human review before the expensive step, and a visible cost estimate before every edit.
Read the complete Phillipe product case study or try Phillipe free.
An assistant adopted across 50 Skool communities.
Community owners could invite the assistant into Skool. It used approved community knowledge to answer member questions and supported engagement-post and page-testing workflows. Reaching 50 communities demonstrated adoption across multiple knowledge environments.
The total number of individual community members who used it was greater than 50 but was not recorded. The project was temporary and was never monetized, so it should not be presented as a revenue case study.
Competitor research and two daily LinkedIn posts.
An anonymized vitamin company used a system that researched competitor posts, collected current company information through Slack, and prepared two LinkedIn posts each day.
The client reported approximately four hours saved each week and a three-percent increase in revenue during the relevant period. The company cannot be named. The revenue change was client-reported, was not independently audited, and cannot be attributed to the system alone.
Evidence is not a guarantee.
Results depend on the workflow, team, data, adoption, implementation quality, market, and measurement method. One1 Studio uses project evidence to explain its process and limitations, not to promise that another organization will reproduce the same outcome.
Where a fact comes from a client report rather than independent measurement, the page says so. Where a count was not recorded, it is not invented later.
GREAT EDITS. NO PROMPTING.