·
Marketing Plan — Internal
COMPUTEX Week  ·  June 1–5, 2026
Today 6pm
This Week
Month View
Reddit
Assets !
Post goes out today

Pre-Show Launch Announcement

Sunday June 1 · Target time: 6pm · COMPUTEX opens tomorrow

Who postsBen (primary)
PlatformLinkedIn + Twitter
GoalAnnounce Halo, open waitlist
Asset neededWaitlist URL (live today)
Link placementFirst comment, not caption
Asset note If Dennis has any setup/pre-show photo from the Qualcomm booth — use it here. Even a phone photo of the demo station being set up is better than no visual. If nothing, text-only post is fine.
Ben LinkedIn Pre-Show Announcement — Full Reveal 6pm today
Lead with the threat. Land Halo as the answer. End with the waitlist.
LinkedIn Draft
In 2024, a company wired $25 million after a deepfake CFO appeared on a Zoom call. Every person on that call was synthetic. There was nothing running on that device to catch it. We built Halo to change that. Halo is an on-device deepfake detector for Windows. It runs silently in the background during live video calls, analyzes the stream in real-time using a Qualcomm Snapdragon NPU, and alerts you with a confidence score — before you act. No cloud. No video data leaves your device. We're showing it live tomorrow at COMPUTEX 2026 inside the Qualcomm booth. The waitlist is open today. Priority beta access for early signups. Link in comments.
Neo's reshare note (post 30–60 min after Ben's goes up):
"Proud of what we've built. If you're at COMPUTEX this week, come find us at the Qualcomm booth."

COMPUTEX Week — June 1–5

3 posts/day — one per founder. Dennis morning, Ben midday, Neo afternoon. Dennis captures all assets at the booth.

Narrative arc: Act I — The Attack (Jun 2–3) Act II — The Launch (Jun 4) Act III — Proof (Jun 5)
AccountsDennis · Ben · Neo · Company Page
Volume3 posts/day — one per founder
Link ruleAlways in first comment, not caption
Cross-commentAll 3 comment within 30 min of each other's posts
Sun June 1 Pre-Show · 6pm
See the Today tab for the full draft and notes.
Mon June 2 Act I — The Attack
Dennis LinkedIn From the Floor
Tease only — no product mention. Problem frame. Goal: 3-5 comments asking "what is it?"
Assets for this post
VIDEO 15-30 sec. Dennis walking the COMPUTEX floor — booth crowds, Qualcomm signage visible. No product reveal. Portrait mode. Voice optional.
Framing: Journalist-at-a-scene energy. Raw, not polished. Film before the floor gets busy (before 9am). The caption is the story, the video is proof you're actually there.
LinkedIn Draft
We're in the Qualcomm booth at COMPUTEX this week. First hour on the floor: live demo. Someone faked their face on a video call — right in front of 50 engineers. The room went quiet. Nobody flagged it. Nobody had a tool that could. Something changes Wednesday. #COMPUTEX2026 #Halo
Company page: Repost Dennis's post at +2 hours. No added caption.
Image Prompt — DALL-E 3 / Midjourney

Editorial photo. Tech conference floor shot from behind someone's shoulder. Blurred crowd, tall LED display screens, exhibition booth structures. COMPUTEX-style hall. Natural indoor lighting, slight motion blur. Candid, no posed subjects. Realistic photography, no text overlays.

Ben LinkedIn Research Credibility
No product mention. Teaching post. Establish authority before the launch. Goal: researchers and security folks reshare.
Assets for this post
PHOTO Ben at a whiteboard, lab, or conference room. Or a simple graphic: one bar at 50% labeled "Human judges detecting deepfakes." White background, minimal.
Framing: Academic-adjacent. Clean and credible. Write this before COMPUTEX — it can be polished from SF. The point is to make the audience ready to believe the product claims on Wednesday.
LinkedIn Draft
The best trained humans detect deepfake video with roughly 50% accuracy. A coin flip. Multiple published studies. Different labs. Same result. You can't tell anymore. Neither can a trained expert. Nobody's tools have caught up yet. More Wednesday. #AIResearch #deepfake #MachineLearning
Image Prompt — DALL-E 3 / Midjourney

Clean minimal graphic on white background. A single vertical bar chart with one bar at exactly 50% height. Label below the bar: "Human detection accuracy — deepfake video." Y-axis 0–100%. Flat design, slightly unsettling. No people, no decorative elements. Digital illustration, simple and stark.

