Mario García Segovia
Professional video editor. Brings the craft and the client work, and decides what the tools have to do to be worth using.
AI video editor · in development
We are a two person studio: a professional video editor and an engineer. We edit for clients today, and we are building the editor we always wanted, built on Claude, that learns how each client works and takes the slow, repetitive parts of the job off the editor's desk.
→ tag_clips(bin: "SEQ 01")Bin ready: clips tagged by shot size, subject and sound.00:00:08:12The product
Many of the hours in an edit go to work that is not creative: logging footage, hunting for the right clip, syncing, renaming, exporting one more version.
Every client has a tone, a format and a set of rules. Editors apply them by hand, project after project, and the knowledge lives in their heads.
A studio can take on only as many projects as its editors have hours. Hiring is the only lever, and for a small team it is an expensive one.
What we are building
An AI video editor that works next to the editor, not instead of them.
It is designed to keep a profile of each client, with their tone, pacing, formats, brand rules and past feedback, and to use it at every stage of the work, from sorting the raw material to the final export. The editor keeps every creative decision: each suggestion arrives as something to apply or discard. The software does the searching, sorting, drafting and checking, so a small team can deliver more work without lowering the standard.
00:00:21:03How it works
The editor covers the full job, not a single feature. Each step hands its work to the next one, like clips on a sequence.
Clips, music and images are indexed and described as they come in, so the material for any idea is a search away instead of an afternoon of scrubbing.
From the brief and the material available, it drafts a two column script and a structure for the piece, in the client's voice and format.
The structure becomes a shot by shot storyboard, matched to real clips from the library where they exist and flagged where a shot is still missing.
A first assembly is laid out on the timeline following the storyboard. The editor refines it, with the tedious placement work already done.
Feedback is pinned to the timeline, turned into a clear list of changes, and remembered for the client's next project.
Repetitive finishing work, such as versions for each platform and exports, is automated and checked against the client's delivery specs.
00:00:39:20Technology
The core of the editor runs on the Claude API from Anthropic. We use Claude for the parts of editing that depend on judgement and language rather than pixels: understanding a brief, reasoning about material, and writing.
Interprets the brief and the client profile, and decides how a piece should be structured before anything touches the timeline.
Analyses footage and transcripts to work out what each clip contains, what it is good for and where it fits.
Writes scripts, shot lists and storyboards in the client's voice, ready for the editor to review and change.
Coordinates the mechanical parts of the workflow, calling our own editing tools to organise, assemble, version and export.
Developed with Claude Code.
Claude Code is where our engineering happens. It is how a team of two can build an editor and a set of internal tools while still delivering client work: the engineer designs the system and decides what goes in, and Claude Code does much of the writing, testing and refactoring. This website was built with it too.
{
"name": "place_clip",
"description": "Place a clip from the bin on the timeline.",
"input_schema": {
"type": "object",
"properties": {
"clip_id": { "type": "string" },
"track": { "type": "string", "enum": ["V1", "V2", "A1", "A2"] },
"record_in": { "type": "string", "description": "SMPTE timecode" },
"source_in": { "type": "string" },
"source_out": { "type": "string" }
},
"required": ["clip_id", "track", "record_in"]
}
}
Claude and Anthropic are trademarks of Anthropic, PBC. by Fuente is an independent company and is not affiliated with, sponsored by or endorsed by Anthropic.
00:00:58:07Services
Before it was software, it was our job. We edit video professionally for clients, and that work funds the development of the editor. It is also where the product gets its direction: every tool we build starts as a problem we hit on a real project.
From raw footage to the finished piece: selection, structure, pacing and rhythm.
Finishing work, and delivery in the formats and aspect ratios each platform requires.
A clear review process, with every change tracked from the first cut to the approved version.
Images and video created with AI for art direction, design and visual assets, finished by a professional editor.
00:01:04:21Private engagement
A system we built individually for one client, a gaming content creator, under a private engagement. We keep the client anonymous. It runs the same idea as our editor, end to end: Claude decides the edit, and code carries it out with ffmpeg.
One click downloads the original video, a light copy for analysis, the audio and the chat. Each match in the stream is detected, and only wins go forward.
Word level transcription, the game HUD read frame by frame, fights and dead time, chat activity, and shouts measured in the audio. The loudest one becomes the candidate for the hook.
Claude writes the plan scene by scene: what stays, what goes, every zoom, sound, subtitle and emote. Code applies the creator's rules the same way every time, and never cuts the creator's voice.
Automatic rule checks, a self check where Claude justifies every cut by citing what is seen or heard, and an independent review by a second Claude model against the data. Then a render from the original on the GPU.
Notes are left at the exact frame of the video. Claude fixes only what the notes say, starting from the approved plan, and each note becomes a rule for the next videos.
| Scene | Action | Source in | Source out | Notes |
|---|---|---|---|---|
| 01 | HOOK | 02:41:07:12 | 02:41:12:03 | loudest shout · sfx |
| 02 | INTRO | channel intro | ||
| 03 | KEEP | 00:12:30:00 | 00:14:02:10 | zoom: chat · sfx: kill ×2 |
| 04 | CUT | 00:14:02:10 | 00:15:48:00 | no voice, no action |
| 05 | KEEP | 00:15:48:00 | 00:16:20:05 | mistake · b&w + sound |
| … | ||||
| 41 | END | 00:41:55:00 | 00:42:10:00 | VICTORY |
The gate is the only path to the delivery folder. If any step is missing or a test fails, it delivers nothing.
Vertical Shorts up to 59 s with the creator's camera on top and the game below, thumbnails judged together with the title, and long compilations across several streams.
One heavy job at a time. A new kind of error stops the run and alerts a person. Nothing specific to one stream is written into the code, and spend on external models has a daily cap.
First delivery sent: a long video, two Shorts and a thumbnail. The client review is under way and the system keeps running, raising the quality in the meantime.
00:01:11:15Roadmap
No dates we cannot keep. This is the order we are working in.
Phase 1 · In progress
Automations for the repetitive parts of our own editing work, built and tested on client projects, including a full automated pipeline for one client.
Phase 2 · Next
The editor opens to a small group of first clients, who use it on real projects with us alongside.
Phase 3 · Later
A version that learns each client's style, formats and feedback, and adapts the whole workflow to them.
00:01:24:02Team
Professional video editor. Brings the craft and the client work, and decides what the tools have to do to be worth using.
Designs and programs the editor and the internal tools, on the Claude API and with Claude Code.
00:01:32:18Contact
For the private beta, for an editing project, or to talk about what we are building.