timbercut
Request a pilot

Autonomous revision agent for video post-production

Notes in.
Verified revisions out.

Timbercut reads every comment in a revision round, turns it into an explicit edit plan, carries out the supported changes and checks each one against the brief before anything goes back to the client. Your team keeps the calls that need taste.

Built for producers, editors and creative directors at agencies, post houses and in-house teams.

Run the sample revision round See how it works

The demo is an interactive simulation with sample data. It runs in your browser with no sign-up.

Producer instruction Theo Brandt · Team chat · Wed 09:05
“1Make the intro punchier, 2use Sarah’s comment from yesterday, 3remove the outdated pricing graphic, 4use the latest brand assets, 5prepare vertical versions, and 6make sure every request from revision round three is accounted for.”
Timbercut’s plan Sample data

  1. Tighten the opening by 20 framesR-02

    Subjective. Proposes a 20-frame tightening and asks the creative director.

    Needs approval

  2. Open on the fold and drop the skylineR-42

    Resolved to Sarah Okafor’s email, Tue 16:40: open on the fold, lose the skyline.

    Completed

  3. Remove the price cardR-01

    Matches three notes about the price card. Brief §4 excludes pricing.

    Completed

  4. Swap in Brand Kit 2026.2R-36 · R-44 · R-37

    Brand Kit 2026.2 lockup and typeface. The vertical end card is missing.

    2 completed1 blocked: missing asset

  5. Reframe for 9:16 and 4:5R-43

    9:16 and 4:5 reframes planned. Two shots need framing calls.

    Needs approval

  6. Reconcile every round 3 comment

    Every comment gets a disposition and a reason.

    48 of 48 accounted for

Round 3 · 48 comments · 5 sourcesV7 → V8

  • 34Completed
  • 6Needs approval
  • 4Duplicate
  • 2Superseded
  • 1Blocked: conflict
  • 1Blocked: missing asset

01The problem

48 notes, 5 places, one cut that has to get all of them right.

Feedback arrives as timecoded comments, chat threads, emails, call notes and a doc someone forgot to share. Some repeat each other. Some contradict the brief. One points to a file that doesn’t exist yet. Before anyone edits, someone has to work out what every note means.

  • Review link00:00:21:04

    “The price card has to go. Pricing isn’t final for the launch markets.”

    Sarah Okafor · Brand Lead

    Two more notes say the same thing

  • Review link00:00:05:12

    “Cut the fold demo. It slows the whole spot down.”

    Daniel Reyes · Product Marketing

    Contradicts brief §2.1

  • Review link00:00:00:00

    “The first few seconds still feel slow to me.”

    Sarah Okafor · Brand Lead

    Subjective. Slow how?

  • Team chatTue 14:05

    “The new vertical end card from the brand team should go on the 9:16s.”

    Sarah Okafor · Brand Lead

    File isn’t anywhere

  • Review link00:00:27:00

    “Make the logo bigger on the end card.”

    Daniel Reyes · Product Marketing

    Tried in V5. Reverted in V6.

  • Team chatMon 10:30

    “Can we raise the music under the VO? Feels flat.”

    Daniel Reyes · Product Marketing

    Overruled in Tuesday’s call

  1. 1

    Interpret

    “Punchier” isn’t an edit decision. Someone has to decide what it means, and whether the person who wrote it gets the final say.

  2. 2

    Reconcile

    Repeats, reversals and contradictions arrive days apart in different tools. The latest note isn’t always the one that wins.

  3. 3

    Prove

    When the cut goes back, the client assumes everything was handled. Without a record, nobody can say what happened to note 37.

The hard part isn’t the edit. It’s the quiet worry that the revision you just sent missed something.

02How it works

Understand. Execute. Verify.

Three jobs, in that order, every round. Timbercut does the reading, the routine edits and the checking. People keep judgment, taste and sign-off.

  1. Understand01

    Build the project picture before touching the timeline.

    Notes are read alongside the brief, transcript, representative frames, asset metadata, brand rules and revision history. Repeats are merged with every source kept. Conflicts, dependencies and missing assets are flagged up front.

    • 4 repeat notes merged, sources kept
    • Brief conflicts found before editing
    • Missing files named, with where it looked
  2. Execute02

    Turn intent into edit operations you can read.

    Each request becomes an explicit operation with its timecode, source and reason: trim, replace, remove, retime, reframe. Supported operations run through connected production tools. Anything subjective or consequential waits for a named person.

    • One reviewable operation per request
    • Subjective calls routed to an approver
    • Routine changes applied, not just listed
  3. Verify03

    Check the cut against every request and rule.

    Every change is checked against the request that caused it and the rules that govern it. The round ends with an audit that accounts for every comment: done, waiting on a decision, merged, superseded or blocked, and why.

    • Evidence attached to each check
    • Blocked checks stay blocked
    • A revision audit you can send

