The cost of a product video depends on what has to be made to get to the final cut. A thirty-second edit from ready-to-use footage is a different job from thirty seconds of original 3D animation.

At Raynhaus, I quote against the actual scope. There is no published fixed rate for a product video. To make a quote useful, I first need to know what the video must explain, what material exists and where the result will run.

Start with the job the video has to do

A video showing someone how a feature works needs a different structure from an ad introducing a physical product. Decide who is watching, what they already know and what you want them to do next.

That decision affects the script, pacing, detail and call to action. If you are still choosing the format, read product demo vs brand film before specifying the length.

Existing material changes the scope

Good supplied footage can reduce production work, but it still needs to be reviewed. Check resolution, framing, sound, permissions and whether it shows the moments the script requires.

A software demo may need fresh screen recordings, a stable product build and a clean example account. A physical product may need filming, photography or a 3D model. If filming is required, we define that production separately rather than assume it is part of an editing quote.

Motion and 3D add different kinds of work

Motion graphics can explain a process, introduce a feature or organise information. The scope depends on the number of scenes, the design of the graphics and how much animation they need.

For 3D, the questions extend to the model, materials, lighting, animation and rendering. An existing usable model is different from a product that has to be built from references. Character work and compositing into live footage introduce further tasks.

This is why runtime alone is a poor way to estimate the job. One complex shot can involve more production than several simple edits.

Count every version you need

A main video, a vertical cut, three shorter ads and two language versions are separate outputs. Some reuse the same work; others need a new edit or layout.

List the destinations, aspect ratios, durations, languages, captions and end cards in the brief. Confirm who supplies and approves translated text. If editable project files are required, put that in the scope too.

Review rounds belong in the quote

We agree what is reviewed at each stage and how feedback is collected. Approving the script and direction before detailed animation helps prevent expensive changes later.

Changing wording in an end card is different from replacing the central concept after production. A useful proposal makes that distinction clear and states how additional work is handled.

How to brief a video within your budget

Send the following:

  • The product and the audience.
  • The purpose and intended placements.
  • Available footage, recordings, models and brand assets.
  • Required versions, languages and deadline.
  • Your budget range, if you have one.

With those inputs, I can propose a feasible approach and explain the work behind the quote. Sometimes the right first scope is one clear demo; sometimes it is a short film with campaign cutdowns. Discuss your video project or explore video, motion and 3D services.

What a useful product video estimate actually estimates

If you are searching for a product video production cost, you probably want a number you can put into a budget. This article cannot supply a market average or a studio price list: Raynhaus does not publish either. It can help you turn a vague request into a scope that different producers can price against the same assumptions. That is the step that makes the numbers meaningful when you receive them.

A quote should describe an outcome, the work required to reach it and the conditions under which that work is priced. “One product video” does not do this. “One approved demonstration of the dispensing mechanism, made from supplied footage, with a horizontal master and a separately composed vertical version” starts to do it. The second description leaves fewer decisions hidden inside the price.

Ask for a breakdown by stage rather than a price for every second of runtime. Useful stages include discovery, script, visual development, asset preparation, production, edit, sound, adaptations and delivery. A small project might combine several stages in one line. What matters is that both sides can explain where an assumption changes the job.

The cheapest proposal may contain the fewest assumptions about what happens next. It may also exclude work another proposal includes. Compare the proposed film before comparing the total. You can then make a deliberate choice about ambition, coverage and the material you are willing to supply yourself.

Build an asset inventory before asking for a quote

An asset inventory is a list of what exists, where it is and whether it is approved to use. It is different from sending a folder containing everything the company has ever produced. Start with the items that support the video’s central demonstration, then add the brand material needed to make the result feel like your company.

For footage, list the original files, orientation, approximate duration, available sound and any restrictions you already know about. Include a low-resolution viewing copy if the originals are large, but keep the original files available for the actual edit. A social download or a compressed messaging attachment may not be a useful production source.

For a software product, identify the version that will be recorded, the example data and the person who can confirm that the workflow is accurate. For a physical product, identify the exact variant, packaging artwork and product references. A model of last year’s packaging can create work rather than save it if the visible details have changed.

Give each asset one of three practical labels: approved and usable, available but needs checking, or still to be created. The middle group is where budgets become unreliable. A producer needs to inspect a supplied 3D model or an audio recording before treating it as ready. That inspection belongs near the beginning of the process, before the visual approach depends on it.

Different production routes have different questions

Editing supplied footage

An edit from supplied footage begins with coverage. Can the available shots tell the required story? A folder can contain hours of beautiful material and still lack a view of the action the product video needs to explain. Ask the editor to identify those gaps before agreeing to solve them through pacing, music or graphics.

