AI video editor · in development

Professional video editing, accelerated by AI and adapted to each client.

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.

by Fuente editor · demo_project / SEQ 01 Interactive demo
Binclick to insert
Program1920×1080 · 25p
00:00:00:00
00:00:00:00 16:9
Assistantscripted demo
→ tag_clips(bin: "SEQ 01")Bin ready: clips tagged by shot size, subject and sound.
Cut · 00:00:19:12Dead air before the detail shot. Trim 1 s 12 f to keep the pace?
DeliveryPrepare the 9:16 version for vertical platforms?
Ask me for something: “add a flash”, “black and white”, “cut here”…
lower_thirdTITLE
SH01 fountain_wideSH02 fish_closeSH03 pool_detailSH04 end_card
Try it Click or drag on the timeline to scrub, press space to play or pause, click a clip in the bin to insert it, select a clip and press Delete, or ask the assistant. Its replies are scripted in this page and no AI model is connected: it shows how the editor is designed to work, not a screenshot of the product, which is in development.

00:00:08:12The product

Professional editing is slow, repetitive and hard to scale.

loggingscrubbingsyncingrenamingexporting

Slow

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.

brand rulesformatslower thirdsversions

Repetitive

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.

one editorone timelineone project at a time

Hard to scale

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 whole editing workflow, in six steps.

The editor covers the full job, not a single feature. Each step hands its work to the next one, like clips on a sequence.

  1. 01 · Resources

    Find and organise resources

    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.

  2. 02 · Script

    Script and structure

    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.

  3. 03 · Storyboard

    Storyboard

    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.

  4. 04 · Assembly

    Assisted edit

    A first assembly is laid out on the timeline following the storyboard. The editor refines it, with the tedious placement work already done.

  5. 05 · Review

    Client review

    Feedback is pinned to the timeline, turned into a clear list of changes, and remembered for the client's next project.

  6. 06 · Delivery

    Postproduction

    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

Built with Claude.

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.

Input

Material and brief

  • Footage and transcripts
  • Music and images
  • The client's brief
  • The client profile
Claude API

The reasoning core

  • Understands the brief
  • Analyses the material
  • Writes scripts and storyboards
  • Calls our editing tools
Our tools

Editing engine

  • Bin and search
  • Timeline assembly
  • Versions and exports
People

Editor and client

  • Apply or discard
  • Review and approve
  • Feedback updates the profile
Reasoning

Understands the job

Interprets the brief and the client profile, and decides how a piece should be structured before anything touches the timeline.

Analysis

Reads the material

Analyses footage and transcripts to work out what each clip contains, what it is good for and where it fits.

Generation

Drafts scripts and storyboards

Writes scripts, shot lists and storyboards in the client's voice, ready for the editor to review and change.

Automation

Runs the repetitive steps

Coordinates the mechanical parts of the workflow, calling our own editing tools to organise, assemble, version and export.

How we build it

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.

Tool definitionJSON
{
  "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"]
  }
}
A simplified example in the tool format of the Claude API: the kind of action Claude can request from the editor, which the editor then carries out. Illustrative, not our production code.

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

What we do today.

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.

  • EDIT

    Video editing

    From raw footage to the finished piece: selection, structure, pacing and rhythm.

  • POST

    Postproduction and delivery

    Finishing work, and delivery in the formats and aspect ratios each platform requires.

  • REVIEW

    Reviews with you

    A clear review process, with every change tracked from the first cut to the approved version.

  • ART

    AI art and design

    Images and video created with AI for art direction, design and visual assets, finished by a professional editor.

00:01:04:21Private engagement

From a stream that lasts hours to videos ready to publish.

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.

InOne live stream, hours long
Out1 long video · 2 vertical Shorts · thumbnails
Before delivery5 checks, or nothing ships
  1. 01Source

    A live stream that lasts hours

    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.

    videoaudiochat
  2. 02Analysis

    Measured automatically, locally

    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.

    transcriptHUDfightschataudio peaks
  3. 03Direction

    Claude directs the edit

    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.

    scene planfixed structurehouse rules
  4. 04Checks

    Nothing ships unchecked

    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.

    lintself checksecond modelGPU render
  5. 05Review

    The client has the last word

    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.

    timecoded notestargeted fixesrules that learn
Edit plan · written by Claudeexcerpt
SceneActionSource inSource outNotes
01HOOK02:41:07:1202:41:12:03loudest shout · sfx
02INTROchannel intro
03KEEP00:12:30:0000:14:02:10zoom: chat · sfx: kill ×2
04CUT00:14:02:1000:15:48:00no voice, no action
05KEEP00:15:48:0000:16:20:05mistake · b&w + sound
…
41END00:41:55:0000:42:10:00VICTORY
Illustrative excerpt with made up timecodes, to show the shape of the plan, not the client's material.
Delivery gatePass
  • Lint: every house rule checked
  • Self check: every cut justified
  • Independent review: a second Claude model
  • Render from the original, on the GPU
  • Delivery gate: all tests pass, old copy removed

The gate is the only path to the delivery folder. If any step is missing or a test fails, it delivers nothing.

Other formats

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.

Fixed limits

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.

Status

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

Where we are, and what comes next.

No dates we cannot keep. This is the order we are working in.

  1. Phase 1 · In progress

    Internal tools

    Automations for the repetitive parts of our own editing work, built and tested on client projects, including a full automated pipeline for one client.

  2. Phase 2 · Next

    Private beta

    The editor opens to a small group of first clients, who use it on real projects with us alongside.

  3. Phase 3 · Later

    Adapted to each client

    A version that learns each client's style, formats and feedback, and adapts the whole workflow to them.

00:01:24:02Team

Two founders. One edits, one engineers.

Co-founderCAM A
Video editor

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.

editingpostproductionclient reviewsAI art
Co-founderCAM B
Engineer

Alex de la Fuente Trenado

Designs and programs the editor and the internal tools, on the Claude API and with Claude Code.

Claude APIClaude Codetoolingautomation

00:01:32:18Contact

Write to us.

Export · Contact

For the private beta, for an editing project, or to talk about what we are building.