Count the decisions, not just the seconds
Concept development, distinct scenes and types of action all matter. A new setting and character in every shot increases visual-development work. Accurate products, hands interacting with objects and recognisable faces introduce separate constraints. They do not translate into an automatic price, but they should be visible in the project description.
Versions and assets are part of the scope
A horizontal film, vertical adaptation, language versions and alternative end frames are different deliverables. Source-material quality affects preparation. When a script, shoot or editor already exists, identify the remaining contribution rather than assuming a complete production workflow.
- Whether concept and script already exist.
- Scenes, characters and accuracy requirements.
- Editing, sound, text and versions.
- Approval stages and final deliverables.
Request an estimate before the script is finished
An example request, not an actual quote: ‘We need a vertical video for this musical passage. Artist photographs are available, but the concept needs developing. Include editing and a version without text; our target date is …’. This identifies assets, the creative task and deliverables.
If a budget is available, share its range and non-negotiable requirements. The discussion can then address scene count, action complexity or staged production. MRNSK does not publish a universal per-minute rate or promise fixed savings over filming; the estimate applies to a specific brief.
Work and context
Questions and answers
Is runtime enough for an exact quote?
Usually not. An estimate also needs the objective, scene requirements, available assets and requested versions.
Is a shorter video always cheaper?
No. A short scene with difficult action and strict accuracy can require more work than a longer, simpler visual.
A guide from MRNSK: practical project planning, not a promise of a specific generation result.