Neo LinkedIn Market Frame
Dollars and stakes. No product mention. Goal: make the problem feel expensive before the solution is named.
Assets for this post
PHOTO Neo in the COMPUTEX halls or a conference room. Business casual, candid. Or a screencap of a relevant headline about deepfake BEC fraud (screenshot, not a live link).
Framing: Don't pose. Walk and have someone shoot. Shows you're at the conference and making the rounds. Background foot traffic = scale signal.
LinkedIn Draft
$2.9 billion. FBI estimate for business email compromise losses in 2023. Before you could swap someone's face on a video call in real time, for free. We're in the Qualcomm booth at COMPUTEX this week. Every enterprise security conversation leads to the same question: "What do you do when you can't verify the person on your screen is actually them?" Nobody has a deployed answer yet. We will on Wednesday. #COMPUTEX2026 #enterprisesecurity
Image Prompt — DALL-E 3 / Midjourney

Candid editorial photography. A man in business casual (dark shirt, no tie) walking through a large modern convention center. Wide shot, crowds of people in background, large illuminated exhibition signs visible. Indoor lighting. Not posed. Realistic, no text overlays.

Tue June 3 Act I — Escalation
Dennis LinkedIn From the Floor
First-person field experiment. Raw and unpolished intentionally. No Halo name yet — "tomorrow" is the only CTA.
Assets for this post
SELFIE VIDEO Dennis talking to camera, 20-30 sec. Show floor in background. Casual. "Day 2, still here, quick experiment..." No script — just tell the story.
Framing: Snapchat-story energy, not a press release. Don't reshoot for perfection. One take that feels real beats three takes that feel rehearsed. Noisy background is fine — it signals authenticity.
LinkedIn Draft
We've been running a live demo from the Qualcomm booth. 12 engineers. 11 said they could spot a fake face on a live call. I showed them the same 30-second clip. 11 were wrong. One: "OK, I need to know what you're building." Tomorrow we tell everyone. #COMPUTEX2026 #Halo
Company page: Repost this one. First time #Halo appears publicly.
Image Prompt — DALL-E 3 / Midjourney

Candid selfie-style portrait. A man in his late 20s talking directly to camera. Behind him: a busy tech conference floor, blurred exhibition booths, people in motion. Natural conference lighting. Authentic expression, slightly conspiratorial. Smartphone portrait mode aesthetic. Realistic, not staged.

Ben LinkedIn Technical Depth
WHY adaptive detection matters — sets up the key differentiator before launch day. No product name yet.
Assets for this post
GRAPHIC Simple timeline: "New generator ships every 6-8 weeks — static detector goes obsolete." White background, minimal. Can be made in Canva in 10 minutes.
PHOTO Fallback: Ben at a laptop or whiteboard. Technical vibe. COMPUTEX badge visible is a bonus.
Framing: Educational, not promotional. The goal is to make "2-week retraining" land as a technical requirement, not a marketing claim. Write this before COMPUTEX — it can be polished from SF or Taipei.
LinkedIn Draft
Why static deepfake detectors go obsolete. Most models are trained on the same generation method they're detecting. When a new method ships — and one ships every 6-8 weeks — accuracy collapses. A detector that doesn't update is irrelevant within a quarter. Ours retrains against every new method within 2 weeks of public release. That's not a feature. It's the only viable architecture. More tomorrow. #AIResearch #deepfake #MachineLearning
Image Prompt — DALL-E 3 / Midjourney

Photography of a whiteboard or glass wall with a hand-drawn diagram. Two boxes connected by an arrow: left box labeled "New method released," right box labeled "Retrained — 14 days." A hand holding a marker partially visible. Office or lab background, blurred. Shallow depth of field. Realistic photography.

Neo LinkedIn Market Frame
Setup post for the launch. Names the gap. "Tomorrow we close it" is the only CTA needed. Under 150 words.
Assets for this post
PHOTO Neo walking the COMPUTEX floor or a wide shot of the hall. Candid, not posed. Background foot traffic signals scale and presence.
Framing: Short and confident. This is the market close before the product reveal. Don't explain too much — the mystery of "tomorrow" is intentional. Keep it tight.
LinkedIn Draft
Two days in the Qualcomm booth at COMPUTEX. Finance teams, HR leaders, legal, healthcare — all asking the same thing. "How do we verify in real time that the person on our screen is actually them?" No enterprise tool answers this today. The gap between what AI can do and what security teams can catch has never been wider. Tomorrow we close it. #COMPUTEX2026 #enterprisesecurity
Image Prompt — DALL-E 3 / Midjourney

