01 / PLAN
Start with the result and the source
Avoid narrating every visible click. Introduce the problem, guide attention to the important decision, explain the result, and keep all claims accurate and supportable.
Write for listening rather than silent reading. Short sentences, deliberate punctuation, and a quick pronunciation test usually improve a voiceover more than an extreme speed adjustment.
02 / WORKFLOW
Complete the workflow step by step
- Prepare.
Outline the demo as problem, preparation, key action, result, and next step.
- Set up.
Write concise narration around visual moments, then verify names, prices, measurements, and product claims.
- Create.
Generate section-by-section audio in TTSHub using one documented voice and pacing setup.
- Review.
Place the voiceover in PeteCut first, align screen recordings or product shots, and add reviewed captions.
03 / QUALITY CHECK
Review the result before the next step
Listen from beginning to end with headphones. Check names, numbers, pauses, volume, and whether the delivery still communicates the intended meaning.
- Narration and on-screen action agree.
- Claims are current and verifiable.
- The voice does not describe obvious details unnecessarily.
- The CTA matches the demonstrated result.
04 / QUESTIONS
Common question
Should I record visuals or voiceover first?
Either can work, but a stable narration outline gives the edit a clear structure. For exact software timing, record the action and refine narration against it.
Can I update this workflow later?
Yes. Save the source and project details, then update the relevant settings, content, or output when the destination requirements change.