Best practices

How to spend credits deliberately, prepare source material that survives the trip, and publish at scale without surprises.

The short version

  • Prove a job on one item, in one language, before running it across the library
  • Credits are taken when a job starts, not when it succeeds
  • Trim video before dubbing — it's priced by the minute, per language
  • Write short steps — they survive the trip to every destination

Spend credits deliberately

The single most useful habit: remember that translation and dubbing are charged the moment you click Run job, not when the work lands. A job you fire by accident has already cost you, and most of what follows is a way of not doing that.

  • Run one language first. Check the output reads the way you want, then fan out to the other sixteen. A batch across every language costs the same whether or not you like the result.
  • Standardize before you translate. Translation works from the standardized text, so if the instructions read badly in English they'll read badly everywhere — at one credit per language, per item.
  • Watch the first job of any new shape. Activity shows each language separately, so you'll see a failure on language one before it repeats across the rest.

The estimate isn't the invoice

The figure shown before you run a job covers the AI work. Publishing is charged on top, by destination: hosting in Maestro bills per item per month, and each send to SharePoint or Dozuki bills per item. Budget for both.

Get video right before you dub

Dubbing is the most expensive thing Maestro does, and the only one priced by the length of what you give it: 2 credits for every minute of video, in every language you pick.

  • Trim first, dub second. Minutes round up per video, so a 4:38 clip is billed as five minutes — in each language. Cutting the thirty seconds of someone finding their notes is real money at ten languages.
  • Cut one long recording into a few short ones. Shorter videos are cheaper to re-dub when a step changes, and you re-dub the step that changed rather than the whole hour.
  • Prove the voice on one language. A dub that fails refunds itself automatically, but a dub you simply don't like does not — it worked exactly as asked.

If a video won't dub

Maestro measures a video's length once, when you add it. If that didn't work, it refuses to price the dub rather than guess — so re-adding the file is usually the fix.

Give it good raw material

Maestro is standardizing whatever you hand it. Clear source material costs exactly the same as unclear source material and comes out better.

DoWhy it matters
Keep each step to one actionShort, single-action steps survive every destination intact. Dozuki caps a step at 350 characters, and Maestro splits anything longer — so a rambling step arrives as two, split where Maestro chose rather than where you would have.
Say the tools and the hazards out loudTools, materials and safety notes are carried through to the published output — but only if they're in the source to begin with.
Keep files under 100MBAnything larger is refused by the server before Maestro sees it. Compress long video rather than splitting it mid-task.
Add content as you get itAdding is free and runs nothing. There's no cost to building the library up first and deciding what to standardize later.

Publish on purpose

Where output goes is a step in every job, not an afterthought — and unlike the AI work, publishing keeps costing after the job is done.

  • Host what people actually read. Keeping an item in Maestro bills per item, per month, for as long as it's there. It's cheap; a library of things nobody opens is less cheap.
  • Check the visibility. Hosted pages are public by default. Set unlisted or private on anything you don't want found.
  • Send once. Sending finished output to a connector charges that connector's fee each time — re-sending the same item twice pays twice, so fix the content first, then send.
  • Connect the destination before the job, not during. An action can't run without a destination, so the connector setup is worth doing while nobody's waiting on the output.

Next steps

Run your first job

The three moves end to end — add content, take an action, choose where it goes — and what each one costs.

Connect your systems

Set SharePoint or Dozuki up properly once, and every job after it has somewhere to land.

Need more help?

If your issue isn't covered here, reach out with your setup details and any error messages you're seeing.

Contact support