Devs have
content teams.
Security has
The Security
Solvers.
A podcast graphics package purpose-built to make Amplify's show look as sharp as their product. Playful, insightful, authentic — and unmistakably Amplify.
AGENT SWARM CONNECTED ●
>_ LOADING ASSETS............
>_ SECURITY SOLVERS INIT
STATUS: ACTIVE
────────────────────────────
PIPELINE: READY
CONTENT MACHINE: ONLINE
>_ _
A content machine.
Not just a podcast.
A long-form interview show hosted by Amplify founder Ali Mesdaq. Six guests. Twelve weeks. Two weeks per guest. Every episode is raw material processed into 16–25+ individual assets across YouTube, LinkedIn, Instagram, and Facebook over ten days.
Recording is step one of twelve. The podcast builds a business development opportunity and a community — without ever selling Amplify directly. The audience feels like they need Amplify before being told they do.
"If I had a creatine business, I'd want to be talking to athletes. The content itself is very interesting, separate from creatine." — Ali Mesdaq
Operations cockpit.
The visual language should feel like a direct extension of the Amplify product — dark, terminal-native, precise. Reference amplify.security directly for type, spacing, and overall feel.
>_ AGENT SWARM CONNECTED ●
STATUS: ACTIVE
The Amplify Vibe.
Three tones run through every episode. Graphics must carry all three. Not locked to one mood.
Playful & Authentic
Baseline energy. Real people, unfiltered. Best moments come when the guest forgets they're being recorded. Don't over-polish. TikToks, reels, BTS moments live here.
Guest Elevation
The guest is the star. Ali is the curious interviewer. Lower thirds, thumbnails, and cut-downs make guests look authoritative and brilliant. They reshare everything.
Insightful & Innovative
Substance layer. At least one non-obvious insight per episode. These moments get quote-graphicked, carouseled, bookmarked. Let the words breathe.
Six assets. Core package for launch.
Everything else builds on top of this system. Designed for repetition — used at volume every single week.
Branded Intro Animation
Dark terminal aesthetic. Establishes show title and Amplify brand. Sets tone before Ali speaks. Marlo inserts in post-production.
Branded Outro Animation
Mirrors intro energy. CTA moment — subscribe, follow, find Amplify. Clean, definitive exit that sticks.
Lower Third — Guest
Clean on dark footage. Cyan accent. Monospace label style. Works across all consistent remote guest frames.
Episode Title Card
Per-episode graphic. Guest name prominent, topic as headline. Base for YouTube thumbnail and LinkedIn header.
Quote / Clip Graphic
Pull quote on dark branded background. Easy to populate weekly from transcript. LinkedIn + Instagram carousels.
Thumbnail Template
Guest face + pull quote. High contrast. Guest looks like the expert they are. YouTube + LinkedIn primary.
Directional mockups.
Not final designs — directional only. Designer to interpret and elevate.
PHOTO
What this is.
What this isn't.
Hard guidelines for the designer. This should feel like a product, not a show.
- Dark navy backgrounds —
#0B0D1Ais the canvas - Cyan as primary accent — headlines, labels, UI elements throughout
- Monospace for all labels, system tags, and terminal-style text
- Magenta sparingly — CTAs and high-energy moments only
- Guest face and words carry the weight — design frames, never competes
- Reference amplify.security directly for type weight and feel
- Consistent templates built for repetition — used at volume every week
- Bright or white backgrounds — this show lives entirely in the dark
- Neon green — that's a completely different brand, full stop
- Gamer / RGB aesthetic — adjacent to that world but not that vibe
- Over-designed — clean, precise, functional. Audience are engineers
- Amplify logo as the hero — brand is ambient, never front-and-center
- Generic podcast templates — should feel like a product, not a show
- Anything that looks like it was made in Canva
Ready to build.
Graphics should inform, conform, and impress.
Client Sign-Off
Present this brief. Confirm brand direction, deliverable scope, and any client notes today.
Designer Concepts
2–3 concept directions for core package. Intro/outro, lower third, episode title card.
Tech Rehearsal
Graphics applied to episode footage. Test in Descript, confirm lower third placement and framing.
Full Package
Approved graphics extended to all 6 deliverable templates. Season 1 ready to ship.
The Security
Solvers.
Descript Workflow Guide
A step-by-step production system for recording, editing, and distributing The Security Solvers podcast. Designed to keep Ali at the mic — not in the edit bay.
Eight steps.
One simple rule.
Ali records and annotates. EyeClap edits and produces. Ali approves once. Everything else is handled.
Record in Descript
Ali records the episode in Descript Rooms. Both participants on camera with consistent framing. No editing required at record time — just hit record and have the conversation.
Share Access to RD
After each recording, Ali shares the Descript project with RD with "Can Edit" permissions. This must happen for every new episode — Descript doesn't carry access over automatically.
Ali Annotates the Raw Transcript
Ali goes through the Descript transcript and highlights sections to cut or flag. This is the only editing input required from Ali — no timeline work, no camera switching.
Ali knows the subject matter. He'll catch technical errors, terminology a guest got wrong, or moments the guest wouldn't want published — things EyeClap wouldn't necessarily flag on their own.
RD's Team Edits in Descript
RD's assistant editor makes all cuts Ali flagged directly in Descript. Removes ums, ahs, and dead air. Cleans up the rough cut based on the annotations.
Export to Adobe Premiere via XML
Once the Descript rough cut is clean, RD exports via XML directly into Adobe Premiere. The XML preserves all Descript edits but gives full production control in Premiere.
If Ali disagrees with a camera switch in the final cut, it's a quick fix — the XML workflow means EyeClap has full control to swap it without re-editing from scratch.
Clip Selection via Google Doc
RD's team downloads the edited long form, transcribes it, and selects 3–5 clip candidates. These are sent to Ali in a Google Doc with timestamps and context for each clip.
This Google Doc is the one moment Ali needs to weigh in on the clip selection. Everything before this is handled by EyeClap. Everything after is too.
Clip Production in Premiere
Approved clips get the full production treatment: captions, graphics overlays, animations where flagged, branding, and export in all required aspect ratios.
Upload to Shade → Distribution
All final deliverables — long form and clips — are uploaded to Shade. From there, distribution cadence, platforms, and scheduling are aligned in the weekly standing meeting.
LinkedIn platform is still evolving on aspect ratio performance. 16:9 and 9:16 will be A/B tested in the early episodes to determine what performs better for this audience.
Deliverables per
episode.
Every episode produces one long form and 3–5 short clips across multiple aspect ratios.
Long Form Episode
16:9 · 1080p+ · 10–20 min · YouTube primary. Chapters and timestamps. Full graphics package applied.
Short Clips — Horizontal
16:9 · 1080p+ · 30–90 sec · LinkedIn and YouTube Shorts. Captions mandatory. 3–5 per episode.
Short Clips — Vertical
9:16 · 1080p+ · 30–60 sec · Instagram Reels, LinkedIn vertical, TikTok. Captions mandatory.
Square Format
1:1 · 1080×1080 · Pending platform testing. Not prioritized in early episodes.
4:5 Format
4:5 · Pending platform testing. May be added if LinkedIn data supports it.
Animated Clips
When Ali flags a complex topic during annotation, motion graphics are added to support the explanation. Takes longer — flagged per clip.
Who owns
what.
Clear ownership at every step. Ali stays at the mic. EyeClap handles everything else.