Walk through all six stages

03Human control

Autonomous where it’s safe. Asking where it matters.

Timbercut is designed to handle the clerical work of a round on its own and to stop at the decisions that belong to people. In the sample round, that’s 34 changes applied and 6 handed to named approvers.

Goes ahead on its own

When a change is explicit, supported, reversible and inside the brief and rules.

  • Fix a typo in a super“Foldes” becomes “Folds”. Two people flagged it; one change, both sources kept.
  • Remove a graphic the client asked to removeThe price card goes, because three notes and brief §4 agree.
  • Swap to the approved brand assetBrand Kit 2026.2 lockup, kept at the size the guidelines allow.

Stops and asks a person

When a note is subjective, changes something agreed, or carries cost or legal weight.

  • “Make it punchier”Proposes a specific 20-frame trim, marked as inferred, for the creative director to approve.
  • A change that breaks the briefBlocks the request and sets out options. Only the brief owner can approve an exception.
  • A new product claimRoutes “Folds in seconds” to legal before it touches the super.

Nothing goes to a client automatically. A person signs off on every revision.

04Creative Decision Graph

Every change remembers why it happened.

The graph records who asked for each change, where they said it, which version it touched, which rule applied and what happened next. Here is one thread from the sample campaign.

  1. V5Superseded

    Logo enlarged after a brand-team request

    Kofi Mensah, brand designer: “The logo feels small on the end card.” The lockup went from 16% to 22% of frame width. No rule was checked.

  2. V6Rule applied

    Logo corrected to the brand guidelines

    Brand guidelines 2026.2 §4.2: “End-card logo lockup: between 12% and 18% of frame width.” Back to 16%. The V5 decision stays in the history, marked superseded.

  3. Round 3Flagged, not repeated

    “Make the logo bigger on the end card.”

    Daniel Reyes asks again. Instead of repeating V5, Timbercut shows the history and proposes 18%, the largest size the rule allows, for the brand lead to confirm.

Explore the Creative Decision Graph

05Interactive demo

Resolve round three yourself.

A fictional launch film for Corvane, a fictional e-bike brand. 48 comments on V7 from 7 people. In about a minute you can run the round and see what happens to every note.

  • Filter comments by outcome, source, person or type
  • Settle a conflict with the approved brief
  • Supply a missing asset from a sample file
  • Approve or reject proposed changes
  • Compare V7 and V8 frames
  • Download the audit as JSON or CSV
Open the demo
Round 3 · after the first passSimulation
Comments
48
Unique requests
44
Applied
34
Need a person
8
  • 34Completed
  • 6Needs approval
  • 4Duplicate
  • 2Superseded
  • 1Blocked: conflict
  • 1Blocked: missing asset

Ready for the client? Not yet: 6 decisions and 2 blocked requests remain. Every comment is accounted for, but not every request is done.

06Status

What’s real today.

Timbercut is an early-stage company. Here is exactly what exists, what we’re building and what we’re not claiming.

Live on this site

An interactive simulation

The demo runs a scripted revision round on sample data, entirely in your browser. It doesn’t edit video, call an AI model or send anything anywhere.

In development

The revision agent

Project understanding, edit planning, execution through production tools and verification. Everything on the product pages describes how it’s designed to work.

Planned

Integrations

Connections to review, chat, storage and editing tools such as Frame.io, Slack, Google Drive, Notion, Premiere Pro, DaVinci Resolve and After Effects. None are live, and none are partnerships.

Not claimed

Customers and results

We don’t have customer results to show yet. When pilots produce something we can verify, we’ll publish it here, with permission.

Bring us a real revision round.

Pilots start with one of your own projects. We map where your notes come from and how your team approves work, then show you exactly what Timbercut would do with the round, and what it would leave for you.

Request a pilot Run the demo first