About Developing Tank
Post-Production suite of tools Built by an Assistant Editor for Avid Media Composer Automation.
Developing Tank started as a script, then another, and another, just so I could get back to the tasks I enjoy.
The Origin Story
Will Smith, an editor and assistant editor with more than 10 years in film and television post-production, working mostly in Avid Media Composer. I built Developing Tank against the problems that filled my own days: repetitive manual work, metadata that never carried through, and four departments waiting on the same numbers.
The same jobs came back at me show after show. A re-edit meant redoing dailies organization from the top. Timecodes went in by hand. Markers vanished out of VFX sequences. Continuity documents and turnover packages ate the hours between the cut going out and the email going out. Better spreadsheets were never going to fix that. The fix was software that reads Avid files.
I want the computer working FOR ME, and I want fewer places where I can make a mistake at 6am.
The scripts I wrote over those years became Developing Tank.
The Problem We Lived
What We Believe
Assistant editors are skilled professionals. Hours of repetitive data entry waste that skill, and the show gets nothing extra for it.
Developing Tank works the way Avid works. It reads the files you already have, leaves your workflow alone, and exports formats you can drop straight back into the bay.
Google Sheets, Airtable, and FileMaker were built for everybody, so getting post-production data into them takes half a dozen steps every time. Developing Tank is built for the person who knows what a framerate is.
What We're Building
Developing Tank takes the manual repetition out of dailies prep, VFX tracking, paperwork, and delivery. We went after the hardest jobs first, scene bin creation, retime conforming, and change detection, and finished them, so your team can spend the day on the cut.
What makes us different:
- Dailies Automation: Scene bins, offspeed prep, and cleaner metadata from Avid files. Learn about Film Dailies →
- Deleted Marker Memory: We remember VFX shots even after editors delete them. Learn about VFX Tracking →
- Continuity and Paperwork: Reports and change lists come from the same sequence data. Learn about Continuity →
- Enhanced Detections: A human review layer for VFX shots the rules read two ways, so you catch the odd ones before a vendor does.
- Google Sheets Sync: Your producer's tracker updates itself. Learn about Google Sheets Sync →
No other tool in this category does these five.
The Principles
Every number here is calculated. We parse your timecodes out of the file data itself and hand back metadata that matches the source exactly. Nothing gets predicted, so nothing gets hallucinated.
You upload what you have and we hand back something you can open. AVB in, CSV out. EDL in, clean pull out. No conversion step waiting on the other side.
Keep Avid, keep Google Sheets, keep your FileMaker database. Developing Tank runs beside your pipeline and takes over the manual parts.
Proof / References
If you’re evaluating Developing Tank for a show, a feature, or an enterprise team, these pages answer the most common trust and rollout questions.
Trust
Data handling, what we do (and don’t) track, and how deletion works.
Legal
Terms, privacy, and the plain-language commitments behind the product.
Help Center
Operational guides and workflow explanations for day-to-day use.
Tutorials
Short walkthroughs that show exactly what you’ll get back from your files.
If any of this sounds familiar, you're our user.
Try a free tool or sign up. No commitment. No credit card.
Concerned about data privacy? Read how we handle your data.
Still comparing options? See how Developing Tank compares to spreadsheets, FileMaker, scripts, and macros.