Run a Demo Video Brand QA Before Launch

A launch video can make a new brand feel real faster than a landing page.

It can also preserve every unfinished decision.

The founder says the old product name in the first ten seconds. The browser bar shows the preview deployment. The captions spell the name wrong. The thumbnail uses last month's icon. The YouTube description links to a short-term waitlist. The Loom account still belongs to the contractor who recorded the walkthrough. The transcript says "AI ops platform" even though the approved category phrase is now "scheduling software for home service teams."

Unlike a web page, a recording is not easy to patch quietly. People download it, forward it, embed it, clip it, quote it, and watch it without the surrounding context. A stale demo video can outlive the website it was meant to promote.

A demo video brand QA pass is a narrow review of recorded walkthroughs, launch videos, sales demos, product explainers, onboarding clips, webinar replays, and founder-recorded screen shares before they reach customers, investors, partners, or press.

It is not a full production critique. It does not grade lighting, editing taste, or camera confidence. It asks whether the video teaches the same public name, URL, category, handle pattern, product state, and contact route as the rest of the launch.

If the demo account itself is still messy, run the demo workspace brand QA first. If the recording uses product screenshots or screen captures, pair this with the screenshot brand safety pass. Video QA is the last mile: it checks what survives once the product, voiceover, captions, thumbnail, and hosting page are packaged together.

Inventory The Videos That Can Travel

Do not only review the polished launch trailer.

List every recording an outside person might see:

| Video | Where it may travel | | --- | --- | | Homepage product demo | Website hero, launch email, sales replies | | Founder walkthrough | Investor updates, LinkedIn, private communities | | Sales demo clip | Follow-up emails, forwarded buyer threads | | Product Hunt gallery video | Launch page, social reposts, scraped previews | | Support tutorial | Help center, onboarding messages, search results | | Webinar replay | Partner pages, nurture emails, community posts | | Loom or async walkthrough | Prospect threads, investor intros, customer onboarding | | App store or marketplace video | Third-party listing, review process, search snippets |

The risk is not limited to public uploads. A private Loom can become public enough when a founder forwards it to ten prospects and one of them shares it internally. A support tutorial can become the first search result for a branded query. A webinar replay can be clipped by a partner who does not know the brand changed two weeks ago.

Write the inventory with file names, URLs, owner, status, and intended audience.

| Field | Example | | --- | --- | | Video name | northline-launch-demo-v3.mp4 | | Public destination | Homepage and launch email | | Host | YouTube unlisted, embedded on site | | Owner | Marketing | | Current status | Needs caption review | | Replace rule | Re-record if URL, category, or product name changes |

"Demo video done" is not a useful status. "Homepage demo v3, YouTube title, captions, transcript, thumbnail, and embed approved on August 12" is useful.

Put The Brand Facts Beside The Recording

Before pressing play, write the facts the video has to obey.

Use the same facts as the rest of the launch:

| Field | Approved answer | | --- | --- | | Public brand name | Northline | | Pronunciation | North-line, two clear syllables | | Exact casing | Northline, not NorthLine or NORTHLINE | | Canonical URL | https://getnorthline.com | | Spoken URL | getnorthline dot com | | Category phrase | Scheduling software for home service teams | | Short description | Helps home service teams assign jobs and keep crews on time | | Handle pattern | @getnorthline | | Demo workspace | Northline Demo Workspace | | Support route | support@getnorthline.com or /help | | CTA | Join the waitlist | | Phrases to avoid | BetaOps, AI field ops, workforce intelligence |

This table should come from actual decisions, not from the video editor's memory. If spelling, casing, abbreviation, or pronunciation is still unclear, finish the brand name style sheet before approving a voiceover. If the URL is still moving, finish the canonical brand URL checklist before recording anything that says the address out loud.

Video makes uncertainty expensive. A typo in body copy can be fixed. A founder saying the wrong URL in a recorded intro usually means re-recording, cutting around it, or shipping a visible correction.

Listen For The Spoken Brand

Most brand QA is visual. Video adds sound.

Listen to the recording without watching the screen first. Ask whether someone hearing only the audio would understand:

What the brand is called.
How to pronounce it.
What the product does.
Who it is for.
Which URL or next step matters.
Whether the company name and product name are the same or different.

Spoken mistakes are common because people fall back to internal language under pressure. The homepage says "Northline." The founder says "Northline Labs." The caption says "North Line." The screen title says "Northline Beta." A viewer should not have to reconcile those versions.

Use a practical audio table:

| Moment | QA question | | --- | --- | | Opening line | Does it say the approved public name and category? | | Product walkthrough | Are feature names public names, not internal project labels? | | URL mention | Is the domain easy to hear and type? | | CTA | Does it match the website and launch copy? | | Support mention | Does it point to a monitored route? | | Closing line | Does the viewer know the next step? |