Wide-angle editorial photograph inside a large technology conference hall. Packed exhibition floor, rows of vendor booths, large LED displays, dense crowd of attendees. Slightly elevated angle looking across the floor. Bright indoor conference lighting. No identifiable faces in foreground. Realistic, no text overlays.

Wed June 4 Act II — Launch Day
Dennis LinkedIn Launch Reveal
PRIMARY launch post. Halo is named publicly for the first time. Every other post this week built toward this one.
Assets for this post
VIDEO HERO ASSET. 30-60 sec landscape. Split screen: left = someone deepfaking themselves on a video call. Right = Halo UI catching it in real time (alert firing, confidence score visible). Multiple takes — pick cleanest. Halo alert must fire within first 10 seconds.
Framing: Capture the demo footage on Day 2 or 3 — do NOT wait until launch day. The left side (deepfake demo) is raw footage; the right side (Halo UI) can be screencaptured and edited in. No narration needed — the visual tells the story.
LinkedIn Draft
Three years. Today we showed it. It catches fake faces on live video calls, running entirely on your device. No cloud. No latency. No data ever leaves your machine. 40+ demos today at the Qualcomm booth at COMPUTEX. The reaction, on repeat: "How is this not already on every enterprise laptop?" Waitlist is open. Link in first comment. #COMPUTEX2026 #Halo #Qualcomm
Company page: Repost immediately after Dennis posts. This is the primary launch announcement.
Image Prompt — DALL-E 3 / Midjourney

A laptop screen on an exhibition booth table. Split-screen interface visible: left half shows a video call with a slightly-too-perfect face; right half shows a dark UI with a circular confidence meter at 94% and a red alert reading "DEEPFAKE DETECTED." Conference environment in background, soft booth lighting. Realistic product mockup photography.

Ben LinkedIn Technical Launch
Credibility post for CTOs and security engineers. Numbers, architecture, methodology. No buzzwords — cite specifics only.
Assets for this post
PHOTO Ben at the Qualcomm booth next to a laptop showing Halo's UI. Or a technical slide: NPU inference pipeline, no API call shown. Should feel credible, not marketing-y.
Framing: Post 1-2 hours after Dennis's to stagger feed impact. Ben's job today is to make the product believable. Cite specifics: sub-30ms, 11 methods, 97%, 2-week cycle. No superlatives without numbers.
LinkedIn Draft
Why on-device deepfake detection is the only enterprise-viable architecture. Speed. Cloud round-trips: 200-800ms. NPU inference: under 30ms. Real-time means local. Privacy. Sending video frames to an external API creates compliance exposure. On-device means zero data egress. Accuracy. 97% across 11 different methods to fake video. Model retrains within 2 weeks of any new method going public. Halo is in early access now. Link in first comment. #AI #MachineLearning #deepfake #Qualcomm
Image Prompt — DALL-E 3 / Midjourney

Clean dark-mode technical infographic. Three stacked rows of stats in monospace font: "Speed: under 30ms NPU inference," "Privacy: Zero data egress," "Accuracy: 97% / 11 methods." Minimal design, dark background, light text. Small chip icon in corner. No people. Digital design mockup.

Neo LinkedIn Founder Story
Mission + practical details. Lead with why we built it. Land on price, compliance, CTA. This is the investor-and-partner signal post.
Assets for this post
PHOTO Neo at the Qualcomm booth — Qualcomm branding visible in background. Professional but real. Or Neo + Dennis together: the "we built this" shot.
Framing: Founder energy, not press release energy. Slightly emotional — this is years of work going public. Don't be stiff. Post 2-3 hours after Dennis's to maximize feed spread across the day.
LinkedIn Draft
We built Halo to run on Qualcomm's Snapdragon chip. They invited us to demo it in their COMPUTEX booth. Today we launched. Fake faces are already showing up on enterprise video calls. Nothing in your current toolkit was designed to catch them. Halo is the first on-device, real-time answer. No cloud. No workflow change. No data leaves your machine. $30/month. SOC 2 certified. On-prem available. Built with Qualcomm. Launching now. Waitlist is open. Link in first comment. #COMPUTEX2026 #Halo #scamai
Image Prompt — DALL-E 3 / Midjourney

