Back Office · office.temerarii.xyz
One published post, granular — the Social for W39 Fri, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW39-Fri-social-4kindSocialweekW39dayFridate2026-10-02campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

The Machine — build-in-public (demystifying data/AI)
copy ready · render pending

Output-policy spec format · dimensions (asset_specs.output_policy)

formatnative cut · 9:16 · 1:1 · 16:9 dims1080×1920 · 1080×1080 · 1920×1080 cadence5/day floor × 9 channels

Channels 9 destinations

TikTokInstagramLinkedInX/TwitterFacebookThreadsPinterestBlueskyYouTube

This post a distinct social asset — its own angle, storyboard, and cuts

social-W39-Fri-4
5-distinct-social/day · 9:16 master → 1:1 / 16:9 cuts per channel

Channel-cuts this asset → 9 native captions (one master · per-platform aspect+copy)

ChannelNative caption
TiktokCold email fails because it is the same note to everyone. Here is how to scale outreach that is actually relevant. (AI-assisted)
InstagramRelevance is the whole game. Enrich each contact first. AI writes the line, you approve. Fewer emails, more replies. #outbound #coldemail #ai #sales #temerarii
LinkedinCold outreach mostly fails because it is the same note sent to everyone. The fix is relevance at scale: enrich each contact with a public signal only they would care about, a hire, a launch, a recent change, then let AI draft one true opening line about it, with a human approving each. You send fewer emails to better-fit people and get far more honest replies. Outbound at scale is relevance, done many times.
XCold email fails because it's the same note to everyone. Enrich each contact, let AI write one relevant line, approve it, send fewer. tmstudio.link/outbound
FacebookCold outreach mostly fails because it is the same note sent to everyone. Here is the fix: enrich each contact with a public signal only they would care about, a hire, a launch, a recent change, then let AI draft one true opening line and a human approve it. Fewer emails to better-fit people, far more replies. Comment OUTBOUND for the workflow.
ThreadsCold email fails because it's the same note to everyone. Enrich each contact with a public signal they'd care about, let AI write one true opening line, approve each, send fewer. Outbound at scale is relevance, done many times.
PinterestOutbound at scale that gets replies: stop blasting one generic email. Enrich each contact with a public signal, let AI write one relevant opening line, and approve each. Cold email strategy, sales outreach, lead generation, B2B sales.
BlueskyCold email fails because it's the same note to everyone. Enrich each contact, let AI write one relevant line, approve it, send fewer. tmstudio.link/outbound
YoutubeCold Email Fails Because It Is The Same Note To Everyone The only thing that earns a reply is being obviously relevant to that one person. In this short we show how to scale relevance: enrich each contact with a public signal only they would care about, a hire, a launch, a recent change, then let AI draft one true opening line about it with a human approving each. You send fewer emails to better-fit people and get far more honest replies. AI-assisted production. Chapters: cold email fails, relevance is the game, enrich each contact, AI writes you approve. #outbound #coldemail #sales

Composition layer × scene 9 scenes · this post's OWN storyboard (distinct per asset)

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–5.2sspatial-parallaxicon·ember-fill♪ bed_in
Cold outreach mostly fails because it is the same note sent to everyone.
on-screen: Cold email mostly fails
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Cold email mostly fails
2s2
matches intent
shared field
signature-3d
hook5.2–10.7skinetic-buildicon·wireframe♪ node_lock
The only thing that earns a reply is being obviously relevant to that person.
on-screen: Relevance is the whole game
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→Relevance is the whole game
3s3
matches intent
NumberedList
template
teach10.7–17.0skinetic-buildicon·wireframe♪ node_lock
The old way bought a giant list and blasted one generic line at all of it.
on-screen: Old way: buy a list, blast it
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Old way: buy a list, blast itcurate items, nodes
4s4
matches intent
ComparisonTable
template
proof17.0–22.5sreceipts-counticon·wireframe♪ node_lock
The real method enriches each contact with a fact only they would care about.
on-screen: Enrich each contact first
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Enrich each contact firstcurate colA, colB, rows, statsLabels
5s5
matches intent
TerminalRun
template
diff22.5–28.4scrossfade-8ficon·wireframe♪ node_lock
Now we pull a public signal per company, a hire, a launch, a recent change.
on-screen: Now: AI gathers the signal
expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape boxground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Now: AI gathers the signalcurate codeLines
6s6
matches intent
ChecklistCard
template
teach28.4–34.3skinetic-buildicon·wireframe♪ node_lock
Then AI drafts one true opening line about it, and a human approves each one.
on-screen: AI writes the first line, you approve
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→AI writes the first line, you approvecurate items, nodes
7s7
matches intent
KpiGrid
template
proof34.3–39.5sreceipts-counticon·wireframe♪ node_lock
You send fewer emails to better-fit people and get far more honest replies.
on-screen: Fewer emails, far more replies
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Fewer emails, far more repliescurate kpis, statsLabels
8s8
matches intent
FlowSchematic
template
step39.5–45.0skinetic-buildicon·wireframe♪ node_lock
So enrich your list first, then let AI write one relevant line per contact.
on-screen: Step: enrich, then one relevant line
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual pipelineshape boxground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Step: enrich, then one relevant linecurate stages, steps
9s9
matches intent
shared field
signature-3d
resolve45.0–50.2scoalescenceicon·ember-fill♪ bed_out
Outbound at scale is not louder spam. It is relevance, done many times.
on-screen: Be relevant or be ignored
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Be relevant or be ignored

Cross-links this post in the day's output set