# StatusOwl — Ad Creative Package

**4 video ad scripts (with 9:16 + 16:9 storyboards) + 3 static concepts.**
Brand voice: watchful, wise, dry-witted, operator-to-operator. No hype, no fake metrics.

> Honesty constraints applied throughout: no invented customer counts, MRR, "trusted by X teams," or testimonials. Where a number would normally go, a bracketed placeholder is used. Any UI shown should be a real screen recording, not a faked dashboard.

**Through-line for all creative:** the gap between *"All systems operational"* and *reality.* That gap is the product.

**Recurring visual device:** the **Confidence Score dial** sliding from 100 → 64 while the vendor's status badge still glows green. The owl's eye = the dial.

---

## VIDEO 1 — "All Systems Operational" (the hero ad)

**Length:** 20s · **Format:** primary brand ad · **Hook type:** ironic juxtaposition
**Goal:** land the wedge in one line. Cold-traffic top-of-funnel.

**Hook (first 2s):** A pristine green status badge: *"✅ All systems operational."* Beat. Then, small, under it: *"— your vendor, 6 minutes ago."*

### Script / VO
- (0–3s) "Your vendor says everything's fine."
- (3–7s) "Your customers are already in your inbox."
- (7–12s) "StatusOwl watches three signals at once — official status, our own checks, and what people are actually saying."
- (12–16s) "One Confidence Score. You find out first."
- (16–20s) "StatusOwl. The status page that's actually watching." [logo + statusowl.io]

### On-screen captions (burned-in, for sound-off)
`All systems operational ✅` → `…says the vendor.` → `Meanwhile: 47 'is it down?' posts` → `Confidence Score: 64 ↓` → `Know before they admit it.` → `StatusOwl.io`

### 9:16 storyboard (mobile / Reels / Shorts / TikTok)
| t | Shot | On-screen |
|---|---|---|
| 0–3s | Full-bleed green status badge, dark bg, subtle scanline | "All systems operational ✅" |
| 3–7s | Badge stays green; angry chat/notification cards slide up over it | "…meanwhile, your customers:" |
| 7–12s | Three vertical signal bars animate in (Official / Synthetic / Social), owl eye forms from them | "3 signals. 1 number." |
| 12–16s | The Confidence Score dial drops 100→64 in amber, vendor badge still green beside it | "Confidence: 64 ↓ (they still say 100)" |
| 16–20s | Owl mark resolves, wordmark, URL | "Know before they admit it · StatusOwl.io" |

### 16:9 storyboard (YouTube pre-roll / LinkedIn / site)
| t | Shot | Notes |
|---|---|---|
| 0–3s | Centered green badge, lots of negative space left; cursor hovers | Wide, calm, premium |
| 3–8s | Split screen: left = green vendor badge frozen; right = real social feed scrolling outage posts | Tension via contrast |
| 8–14s | Camera pushes into a real StatusOwl dashboard; the dial ticks down; sparkline dips before the badge flips | Use real screen capture |
| 14–20s | Pull back to owl mark on parchment, amber eye, wordmark, CTA | End card holds 2s |

**CTA:** "See your stack's Confidence Score free → statusowl.io"

---

## VIDEO 2 — "The 4-Minute Window" (problem/agitate, for SRE ICP)

**Length:** 30s · **Format:** consideration, retargeting · **Hook type:** specific pain
**Goal:** speak to the SRE who's been burned. Higher-intent.

**Hook (first 3s):** A clock. "There's a window between when a vendor breaks… and when they admit it." Clock ticks: 00:00 → 04:00.

### Script / VO (operator tone)
- (0–4s) "Every outage has a window — the gap between when it breaks and when the vendor says so."
- (4–10s) "In that window, your customers are filing tickets and you have no idea why."
- (10–18s) "StatusOwl closes the window. Our synthetic checks and social signals catch the dip while the official page is still green."
- (18–26s) "One Confidence Score across your whole dependency chain. Alerts the moment trust drops."
- (26–30s) "Stop finding out last. StatusOwl.io." [logo]

### On-screen captions
`The 4-minute window` → `Vendor: ✅  Reality: ❌` → `Synthetic + Social caught it at 00:42` → `Official page flipped at 04:10` → `You were already alerted.` → `StatusOwl`

### 9:16 storyboard
| t | Shot | On-screen |
|---|---|---|
| 0–4s | Big mono countdown clock on ink bg | "the window" |
| 4–10s | Ticket cards pile up, no explanation, user looks lost | "why are we getting paged?" |
| 10–18s | Timeline bar: synthetic dip @0:42 + social spike @1:10 light up amber; official flips red @4:10 | "we knew at 0:42." |
| 18–26s | Dependency graph (Stripe→Auth→API) one node pulses amber, alert toast fires | "alerted on trust drop" |
| 26–30s | Owl + CTA | "Stop finding out last · StatusOwl.io" |

### 16:9 storyboard
Same beats, but use a **horizontal incident timeline** as the spine across the full frame: synthetic, social, and official plotted as three lanes; the amber markers fire left of the red one. End card right-aligned with breathing room on the left (asymmetric, on-brand).

**CTA:** "Map your dependencies free → statusowl.io"

---

## VIDEO 3 — "Trust, Verified" (for the status-page buyer)

**Length:** 15s · **Format:** punchy, social-native · **Hook type:** reframe
**Goal:** sell the *public status page* job-to-be-done. For founders/teams who need a status page customers believe.