The work can include selecting takes, organising files, matching colour between sources, cleaning sound, building the structure and creating titles. It can also include removing unwanted details or repairing a shot. Those repairs should be described separately when they are material to the scope. “Editing only” is not a reliable description if the plan depends on extensive compositing.

A practical way to reduce uncertainty is to supply a short select reel with references back to the original files. It shows what you believe is useful without forcing the editor to accept those selections. Keep a note of any shot that cannot be used publicly. Finding out at final review that the strongest shot has no clearance can force a structural change.

Recording a software demonstration

Screen capture has its own preparation work. The example account needs plausible, approved data. Notifications, personal information and unfinished features should be addressed before recording. Decide whether the demo shows one continuous task or a sequence of shortened steps. The viewer should be able to distinguish a real interaction from a graphic explanation layered over it.

The interface also needs to remain stable long enough to finish the video. Agree who signs off its accuracy and what happens if the product changes after capture. A new button label can affect screen recordings, voiceover, captions and translated versions. Treat an interface update as a dependency rather than a tiny cosmetic correction.

You can save time by preparing an approved walkthrough, but avoid scripting every cursor movement before a creative approach has been agreed. The important input is the correct sequence of actions and the outcome it produces. The editor can then decide how to show that sequence clearly without making viewers watch every loading state or repeated action.

Creating a physical product film

A physical product may need filming, still photography, animation or a combination. Establish who provides the product, its condition and any required spare units. Surfaces that look clean in person can show marks in a close shot. Packaging artwork, labels and reflections can become important parts of the image rather than background details.

A shoot introduces coordination beyond editing: location, equipment, crew where needed, product preparation and the agreed coverage. These are scope questions, not promises that every production needs a large team. A simple tabletop demonstration and a film involving people in multiple locations should not be priced as versions of the same generic deliverable.

Before committing to filming, describe which details the audience must actually see. If the useful explanation is inside an object, a diagram or a short 3D sequence may communicate it more clearly. If touch, handling or a real environment is central to the decision, filmed evidence may be the better starting point. Choose the method for the explanation, then estimate that method.

What changes a 3D product animation quote

A supplied 3D model is a starting point, not a guarantee that the scene is ready. It may require cleanup, revised materials, packaging artwork, a different level of detail or changes to suit close framing. Ask whether the estimate includes checking the files and whether any model preparation is provisional until that check is complete.

Describe the visible action rather than simply asking for “premium 3D.” Does a lid open? Does liquid move? Does the camera travel through an assembly? Are different product variants shown? Each question introduces different decisions about construction, motion and the look of the final image. A reference film is useful when you identify the exact qualities you want from it.

The number of distinct setups matters as well. Reusing one approved lighting and material treatment across several views can be different from inventing a new visual world for every shot. That is a creative choice as much as a production one. Repetition can establish a clear product language; it can also become monotonous if the story requires contrast.

Ask where you will approve appearance and motion. A still frame can settle materials and lighting before detailed animation. A rough animation can settle timing before final rendering. These checkpoints give you decisions you can judge without asking the producer to finish every frame before you know whether the direction is right.

Runtime, shot count and complexity are separate variables

Two videos with identical durations can require different amounts of work. One may use an uninterrupted screen recording with a short title. Another may contain many original scenes, each with different animation, sound and artwork. Runtime tells you how long the viewer watches. It does not tell you how much has to be designed or made.

For planning, make a scene list. For each scene, record what appears, what changes, what the audience learns and what source material exists. You do not need a finished storyboard to do this. A sentence describing the required evidence is enough to expose a missing shoot, an unprepared interface or a model that nobody has supplied.

Then look for scenes that can share work. Could the same product setup show two useful details? Could a demonstration use one well-prepared example account instead of several? Could a single diagram replace a difficult transition without weakening the explanation? These are sensible ways to change scope because they preserve the information the audience needs.

Reducing runtime only helps when it removes actual work. Cutting a finished ending from a video does not erase the cost of creating it. Make decisions about scenes and production routes before they are built, when a smaller scope can still change what the producer needs to do.

Voice, music and sound need named responsibilities

Decide whether the story is carried by voiceover, on-screen text, interview audio or the action itself. This affects the script and the review process. A voice-led film needs approved wording before recording. A text-led demonstration needs enough screen time for the words to be read alongside the relevant image.

Music is also a rights and delivery question. Confirm who selects it, who licenses it and what use the licence allows. Do not assume that a track heard in a reference video is available for your campaign. The same principle applies to stock footage, sound effects and any supplied recording. A link to a reference is a direction, not permission to reuse it.