Editorial photograph. Two men in their late 20s standing at a technology exhibition booth. Behind them: a branded banner and a laptop on a display stand showing a software UI. They face the camera, confident but not stiff. Conference environment, natural lighting. Professional but candid. Realistic, no text overlays.

Thu June 5 Act III — Proof
Dennis LinkedIn Social Proof
Make the reader feel like they missed something important. CISO quote is the headline. Short — let the quote do the work.
Assets for this post
VIDEO A genuine reaction moment at the booth. If you captured someone watching the demo — use it (get verbal consent on camera first: "Mind if I share this clip?"). 15-30 sec.
PHOTO Fallback: Dennis at the booth on the last day, slightly tired and real. Or a wide shot of the booth area with foot traffic. Authentic beats polished on the closing day.
Framing: If you have a real reaction clip, it replaces the text post — just write 2-3 lines of caption. If not, the CISO quote format works. Either way: make the reader feel like they missed something.
LinkedIn Draft
Last day at COMPUTEX. Day 4 in the Qualcomm booth. A CISO came through. Watched the demo. Didn't say anything for 10 seconds. Then: "How is this not standard issue on every enterprise laptop right now?" 100+ demos this week. That reaction, almost word for word, every single time. If you missed us at the show — waitlist is open. Link in first comment. #COMPUTEX2026 #Halo
Company page: Repost. Last chance for people who saw the launch posts but haven't signed up yet.
Image Prompt — DALL-E 3 / Midjourney

Candid editorial photograph. A person in business attire, seen from profile or three-quarter angle, leaning slightly forward, watching a laptop screen with an expression of genuine surprise. Exhibition booth environment, soft ambient lighting. Other attendees blurred in background. Realistic, not staged.

Ben LinkedIn Technical Proof
Transparency post. Address the hard questions — false positive rate, non-Qualcomm hardware. Honesty builds more trust than polish. Skeptic-converter.
Assets for this post
PHOTO Screenshot of Halo's detection confidence score UI. Or Ben at the booth wrapping up — technical but relaxed. Or a benchmark summary graphic (accuracy / FPR).
Framing: Answer the questions a skeptical CTO would ask. Don't hide the false positive rate — stating it as a work-in-progress with a target is more credible than claiming perfection.
LinkedIn Draft
Four days. 100+ live demos. Most common first reaction: "I didn't know this existed." Most common follow-up: "We need this." For the technically skeptical: Trained on public and proprietary data. Tested against every major method within 2 weeks of release. 97% accuracy on internal benchmarks. Most common technical question: "What's your false positive rate?" Current: under 3%. Full benchmark published when we hit our target. Early access is open. Link in first comment. #AI #deepfake #MachineLearning #COMPUTEX2026
Image Prompt — DALL-E 3 / Midjourney

A laptop screen showing a clean dark-mode analytics dashboard. Two key metrics prominent: "Detection Accuracy: 97%" and "False Positive Rate: under 3%." Small confidence meter UI in corner. Booth table surface below, shallow depth of field. Realistic product screenshot aesthetic, no people.

Neo LinkedIn Strategic Close
Summarize the arc. Redirect to waitlist one last time. Also an investor/partner signal: "we're a real company with real traction."
Assets for this post
PHOTO Neo and Dennis at the end of the show — the "we did it" shot. COMPUTEX signage visible if possible. Slightly candid and imperfect is fine. This is the closing frame, not the hero shot.
Framing: Look forward, not backward. Don't linger on this week — point to what's next. Post in the afternoon after Dennis and Ben to close out the day's feed.
LinkedIn Draft
COMPUTEX is over. The conversation isn't. We spent the week in the Qualcomm booth. Hundreds of conversations. Finance, HR, healthcare, legal — all asking the same question: "How do you verify in real time that the person on your screen is who they say they are?" Halo is the answer. On-device. Real-time. No cloud. Built with Qualcomm. We launched the waitlist this week. The response was bigger than expected. If you're in security, compliance, HR, or legal and you run video calls — this is for you. Link in first comment. #COMPUTEX2026 #Halo #scamai
Image Prompt — DALL-E 3 / Midjourney

Candid editorial photograph. Two men in casual-professional clothing near a large exhibition venue or entrance. End-of-day atmosphere, slightly tired but satisfied expressions. Large conference signage or building exterior visible behind them. Natural light, authentic, not posed. Realistic photography.

