The final shot. And the decisions behind it.
AI asset management for creative teams. Bring selected generations, prompts, references and review decisions into one shared project, so the next person can pick up the shot.
30 days of Team features with 100 GB trial storage. No card or automatic renewal. See trial terms
- Keep your current AI tools
- For solo artists and teams
A revision to test
The client wants the earlier look. A new artist has the shot.
The final export shows the result. To carry the look forward, the next artist also needs the selected version, its references and the decisions that shaped it.
“Keep the approved lighting. Change the product.”
- Which version?
- The chosen frame and its related alternatives.
- Which inputs?
- The prompt, references and model details the team saved.
- Why this choice?
- The review note behind the selected direction.
Your first real test
Put one real shot to work.
Add its selected versions, the references that matter and why one direction was chosen. Give the next person the intended view. Can they find the final and explain the choice?
Keep the test small. Make the result useful.
Start with a shot that needs a revision or handoff. You choose what to add and review the details you keep; the useful payoff is a record someone can work from.
Working alone? Reopen the shot yourself later. Judge BTW by whether the saved context helps you continue the work.
Case study · No Notes Studio
About 5 hours
per producer, per week — reported by No Notes Studio.
Less searching. More making.
The studio reports spending less time finding the prompt, reference and version behind a previous shot, and assembling the context a client asks for.
Self-reported by No Notes Studio; an individual result, not a forecast for your team.
From selected generation to shared final.
Take one real shot through the record your next revision or handoff will need.
Step 01
Save the shot while the choices are fresh.
Add selected work in BTW or through the optional browser extension. Review the prompt, tool and model details, and fill in the context you want to keep.
- You choose the file and the project
- Add missing details before saving; the extension saves what you explicitly add
Step 02
Keep the references behind the look.
Save the prompts and references that matter to the project in the Library. Search the material you have kept when the next version needs the same direction.
- Organize saved references and prompts by project and folder
- Keep source details with the material you choose
Step 03
Follow the decisions through the project.
Use the timeline and Ledger to see the work and decisions recorded in BTW. The next person can follow how the selected direction developed.
- Find recorded versions in the project history
- Keep decisions and notes close to the work they explain
Step 04
Hand over the final with its context.
Mark the selected version final, choose the view you want to share and check its scope. The recipient gets the work and the context you include.
- Keep the final identifiable among its related versions
- Choose the shared history and download permissions before sending
30 days on Team, no card
In their words
“Honestly, we love it. We don't lose track of how things were made anymore, and if a client ever asks how something came together, we can just show them.”
30 days on Team, no card
Production questions
When a client asks how the AI work was made.
Keep the inputs and human decisions you recorded available for review, handoff and relevant disclosure questions.
Which inputs and human decisions should the handoff explain? Client delivery guide →
What can a saved record establish, and what still needs checking? Production evidence guide →
Which disclosure questions should the team consider for this use? Article 50 guide →
BTW helps you organize and share the record you keep. Your team still decides what needs verification, permission or disclosure for each production.
Tool documentation
What should you keep for the next revision?
Practical guides for the tools in your production: check saved details, add missing context and prepare the client handoff.
Documentation guide
Google Veo documentation
The role of SynthID and the Flow inputs worth keeping for the next revision.
Read the guide →
Documentation guide
Midjourney documentation
Document the prompt, parameters and references alongside the selected image.
Read the guide →
Documentation guide
Stable Diffusion documentation
Keep seeds, checkpoints and available parameters for the next person working on the shot.
Read the guide →
Documentation guide
Adobe Firefly documentation
Understand Content Credentials and add the production record they do not replace.
Read the guide →
Get started
Give the next person more than the final file.
Start with one real shot. New accounts get 30 days on the Team plan, no card.