Spend on the change that moves the image forward
Give each run a question, keep the successful parts, and stop paying for variations you cannot judge.
You do not need a bigger batch every time you get stuck. You need a clearer next decision.
“Does softer light make the label easier to read?” is a useful experiment. “Maybe the next one will be better” can keep going forever.
Give the run one question
Before using Image, Video, or another generation tool, write the detail you want to improve and what will count as a useful result.
For a product shot: correct bottle, readable label, room for copy. For video: recognizable face, stable object contact, one clear action.
Keep the requirements short enough to use while choosing.
Change one thing you can learn from
Asset: bottle hero
Question: does softer light help the label?
Keep: model, reference, ratio, product position, image count
Change: hard side light to broad soft side light
Result: label better / same / worse
Next: keep it, make one correction, or stop
Use a practical supported preview setting when it can answer the question. Increase quality when you need to inspect fine detail. Approve the still before video and the narration before a speaking render.
A seed can help organize comparisons when available. It is not a guarantee of identity across models or settings.
Read the total for the actual action
Quantity, resolution, duration, audio, and the selected workflow can change the price. Check the displayed total after finalizing the inputs; review a fresh quote when the configuration changes.
Judge a workflow by usable output. If one route repeatedly fails the label, its lower per-run price may not make it cheaper to finish.
Set a personal attempt or token limit before exploring. When the same failure repeats, change the source, mode, or brief instead of automatically repeating the run.
Know when you already have the image
If the required details pass and the asset fits its purpose, save it. You can make a different creative direction later without treating this one as unfinished.
For a delayed or uncertain submission, inspect the existing saved job before creating another. A timeout does not prove that nothing was submitted.
Next: use the troubleshooting guide to choose a specific repair instead of another guess.