CEO scene videos
A researched CEO in. A 45–75 second video out. The laugh, if there is one, is recognition ("that's right"), not performance. The close is a no-oriented question. Delete is a valid outcome. This is not a sequence, a roast, or a product tour.
This page is a content tactic for P1 at 50–500 employee plants. It does not mint problems or proofs. It does not authorize a claim the communication instructions would forbid on a call. Doctrine (Voss, Storyworthy) stays internal. The buyer never hears the names.
Other content strategies (where this sits)
Use video when the job is to put one scene in front of one named owner. Everything else below is a different job. Do not stack them in one send.
| Strategy | Job | How (short) | When |
|---|---|---|---|
| CEO scene video (this page) | One human, one mismatch, one no-oriented ask | Research packet → 45–75s recording → one email → one follow-up or stop | Name, public artifact, dinner-test script |
| Teach-first | Trust without a pitch | Accounting AI course; association rooms; no product tour | We are in their professional room as teachers |
| Unnamed floor shorts | Same five-second moment, no personalization | 15–30s, no logo overlay, no named company | Paid/organic; never a stalker thumbnail |
| Written accusation-audit note | Same Voss spine, no camera | Two paragraphs, same beats as the video | Video would feel like theater to that owner |
| Physical mail | Mailroom still exists | One page + QR to their scene video. No brochure. | Family plants; use sparingly after the packet exists |
| Expo presence | Be in their room | Expo signal research | They are exhibiting or attending. They are selling, not shopping for ERP. |
| ERP conference prep | Coffee with people already comparing systems | Conference prep; ads in Conference-city Google Ads | Stratosphere-class rooms. Not a machine show. |
| Working session | Artifact on the table | Proof ladder after they said it is not a bad time | Never the first cold beat |
| Micro vertical | Language and list that match one Friday | Micro vertical | When a wide "manufacturing" sentence would also fit a job shop |
| Consultant partners | Trust we cannot buy | Consultant partnerships | Lean / CI advisors already in the plant |
| CFO advice | Learn from P2, not mine a Rolodex | CFO advice | After "that's right," or rarely with an artifact |
| CEOs and AI | Control conversation with P1s who asked | CEOs and AI | Public AI artifact. Not the whole ICP. |
| Peer voice email | Comparable human, approved scene | Peer voice content | We have consent and a slice. One send, not a sequence. |
Comedy is a tone of recognition, not a channel. If the scene is true, a slight smile is enough. If the scene is fake, no comedian can save it.
What we take from ClickHouse
ClickHouse's public GTM is not a documented "comedy videos to CEOs" program. Do not copy a myth. Their documented motion is developer-led: one job (speed), real artifacts (queries, latency, peer write-ups), community before an SDR machine, irreverence at feature bloat, not at the buyer. They skipped the generic enterprise playbook. We skip the generic "personalized video sequence" playbook the same way.
Copy the craft. Change the audience.
| ClickHouse (engineers) | Us (plant CEOs) |
|---|---|
| Extreme specificity. Real queries, real latency. No "data platform" sludge. | Extreme specificity. A screen, a cell, a press, a Friday. No "digital transformation." |
| Un-corporate voice. Peer, not brochure. | Dinner test. Peer at the shop, not a comedian on a stage. |
| Show the artifact. Let the room feel the gap. Do not explain the moral. | Same. Hunt "that's right." Stop. |
| Irreverence at generic vendors and sludge, not at the buyer. | Irreverence at the lying spreadsheet, never at the owner, the family, or QuickBooks-as-identity. |
| One job. Speed. Not a suite tour. | One job. Friday stops lying. Not a platform tour. |
| Community / peer proof before SDR theater. | One researched human before a 200-touch sequence. |
What we do not import: engineer memes, roasting culture, volume spray, "watch me be clever," logo-stamped thumbnails that feel like surveillance, Hacker-News cadence aimed at a family owner.
The ClickHouse lesson in one line: one true artifact, shown without a moral, in a voice that could survive dinner with that audience. Their audience was engineers. Ours is a family owner who still walks the floor. The artifact and the voice change. The refusal of sludge does not.
Communication rules on this video
Every outbound message still follows the six-step order in communication instructions. A cold video is too short to carry all six. Do not reorder. Truncate.
| Step | On the cold video | Why |
|---|---|---|
| 1. Reality | Yes. Identity + one scene + "I may be wrong." | Start at the mismatch. Invite "that's right." |
| 2. Problem hypothesis | Yes. Labeled inferred. One physical location. | Elephant. Scene, not thesis. But/therefore, not and-then. |
| 3. Impact hypothesis | Only as the 'therefore' inside the scene. No ROI slogan. | "Therefore somebody decides on a lie" is a scene of consequence. "$X leaking" is a brochure. |
| 4. Mechanism | No. | A capability list is an and-then tour. It waits for a live artifact. |
| 5. Proof | No. | Case studies and "we help manufacturers" are seller-hero. |
| 6. Choice | Yes. One no-oriented question. | The story does not close itself. Delete is valid. |
Voss tools, mapped to beats. The buyer hears a human, not a method.
| Beat (seconds) | Voss tool | Storyworthy | Say |
|---|---|---|---|
| 0–8 | Transparent identity + no-oriented time | Start at the mismatch, not the company intro | Name, company, "this is a short recording. If this is a bad time, delete it." |
| 8–20 | Accusation audit | Elephant | The ugly thing they already think about this video. Invite correction. Smile if it is on us. |
| 20–45 | Label the scene as hypothesis | Five-second moment; scene not thesis; but/therefore | One physical location. "It looks like… I may be wrong." |
| 45–60 | No-oriented / calibrated choice | They are the protagonist; we are the setting | One question. Easy no. No calendar trap. |
| 60–75 | Stop | Do not explain the moral | End. Silence is the pause they cannot take on a voicemail. |
Prohibited in the video, same as any message: superlatives, hypothesis as fact, feature lists, manufactured urgency, seller-as-hero, "I understand," "I'm hearing that," QuickBooks-sunset fear, "your people are the problem," "Got 15 minutes this week?" as the first close.
Selling with love (this motion)
| Dimension | On this page |
|---|---|
| Love impact | The video exists only if a recognizable better Friday is possible. |
| Love client | Skip counters. Skip grief. Skip in-flight implementations. Recommend a conversation only if the artifact could be their mismatch. |
| Love product | Do not smuggle a tour into a joke. |
| Love process | One send, one follow-up, then stop. Preserve the right to say no. |
| Love self | Five to ten researched videos a week. Desperation records twenty nameless "hey FirstName" takes. |
Hype = enthusiasm minus evidence. Productive energy = curiosity + competence + their Friday.
Comedy rules
Comedy that is allowed is accusation-audit warmth and recognition of a scene they already live. The laugh we want is the same sound as "that's right."
| Allowed | Forbidden |
|---|---|
| Punch at us ("this is going to look like a software video") | Punch at them, their town, their photo, their family name, their accent |
| Punch at sludge (tab named Final, Final2, UseThisOne) | Punch at Excel, QuickBooks, or "your people still use spreadsheets" as stupidity |
| Specificity as the joke | A bit that needs a tag explaining why it is funny |
| One smile after the scene | Laugh track, jump cut, stock robot b-roll |
| Dinner-test with a plant person in the room | A joke you would not tell in front of their plant manager |
| Hired performer reading our spine | Comedian "doing a bit" on their LinkedIn headshot |
Do not: deepfake them or us; overlay their logo as a trophy; joke about succession; joke about a vendor sunset; use "AI" as a punchline.
If the packet cannot support a true scene, do not add jokes to fill the hole. Write a two-line note or skip the account.
Step-by-step (how we do this)
Cap five to ten fully researched videos per week. Roles: researcher (packet), writer (beats — usually the person who will take the meeting), performer (same person, or a directed reader), plant-literate veto (someone who has stood next to a press), sender (our email, never a comedian's).
Step 1 — Identify the CEO
- Pull P1 in
50_100and100_500for processes we actually sell into. ZoomInfo (or equivalent) verifies name, title, email, phone. Identity only. See Sales stack. - Dedup against Salesforce. Remove anyone who asked not to be contacted, any in-flight implementation of someone else, any account in grief or disaster in the news. Love of client: skip.
- Family-owned (SG_001): keep, but raise the bar. The scene must be operational. Do not joke about the surname on the building.
- If the only "personalization" available is a first name, do not record. Put them on a later pass or a written note.
This is not a purchased-list spray. A send is not a qualified opportunity.
Step 2 — Build the research packet
One page, internal. If a beat is missing, you are not ready. Sources: company site, careers, expo see-us-at, ERP signal research artifacts, capital only if the sponsor is public. Firecrawl / Cloudflare Browser Run for the public page. No Facebook, no employee scraping, no guessing they run Global Shop.
ceo_name:
company:
domain:
process: # molding / extrusion / ...
artifact_url: # the one public thing
artifact_kind: # job_post | facility | iso | expo | site_scene
scene: # one sentence, physical location
hypothesis: # mismatch, labeled inferred
accusation_audit: # what they already believe about this video
no_oriented_ask:
do_not_say: []
scene example (fictional, for craft): "Friday, the job-cost workbook
with tabs named Final and Final2." Not: "inefficient processes."
hypothesis stays inferred. The video must say we may be wrong.
One artifact only. Two artifacts is two videos, which means we have not chosen the five-second moment.
Step 3 — Write six beats, then dinner-test
Write six lines. Read them out loud. If you would not say it across a table at dinner — if it sounds like a brochure, a keynote, a thesis, or a victory lap — rewrite.
Accusation-audit bank (pick one, make it true):
- "This is going to look like a software person who has never stood next to a press."
- "You did not ask for a video."
- "If this is a pitch in costume, you should delete it."
Scene bank (only with an artifact that supports it):
- Job post for order-entry / "advanced Excel" for planning → the planner's workbook, not "you hired the wrong people."
- New facility / UCC on a machine → the new cell and the old process meeting.
- ISO / customer portal language → the binder vs the scorecard.
- "See us at NPE" → they are selling; we do not pretend they are shopping for ERP.
No-oriented asks:
- "Would it be a bad idea to look, for twelve minutes, at where the schedule stops matching the floor?"
- "Is it ridiculous to send this to someone else if you are not the person who lives that Friday?"
- "Would you rather I did not follow up at all unless you reply?"
Never: "Got 15 minutes this week?" That is a forced yes.
Dinner test: one colleague who has been in a plant listens once. If they wince, cut. If they say "that's right" about the scene, keep. If they laugh at us, keep. If they laugh at the owner, reshoot the copy.
Step 4 — Record
| Do | Do not |
|---|---|
| Phone or webcam. Plant-noise optional, cafe-performance not. | Studio lights, stock b-roll of robots, laugh track |
| Face to camera. Say their name once. | Overlay their logo, headshot, or LinkedIn as a trophy |
| 45–75 seconds. One take is better than clever. | Two minutes of setup. "I know you are busy" as filler |
| Real human. Prefer the person who will take the meeting. | HeyGen / deepfake of us or of them. Undisclosed synthetic. |
| Comedian only as a directed reader of this spine | Comedian "doing a bit" on their town, photo, or family name |
Thumbnail: our face, plain.
If a hired performer records: they get the packet, the six beats, the prohibited list, and a veto from the plant-literate colleague. Ad-lib that shames the buyer kills the take. We send from our address. They are production, not the relationship.
Watch the take once. If we are the hero, reshoot.
Step 5 — Send
One channel first. Email unless we already have a live LinkedIn correspondence. The video is the message. Do not write the pitch under it.
Subject (label, not a tease):
- "This might be the wrong Friday"
- "Delete if this is a software pitch"
- Their company name + a generic sludge image ("Excel tab named Final2") only if that image is honestly generic, not stolen from their files
Body:
Maria —
If this is a bad time, delete it.
Would it be a bad idea to look at the Friday where the schedule and
the floor disagree — or would you rather I left you alone?
[video]
No "just bumping this." No fake deadline. No CC of the plant manager to manufacture pressure (reactance).
Log in Salesforce: account, contact, link, artifact URL, hypothesis
status inferred. Not "video sequence step 1 of 8."
Optional physical: the same two lines on one page, QR to the unlisted video, our name and number. No brochure in the envelope.
Step 6 — After they watch (or do not)
| What happens | We do |
|---|---|
| Delete / no reply | One follow-up, seven days, still no-oriented: "Would you rather I did not follow up again?" Then stop. |
| "You're right, we should talk" | Treat as counterfeit yes until a scene is confirmed. Book only with artifact, owner, date. |
| "That's not our Friday" | "That's right — thank you." Ask one calibrated question or leave. Do not rescue the pitch. |
| Forwards to a controller | Stay on Voss. They are not a back door to force the CEO. |
| Meeting | Do not replay the joke. Discovery: "Where does the current system stop matching physical reality?" Then proof ladder. |
Re-engage line, if we ever re-enter months later with a new artifact: "Have you given up on examining where the system stops matching the work?" Same as the communication instructions. Not a third bump of the same video.
ConnectAndSell is a call channel. Do not read the video script on a cold call. The call still opens: identity, "is now a bad time," stop.
Step 7 — If they take the meeting
The video earned a conversation, not a deal. Resume the six steps from the top, live:
- Reality — their artifact on the table, not our recording.
- Problem hypothesis — confirm or correct. Hunt "that's right."
- Impact — scene of consequence, labeled.
- Mechanism — one layer that makes this Friday possible. Classify it (native / configured / integrated / roadmap).
- Proof — one comparable human's moment. Buyer stays protagonist.
- Choice — no-oriented next step with artifact, owner, date.
A verbal "yes" is not adoption. Valid next step contains artifact, buyer owner, Naologic owner, due date, meeting date, acceptance criterion.
Step 8 — Measure the motion
Weekly, not vanity:
- Packets started vs packets that earned a recording (if this is low, we are picking names without artifacts).
- Replies that correct us (useful. Black swan.).
- Replies that say "that's right" (recognition. Not yet a deal.).
- Meetings that put an artifact on the table.
- Stops honored (love of process).
Do not optimize for views, watch time, or "personalized videos sent." Volume is how the dinner test dies.
Worked example (fictional plant — do not send)
Artifact: careers page hiring a production planner, "advanced Excel, pivot tables, ERP a plus." Company makes injection-molded parts. Owner-CEO named on the site.
Beat 1 — "Maria, this is Gabriel at Naologic. This is a recording. If this is a bad time, delete it. No sequence behind it."
Beat 2 — "This is going to look like a software video. It might be. You can decide."
Beat 3 — "I may be completely wrong. It looks like the planner still has to make Friday's numbers true in Excel even if something called an ERP is already in the building. Schedule says one thing, the floor did another, therefore somebody decides on a lie. If that is not your Fridays, I have the wrong shop."
Beat 4 — "Would it be a bad idea to look at that for twelve minutes, or would you rather I left you alone?"
No product name beyond who we are. No "AI." No "we help manufacturers scale." No moral.
The only joke is Beat 2, and it is on us.
What this is not
- A way around communication instructions.
- Proof of a problem. The video is
inferred. - License to deepfake, roast, or buy a comedian to mock Excel users.
- A 50-touch "personalized video" factory.
- Content for 500–5000 procurement. Wrong room.
- Authority to mint
SG_states or bind a CRM opportunity from a send.
Related knowledge
- Communication instructions
- ERP signal research
- Expo signal research
- Conference prep — ERP conference rooms; video only if we already have a named P1 and an artifact
- Accounting AI course — teach-first
- Sales stack
- Persona list — P1
Change log
- 2026-09-05 — Point ERP conference rooms to conference prep; scene video is not the Stratosphere template.
- 2026-08-31 — Content map; ClickHouse specificity without copying a mythic roast campaign; six-step truncation; Voss spine; comedy rules; eight-step record/send/stop for P1 scene videos.