====== ELF Demo Script ======

Target demo length:
  * 15–20 minutes
Goal:
  * Show ELF solves daily traffic workflow with minimal friction
Tone:
  * Practical station ops
  * Calm, not salesy

----

===== Pre-demo Setup (5 minutes before) =====

Checklist:
  - Use a sample station dataset (3 advertisers, 5 campaigns, 20 spots)
  - Have 1 “problem” scenario ready (conflict/spacing issue)
  - Have a "daily log export" button/path ready
  - Know their Rivendell version and current traffic workflow

Ask 3 questions (quick):
  1) How do you build logs today?
  2) Biggest pain point (conflicts, time, reporting, approvals)?
  3) Who touches traffic? (1 person? multiple?)

----

===== Agenda (say this out loud, 20 seconds) =====

“Here’s what I’ll show:
  1) Campaign creation
  2) Scheduling a day
  3) Catching a conflict
  4) Exporting a Rivendell-friendly log
  5) How support/hosting works if you want it”

----

===== 1) Dashboard / Overview (1 minute) =====

Show:
  - The main screen / navigation
Say:
  “ELF focuses on the core traffic flow: advertisers → campaigns → schedule → logs.”

Point out:
  - Where advertisers live
  - Where campaigns live
  - Where schedules/logs are generated

----

===== 2) Advertiser + Campaign (4 minutes) =====

Flow:
  - Open an advertiser
  - Create or open an active campaign

Narration:
  “This is built for small stations: quick entry, clear status, minimal steps.”

Show:
  - Flight dates
  - Spot count / rotations
  - Any separation or constraint options (if present)

Key line:
  “You can keep it simple or add rules when you need them.”

----

===== 3) Schedule a Day (4 minutes) =====

Flow:
  - Pick a date
  - Run schedule generation (or show schedule builder)
  - Show scheduled spots list

Narration:
  “ELF tries to make the daily log a repeatable operation, not an art project.”

Key line:
  “If you can generate tomorrow’s log in a couple minutes, you win.”

----

===== 4) The ‘Problem’ Moment (3 minutes) =====

Show:
  - A conflict case (duplicate advertiser too close, missing spot, overbook, etc.)
  - How ELF flags it and how you fix it

Narration:
  “This is where most systems either ignore reality or get complicated.
   ELF tries to give you guardrails without turning it into enterprise software.”

Key line:
  “You want the system to catch issues before airtime.”

----

===== 5) Export to Rivendell (3 minutes) =====

Flow:
  - Generate/export a log
  - Show format / file naming
  - Explain where it lands

Narration:
  “ELF’s output is meant to be automation-friendly. The goal is fewer manual steps.”

Key line:
  “If you’re already using Rivendell, this should fit your workflow.”

----

===== 6) Support / Hosting Options (2 minutes) =====

Be straightforward:
  - “ELF is open source.”
  - “Stations pay for setup, hosting, support, and customization.”

Explain 3 options:
  1) Self-host + support
  2) Hosted plan
  3) Managed station (priority + monitoring + backups)

Mention pilot:
  “I’m onboarding a small number of early stations. Discounted setup and direct support.”

----

===== 7) Close (2 minutes) =====

Ask:
  1) “Would you want to try this with your real data?”
  2) “If we did a pilot, what’s your timeline?”
  3) “Who else needs to see it?”

Offer next steps:
  - Pilot install
  - Migration plan (if needed)
  - Training session
  - Support plan choice

----

===== Follow-up Email (same day) =====

Include:
  - Summary of pain points they named
  - Proposed pilot plan (1–2 bullets)
  - Pricing link
  - Next meeting time