Month View — June & July

Post-COMPUTEX rhythm: 3 posts per week across all accounts. Consistent over clever.

Cadence post-show3x/week total, not per person
Ben's laneThreat landscape · Expert POV
Dennis's laneProduct · Demos · Behind the scenes
Neo's laneMarket · Partnerships · Strategy
Company pageReposts only. Never original content.

Week 2 — Post-COMPUTEX   Jun 8–12   Theme: What the market told us

Mon Jun 8 COMPUTEX Recap — What people actually said
Owner: Ben or Dennis  ·  Not a highlight reel — one honest observation
We showed Halo to hundreds of people at COMPUTEX this week. The most common reaction wasn't "impressive technology." It was: "why doesn't this already exist?" That tells you something about where enterprise security is right now on live video calls. [1–2 sentences on a specific conversation or moment from the booth] Waitlist is open. Link in comments.
Wed Jun 10 Most Common Booth Question — Builds trust by engaging real complexity
Owner: Dennis  ·  Pick whichever question came up most (e.g. "does it work on Zoom?")
The most common question we got at COMPUTEX: [question] Here's the honest answer: [answer in 2–3 sentences] [One sentence connecting back to why Halo is built this way] If you have other questions about how it works, drop them in the comments.
Fri Jun 12 Waitlist Milestone — Only post if the number is worth sharing (100+, 250+)
Owner: Neo  ·  Lead with the insight, not the number
[X] people joined the Halo waitlist this week. The breakdown surprised us: [Y]% were in crypto and Web3, [Z]% were in HR and recruiting. The threat is landing in exactly the places we expected. Waitlist still open. Priority beta access for early signups. Link in comments.

Week 3   Jun 15–19   Theme: Making the threat specific and personal

Ben
Anatomy of a deepfake attack
Walk through the $25M Arup attack step by step — who they researched, how they cloned the CFO, what signals a human missed. End: "Halo catches it at the video stream level." Ben's highest-leverage content type.
Neo
Crypto / Web3 specific incident
Find a recent deepfake incident in crypto. Use it as the hook. Frame as a pattern, not a one-off. End with Halo as the answer for that vertical specifically.
Dennis
Engagement / Poll post
"Does your company have a policy for verifying who's on a video call before wiring money or sharing confidential info? Yes or No." Comments are your lead list. Reply to every one.

Week 4   Jun 22–26   Theme: Social proof and momentum

Neo
Waitlist progress + demographics
By now you should have a meaningful number and demographic insight. Lead with the insight ("who is actually signing up and why"), not just the count. Makes waitlist progress feel like market validation.
Ben
Why Qualcomm NPU specifically
Technical post on why real-time inference for deepfake detection during a live call requires a dedicated NPU — and why on-device is the only architecture that works at sub-100ms latency. For the security engineer audience.
Ben or Neo
Why we built this — founder story
One personal, honest post. The moment the team realized this product needed to exist. Not corporate, not polished. The posts that get shared by people who weren't already following you are always the human ones.

July — Pre-Beta   Theme: The waitlist is becoming a community

Ben (weekly)
Incident reporting
Every major deepfake news story is a post. "This happened. Here's what the attack looked like technically. Here's what Halo would have caught." Keeps Halo relevant without forcing it.
Neo
Beta cohort preview
"We're selecting the first 50 Halo beta users this month. Here's what we're looking for — and how to move up the list." Creates urgency. Activates the waitlist.
Dennis
Product reality posts
Honest glimpses of what the team is actually working on. "Biggest technical challenge we hit this week: [X]. Here's how we're solving it." Builds trust through transparency, not polish.
Ben (once)
LinkedIn long-form article
"Why Real-Time Deepfake Detection Is the Next Mandatory Layer in Enterprise Security." Published as a LinkedIn article, not a post. Anchors SEO, gets shared in security newsletters, extends Ben's expert witness credibility.

Reddit requires a completely different strategy

LinkedIn and Twitter are day-in-the-life and COMPUTEX content. That won't work on Reddit. The audience is technical, skeptical of promotion, and will downvote anything that reads as a product pitch. The angle here is purely educational — you're a credible source on deepfake threats, not a company promoting a product. Halo is mentioned only when directly relevant or when someone asks.

