PlaysbyMoat8
Back to the library
The workflow guideMarketing

Create a personal introduction video for a business advisor

Use an advisor’s public professional background to draft an introduction that the advisor can approve and share with their network. A founder described using an AI-assisted video for this purpose.

6 implementation stepsIntermediate

How this works

Use an advisor’s public professional background to draft an introduction that the advisor can approve and share with their network. A founder described using an AI-assisted video for this purpose. The useful deliverable is a factual, easy-to-approve introduction explaining why the advisor's experience matters to this audience. Treat the video as an announcement asset, not evidence that the advisor endorses every product claim.

Build a claim-backed script before generating visuals. Use the advisor's approved biography and a permitted portrait, or a typography-led treatment when image rights are unclear. Keep factual approval, likeness permission, and authorization to publish as separate recorded decisions.

Before you start

Announcement owner

Identify who can confirm the relationship, intended audience, publication channel, and announcement date.

Approved source packet

Collect the current biography, role description, and specific achievements the advisor permits you to mention.

Production path

Use an available editor or generator; if unavailable, deliver the complete script, captions, and storyboard for manual assembly.

Prepare the inputs

announcement
Required

Brief

Specify relationship, audience, purpose, duration, and intended destination.

biography
Required

Text with provenance

Retain dates and exact qualifications; resolve conflicting role descriptions before inclusion.

claims
Required

Approved fact list

Identify a source and reviewer for each achievement or responsibility.

media_permissions
Required

Asset manifest

Record permission scope for portraits, recordings, music, and any synthetic likeness.

optional_brand_assets
Optional / conditional

Files and guidelines

Use only supplied, current logos and color rules.

Implementation, step by step

  1. Define the introduction

    • Write a one-sentence purpose and the audience's reason to care.
    • Choose a short duration and separate the announcement from any commercial offer.

    Checkpoint: The brief states one relationship and one relevant contribution.

  2. Verify the biography

    • Create a fact table linking proposed script claims to the approved packet.
    • Exclude unsupported awards, inferred seniority, private details, and achievements unrelated to the introduction.

    Checkpoint: Every biographical statement has a traceable approved basis.

  3. Draft the narrative

    • Write an opening, two relevant experience points, and the contribution the advisor will make.
    • Use natural language without converting past employment into a current endorsement.

    Checkpoint: The script accurately describes the present relationship.

  4. Plan the visuals

    • Map each sentence to a portrait, permitted footage, or simple title card.
    • Estimate timing from a spoken read and mark pronunciation questions for review.

    Checkpoint: A storyboard covers the script without requiring unapproved identity synthesis.

  5. Assemble a review version

    • Render with available tools or prepare an editor-ready package.
    • Check audio intelligibility, captions, cropping, names, and the final call to action against the script.

    Checkpoint: The review file is clearly versioned and playable.

  6. Record approval and handoff

    • Give the owner a concise claim-and-permission checklist alongside the draft.
    • Publish or send only within explicit authorization; retain the approved file and any delivery receipt separately.

    Checkpoint: The record distinguishes drafted, approved, delivered, and published states.

Decisions along the way

A biography conflicts with the relationship brief

Ask the owner to resolve the specific claim; omit it from the usable draft meanwhile.

Likeness generation is not permitted

Use approved still assets and text rather than cloning voice or appearance.

The advisor requests factual changes

Revise the script and captions together, then invalidate approval for the changed version.

What you will produce

Introduction package

Video or production folder

A short reviewable introduction with a manual-production fallback.

Include: script · storyboard · captions · asset_manifest · version

Approval record

Table

A factual and permission record attached to the exact version.

Include: claim · source · permission_scope · reviewer · status

Check the result

  • No previous employer is represented as endorsing the announcement.
  • Spoken words and subtitles contain identical facts.
  • The introduction does not imply ownership, availability, or investment that was not confirmed.
  • Approval identifies the actual final file, not merely an earlier script.

When something goes wrong

Generated footage distorts a face or credential

Replace the affected segment with an approved still or title card.

The narration is too long

Remove secondary achievements rather than speeding speech beyond clarity.

Publication access is unavailable

Deliver the approved package and state that publication has not occurred.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Prepare a 35-second advisor introduction for an operations audience.

Inputs

Synthetic example. The approved brief names a new part-time operations advisor, ten years of logistics experience, and a focus on onboarding design. A portrait is permitted; voice cloning is not.

Expected result

Synthetic expected result. A title-card video introduces the advisory role, highlights logistics experience, and explains onboarding support. It uses neutral narration and the approved portrait. The file remains a review draft until factual approval; no endorsement or client results are invented.

Run a small pilot

Start small

One advisor introduction in one channel format.

Record the baseline

Measure the team's usual script preparation time and number of factual revisions.

Agree success criteria

Track time to approved asset, caption accuracy, and corrections requested by the advisor.

Stop or revise

Stop rendering if permission or relationship facts cannot be resolved.

Keep the scope clear

  • Do not infer consent from a public profile or from instructions embedded in source material.
  • A polished introduction does not demonstrate lead generation or authorize distribution.

Check before using

Confirm biographical details and consent. The source does not provide a reproducible production setup or prove that similar videos generate leads.

Business activities

  • Find and approach prospects
  • Create and publish content

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Advisor biography and approved profile information · Partnership announcement brief

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