If the name is unusual, do not improvise pronunciation. Record it the way the team wants customers to repeat it. This matters for sales calls, podcasts, customer referrals, investor intros, and support conversations. A name that looks good in a logo still has to survive being said out loud.

Watch The Screen Like A Stranger

Now watch the video with the sound off.

Look for brand facts inside the frame:

Browser address bar.
Tabs and bookmark bar.
Workspace or account name.
Product logo and favicon.
Page titles.
Empty states.
Notifications.
Email previews.
Calendar links.
Help widget labels.
Social handles.
Payment, auth, or analytics provider names.
Old beta badges.
Personal names, emails, phone numbers, or real customer data.

Pause at each major transition. Video hides mistakes because the viewer is moving with the presenter. A wrong URL may only appear for three seconds, but someone can pause, screenshot, or quote it.

Use the same standard as screenshot QA: if a frame contains a brand fact, that fact must match the approved launch source. Do not assume motion makes it invisible.

| Weak frame | Better fix | | --- | --- | | Address bar shows northline-beta.vercel.app | Re-record from the canonical domain | | Workspace says Beta Test Org | Rename the demo account before capture | | Tab title shows repository name | Fix metadata or crop only if the tab is irrelevant | | Profile menu shows founder Gmail | Use a clean demo user | | Notification mentions old plan name | Update product copy or avoid that flow | | Browser bookmark bar exposes tools | Hide the bar or record from a clean profile |

Avoid solving stale brand facts with blur unless the issue is genuinely sensitive data. A blurred old domain or old product name tells careful viewers that something was hidden. Re-recording from a clean environment is usually the better brand fix.

Check Captions And Transcripts As Public Copy

Captions are not an accessibility afterthought. They are launch copy.

They also create search and AI-readable text that may be separated from the video. A transcript can be indexed, pasted into a sales note, summarized by a tool, or used by a buyer who never watches the full recording.

Review:

Auto-caption spelling of the brand name.
Product and company name consistency.
URLs and email addresses.
Speaker names and titles.
Feature labels.
Category phrase.
Any legal, pricing, support, or privacy claims.
Filler words that make the transcript confusing.
Accidental private comments from screen-share setup.

Auto-captions are especially risky for invented names, compressed names, acronyms, and modified domains. "Northline" may become "north line." "Getnorthline dot com" may become a useless phrase. A category phrase may be simplified into something broader and less accurate.

For important launch videos, export the captions or transcript and search it like source code:

old name
old domain
beta
test
staging
founder email
old category phrase
old plan name

Then read the transcript around each match. Do not replace blindly. Some references to old names may be intentional, especially in rebrand videos. If so, make the bridge explicit: "Previously called BetaOps, Northline is the same team on a new domain." If the bridge is not needed, remove the old name before publication.

This connects to the broader launch copy QA pass. Captions and transcripts are just another place launch copy can drift.

Treat The Thumbnail, Title, And Description As A Landing Page

The video host page may be seen before the embedded video.

Check the packaging:

| Field | What to verify | | --- | --- | | Video title | Current brand name and clear topic | | Description | Canonical URL, accurate category, monitored contact route | | Thumbnail | Current visuals, no stale screenshots, safe crop | | Channel or account name | Official brand or clearly intentional founder account | | Tags or categories | No old name, beta category, or misleading keyword stuffing | | Chapters | Feature names and timestamps match the recording | | Pinned comment | Current CTA and support route if used | | Embed title | Does not expose a draft file name |

A video titled Northline Demo v7 FINAL may be understandable internally, but it looks careless when embedded. A thumbnail with a tiny old URL in the corner can outlast the recording if people share the card. A description that links to a temporary waitlist can keep sending buyers to the wrong path after the homepage is fixed.

For thumbnails, apply one simple rule: the viewer should be able to tell whether the video is official without reading tiny text.

That does not mean every thumbnail needs a logo lockup and a giant headline. It means the image should use current product visuals, current brand assets, and a crop that still makes sense at small sizes. If the thumbnail is a screen capture, run it through the screenshot safety pass. If the video will be pasted into Slack, LinkedIn, or an email draft, run the brand link preview QA on the final URL too.

Review The Hosting Account And Playback Path

The host can undermine the brand even when the video itself is clean.

Open the video from the same path an outsider will use. Check:

Does the URL look official enough for the audience?
Is the account name current?
Is the profile image or channel avatar current?
Is the video public, unlisted, private, or embedded-only by design?
Are suggested videos, end screens, or overlays creating confusion?
Does the embed work on desktop and mobile?
Does the player show a stale file name before playback?
Does the share button reveal an unapproved host or personal account?
Are comments enabled only if someone will monitor them?
Does the video have a clear replacement path if it changes?