**Hook (first 2s):** "Anybody can put a green dot on a status page." (cut) "Yours should mean something."

### Script / VO
- (0–4s) "Anybody can paint a status page green."
- (4–9s) "StatusOwl pages are backed by independent checks — so 'operational' is a fact, not a vibe."
- (9–13s) "An honest status page your customers actually trust."
- (13–15s) "StatusOwl.io." [logo]

### On-screen captions
`green ≠ true` → `independently verified` → `an honest status page` → `StatusOwl`

### 9:16 storyboard
| t | Shot | On-screen |
|---|---|---|
| 0–4s | A too-perfect all-green status page, slightly suspicious sheen | "green ≠ true" |
| 4–9s | A verification check-mark stamps each row; little "verified by synthetic check" tags appear | "independently verified" |
| 9–13s | Clean branded public status page on a phone, calm and credible | "customers trust it" |
| 13–15s | Owl + URL | "StatusOwl.io" |

### 16:9 storyboard
Show the **public status page** filling the frame on a laptop, then a customer's POV checking it on mobile and visibly relaxing. Verified badges animate subtly. End card with owl mark, parchment bg.

**CTA:** "Launch a status page customers trust → statusowl.io"

---

## VIDEO 4 — "Meet the Owl" (founder/brand, organic + PH)

**Length:** 30–40s · **Format:** founder-to-camera or VO over screen capture · **Hook type:** origin/empathy
**Goal:** humanize for Product Hunt / community / About page. Highest trust, lowest polish needed.

**Hook (first 3s):** "I got paged at 3am for an outage that wasn't even ours."

### Script (founder VO, real screen capture behind)
- (0–6s) "I got paged at 3am for an outage that wasn't ours — a vendor was down, but their status page was still green."
- (6–14s) "By the time it went red, we'd already lost an hour and a pile of customer trust."
- (14–24s) "So we built StatusOwl. It watches official status, runs its own checks, and reads the room on Reddit and HN — and rolls it into one Confidence Score."
- (24–32s) "Now we find out first. And our own status page is something customers actually believe."
- (32–40s) "It's [free to start / Founding Owl pricing for early teams]. I'd love your feedback. — StatusOwl.io"

### On-screen captions
`3am. Paged. Not even our fault.` → `vendor said: all good ✅` → `so we built an owl that doesn't lie` → `3 signals → 1 score` → `try it · StatusOwl.io`

### 9:16 / 16:9 note
Keep it real and a little rough — this one earns trust by *not* being a slick ad. Founder face in a corner bubble (9:16) or split (16:9), real dashboard behind. No stock music swell; light, dry tone. This is the PH first-comment video.

**CTA:** "Be a Founding Owl → statusowl.io" (PH-exclusive code in description)

---

## STATIC AD CONCEPTS (3)

Design system per brand-kit.html: parchment/ink, amber accent, Fraunces display + grotesque, asymmetric, generous negative space. No centered-template look.

### Static 1 — "The Two Badges" (the wedge, one image)
- **Visual:** Two status badges, asymmetrically placed. Top-left, big: `✅ All systems operational` (vendor green, slightly faded). Bottom-right, sharp amber: `Confidence: 64 ↓ (StatusOwl)`. A thin connecting line/owl-eye between them.
- **Headline (Fraunces):** "One of these is telling the truth."
- **Subhead:** "StatusOwl fuses official status, synthetic checks, and social signal into one Confidence Score."
- **CTA chip:** "Know before they admit it →"
- **Use:** LinkedIn, Reddit, blog OG image.

### Static 2 — "The Dependency Chain"
- **Visual:** A horizontal dependency graph (Your App → Stripe → Auth0 → AWS region) on ink bg; one node glows amber, a hairline crack spreading. Owl eye watches from the corner.
- **Headline:** "Your uptime is only as honest as your weakest vendor."
- **Subhead:** "Score every dependency. Get alerted when trust drops — not when the ticket queue does."
- **CTA chip:** "Map your stack free →"
- **Use:** retargeting, X/LinkedIn, SRE communities.

### Static 3 — "The Owl Eye / Confidence Dial"
- **Visual:** Hero owl mark, the eye *is* the Confidence dial at 92 in amber; everything else minimal parchment. Big negative space. Most brand-forward of the three.
- **Headline:** "Watchful. Wise."
- **Subhead:** "The status page that's actually watching."
- **CTA chip:** "statusowl.io"
- **Use:** brand awareness, PH gallery, profile banners, end-card.

---

## Production notes
- **Music:** restrained, low synth pulse or none. The dry confidence is the tone — avoid hype-trailer music (reads as slop).
- **Type in motion:** Fraunces for the punchline, grotesque for captions, mono for any number/score (tabular figures). Animate numbers with tabular alignment so the dial doesn't jitter.
- **Color discipline:** 80% ink/parchment, 15% slate/teal, 5% amber. Amber appears only on the score/the moment of truth — that's what makes it pop.
- **Real UI only:** every dashboard frame = real screen capture from statusowl.io. Do not mock fake data that implies customers we don't have.
- **Render pipeline:** `~/Projects/meetday-video/make_video.py` renders an HTML template frame-by-frame via Playwright + ffmpeg on PHANTOM (9:16, 1080x1920, 30fps). A StatusOwl-specific `template.html` is needed to reuse it — see statusowl-launch/video/ if a sample was produced.