AI video production is a chain of decisions: invent a shot, edit a story, then deliver a usable asset. Compare three documented workflows and prepare your own footage before spending generation credits.
This is a documentation-based comparison, checked October 5, 2026. We did not benchmark these services, buy plans or generate paid outputs. Model availability, quotas and terms change; verify your chosen workflow in the linked official documentation.
Runway
Choose for: reference-driven generative shots and model-specific video workflows.
Runway’s API documentation distinguishes text-to-video, image-to-video and video-based models. Supported aspect ratios and asset encodings depend on the selected model. A centered automatic crop can change a reference composition.
Producer question: which exact model, input route and crop behavior will preserve your intended framing?
Choose for: generating clips from text and working with explicit camera/style controls in Firefly.
The Generate Video documentation walks through model selection and generation controls. Firefly also offers partner models; record the actual selected model rather than assuming every output shares identical terms.
Producer question: are you selecting Adobe’s video model or a partner model, and which usage conditions apply?
Choose for: transcript-led editing of recorded speech and subtitle handoff.
Descript describes editing video by editing the transcript. Its subtitle export workflow produces sidecar subtitle files. A transcript edit and an invented visual shot solve different production problems.
Producer question: do you need editable captions, burned-in captions, or both for the final platform?
No single service wins every stage. For an interview, accurate edits and caption review may matter most. For a missing establishing shot, references and controlled generation matter. Test one representative shot before committing a whole sequence.
The producer’s useful stack starts with the change
A producer’s assignment extends far beyond generating a shot. The schedule, crew availability, location, transport, permissions, budget, coverage, client expectations and post handoff have to agree. A convincing first plan is inexpensive compared with repairing inconsistent instructions after the location cancels. Use the footage lab as one supplemental inspection route; use the guide and change log below to keep the production decisions connected.
This comparison covers twelve candidates described in the source topic, with current documentation and independent practical examples. It does not inherit another publisher’s claimed eleven-shoot test, numerical ratings, universal time savings or outdated prices. A tool’s documented feature is a starting point for a trial, not evidence that your crew receives a correct call sheet or that every department adopted the latest plan.
A change touches more than its first document
Suppose a fictional two-day Harbor product film loses the Tuesday kitchen location. Thursday is available, but the camera operator is booked elsewhere Friday and the client still expects Monday delivery. Recheck the schedule and call sheet, then crew and talent confirmations, location access, transport and permissions, cost consequences, coverage and post capacity. A moved row is not proof that those people accepted the change. Keep the exact old and new versions, the decision time, recipients and affected records together.
Integration can reduce repeated typing when linked records share the same source. Test that propagation deliberately: change one source, inspect the resulting documents and ask a real recipient which version they see. A readable grid can help execution while a canvas can help compare alternatives; neither format guarantees correctness. The last mile is distribution and acknowledgment. Someone arriving at the old time is a communication failure even when every database row is current.
Trial the complete handoff
Bring a representative script, breakdown, schedule, contact list and review clip into a pilot. Make a deliberate location or talent change on a copy. Record setup, revision, checking and recipient time separately. Verify which fields update, which remain manual and which exports preserve the required information. Ask a crew member to find their instruction and a client to find the current review version. Keep defects visible rather than measuring only the speed of creating the first document.
AI can suggest tagged elements, find transcript phrases, draft updates and identify possible inconsistencies in supplied material. It cannot infer current availability from a name in a script or establish that a supplier accepted a revised date. Scheduling involves travel, access, light, capacity and applicable working rules. Budgets need checked source quantities, rates and arithmetic. Treat assistance as a reviewable first pass; obtain the actual constraints and confirm the resulting plan with responsible people.
Twelve candidates, compared by the output the next person needs
StudioBinder: connect breakdown and crew-facing paperwork
StudioBinder documents script tagging, stripboards, shot lists, production reports and call-sheet workflows. Test a revised source through the downstream document rather than assuming synchronization covers every field or communicates every change. A useful pilot checks a tagged location, the resulting shooting day and the call sheet seen by a recipient. The current free-plan support page says sample call sheets can only be sent to yourself. That corrects the source’s claim that the free tier necessarily runs complete crew distribution. Verify required collaborators, projects and sending entitlement before adopting a zero-cost stack. Its breakdown tutorials describe the workflow without establishing an independently measured advantage.
Claude: draft from the changed facts
An assistant can turn an actual revised schedule and decision record into a client update, risk questions or department-specific messages. Supply the source versions, confirmed constraints and unknowns. Ask for a separate list of possible inconsistencies, with the record behind each concern. Read the result against the actual production rather than assuming a confident passage is a safety assessment. Projects or retained context can help organize work, but account limits and attachments require checking. The assistant does not update every production system or contact each recipient merely by drafting a message. Compare current plans against the complete document workload; no universal long-document winner or unlimited free allowance is claimed.
Frame.io: identify the review version and the actual note
Review should preserve the clip version, time reference, requested change and responsible reviewer. Frame.io documents comments and exports and search over transcript, comments and metadata. Check the account’s feature availability and test an exact spoken phrase against the original clip. Search does not eliminate checking neighboring context or speech errors. Its comment export can be filtered, so verify whether the handoff contains all notes or only the visible subset. Camera-to-cloud is a separate supported-device/upload route to evaluate. A completed comment is activity evidence, not independent proof that the final cut satisfies the client or reached its destination.
Yamdu: coordinate departments around the same source
Yamdu describes production and shooting schedules, departmental breakdown suggestions, cast, crew, locations and linked budgeting workflows. Departments confirm AI suggestions; they are not automatically validated production facts. Pilot the roles that will actually use the system: wardrobe needs the appropriate talent/scene information, transport needs a current location and time, and the producer needs a readable effect of a change. Setup and administration are part of the cost. Complex scripted work can justify more structure, while a small commercial may not need every department feature. Obtain the actual project/account quote and confirm the destination exports rather than copying an old approximate monthly entry price.
Storyflow: preserve the reasoning while alternatives move
References, sequence, locations and unresolved questions can be useful on a connected visual board. Ask the AI to propose consequences from the actual changed inputs, then reconcile that list with the formal production records. The current pricing page describes canvas context, Tactics, documents, generated boards and Pro/Max conversation memory; the upcoming public Free plan and paid-member invitation exception are different access routes. A canvas can hold manually entered tables and planning records, so do not equate “not verified as a specialized production system” with an inability to hold any budget or schedule information. Test actual crew paperwork, dependency behavior, recipient access and review exports separately. A generated plan does not verify availability or authorize sending a call sheet.
Descript: use the transcript to propose a structure
Descript’s transcript-led editing is useful when a producer needs a rough interview assembly or a selects structure. Keep the original recording and inspect the words against the sound. Filler removal, a transcript deletion and a generated voice operation have different effects. Agree permitted voice treatment and review speech context before delivery. Caption sidecars are different from burned-in text; inspect the requested handoff format. Count transcription allowances, export entitlements and correction time in the actual tier. A rough assembly can help the finishing editor without pretending it replaces every native editing, color, audio or delivery requirement.
ChatGPT: a second candidate for factual assistance
A general assistant can work with supplied documents, images and reusable instructions to prepare updates, checklists and possible change consequences. Test the same representative script and schedule rather than assuming every model or account has the same context, file or tool access. Ask it to identify unsupported assumptions, then verify them yourself. Retain the source behind each claim and separate drafting from mutations in external systems. If one assistant already meets the workload, a second subscription needs a distinct demonstrated reason. Compare the actual feature and cost route; a broad ecosystem does not establish an independently tested production advantage or a safely scheduled shoot.
Airtable: build the tracker you actually need to maintain
Airtable can relate productions, people, deliverables, versions and destinations, then present collaborator-specific views. Its platform overview describes interfaces, automations and AI capabilities. For thirty deliverables, link each output to its current source rather than repeating an ambiguous filename across unrelated sheets. Test which automation fires, who can edit the source and what happens when a record is deleted or renamed. AI summaries do not establish that the underlying dates or permissions are correct. The flexibility brings maintenance, access design and migration responsibilities; account editor billing and feature tiers belong in the quote. A custom database does not automatically become a validated call-sheet system.
Celtx: distinguish writing access from production entitlement
Celtx connects scripting with production planning, including breakdown, scheduling and budget workflows. Its current plan page separates writing and production planning arrangements and describes trials and plan changes. A free studio after cancellation does not prove that every production feature or export remains available. Pilot a tagged scene through the required schedule and budget record, and check the actual call-sheet/distribution requirement. For independent work, an integrated route may reduce duplication when the team uses it clearly. Verify that claim with a changed scene and recipient rather than repeating an untested assertion that one interface is universally cheaper, more familiar or more polished.
Notion: maintain knowledge and structured dates deliberately
Notion pages and databases can retain contacts, decisions, kit lists, wrap notes and linked asset records. Current subtasks and dependencies and timeline documentation correct the source’s absolute claim that it can schedule nothing. Evaluate the specific date-change behavior and account configuration instead of treating a calendar as a complete production constraint solver. Name the record governing the current version, make the archive navigable and test effective recipient access. AI search is useful only when the retained records are accurate and available. A searchable wrap report helps the next project, but a dormant wiki cannot confirm today’s crew availability.
Runway: a previz route with an explicit treatment
Runway can help demonstrate a proposed framing or movement before a shoot. The existing comparison above links its model-specific input documentation. Record the selected model, source reference, crop behavior, generation usage and intended treatment. Inspect continuity and compare normal playback, not just an attractive still. Whether a generated shot becomes an actual deliverable depends on the brief, terms and recipient acceptance; the source’s blanket “reference only” claim is too broad. Keep generated candidates distinct from photographed footage, retain rejection reasons and check the applicable commercial route before promising an output. Credits spent on variants belong in the project estimate.
Google Sheets: a transparent baseline with owned maintenance
A shared spreadsheet can hold a budget, deliverable tracker and explicit schedule, using formulas and version history. Build the smallest useful structure and test actual recipient access. Formulas, linked sheets and configured automation can propagate some changes, so “everything is manual” is not a universal product limitation. The important question is which records your configuration updates and which instructions still need an owner. Check quantities, rates, rounding, currency and excluded costs separately. A budget formula is not a supplier quote; a date entry is not confirmation. Workspace administration and organizational access can change the cost and sharing route even when personal spreadsheet access is available.
One location change, seven consequences and one distribution record
For the fictional Harbor refill film, revision V03 uses a Tuesday kitchen and a Monday client review. At 21:00 on Monday, the location becomes unavailable. Producer Mara proposes Thursday at a replacement kitchen; Theo has not yet confirmed talent, Jo has not confirmed transport, and editor Ellis needs the actual transfer time before agreeing the first cut. This example is a planning exercise, not an accepted production schedule.
Schedule: retain V03, create proposed V04 and record the changed location/day. Check other scene and crew constraints.
Call sheet: inspect location, call times, contacts and travel instructions generated from V04; invalidate the earlier issue explicitly.
People: Theo confirms talent and Mara confirms crew availability. A name in the distribution list is not an acknowledgment.
Logistics: Jo checks access, transport, required permissions and the actual receiving contact. Do not reuse the old route.
Cost: obtain revised location and transport quotes. Keep them unknown until received; no invented savings or overtime allowance.
Coverage: compare the amount-line close-up and lid action against the new setting. Retain the reference frame that explains each requirement.
Post/client: Ellis checks the transfer and review window; Mara gives the client the scope/date consequence and asks for the necessary decision.
A complete change line reads: “Kitchen unavailable; proposed Thursday replacement, V03→V04. Decision recorded Monday 21:00; still awaiting location/talent confirmation. Mara owns the revision. Theo, Jo, Ellis and the client need the affected instructions; acknowledgment remains open. Recheck schedule, call sheet, people, logistics, cost, coverage and post.” Enter real evidence when it exists. The local change log below preserves these full fields; it neither sends messages nor verifies that someone read them.
At wrap, compare what changed with the actual result. Which estimate repeatedly ignored travel? Which reviewer received the wrong version? Read several projects before turning one exceptional event into a permanent rule. Retain client-facing changes when decided, with their consequences, rather than discovering at invoice time that the decision exists only in someone’s memory.
Four common changes need different recipients
Shoot date: confirm crew, talent, location and client availability, then inspect the issued call sheet, cost consequence and post window. Location: tell transport and the receiving contact; revisit access, permission and the applicable insurance record with its actual owner, alongside the call sheet and coverage. Talent: involve casting and wardrobe, verify the relevant release record and inspect affected scene/schedule instructions. Delivery date: involve the client, editor, music and voiceover suppliers; confirm the downstream dates instead of changing only the headline deadline. Choose the communication deadline from the real consequence, not an arbitrary universal one-hour rule. Record the actual notification and acknowledgment separately. The local worksheet cannot inspect a policy, validate a release, send an update or confirm availability.
Five stack shapes and the costs the headline misses
Commercial/branded: a paperwork route such as StudioBinder, a review route such as Frame.io, one factual assistant and an optional visual planning surface. Independent: the production features actually available in Celtx or another affordable account, an assistant if useful, and a checked spreadsheet. Documentary/unscripted: transcript search, a rough-assembly route, archive identity and an evolving structure; preserve source context and permitted treatment. Complex scripted: departmental coordination such as Yamdu plus the required review/distribution route. Low-cost: already available tools and verified continuing free features, with actual external delivery tested. A free self-only call-sheet sample is not a complete free crew workflow.
Cost the active projects and quiet months separately. Include collaborators, minimum seats, storage, transcription, generation usage, setup, maintenance, learning and export requirements. Project-based billing and an annual subscription create different cash commitments. Do not add old $69/$25/$59/$65 totals as current quotes. If a fictional second system costs $20 monthly for twelve months but is used in five, cash spend remains $240; cancel/restart terms or a project quote may change that comparison. Count checking and revision time before valuing apparent AI savings.
Additional candidates include Movie Magic Scheduling/Budgeting for specialized work, Shot Lister for shoot-day shot management, Dropbox Replay or Vimeo’s applicable review offering, SetHero for a call-sheet route and Boords for storyboards/animatics. Trial the exact required version, recipient and feature tier. A change log in an existing shared surface and a readable wrap report can be valuable without buying another application. No universal market-leading, fastest or lowest-cost ranking is claimed.
Six filled planning records for the same production
Mindmap: root “move kitchen day”; branches schedule V04, Theo/talent, Jo/access/transport, Mara/crew/client, Ellis/post, revised quotes and amount-line coverage. Every branch has an unresolved confirmation rather than an invented green status. Link the call-sheet issue to the accepted schedule, not only the proposed date.
Story Plan: the Harbor film introduces the bottle, shows measuring the refill and confirms lid attachment. The location change must preserve those three actions. Mira checks instruction clarity; Mara decides whether revised coverage changes scope; Ellis retains sequence notes for the cut. A change of setting cannot silently change the demonstrated product instruction.
Marketing Campaign: planned product-page film, customer-email graphic and social cut share the accepted amount instruction. Theo owns wording, Jo owns designed derivatives and Ellis owns the video version. Monday remains a proposed review date until the revised transfer is feasible. Publishing owners later inspect real destinations; planned channels are not release evidence.
Brand Strategy: practical product care, ordinary handling, unchanged label and readable steps. Keep warm neutral surfaces as a proposed visual treatment, not a production constraint that overrides correct instructions. A replacement kitchen that changes light needs a new sample review; Mara records the accepted exception and its scope.
Storyboard: H01 bottle/refill context, H02 opening, H03 readable amount line, H04 lid attachment, H05 finished use. Mark H03’s reflection issue and inspect a sampled reference. The prep lab helps produce that contact sheet; it does not supply missing footage or infer whether the instruction is correct.
Second Brain: record Monday’s location message, V03, proposed V04, current brief and open confirmations. Retain the reason “original location unavailable,” the people informed and any later acceptance. Attach the relevant brief and Tactic when testing a planning AI; ask for notes and a mindmap of affected work, then verify the sources. Current-board context, attached documents and conversation memory are distinct mechanisms and depend on the actual account.
Inspect the feature that carries the next revision.
StudioBinder: reconcile contacts, the issued sheet and delivery evidence
In the Harbor example, Mara first checks Theo’s and Jo’s current contact details in the production contact database and keeps the relevant cast/crew lists together. StudioBinder documents email/SMS call-sheet distribution and a dashboard showing views, confirmations and bounced delivery. Preview V04 with each recipient’s call time, replacement address and specific note; issue the accepted sheet through the eligible account, then inspect the dashboard for the people still missing it. A bounced email needs a corrected address and another real delivery attempt. A view is different from a confirmation, and neither proves that the person can attend Thursday. The pricing comparison distinguishes basic CRM from CRM/messaging and advanced analytics entitlements; trial the exact tier. Keep the free-plan self-only limit from the support page in view even though the public marketing page advertises free creation and sending.
Frame.io: stack the cut, compare revisions and attach the note correctly
Retain Harbor V03 while uploading the complete V04. Frame.io’s current versioning instructions describe dragging a fully uploaded new asset onto the previous asset to create a stack. Open the stack and select the version number to inspect an earlier cut; do not assume filename order means review order. Use Compare Versions to view V03 and V04 side by side with linked playback, and choose the correct left/right asset header before adding a note. Check whether H03’s amount-line reflection was corrected without changing the instruction. Mounted Storage version saves are a different mechanism from uploaded asset versions, with different storage accounting. Our local log can retain the version reference; it does not create Frame.io stacks or synchronize review notes.
Yamdu: make the department’s asset change explicit
Link the replacement kitchen to its location record, the talent/scene and the bottle/refill props needed for H01–H05. Jo should see the revised access information; the relevant creative department checks its costume, set or prop material against the same scene. Yamdu’s current feature list includes cast, location, costume and production-design records, company databases, distribution and exports. Give the department the actual revised file or record and inspect its permitted view, rather than calling a changed location title a complete asset handoff. Keep the record owner, current revision and unresolved availability visible. This is an applied checking procedure, not a vendor-account test or a claim that every dependency automatically updates.
Storyflow: spend the context budget on the actual change
The supplier’s creator page currently describes up to three Tactics, five documents and three boards as attached context. For Harbor, use the current brief, V03 schedule, location message, accepted product wording and relevant handoff record; attach the current reference and affected-planning boards, staying within the documented slots. Ask for a mindmap of the changed day’s consequences, with unknowns still marked unknown. Some older help/blog pages describe different limits and draft/edit behavior, so inspect the attachment controls and actual account allowance before promising that every upload is read. Mentioned files, active-board context and cross-conversation memory are distinct mechanisms; memory does not prove the latest decision is current.
Current pricing lists the full 200+ Tactics library and unlimited boards/uploads on paid plans, while AI usage remains metered. Pro adds image generation and conversation memory; Max adds shared Team Workspace roles and permissions. For a treatment exercise, ask Pro for a clearly marked illustrative replacement-kitchen reference, retain its source status and compare it with the location’s actual scout material. Assign actual edit/view responsibilities in the eligible workspace and inspect a recipient’s access. None of these features establishes call-sheet sending, day-out-of-days, a specialized crew database, releases or formal timecoded proofing. The future standalone Free tier and free invited collaboration remain different routes; legacy “start free” template/help copy does not override the current early-access FAQ.
Descript: make a permitted temporary narration track
AI Speakers is the current voice workflow behind the source’s older Overdub terminology. Write a short, approved placeholder for the H03 refill instruction, select an appropriate stock AI Speaker and generate a clearly marked temporary narration track. Inspect pronunciation, timing and the source wording before using it to judge the rough assembly. A permitted custom voice clone is a separate route; do not treat a recorded interview as permission to clone its speaker. Keep the temporary track distinct from the accepted final narration and include its identity in the handoff. This complements transcript editing and filler removal without turning the local FFmpeg review-copy lab into a speech generator.
ChatGPT: distinguish image generation, reusable instructions and account access
ChatGPT Images can generate or edit an illustrative reference from an explicit instruction and supplied image. For Harbor, propose a replacement-kitchen composition using the accepted bottle layout, mark it as generated and compare it with the actual scout. It cannot establish access permission or prove how the real amount line photographs. File analysis and image creation are separate tasks with account limits; neither updates the issued schedule automatically.
For recurring updates, keep reusable instructions requiring source versions, affected records, unknowns and recipient-specific drafts. The current official GPT guide, checked October 7, says personal Free, Go, Plus and Pro accounts cannot create or publish new GPTs. Existing GPT use/editing and permitted Business, Enterprise or Edu workspace creation are different routes. In an eligible workspace, put behavior in instructions and factual references in knowledge, test a location-change draft and inspect the actual source links. The same guide describes planned GPT retirement and migration toward Plugins; check account notices, preserve the instructions and test the replacement before relying on a long-lived custom-GPT workflow. A saved instruction document remains useful without buying a second assistant or promising unavailable personal creation.
Google Sheets: put the question on the affected cell
In the schedule, Jo can attach a comment to the replacement-location cell asking whether Thursday access is confirmed. Where account access supports it, assign that action to the actual responsible person, then retain the decision and the governing version. Resolving the comment means the thread was marked resolved; it does not prove a permit exists or a crew member accepted the new call time. Use named versions before a significant re-plan and inspect the version history when a value changes. Confirm recipient access instead of assuming a share link is universally open. Spreadsheet comments, formulas and configured automation can help coordination, while the local change log preserves only what its user enters.
Runway: use the current edit route for a bounded reference change
The original also mentions editing/effects utilities. Current Edit Studio describes an Aleph 2.0 route: upload a qualifying clip, choose a clear keyframe, describe the bounded change, compare the image adjustment and generate the affected video range. For Harbor, explore a replacement background as a labelled reference while checking that the bottle and amount instruction remain correct through playback. The current specifications limit length, resolution, frame rate and cuts; inspect them before estimating credits or supplying footage. Older standalone editor/inpainting instructions have been retired or replaced, so follow the current deprecation guidance. Image generation and video editing remain different paid-model routes, and the local FFmpeg trim/scale tool performs neither Runway effects nor generative replacement.
Price the seats and the production workload
These are public USD list rates checked on October 7, 2026, before tax, promotions, additional storage, AI overages, and regional checkout adjustments. An annual monthly equivalent is a comparison unit: it does not mean that the vendor offers a cancel-any-month subscription at that rate. These figures replace the original article’s historical price examples; a personalized checkout quote and a production entitlement remain separate checks.
StudioBinder: included operators change the comparison
The monthly pricing comparison shows Starter at $29 with one user, Indie at $49 with two users, and Professional at $99 with four users. Organization plans show Agency at $199 with ten users and Studio at $299 with twenty. These are plan totals rather than a flat per-user price. Check the feature row for the call-sheet messaging and analytics you need; a contact database, a preview sent to yourself, and an externally distributed sheet with delivery tracking are different entitlements.
Claude: annual billing is $200, not $17 multiplied by twelve
Claude Pro is $20 monthly or $200 billed annually, approximately $16.67 per month. The rounded $17 display should not become a $204 budget. Team Standard is $25 per person monthly or $20 per person per month billed annually, with a two-person minimum. Free can support a small drafting workflow within its limits; neither a personal nor a team subscription buys unlimited usage or includes separate API charges.
Frame.io: members and outside reviewers are different
Frame.io Pro is $15 per member monthly or $156 per member billed annually ($13 monthly equivalent), with up to five members. Team is $25 monthly or $264 annually per member ($22 monthly equivalent), with up to fifteen members. Pro starts with 2 TB of standard storage and additional-member storage; mounted storage is a separate allowance. Free permits two members, two projects, and 2 GB. External share-link reviewers can view and comment without a paid member account, so do not buy a member seat merely because a client needs to review a cut.
Yamdu: a one-project team can outgrow the entry price quickly
The US subscription selector lists Flex at $45 monthly for one user and one project, with another user at $22 monthly and another project at $45 monthly. Five paid Flex users on one project therefore cost $45 + four × $22 = $133 monthly. Studio is $265 monthly or $199 per month billed annually ($2,388 for a year), including ten users and unlimited projects. External contacts are not automatically paid application users; decide which department owners need to operate inside the system before calculating seats.
Storyflow: distinguish public paid plans from an invited guest
Storyflow’s pricing page lists Plus at $9.99 monthly or $7.99 per month billed annually ($95.88 yearly), Pro at $19 monthly or $14 annually ($168 yearly), and Max at $49 monthly or $39 annually ($468 yearly). Unlimited paid-plan boards and uploads do not imply unlimited AI credits. Pro adds image generation and longer memory; Max adds permission roles. A free invited collaborator is a different case from a new standalone free account. Older free-plan descriptions conflict with the current pricing surface, so use actual account availability rather than promising a new free workspace. Do not apply a team discount until its eligible seat count and checkout terms are known.
Descript: budget imported media hours and each editor
Descript Hobbyist is $24 monthly or $16 per person per month billed annually ($192 yearly), with ten media hours per month. Creator is $35 monthly or $24 annually ($288 yearly) with thirty media hours; Business is $65 monthly or $50 annually ($600 yearly) with forty. Creator and Business support additional separately billed people within their respective plan limits. AI credit allowances and export quality differ. An eleven-hour documentary ingest exceeds Hobbyist’s ten-hour allowance before any subscription arithmetic becomes useful.
ChatGPT: pay for the actual workflow, not an unavailable creation route
ChatGPT Plus is $20 monthly; there is no annual Plus subscription. Business Standard is $25 per user monthly or $20 per user per month billed annually, with a two-seat minimum: $50 monthly or a $480 yearly commitment at the minimum. Five Standard users are $125 monthly or $1,200 yearly. API usage is separate. Personal-account GPT creation is currently unavailable even on Plus and Pro; a permitted Business, Enterprise, or Edu workspace is a distinct route, subject to permissions and the announced GPT migration. Save a reusable instruction document even when a workspace feature changes.
Airtable: comments can create a billable Team collaborator
Airtable Team is $24 per billable collaborator monthly or $20 per month billed annually ($240 yearly); Business is $54 monthly or $45 annually ($540 yearly). The current plan support guide makes the billing distinction: Team bills Commenter or higher, while Business bills Editor or higher. A five-person Team setup with five billable collaborators is $120 monthly or $1,200 yearly. Read-only recipients and publicly shared views should not be casually counted as editors; free-plan record and automation limits still need a workload check.
Celtx: production tools require the right bundle
The annual pricing selection displays Writer at $11.24 monthly equivalent, Writer Pro at $18.74, and the three-member Team bundle at $44.99 ($539.88 for a year at the displayed rate). Team includes production planning; on the writing plans, breakdown, schedule, budget, and call sheets are optional add-ons. The selectable Team member count changes the quote. A free trial or a free writing account does not establish continuing access to all production tools. Our monthly-toggle verification did not expose a reliable numerical quote, so we do not invent one or derive it from a discount percentage.
Notion: a workspace seat and an AI entitlement are separate checks
Notion’s USD annual selection displays Plus at $10 per member per month ($120 yearly) and Business at $20 ($240 yearly). Five paid members therefore represent $600 or $1,200 yearly respectively. Full AI Agent access belongs to the eligible higher plan; a trial on a lower plan is not an unlimited recurring entitlement. Guests, members, and the actual permission model should be decided before inviting a whole crew as paid members.
Runway: credits reset on their own schedule
Runway Standard is $15 monthly or $12 per month billed annually ($144 yearly), with 625 credits per month. Pro is $35 monthly or $28 annually ($336 yearly), with 2,250 monthly credits. Max is $95 monthly or $76 annually ($912 yearly), with 9,500 monthly credits and its stated rollover terms. The free allowance is 125 one-time credits. Buying an annual subscription does not make twelve months of credits available immediately, and generation duration, model, resolution, and retries determine the cost of a usable shot.
Google Sheets: personal free use is not a paid Workspace bundle
A personal Google account can use Sheets for a $0 subscription workflow. The US Workspace pricing page shows Business Starter’s regular rate at $7 per user per month with a one-year commitment, billed monthly: $84 per user over that commitment, or $35 monthly and $420 over the year for five users. Temporary promotional rates are excluded here. This buys a broader Workspace package; it does not turn a spreadsheet into a verified scheduling, rights, or payroll engine.
Five costed stacks with explicit assumptions
These examples preserve the original article’s five production situations, but use the current rates and required scopes above. A “five-person production” does not mean five paid seats in every application. Identify the operators, use legitimate guest or review access where available, and add seats only when the person needs member capabilities. Hardware, payroll, permits, media storage beyond allowances, taxes, and AI overages remain outside these software subscription totals.
Commercial production: $93.99 per month
StudioBinder Indie ($49, two included operators) + one Frame.io Pro member ($15) + one Claude Pro account ($20) + one Storyflow Plus account ($9.99) = $93.99 monthly. Use the paperwork operator for the current call sheet, Frame share links for client feedback, Claude for checked revision reasoning, and the board for visual dependencies. Confirm the chosen StudioBinder tier actually includes the required outbound delivery and analytics before paying; upgrading that tier changes this total. One paid AI account is operated by its account holder, not shared credentials across the crew.
Independent film: $539.88 yearly plus $29.99 monthly
Celtx’s three-member Team annual bundle ($539.88 yearly at the displayed $44.99 equivalent) + one Claude Pro account ($20 monthly) + one Storyflow Plus account ($9.99 monthly), with personal Sheets and Frame.io Free within their limits. The comparison equivalent is $44.99 + $20 + $9.99 = $74.98 per month, or $899.76 over twelve months if the monthly subscriptions remain active. The initial annual Celtx commitment is real even if a solo producer only uses one of the three bundled seats. Do not describe $74.98 as an all-monthly cancelable plan.
Documentary: $79.99 monthly for an eleven-hour ingest
One Frame.io Pro member ($15) + one Descript Creator editor ($35) + one Claude Pro account ($20) + one Storyflow Plus account ($9.99) = $79.99 monthly. Creator’s thirty media hours accommodate the example’s eleven imported interview hours; Hobbyist’s ten do not. A lower-volume project fitting Hobbyist can substitute $24 and total $68.99 monthly. With annual Frame.io Pro ($156), Creator ($288), Claude Pro ($200), and Storyflow Plus ($95.88), the same one-operator stack commits $739.88 yearly, approximately $61.66 per month. Track media-hour and AI-credit consumption rather than assuming the lower total removes usage limits.
Complex production: $177.99 monthly for five Yamdu operators
Yamdu Flex for one project and five paid users ($45 + four × $22 = $133) + one Frame.io Pro member ($15) + one Claude Pro account ($20) + one Storyflow Plus account ($9.99) = $177.99 monthly. This gives five people access to the production system, with one operator in each other paid app and clients using eligible review links. Extra Yamdu projects cost more; adding paid Frame members or board operators also costs more. Studio’s $265 monthly ten-user, unlimited-project bundle is a different scope, while its $2,388 annual commitment has a $199 monthly equivalent. Compare those scopes when departments or simultaneous productions grow, rather than treating the old low entry price as a complete crew budget.
Near-free production: $0 subscriptions, with explicit manual work
Personal Google Sheets + a free Claude account within its limits + Frame.io Free within two members, two projects, and 2 GB can make a $0 subscription stack. Keep a checked schedule and call-sheet document, a contact list, and the change log with a named owner. This does not include automated legal or payroll paperwork, unlimited media review, unrestricted AI use, StudioBinder external delivery on a self-preview free entitlement, Celtx’s paid production bundle, or a promised new free Storyflow workspace. The cost advantage is meaningful only if the producer can sustain manual verification and distribution without losing a revision.
Questions before adopting the production stack
Which production tools should I trust?
Trust the demonstrated route: source revision, downstream paperwork, intended recipient and recoverable records. StudioBinder, Frame.io and Yamdu are candidates for different jobs; an established name does not prove your configuration is correct. Test the crew/client access and keep actual results.
Which pricing model is fair and transparent?
Keep the quote date, term, paid collaborators, storage, usage and required features together. A clear entry rate may omit external call-sheet sending, transcription or review requirements. Compare active projects and quiet months rather than calling every free tier a complete production system.
Which improvements should a producer evaluate?
Current transcript search, breakdown assistance and document drafting may address real friction. Repeat the complete source-to-recipient trial after a relevant release and record correction time. No common measured recent-improvement ranking is claimed.
What would you buy first?
Start with the missing crew-facing output or failed handoff. Check existing tools, then trial one candidate through a deliberate change. Add review, writing or visual planning only when each solves an observed need.
When is Storyflow the wrong primary tool?
A visual board does not establish specialized breakdown, day-out-of-days, call-sheet sending or timecoded review functionality. Test those requirements separately. It can still hold planning tables and reasoning, so do not confuse an unverified specialized workflow with a blanket inability to contain production information.
Is there one best AI tool for producers?
Paperwork, writing, review, departmental coordination and reference generation require different outputs. Use the twelve candidates against your actual constraints. No common benchmark here establishes one universal winner.
Can AI schedule the shoot day?
It can propose a plan or possible inconsistencies from supplied constraints. Confirm availability, travel, access, light and applicable working requirements before adoption. A plausible draft does not establish a feasible or authorized shoot.
What is genuinely free?
Distinguish continuing access, temporary trials and existing paid subscriptions. StudioBinder’s current free call-sheet samples can only be sent to yourself. Verify production and export access in Celtx and other accounts before promising a complete zero-cost crew workflow.
StudioBinder or Yamdu?
Trial StudioBinder’s connected paperwork route and Yamdu’s departmental coordination against the actual project. Include setup and recipient effort. A two-day shoot and a complex scripted production may justify different configurations; neither headcount alone nor a feature list settles it.
How do producers use AI day to day?
Draft updates from changed facts, review possible breakdown omissions, locate spoken material and propose a rough transcript structure. Verify every relevant source and distinguish a draft from an actual system update or distributed instruction.
Is Frame.io worth paying for?
Test the required storage, versions, recipient comments, transcript/search access and complete export. Familiarity can reduce friction, but the actual account and workload determine value. Compare a scoped review alternative when that meets the requirement.
Can generated footage enter client work?
Agree the treatment, applicable rights/terms and acceptance criteria. Mark generated material clearly in the production record and inspect continuity. A reference and a final deliverable may be different routes; neither universal approval nor universal prohibition is established by this guide.
What should the change log contain?
Keep what changed, when decided, who was informed and what it affects. Add the exact version, responsible person and acknowledgment evidence when useful. The workbench preserves entered records but does not send or verify notifications.
Claude or ChatGPT?
Test the same real script, schedule and drafting request with the account you can use. Compare accuracy, limits and correction work. Keep one when it meets the need; a second subscription needs a separate demonstrated purpose.
Do I still need a production system with Notion or Airtable?
Possibly. A configured database can hold records, dates and automations, but you must maintain its source relationships, permissions and outputs. Test actual crew paperwork and recipient access before building or buying another system.
How much should I spend?
Calculate the complete annual/project commitment and net checking time for your workload. There is no universal $70 ceiling. Start with available access, then pay for a verified missing function rather than an attractive first-plan demo.
What is the most common tooling mistake?
Updating the visible schedule while leaving a downstream document or recipient on the old version. Inspect affected records and acknowledgment explicitly. A second avoidable mistake is buying a large system without assigning its maintenance and distribution responsibilities.
Should the client see the production plan?
Show a bounded, readable plan early enough for meaningful decisions. Explain changes, scope and unresolved assumptions. Test the recipient’s actual access; a visual board or formal schedule is useful only when the client can understand the requested decision.
Keep the change and the people it affects together
This local editable log keeps seven complete text fields per change. Record facts, open decisions and exact versions. Papa Parse produces a formula-safe CSV; JSON preserves the exact full text for restore. No model is called, no schedule is optimized, no messages are sent and no acknowledgment is verified. The footage lab remains a separate source-inspection and FFmpeg review-copy tool.
No changes entered. Add a record or inspect the fictional example.
Unsaved work stays in this tab. Export before leaving.
JSON contains project and record text, not footage or a backup of your production systems. CSV neutralizes spreadsheet formula prefixes and is a reading handoff; use JSON for exact restore. A rejected or superseded import keeps existing work. Remove confidential contact or client information before sharing a download. Importing a record does not prove its source or authorize its plan.
Change the plan. Keep the complete handoff.
This original silent 32-second portrait lesson teaches the actual local change log and supplemental footage lab. It combines animated instructions with captured local tool states. Harbor, Mara and the proposed V04 are fictional examples; no availability, acceptance, notification or publication is claimed.
Native controls let you pause or revisit any step. Full primary instructions remain readable above the reserved caption and controls area.
The complete written lesson
Record the change. Keep the old plan. Describe what changed and which facts remain unconfirmed.
Name the exact version. V03 becomes proposed V04. A new filename does not prove anyone accepted the plan.
Name the recipients. List who needs the new instruction. Enter acknowledgment evidence separately.
Trace the consequences. Recheck schedule, call sheet, people, logistics, cost, coverage and post.
Inspect actual footage. Use the existing prep lab to sample frames. Browser seek times are approximate.
Make a review copy. FFmpeg trims and scales locally. The WebM is not an archival master or AI upscale.
Export the whole reason. JSON keeps exact records. CSV neutralizes formulas. Keep footage separately.
Restore, then verify. Restore JSON and inspect the next handoff. The tool sends no messages and confirms no availability.
Choose a browser-playable video, select 4–24 evenly spaced frames and build your sheet. Frame timestamps are approximate browser seeks, not certified frame-accurate edit points.
Load a video or try the demo. Nothing is uploaded.
Export a shorter, smaller video with FFmpeg
Single-thread ffmpeg.wasm runs on your device. Its engine downloads only when you request an export (about 31 MB). The output is a WebM/VP8 video with Vorbis audio when the source has sound. Processing can be slower than playback.
Load a video above before exporting.
Compatibility: MP4/H.264 is a practical starting point; codec support varies by browser. HEVC, ProRes and unusual containers may require conversion first. Large sources can strain device memory. If extraction fails, try a shorter lower-resolution copy. The demo records an original animated canvas with MediaRecorder when available.
A handoff that carries your decisions.
Describe the shot, retain source measurements and export a JSON or Markdown production brief. These fields are your decisions, not AI-generated recommendations. This lab makes no external generation requests.
No project data is saved between visits. Export a copy to retain your decisions.
Make the next decision visible.
Keep source footage, generated candidates and approved edits separately identified.
Start with a reference you can explain
Inspect the uploaded video’s duration and dimensions, then extract frames to discuss composition. Browser seeks are approximate; inspect final edits in your native editor when frame accuracy is required. A reference should clarify the subject and motion rather than merely resemble the intended color palette.
Write one achievable visual event
State the subject, movement, camera behavior and intended end state. Separate unrelated events into different shots. This is an editorial suggestion, not a guarantee that a model will follow every instruction.
Review a candidate at normal playback
Look for identity drift, temporal discontinuities, unreadable text, unwanted crops and incorrect actions. Scrubbing frames can expose a defect but does not replace reviewing the full sequence with sound. Record rejected candidates and the specific reason for rejection.
Export to the destination you actually need
The prep lab emits a VP8 WebM review copy, not an archival master or a guaranteed platform-compatible delivery. It rescales pixels with FFmpeg; it does not recover detail with AI upscaling, stabilize a shot or certify broadcast compliance. Verify your destination’s format before a final delivery.
Ask a better review question.
“What changes between the opening and the final frame?”
Sources and processing boundaries.
Product descriptions above link to their official documentation. Local frame extraction uses the browser’s video decoder and Canvas. Local trimming uses pinned ffmpeg.wasm 0.12.15 with single-thread core 0.12.10, GPL licensing included. Processing may consume substantial memory and time on mobile.
Your selected files stay in this browser. This page downloads its runtime assets, fonts and motion libraries; it does not submit footage to any AI service. References and exported briefs may contain personal information: review them before sharing.