For creators who already have an editor

Record more. Explain less.

Watch your next video as a Footage preview before your editor starts, then send them one link: the script, a clip and range on each line, your notes. Ask your own Claude what a reference you saved did and how your best video did. When the cut comes back, your notes land on the exact second.

Claude, with ReadyToEdit connected

You: how did that reference I saved do, and how did my best video this month do?

Read 1 saved reference and 9 of your posts from ReadyToEdit

Assistant: The reference opens on the result and names the price in the first three seconds: 212k views. Your best this month, “The $15 mic that beat my $200 one”, opens the same way and reached 41k. The two that opened on a question stayed under 9k.

You: write the four-mics one that way. the fan test is 1:12 to 1:22 in the kitchen video. never call anything ‘the best’

Saved to ReadyToEdit

Assistant: Draft 1 saved, four beats. Beat 3 plays mic-test-kitchen.mov 1:12–1:22, the fan test you named. The other three have no clip yet; they stay on the page, empty. The Footage preview and the editor link are below.

Fig. 1ExampleYour own Claude, with the ReadyToEdit MCP connected. Your lines are the green ones.

On Light

Your own Claude knows your numbers.

Connect the ReadyToEdit MCP to Claude, Codex or Cursor and it works with what ReadyToEdit holds: your footage, your scripts, your audience and style, the numbers on the posts you connect, and the reference posts you saved. Ask what a reference did and how your best video did, then have it write the next script and put your clips on its lines.

  • Footage preview, before the edit

    Every clip on the script plays in order as one video, so you see the pacing before your editor opens a timeline.

  • One link for your editor

    The script, a clip and range on each line, your marks and notes. No account to make.

  • Notes on the cut

    Paste the cut’s Drive link and leave each note on the second it is about.

Start with whats-working and editor-handoff, two of the ReadyToEdit skills for Claude, Codex and Cursor. Light includes about 10 footage hours of playback a month.

How the week changes

Today’s video editing brief: a folder and a paragraph

The files reach your editor on Monday. The reasons stay in your head, and rounds two and three are spent getting them out. One week’s brief, item by item, against the draft 2 handoff in Fig. 3.

  1. 01The footage

    Today

    lorem-sound/112-four-mics/A Drive folder. Four files, no notes.

    With ReadyToEdit

    The same four files, playable in the page, and each one you kept opens from the line it goes under. They stay in your Drive.
  2. 02The order

    Today

    “kitchen test is the main one. use the good bit, keep it tight.”A paragraph in Slack, Sunday night.

    With ReadyToEdit

    The script in four beats, readable top to bottom as Whole script.
  3. 03Which ten seconds

    Today

    Not sent. It is in your head.→ asked in round two

    With ReadyToEdit

    mic-test-kitchen.mov · 1:12–1:22On beat 3, and it plays in the page.
  4. 04Why C comes before D

    Today

    Not sent. It is in your head.→ asked in round two

    With ReadyToEdit

    Your note on beat 2, added with the waveform still in draft 2: “Point at C, then at D.”
  5. 05What it must never say

    Today

    Not sent. It is in your head.→ round three, when a title card says “best”

    With ReadyToEdit

    Out of the script before your editor reads it. You said it once.
  6. 06How it plays

    Today

    Not sent. It is in your head.→ first seen in the first cut

    With ReadyToEdit

    A Footage preview you watched before sending: every kept clip in script order, played as one video.

Enclosed

Today2 of 6

With ReadyToEdit6 of 6

While you read the draft

Full plans

Your call, on the record

You read the draft with the assistant open beside it. What you tell it is kept with the draft, and every call you make on the page is marked where it happened, so the version your editor opens already carries the reasons.

Draft 1 · weekly video · Lorem Sound

Four microphones under $40, one noisy kitchen

You: leave the poll out. people voting proves nothing about sound.

Tue 10:52 · beat 1

Your call: rejected the poll

01We put four microphones under forty dollars in the loudest room we have.

  • Kept: mic-test-kitchen.mov · 0:08–0:19supporting
  • Rejected: community-poll.pnga poll proves nothing about sound

You: never call anything ‘the best’. we tested four mics in one kitchen.

Assistant: Noted: say which one held up in this room, and never “best”.

Remember thisRemembered.

Tue 11:03 · beat 2

Your call: struck “best”

