any2.video
~/resources / marketing-video-production-for-software-companies
article 5 Sept 2026 · 4 min read

Marketing Video Production for Software Companies: What a Verified Walkthrough Costs and What Arrives

Production for software is not a shoot. There is no crew, no studio and no talent. There is an environment, an operator and evidence. Here is what that changes about the process, the deliverables and the invoice.

Ask a video production company for a quote and you get a structure inherited from advertising: pre-production, shoot day, post, revisions. Day rates for people who will be in a room. That structure prices the wrong things for software, where nobody is in a room and the expensive part is knowing which menu holds the setting.

Production for a software product has a different shape, and once the shape is right the pricing becomes simple enough to publish, which is why ours is on the pricing page rather than behind a call.

What replaces pre-production

Not a storyboard. A brief of one sentence, and an environment.

The brief names one product and one task with a finish line. From it we confirm three things in a single reply: the scope, the access needed, and the environment it will run on. That exchange is usually two emails and it replaces the discovery call, the treatment and the shot list, because there is nothing to design. The product already decides what the screen looks like.

The environment is the real preparation. A clean instance, seeded with whatever data the task needs, snapshotted so a second take starts where the first did. Building it takes longer than the recording, and it is reusable for every subsequent task on that product, which is why the first video in a batch costs more attention than the tenth.

What replaces the shoot

An operator running the task on camera, with the recorder started before the task and stopped after it fails. Every attempt is logged with a timestamp. There is no crew and no talent, and the footage nobody plans for — the attempt that did not work — is the footage that ends up mattering.

Then verification, which has no equivalent in advertising production at all: the result is checked against evidence the product produced independently. The file exists in the bucket and its checksum matches. The alert arrived. The restored machine boots. Four seconds of that on screen is the difference between a demo and a walkthrough.

The three modes, and why the rate differs

Rate follows how much real operation is involved, because that is where the cost is.

  • Live Operation, 15 tokens a finished minute. Screen recording of a real run on your product. Highest evidential value, most operator time.
  • Slide-Rendered, 10 tokens a finished minute. Built from the run log, photographs and the manual, narrated. For hardware, physical steps and air-gapped systems where a camera is not useful.
  • Designed, 6 tokens a finished minute. Motion graphics on verified facts. For concepts, release notes and comparisons where nothing is filmed.

One token is one US dollar, so a four-minute live walkthrough is sixty dollars of production and a sixty-second designed explainer is six. The unit is the finished minute, not the day, because the day is not what you are buying.

What arrives

Every delivery, regardless of mode:

  • The video, as an MP4 and on YouTube, public or unlisted as you prefer
  • A written guide with the exact steps that worked
  • Troubleshooting notes: what failed first, and the fix
  • Captions and narration in the languages you asked for
  • The version tag, the run date and the verification record
  • A vertical cut for social

The guide and the troubleshooting notes are included rather than upsold, because a walkthrough without them is only half of the asset. The written version is what gets found in search and cited in answers; the video is what convinces the person who arrives.

The line item nobody quotes for

A traditional production ends at delivery. A software video's real cost starts there, because the product keeps moving and the video does not.

Each video is bound to the product version it ran against. When you ship, the tasks the changelog touched are re-run, at half the original rate. A clean re-run republishes quietly; a failed one is flagged with its log, which tells you a release broke a documented path on release day rather than in a support ticket a month later.

Ask any production company you are evaluating what happens on your next release. The answer is usually a new quote.

Add-ons, and what is already included

  • Extra language track, +2 tokens a minute. One verified run, narrated and captioned again.
  • Re-run on your next release, 50% of the original.
  • Written guide and troubleshooting notes: included.
  • Vertical cut for social: included.
  • First sample, one product and one task: free.

A realistic first batch

Six tasks, live, averaging four minutes: 360 tokens. English plus German on all six: another 192. Around 550 dollars for the set that covers your highest-volume support questions, with guides, troubleshooting notes and captions, re-runnable at half rate when you ship.

The full sheet of rates and inclusions is on the pricing page, and there is a one-page version to circulate in the service datasheet.

Start with the free one. Send one product and one task in a sentence.

$ get-sample →