About Developing Tank

Built by an Assistant Editor Who Wanted Time To Be Creative.

Developing Tank didn't start as a company. It started as a script, then another, and another, just so I could get back to the tasks I enjoy.

See What We Built →Join the Waitlist
The Origin Story

I have been on projects where, seemingly, every day, there is a complete re-edit with a cut that needs to go out. That meant every day, spending hours making a new continuity or a day retiming a day of slow-motion dailies, if I'm a picture Assistant Editor. On projects where I've been a VFX Assistant Editor, the Picture Editor mistakenly dropped a few markers, subcaps aren't aligned at all, switched from B camera to A camera on a shot flagged for VFX, or the shot got extended past the handles. Okay, yes, some of them are simple annoyances that go with the job, but a few seconds and minutes here and there add up.

Constantly trying to eliminate any place I could make a mistake, I constantly work to find ways to make the computer work FOR ME, not the other way around.

The scripts I have created over the years became Developing Tank.

The Problem We Lived
🌅
Dailies Prep Dread
You don't want to spend HOURS clicking and dragging to get dailies ready first thing in the morning just to be able to do the fun part.
⌨️
Re-entering Timecodes
After every recut. Frame counts, markers, metadata. EDLs don't carry much of the information needed. Good luck if your tracker got deleted.
🔧
Being the Only Person Who Knew How to Fix Things
You know how the spreadsheet formulas work, but one person mistakenly changes it and the whole workflow grinds to a halt.
🌙
The Cut Goes Out
After the cut is ready to go out, you are stuck updating the tracking documents and continuity just to hit send on that email.
What We Believe
"Manual work is the wrong way to spend a career."

Assistant Editors are skilled professionals. The hours spent on repetitive data entry aren't just inefficient — they're wasted talent.

"Your tools should work for you."

Developing Tank works with Avid, not against it. It reads your files, respects your workflow, and exports formats you can use immediately.

"Post-production professionals deserve better software."

Most of the tools we use — Google Sheets, Airtable, and FileMaker — are general-purpose tools and require multiple steps to get our data into them. Developing Tank is built for the person who knows what a framerate is.

What We're Building

Developing Tank is a suite of tools for editors, VFX editors, and assistant editors that removes manual repetition from every stage of post — from dailies to delivery. We're starting with the hardest parts: Dailies organization, VFX tracking, paperwork completion, ALE file repair, sequence parsing, and change detection. More is coming.

The Context
1:30 AM
The time we wrote the first script instead of sleeping
22
Episodes in that season (every day a new cut)
30 sec
How long it takes now instead of hours
0
AI guesses in our output (deterministic only)
The Principles
🎯
No AI Guessing

Deterministic automation only — calculated, not predicted. Your timecodes are parsed from actual file data. Your metadata is exact. No hallucinations here.

📤
Files In, Files Out

You upload what you have. We give you back something usable. AVB in, CSV out. EDL in, clean pull out. No surprises, a file you can actually use immediately.

🔗
Workflow Compatibility

Doesn't replace Avid or Google Sheets (or even your FileMaker) — works alongside them. You keep your pipeline. Developing Tank just makes the manual parts disappear.

If any of this sounds familiar, you're our user.

Try a free tool or join the waitlist. No commitment. No credit card.

Try a Free Tool →Join the Waitlist

Concerned about data privacy? Read how we handle your data.