For a tiny launch, an unlisted YouTube video may be fine. For a sales-led product, a hosted Loom may be more practical. For a polished public page, a branded video platform may be worth it. The brand QA question is not "Which host is best?" It is "Does this host make the recording feel official and controllable enough for how it will travel?"

Be careful with personal accounts. A founder-hosted walkthrough can feel direct in an investor email, but the same account may look strange on a homepage. A contractor-owned Loom may work for internal review, but it should not become the permanent public demo unless ownership and replacement are documented.

If the video host is launch-critical, add it to the brand asset handoff sheet. Record who owns the account, where the source file lives, who can replace the embed, and whether captions and thumbnails are stored separately.

Test The Final Embed, Not Only The File

A clean MP4 can still fail in the place customers watch it.

Test the final video in context:

| Placement | What to check | | --- | --- | | Homepage | Load speed, poster image, crop, mobile controls, CTA nearby | | Product page | Does the video support the page promise? | | Launch email | Does the fallback image and link look trustworthy? | | Sales follow-up | Does the preview title look like a real brand asset? | | Help article | Does the tutorial match current UI and support route? | | Marketplace listing | Does the host, thumbnail, and title meet listing rules? | | Social post | Does the crop still show the right cue on mobile? |

Use a clean browser profile. Turn on captions. Watch on mobile. Open the link from an outside email account if the video is meant to be forwarded. If it is embedded, click through to the host and check what the viewer sees there too.

The surrounding page matters. If the video says "Join the waitlist" but the page CTA says "Start free trial," the video is already stale. If the video tells people to visit /demo but the link beside it points to /contact, fix the mismatch before publishing.

Give Each Video A Re-Record Trigger

Some launch videos age quickly. That is fine if the team knows when to replace them.

Write down the trigger:

| Trigger | Action | | --- | --- | | Brand name, casing, or pronunciation changes | Re-record or retire | | Canonical URL changes | Re-record if spoken or visible | | Product category changes | Re-record intro and captions | | Signup path changes | Update CTA, description, and embed placement | | UI changes materially | Re-record walkthrough or add a dated note | | Pricing or plan names change | Pull any affected sales/demo video | | Demo data becomes unsafe | Remove immediately and recapture | | Host account changes owner | Verify URLs, embeds, captions, and thumbnail |

This is where video QA becomes operational. A launch video should not sit in the site forever just because nobody remembers who can edit it. If the homepage video is important, assign an owner and a review cadence.

For example:

| Video | Owner | Review date | Re-record trigger | | --- | --- | --- | --- | | Homepage product demo | Marketing | 30 days after launch | URL, category, signup path, major UI change | | Sales walkthrough | Revenue | Before first paid campaign | Pricing or plan name change | | Support setup tutorial | Support | Monthly for first quarter | UI or onboarding step change | | Founder intro | Founder ops | After launch week | Category, CTA, or public proof change |

The first month after launch usually changes the most. Customers ask new questions. The category phrase tightens. The signup path changes. A feature moves. The launch video should not become a museum piece unless it is explicitly archival.

Run A Stranger Playback Test

Before publishing, ask someone outside the project to watch the final version.

Give them no briefing. Then ask:

What is the company or product called?
What does it do?
Who is it for?
What URL or next step did you remember?
Did anything look unfinished, private, or inconsistent?
Would you know where to ask a question?

This test catches problems internal reviewers miss. The team already knows that Northline Labs operates Northline. The viewer may not. The team knows getnorthline.com is the permanent domain. The viewer may only remember the staging URL that appeared in the address bar. The team knows a feature name is internal. The viewer may repeat it in a buyer thread.

If the viewer cannot answer the basics, the video is doing too much, saying too little, or using the wrong brand facts.

Do not overreact to every taste comment. Fix the issues that affect recognition, trust, action, or safety. A slightly plain video can launch. A video with the wrong name, wrong URL, stale captions, or unsafe demo data should not.

Keep A Short Approval Record

The approval record can be simple:

| Item | Approved? | | --- | --- | | Video file name and source location are recorded | | | Public brand name, pronunciation, and casing are correct | | | Canonical URL is correct when spoken, visible, linked, or described | | | Screen recording uses a clean demo workspace | | | No private customer, employee, API, billing, or internal data is visible | | | Captions and transcript use current names and links | | | Thumbnail uses current assets and safe crop | | | Host page title, description, account name, and privacy setting are correct | | | Embed works on desktop and mobile | | | CTA matches the page where the video appears | | | Owner and re-record trigger are documented | |

Keep this beside the launch copy checklist, asset handoff sheet, or content calendar. The point is not bureaucracy. The point is preventing a stale recording from becoming the most durable public explanation of the brand.

If mistakes slip through after launch, add them to the brand correction queue. But do the video QA before the first wave of shares whenever possible. Videos are persuasive because they feel concrete. Make sure the concrete version is the current brand.

Run a Demo Video Brand QA Before Launch