Hard Rules
No promotional copy Never open a Reddit post with anything resembling a product announcement. You're sharing knowledge, not marketing.
Link in comments only Do not put the waitlist link in the post body. If the discussion goes well and someone asks where to learn more or try it, drop the link in a reply at that point.
Engage before you post Before posting in any new subreddit, spend a few days commenting on existing threads genuinely. A 0-karma account that appears to only post about Halo will get flagged immediately.
Target Subreddits
r/cybersecurity
Security professionals, practitioners
Technical angle. "We built an on-device deepfake detector for live video calls using a Snapdragon NPU. Happy to talk architecture — what questions do you have?" Ask something specific to drive comments.
r/netsec
Network / infosec engineers
More technical than r/cybersecurity. Focus on on-device inference, latency constraints, and why cloud-based detection fails for real-time use. No product pitch at all — pure architecture discussion.
r/CryptoCurrency
Crypto community, retail + semi-professional
Lead with the executive impersonation threat and real incidents. "Deepfake attacks targeting crypto executives on video calls are scaling. Here's how they actually work." Factual, educational, not promotional.
r/recruiting
HR professionals, recruiters
Lead with the Gartner stat and hiring fraud data. "We're watching deepfake candidate fraud scale in real-time. Here's what the attack pattern looks like." Frame as a practitioner sharing what they're seeing.
r/privacy
Privacy-conscious users and professionals
On-device processing angle. "Why does on-device AI matter for deepfake detection — and why cloud-based tools create a different problem than they solve." Privacy community responds well to this architecture argument.
Content Ideas for Reddit
Educational Post
"How the $25M deepfake video call attack actually worked — a technical breakdown"
Walk through every step. Who they researched, how they built the fake, what the victim saw, why it worked. This is genuinely interesting to security communities and gets shared. Post in r/cybersecurity or r/netsec.
Discussion Starter
"What does your company actually do to verify who's on a video call before approving a wire transfer?"
Genuine question, invites honest answers. Surfaces the gap in most organizations' processes. Comments are your market research. Post in r/cybersecurity or r/sysadmin.
Architecture Discussion
"Why on-device inference is the only viable architecture for real-time deepfake detection during live calls"
Technical, specific, genuinely useful for people building in this space. No product pitch. Post in r/netsec or r/MachineLearning.
Hiring Fraud Data
"Deepfake hiring fraud jumped 1,300% last year. Here's what the actual attack looks like in an interview"
Walk through what a recruiter experiences. What signals exist. What doesn't work as a defense. Post in r/recruiting. Do not mention Halo in the body.
When to activate Reddit Do not post to Reddit this week. COMPUTEX content will read as promotional — Reddit communities will clock it immediately. Activate Reddit in Week 3 (June 15+) once the launch noise settles and you can post purely educational content without it looking like a launch push. Build karma in each subreddit by commenting genuinely for 1–2 weeks before posting original content.
Dennis is the primary shooter at COMPUTEX. This page lists every content asset needed across the full marketing plan — what it is, who captures it, when it's needed, and exact specs. Check off each asset as it's captured. Priority 1 assets are needed before end of COMPUTEX (June 5). Everything else can be produced after the show.
Assets captured
0 / 13
Not yet captured
Captured, needs edit
Ready to post
checkbox Check when done
Booth & Live Demo Assets Captured at COMPUTEX · June 2–5 · Dennis responsible
Pri Asset Who Specs Used in Status
P1 Hero Demo Clip
Person deepfaking themselves on camera → cut to Halo interface on second device → alert fires → confidence score appears on screen. The single most important asset of the launch. Capture multiple takes from different angles.
 Dennis
30–60 seconds
Landscape, high res
Both screens visible in frame
Capture 3+ takes
Jun 3 post Landing page All future product posts
Not captured
P1 Qualcomm Booth Context Photo
Photo establishing you're inside the Qualcomm booth. Qualcomm branding clearly visible in frame. Demo station in shot. Capture on Day 1 arrival before it gets crowded.
 Dennis
Photo (landscape)
High resolution
Good lighting — morning is better
Jun 2 post Press / PR
Not captured
P1 Demo Setup Wide Shot
Both devices visible side by side — the deepfake source device and the Windows device running Halo. Clean frame showing the full setup. Used as a static image when the video isn't appropriate.
 Dennis
Photo (landscape)
Both screens readable
Neutral background
Landing page hero LinkedIn thumbnails
Not captured
P2 Booth Reaction Moments
Genuine reactions from people watching the demo — surprise, concern, leaning in. Do not stage this. 10–30 seconds each. Even one good reaction clip is enough. Get permission if faces are visible.
 Dennis