02The cheapest one was not the worst. (struck: The best budget mic on every list) The one everyone recommends was.

  • your video · 12 Mar“If you buy one, buy D.” Cited because this line takes it back.
  • No clip matched this line. It stays on the page, empty, until you add one.

You: find the ten seconds where C beats D

Assistant: mic-test-kitchen.mov 1:12–1:22: same sentence, fan on. D clips on the p’s; C doesn’t.

Tue 11:20 · beat 3

Your call: kept 1:12–1:22

03Here are the ten seconds that changed our minds.

  • Kept: mic-test-kitchen.mov · 1:12–1:22supporting
  • Your note: “Play it clean. No music under this one.”

You: the hand sliding the mic closer is fine as b-roll. the proof is the close-then-far take.

Tue 11:31 · beat 4

Your call: kept both, labelled

04The setting that mattered more than the microphone: how close you sit.

  • Kept: mic-test-desk.mov · 2:25–2:38supporting
  • Kept: mic-test-desk.mov · 0:40–0:46illustrative B-roll, not proof
ApprovedDraft 2, Tue 11:47, after you put the waveform still on beat 2 · sent to your editor
Fig. 2ExampleLeft, what you told the Studio assistant while reading draft 1; right, the draft, with your calls in red and a line from each instruction to the mark it made.

What they open

What your editor opens

One read-only link, and no account to make. Change the draft and update the link: the address stays the same. Revoke it when the video is out.

  • Read-only, no account
  • Download handoff, as a text file
  • Update in place, or revoke
  • Never indexed by search engines
The editor handoff page for “Four microphones under $40, one noisy kitchen”: four script lines, each with its clip button, beside a player showing a waveform still and a list of the four evidence files.
  1. Each line with its clip. Press it and the range you kept plays.
  2. Whole script, for reading it through once before cutting.
Fig. 3ExampleThe handoff for draft 2. Beats 1, 3 and 4 carry the ranges kept in Fig. 2. Beat 2, empty in draft 1, has the waveform still you added before approving, with your note “Point at C, then at D.” The file list is the whole folder, rejected poll included.

Inside your workspace

Full plans

Your editor can ask it what they would ask you

Invite your editor into the workspace, or into one project. They browse the same library you do: every recording, the notes, your past posts. When they would message you — which take, why this order, where you said the number — they ask the assistant and get the file and the timecode.

studio — four mics · your editor

Maya was invited to Lorem Sound · browses the same library you do

You: she leads with mic C, not the ranking. is that about the fan noise or the price?

Assistant: Both. Earlier in this chat she said “open on the one that surprised us. the ranking can wait.” C is the surprise: the cheapest of the four, and it held up with the extractor fan on, mic-test-kitchen.mov 1:12.

You: where does she say how close to sit?

Assistant: mic-test-desk.mov 2:25–2:38, the close-then-far comparison. She says it once, at 2:31.

It answers from what the project holds, and says where each part came from.
Fig. 4ExampleYour editor, asking the assistant instead of messaging you. Green is whoever is typing; here, your editor.

How it finds the answer

It looks your project up every time it answers, and the answer cites what it used. What it searches:

  1. 1every line said in your recordings
  2. 2what it has seen in your footage
  3. 3your stills and screenshots
  4. 4your notes and documents
  5. 5your past posts, and what you decided in review

It has already watched and transcribed your footage, so finding a moment never means rewatching it.

Teach it your answers

  1. 01

    Remember this

    Press it under any answer you would give again. The note it would save opens right there.

  2. 02

    You keep it, or not

    Read the note, fix what is off, and keep only what is true.

  3. 03

    It is searched from then on

    The next time anyone asks, a kept note is one of the things it finds.

FutureAnswering your editor the way you would, from everything you have taught it, for the questions you have not answered yet.

Where you decide

Every call stays yours

  1. The angle

    Full plans

    Each week the Read proposes angles from what you added, on the cadence you set (Friday afternoon by default). You approve one or dismiss it. Nothing is drafted until you ask.

    Approve (chosen)Dismiss

    Proposal approved: “The one everyone recommends lost.”

  2. Each clip

    Full plans

    A suggested clip sits beside the line it would go under. Play it, then keep it or reject it. Only the clips you keep are placed in the edit your editor opens.

    ✓ Keep (chosen)✕ Reject

    Kept: mic-test-kitchen.mov · 1:12–1:22

  3. The draft

    You, or a teammate you invite to the project, request changes or approve. Each decision saves a snapshot of the draft, so you can see what changed between rounds. Changed your mind? Reopen it.

    Request changesApprove (chosen)

    Draft 2 approved, Tue 11:47, with its snapshot.

