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

Checklist:

1. Use a sample station dataset (3 advertisers, 5 campaigns, 20 spots)
2. Have 1 “problem” scenario ready (conflict/spacing issue)
3. Have a “daily log export” button/path ready
4. 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?)

“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”

Show:

1. The main screen / navigation

Say:

“ELF focuses on the core traffic flow: advertisers → campaigns → schedule → logs.”

Point out:

1. Where advertisers live
2. Where campaigns live
3. Where schedules/logs are generated

Flow:

1. Open an advertiser
2. Create or open an active campaign

Narration:

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

Show:

1. Flight dates
2. Spot count / rotations
3. Any separation or constraint options (if present)

Key line:

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

Flow:

1. Pick a date
2. Run schedule generation (or show schedule builder)
3. 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.”

Show:

1. A conflict case (duplicate advertiser too close, missing spot, overbook, etc.)
2. 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.”

Flow:

1. Generate/export a log
2. Show format / file naming
3. 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.”

Be straightforward:

1. “ELF is open source.”
2. “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.”

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:

1. Pilot install
2. Migration plan (if needed)
3. Training session
4. Support plan choice

Include:

1. Summary of pain points they named
2. Proposed pilot plan (1–2 bullets)
3. Pricing link
4. Next meeting time