Short clips (10–30s each)
Candid preferred
Verbal OK from subject if face visible
Jun 5 post Week 2 recap
Not captured
P2 Founder Talking-Head Clip
Ben or Dennis on camera, 60 seconds max. "We're at COMPUTEX 2026 showing Halo for the first time. Here's what it does and why we built it." Conversational, no script, one take. Booth or nearby background fine.
 Dennis
60 seconds max
Portrait or landscape
No script — one natural take
Week 2 recap post Ongoing founder content
Not captured
P2 Halo Alert Screenshot (close-up)
Clean close-up screenshot of the Halo interface at the exact moment the alert fires — alert notification + confidence score clearly readable. Useful as a standalone image when video isn't available.
 Dennis
Screenshot (high DPI)
Alert + score both in frame
Capture during demo runs
Landing page LinkedIn post graphics Twitter image posts
Not captured
P3 B-roll — Booth Environment
General b-roll of the booth setup, COMPUTEX hall, hardware on table, device screens. Useful as cutaway footage for edited videos later. No specific shot needed — just capture variety.
 Dennis
Short clips (5–15s each)
Mix of wide + close
Any time during the show
Week 2+ video edits July product posts
Not captured
P3 Halo Passive State Screenshot
Screenshot of Halo sitting quietly in the background during a normal-looking call — before any alert fires. Shows the "you don't even know it's there" UX. Useful for explaining how it works without triggering alarm.
 Dennis
Screenshot (high DPI)
Taskbar / background state visible
"How it works" section Landing page
Not captured
Landing Page Assets Needed today or tomorrow · Team responsible
Pri Asset Who Specs Used in Status
P1 Waitlist Page URL
The live waitlist URL must be confirmed and tested before 6pm today. All LinkedIn posts and QR code point to this. Ensure UTM parameters work on each link variant.
 Team
Live URL confirmed
UTM params tested
Email signup functional
6pm post today QR code at booth All week 1 posts
Not confirmed
P1 QR Code — Booth
A printed QR code linking to the waitlist page with the COMPUTEX UTM tag (?utm_source=computex_booth). Place it at the demo station. Anyone who watches the demo and wants to sign up scans it directly. Print at least 3 copies.
 Neo
Printed, A5 or A4 size
UTM tag: computex_booth
Test scan before printing
COMPUTEX booth Jun 2–5
Not created
P2 Halo Logo / Brand Mark
Clean Halo logo on transparent background and on dark background. Used on the landing page, any press kit, and as a watermark on future content. PNG and SVG formats.
 Team
PNG (transparent bg)
SVG preferred
Dark + light variants
Landing page All marketing materials
Not confirmed
Post-COMPUTEX & Ongoing Assets Needed June 8+ · Can be produced after the show
Pri Asset Who Specs Used in Status
P2 Edited Demo Video (clean cut)
A polished 30–45 second edit of the hero demo clip. Trim dead air, add simple captions labeling "Deepfake source" and "Halo detecting". No music needed. Subtitles optional but helpful for silent LinkedIn autoplay.
 Dennis
30–45 seconds
MP4, landscape
Subtitles / labels on screen
Needed by Jun 10
Week 2 content Landing page hero video Twitter drops
Not yet
P2 Founder Headshots
Clean headshots of Ben, Dennis, and Neo for use in thought leadership posts, press inquiries, and the landing page About section. Existing LinkedIn photos are fine if high-res. No new shoot needed unless the existing ones are low quality.
 Team
High-res JPEG/PNG
Each founder
Existing LinkedIn photos OK
LinkedIn long-form article Press / PR kit
Not confirmed
P3 Screen Recording — Halo Live During a Real Call
A screen recording of Halo running passively during an actual (internal) video call — showing it in its natural habitat, not a staged demo environment. Useful for posts that explain how it integrates into daily work without friction.
 Dennis
60–90 seconds
Screen record (OBS or built-in)
Capture after show — no rush
Week 3–4 product posts July beta content
Not yet
P3 COMPUTEX Wrap Reel
A 60–90 second montage of the best footage from the booth — demo moments, booth context, reactions, talking head. Used for the Week 2 recap post and as a lasting summary asset. Edit after the show ends.
 Dennis
60–90 seconds
Landscape MP4
Needed by Jun 8
Week 2 recap post Archive
Not yet