Sound work can include an edit, noise reduction, voice treatment, music selection and a final mix. Specify the required output rather than treating all audio as a single invisible finishing step. A film that needs to work without sound may need different visual information from one intended for a controlled presentation with speakers.

If synthetic voice is being considered, agree its use openly, including pronunciation, language review and any restrictions from the provider. It should be chosen because it suits the production and the audience. It does not remove the need to approve the script or listen carefully to the final result.

Accessibility belongs in the original delivery list

Captions, transcripts and descriptions of meaningful visual information should be discussed when the video is planned. They can affect the script, the layout and the files delivered. The W3C media planning guidance is a useful reference for deciding what a particular video needs. Exact requirements depend on its content and the applicable standard.

For the quote, name who prepares and checks these materials. Captions need to match the approved edit. A transcript needs an owner. Text should remain readable against the image and should not be hidden by interface controls or a platform’s overlays. Review an actual exported version rather than assuming the editing timeline proves the result is usable.

Also decide whether captions are supplied as a separate file, burned into the image, or both. These are different outputs with different uses. If a platform needs another layout, include that version in the delivery list rather than waiting until a team member tries to upload the master.

Make a version matrix instead of saying “social cutdowns”

Write a simple list with one line per deliverable. Each line should name the destination, aspect ratio, approximate duration, language, audio treatment, caption treatment and final call to action. That list is your version matrix. Its purpose is to stop an ambiguous phrase from expanding silently into many separate edits.

For example, a hypothetical brief might require one horizontal website demo, one vertical ad introducing a single feature and one silent loop for an event screen. Those are three different viewing situations. The ad needs an opening that makes sense without the website around it. The loop needs an explanation that works when someone starts watching halfway through.

Do not multiply versions mechanically. Ask whether each one has a real owner and a real placement. If the team cannot name where a version will run or what it should achieve, keep it optional until that is clear. A smaller approved list is easier to review and maintain than a large collection created for possible future uses.

For localisation, include the person who approves meaning, product terminology and pronunciation in each language. A translated sentence may require different timing or composition. A version that changes only captions is different from one with new voiceover, new screen capture and new on-screen text. Describe the change so the quote can reflect it.

Use approval gates to control rework

A useful review process gives each stage a specific question. At script review, ask whether the message, product facts and sequence are correct. At storyboard or treatment review, ask whether the images communicate that message. At rough-cut review, assess structure and pacing. At final review, check the agreed finish and delivery details.

This does not mean the first idea can never change. It means the effect of changing it is visible. A script correction before recording and a script correction after every language version has been mixed are different amounts of work. Agree how the producer will flag additional work and how you will approve it before it happens.

Collect comments from your internal reviewers before sending them. Contradictory instructions are not a useful review round. One person needs to decide which comments represent the company’s position. Product, legal or technical specialists can contribute, but the producer should receive one prioritised response that identifies any unresolved decision.

Use timecodes and describe the problem. “At this point I cannot tell which control was selected” is actionable. “Make it more dynamic” could mean faster cuts, more animation, a different opening or something else entirely. A clear problem lets the creative person propose the right correction without guessing at the intention behind the comment.

A quote comparison worksheet you can copy

When proposals arrive, read each one against the same questions. You can paste these into a document and leave a short answer beside each. An unanswered question is a clarification request, not automatically a reason to reject the producer.

  • What is the main deliverable and the audience question it answers?
  • Who writes and approves the script, product claims and voiceover?
  • Which footage, screen recordings, models and artwork are supplied?
  • What asset preparation, filming, design or animation is included?
  • Which versions, languages, captions and other files are delivered?
  • At which stages do reviews happen, and what does a round include?
  • Who handles music, stock and other usage permissions?
  • Which milestones depend on client feedback or third-party inputs?
  • What happens if the approved scope or product changes?
  • Are source files included, and are any licensed elements excluded?
  • What does the handover include after the final export is accepted?

Then mark differences in plain language. One quote may include writing and another may expect an approved script. One may include only a horizontal master and another may include separately designed vertical edits. Ask each producer to price the same final scope if you need a direct comparison. Do not force unlike proposals into a price-per-second calculation that hides the work you are actually buying.

Three hypothetical briefs and how their scopes differ

A software feature explanation

Imagine a team that needs to explain one scheduling task on its website. The product is stable, the example account is prepared and the marketing lead can approve the wording. The main work could be scripting a clear sequence, recording the task, editing out dead time and adding enough graphic emphasis to make the interaction legible.

The unknowns are still important. Who prepares the example data? Is the interface approved? Does the video need narration? Does the text remain readable in the actual player? If the team then asks for a launch ad, that should be assessed as another communication job rather than assumed to be a shorter export of the demonstration.

A physical product with no usable footage

