# Creator Script + Research Sample

This sample shows how I turn a topic into short-form scripts with source-aware research notes, hook options, b-roll direction, and a clear review boundary. It is written for creator, founder, and online-business content where the goal is retention without sounding AI-generated.

## Workflow

1. Define the audience and promise.
2. Find the tension: what is the viewer doing wrong, missing, or underestimating?
3. Write 3-5 hook options before writing the script.
4. Draft in natural spoken language, not polished blog language.
5. Add b-roll, on-screen text, and cut notes.
6. Flag any factual claims that need source confirmation before publishing.

## Sample 1: Remote Job Filters Are Lying To You

Audience: remote job seekers, career coaches, job-search tool users.

Goal: explain a pain point and tee up a practical workflow/tool.

Hook options:

- "Remote job boards are full of fake remote listings."
- "The word remote does not mean what you think it means anymore."
- "If a job says remote, I still check these three lines before applying."

Script:

Most people search for remote jobs by trusting the tag.

That is the trap.

A listing can say remote at the top, then quietly say "must be near our office," "hybrid after training," or "onsite meetings required" three paragraphs later.

So before I save or apply, I check three things:

First, the location line.

Second, the first paragraph after responsibilities.

Third, the compensation or compliance section, because that is where state and country restrictions usually hide.

If those three sections disagree, I mark the role as unclear instead of wasting time.

The better system is not more applications. It is fewer fake leads in the queue.

On-screen text:

- "Remote tag != remote job"
- "Check: location / requirements / restrictions"
- "Bad leads cost time"

B-roll:

- Screen recording of a job tracker.
- Highlighted listing phrases: "remote," "hybrid," "must be located in..."
- Spreadsheet row changing from `lead` to `blocked`.

CTA:

Send me five listings and I will show you which ones are actually remote.

Fact checks needed:

- Verify any specific listing examples before showing them publicly.
- Do not name companies unless the source is public and current.

## Sample 2: Why AI Automations Fail After The Demo

Audience: small business owners, operators, no-code/AI automation buyers.

Goal: position an integration-first automation service.

Hook options:

- "Most AI automations fail after the demo."
- "The problem is not the bot. It is the handoff."
- "If your automation needs a brand-new dashboard, your team probably will not use it."

Script:

The biggest mistake with AI automation is building a shiny new workflow that nobody asked for.

The demo works.

The client nods.

Then everyone goes back to Gmail, texts, spreadsheets, and whatever messy system they already trust.

That is why I start with the handoff.

Where does the lead come in?

Who has to approve the reply?

Where does the status get tracked?

What happens when the AI is unsure?

The useful version is usually boring:

A form comes in, the lead gets summarized, the draft reply is created, the row is logged, and a human approves before anything sends.

That is the whole point. Make the current workflow faster without pretending people will magically change how they work.

On-screen text:

- "Demo works. Handoff breaks."
- "Start with the existing workflow."
- "Draft-only until approved."

B-roll:

- Simple form to sheet to draft reply diagram.
- Inbox labels.
- Approval queue.

CTA:

Send me one repetitive handoff and I will tell you what should stay manual.

Fact checks needed:

- Use a fake demo inbox or sanitized form data only.
- Do not imply messages send automatically unless the client asks for that and approves it.

## Sample 3: The Creator Content Backlog Problem

Audience: creators, editors, agencies, personal-brand operators.

Goal: sell scene finding, hooks, scripts, and content queue organization.

Hook options:

- "Your best clips are probably buried in footage you never posted."
- "The editing problem starts before the timeline."
- "If your editor has to find the idea and edit the video, the queue is already slow."

Script:

A lot of creators do not have an editing problem first.

They have a selection problem.

There are calls, podcasts, clips, notes, voice memos, and half-finished ideas everywhere.

The editor opens the folder and has to guess what matters.

That is where the queue slows down.

The faster workflow is to separate the job:

First, find the moments.

Then label the hook.

Then write the angle.

Then edit.

For every clip, I want a simple note:

What is the tension?

What is the payoff?

What should the viewer feel in the first three seconds?

That turns a folder of raw material into a production queue.

On-screen text:

- "Footage is not a content plan"
- "Moment -> Hook -> Angle -> Edit"
- "Make the queue visible"

B-roll:

- Transcript with highlights.
- Clip map table.
- Short-form script cards.

CTA:

Send me one long video and I will return a scene map with the strongest short-form angles.

Fact checks needed:

- Confirm rights to use footage.
- Confirm whether AI transcript tools are allowed.

## Delivery Format

For a client, I would deliver:

- 3-10 script options in a Google Doc or Markdown file.
- Hook variants.
- B-roll and on-screen text notes.
- Source/research notes.
- Questions requiring client approval.
- Status tracker for draft, reviewed, approved, posted, or archived.