Revision memory

Full plans

The notes you stop repeating

Some corrections you make every week: cut the hype, lose the exclamation marks, write your own opening. Make the same one across drafts and it carries into the next draft, and is listed on a screen called What I’ve learned, in sentences like these.

  • “You cut the marketing words out of what I write.”

    You rewrote the sales language in “Four microphones under $40, one noisy kitchen”.

    7 drafts
  • “You’d rather state a thing than exclaim it.”

    5 drafts
  • “My openings do not survive. You write your own.”

    4 drafts
  • “You take the emoji out.”

    3 drafts

ExampleThe sentences as What I’ve learned prints them.

Before you connect anything

What it will not do

  • Edit, render or generate video, voices or avatars. The cut is your editor’s.
  • Decide which take is your best. It suggests a range; you keep or reject it, and your editor makes the exact cut.
  • Score a hook or predict views. The close read of an opening gives timestamped facts and a comparison with your own earlier openings, never a number.
  • Post your video, or post anywhere but Bluesky and Mastodon. To those two it posts a draft’s text, once you connect the account for the project and confirm the exact thread, then reads back its likes, replies and reposts. For YouTube, X, LinkedIn and the rest, you paste it yourself and press Mark as posted.
  • Take audio-only files, so a podcast feed is not material yet. It has no Frame.io or Notion integration either.
  • Watch or transcribe your footage on Light. You or your own AI put each clip on its line; Pro and Team read every recording.
  • See everything in your footage. It describes what it watches, and a description can miss a detail. Play a suggestion before you keep it.

Light

Your own AI, through the MCP

$20/month

Starts with a 14-day trial, no card.

About 10 footage hours of playback a month (2,250 credits), up to 3 projects.

Start your free trial

Creates your workspace and starts the trial.

Several recordings a week

Pro

Adds ReadyToEdit’s own AI

$149/month

About 120 half-hour recordings a month (25,000 credits), up to 3 projects.

Start your free trial

Starts with the Light trial. Choose Pro any day.

Team

Adds ReadyToEdit’s own AI

$299/month

About 288 half-hour recordings a month (60,000 credits), up to 10 projects.

Start your free trial

Starts with the Light trial. Choose Team any day.

Light is ReadyToEdit’s production workspace, with your own Claude, Codex or Cursor as the writer, connected through the ReadyToEdit MCP. Pro and Team add ReadyToEdit’s own AI.

After the trial, the workspace is read-only until a plan is chosen: everything in it stays, and links you sent keep working. Choose a plan in Settings, during the trial or after it, and cancel there at any time.

Questions

Does it replace my editor?
No. It prepares what you would otherwise brief: the script, a suggested clip for each line and your notes on them. Your editor still makes every cut, and nothing is edited, rendered or generated.
Can it pick B-roll for my script?
On Pro and Team, it suggests clips from footage you have connected, beside the line each would go under; on Light, you or your own AI place them. Never stock, never generated. Supporting footage and illustrative B-roll are labelled differently, a line with no match stays visibly empty, and you keep or reject each suggestion.
Does my editor need an account?
No. They open one read-only link with Beats & clips, the whole script, playback of each line’s range and the original Google Drive links. Download handoff gives them a text file. You can update the link in place or revoke it.
Does it work with Google Drive, Frame.io or Notion?
Google Drive, yes: import a folder or single files. They stay in your Drive, the handoff links to the originals, and Drive sharing still decides who can open them. There is no Frame.io or Notion integration; the handoff is a link you can paste into either.
Will it sound like AI?
A first draft can. You rewrite it, and the corrections you keep making carry into later drafts, on a list you can read and overrule: your own AI reads them through the ReadyToEdit MCP on Light, and ReadyToEdit’s drafts use them on Pro and Team. Nothing appears on camera that you did not film.

Make the calls. Send the link.

Connect the Drive folder you already send, ask your own Claude for the next video and what it must never say, and watch the Footage preview before your editor starts.