Now imagine a brand launching a small object with no approved images beyond packshots. The requested film shows handling, a close detail and the product in use. Production cannot begin with editing because the necessary evidence does not exist. Filming or an agreed alternative must be planned first, including who provides the product and who confirms that the action is accurate.

A lower scope might use fewer setups or a controlled demonstration instead of a broader lifestyle story. That is a decision about what is shown. It is more useful than asking for the same film to be made “more cheaply” without changing any of its requirements.

A 3D launch sequence with several variants

A third brief might ask for an animated reveal of a product range. A supplied model covers one variant, while the packaging and surface treatment differ across the others. The producer needs to inspect the model, establish the visual treatment and identify which changes can share a scene setup.

The quote should distinguish development of that shared treatment from making each additional variant and each delivery version. If more variants are likely, ask how the project should be organised to support them. This is a planning question; it is not a promise that future versions will be automatic or free.

Ways to reduce scope without weakening the explanation

Start with the audience’s unanswered question and protect the scene that answers it. Remove material that repeats information already supplied clearly by the page or campaign. A film does not need to carry the entire company history, every product benefit and every feature at once.

Supply organised, approved inputs. A clean logo package, final wording, current artwork and a named approver reduce avoidable uncertainty. This does not replace creative work, but it prevents the producer from discovering basic facts after a scene has already been built around the wrong version.

Separate essential versions from optional ones. Design for plausible future adaptations, while commissioning only the outputs you can actually place. If several teams need the video, align their requirements before production. Adding their needs after approval is one way a manageable project becomes a moving target.

Keep enough room for checking the final result. Removing every review or testing step may make a proposal shorter while increasing the chance of a mistake reaching the public. A useful reduction changes ambition or coverage. It should not depend on skipping the point at which someone verifies that the product, words and delivered files are correct.

Questions about product video pricing

Is a longer video always more expensive?

No. Duration is one input. Original scenes, difficult assets, filming, voice work, animation, reviews and adaptations also affect the scope. Ask the producer what work would actually disappear if the video became shorter. That answer is more useful than assuming every second has the same production cost.

Can you give an estimate before the script exists?

A provisional estimate can be based on an agreed outline and explicit assumptions. It should say what still needs checking. A discovery or planning stage may be the right first commitment when the product story, asset condition or production method is unresolved. Do not mistake an early allowance for a final scope.

Are project files the same as the final video?

No. Final exports are the usable viewing files. Project files may depend on software, plugins, fonts, stock licences and linked assets. If your team needs to reopen or adapt them, state that before the agreement and define the handover. Ask which dependencies can be transferred and what maintenance remains your responsibility.

What should I send if I have no idea what the budget should be?

Send the product, audience, destination, available assets, deadline and the question the video must answer. State the constraints you do know. A useful first conversation can identify a feasible production route and the choices that need deciding before a firm quote. You do not need to invent a budget figure to prepare those facts.

Prepare the handover before the final export

A delivery specification is a small document with a large practical effect. It tells the producer where each file will be used and tells your team which file to use when the project is complete. Name the main master, the placement versions, caption files, transcripts and any agreed thumbnail or poster image. A folder of unnamed exports leaves the next person to reconstruct decisions that were already made.

Agree a naming convention that distinguishes language, orientation, duration and approval status. Avoid calling several different files final. Keep one clearly approved set and archive superseded versions away from the upload folder. This is especially useful when a campaign has several approvers or when a new colleague takes over the account after production finishes.

Test the deliverables in their real setting. Put the website video in its intended player and check the text, poster frame, sound controls and captions. Upload a test version through the actual publishing workflow where that is possible. A file that plays correctly on an editor’s monitor can still be the wrong choice for a particular destination or content team.

If you expect later updates, identify the parts likely to change. A product interface, packaging label or closing offer can become outdated before the rest of the film. Ask what information the producer will retain and what a future update would require. This does not turn an update into included work; it lets you plan one without discovering that the approved assets are scattered across old messages.

Keep a record of approvals, licensed materials and the delivery list alongside the final files. Your future team should not have to guess whether a music licence covered the planned use or which person approved a claim. The producer can explain the creative and production dependencies, while your company remains responsible for its product facts and business permissions.

Finally, define acceptance in observable terms. The correct product appears, the approved wording is used, the required versions are present and the exports work in the agreed setting. Aesthetic judgment still belongs in the earlier creative reviews. Final acceptance should not become a completely new brief after the film has been built around decisions both sides already approved.

When those details are settled, a quote becomes easier to assess. You are buying a defined piece of communication, the process needed to make it and an organised handover that your team can use. That is the useful answer to the cost question before any number is signed off. Send those requirements through the project brief so we can discuss a scope based on the film you actually need.