Back Office · office.temerarii.xyz
One asset, all the way in — composition, the wireframe + storyboard, the output format stack, and the template, all read from the SAME content-index record. The expected output matches what /media surfaces for this post.
post topic-x-outbound-scalekind topicweek —date —campaign strategic-relations-pillarpillar strategic_relationsbeat —asset videoduration 138.1sground blackscenes 19

Checklist the per-video bar — engine/sim

94.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-x-outbound-scale good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_generictoo_complex · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SceneReel
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 19 scenes · 138.1s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–7.2sspatial-parallaxicon·white-knockout♪ —
Cold outreach fails because it's generic. We can make a thousand emails each feel hand-written, and here's the real method.
on-screen: Personal at a thousand sends
expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
ListCard
template		legacy7.2–14.100000000000001scrossfade-8ficon·ember-fill♪ —
The old way blasted one template to ten thousand inboxes, hit the spam folder, and called the silence a strategy.
on-screen: Old way: blast the same email
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Nexus leads · crossfade-8f · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ListCardshape tetraground blacktreatment ember-fillmotion crossfade-8fpower morphinstrument decay→three-symboliccurate items
3s3
matches intent
NumberedList
template		teach14.1–21.4skinetic-buildicon·wireframe♪ —
It starts with precision: define the exact role, company size, and trigger that makes someone worth contacting.
on-screen: Step 1: define who, exactly
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4s4
matches intent
ChecklistCard
template		teach21.4–29.2skinetic-buildicon·white-knockout♪ —
Then we diagram the data flow: find matching companies, enrich each contact, and verify the email so nothing bounces.
on-screen: Find -> enrich -> verify
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5s5
matches intent
JsonDiff
template		teach29.2–36.7skinetic-buildicon·liquid-chrome♪ —
We pull each prospect's details through enrichment APIs into a clean table, the same Clay-style stack the best teams use.
on-screen: Enrich each lead via API
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape tetraground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate fileName, lines, nodes
6s6
matches intent
LogStream
template		teach36.7–45.400000000000006skinetic-buildicon·ember-fill♪ —
It flows into research: for each lead the model reads a real signal, recent news, a hire, a post, and writes one true opening
on-screen: Lead -> research -> hook
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape tetraground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, rows
7s7
matches intent
BlueprintGrid
template		teach45.4–51.9skinetic-buildicon·wireframe♪ —
That first line is the entire game. It has to prove you actually looked, which a template never can.
on-screen: The hook is the whole game
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes, rows
8s8
matches intent
BuildLog
template		teach51.9–59.4skinetic-buildicon·white-knockout♪ —
We diagram the message: a fixed structure with researched variables slotted in, so it scales without sounding like a
on-screen: One template, many variables
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual node-graphshape tetraground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate lines, nodes
9s9
matches intent
ProcessFlow
template		teach59.4–66.6skinetic-buildicon·liquid-chrome♪ —
The model writes only the personalized lines per lead; the proven body stays fixed, so quality holds at volume.
on-screen: Generate the variable lines
expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual node-graphshape tetraground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, steps
10s10
matches intent
StackTrace
template		teach66.6–74.39999999999999skinetic-buildicon·ember-fill♪ —
It flows into sending: warmed inboxes, drip the sends so you stay human-paced, and follow up automatically if they go quiet.
on-screen: Warm -> send -> follow up
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape tetraground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate errMsg, errType, fix, frames, nodes
11s11
matches intent
AnnotatedDiagram
template		teach74.4–81.30000000000001skinetic-buildicon·wireframe♪ —
We send from separate warmed domains, never the main one, so a campaign can never burn your real reputation.
on-screen: Protect the domain
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate callouts, nodes
12s12
matches intent
PipelineMap
template		teach81.3–88.8skinetic-buildicon·white-knockout♪ —
We diagram what happens on a reply: detect it, stop the sequence, and route the lead straight into the CRM for a
on-screen: Reply -> route -> CRM
expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual node-graphshape tetraground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes, stages
13s13
matches intent
SchematicCard
template		teach88.8–96.39999999999999skinetic-buildicon·liquid-chrome♪ —
The machine starts the conversation; a person finishes it. Automation books the meeting, it never fakes the relationship.
on-screen: A human closes, always
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape tetraground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes
14s14
matches intent
StepFlow
template		teach96.4–104.2skinetic-buildicon·ember-fill♪ —
Every send flows into tracking: opens, replies, and meetings scored per segment, so you double down on what lands.
on-screen: Sent -> tracked -> scored
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape tetraground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, steps
15s15
matches intent
CheatSheet
template		teach104.2–110.7skinetic-buildicon·wireframe♪ —
Start narrow: one tight segment, one hundred sends, and read the reply rate before you scale a single thing.
on-screen: Test one segment first
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes, points, uses
16s16
matches intent
LegacyCard
template		teach110.7–118.3skinetic-buildicon·white-knockout♪ —
We diagram the scaling rule: find the segment that replies, pour volume there, and retire the messages that don't.
on-screen: Winner -> scale -> repeat
expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual node-graphshape tetraground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes
17s17
matches intent
RankList
template		proof118.3–125.0sreceipts-counticon·liquid-chrome♪ —
Done right, a small list outperforms a giant blast, because relevance beats volume every single time.
on-screen: Replies, not just sends
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape tetraground blacktreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate rows, statsLabels
18s18
matches intent
shared field
signature-3d		futurist125.0–131.6sspatial-parallaxicon·ember-fill♪ —
Soon every cold message arrives already knowing your world, and the only ones that send are the ones worth your time.
on-screen: Outreach that does homework
expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape tetraground blacktreatment ember-fillmotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
19s19
matches intent
shared field
signature-3d		resolve131.6–138.1scoalescenceicon·white-knockout♪ swell
Want outbound that actually gets replies? We'll build the engine. Start at temerarii.xyz.
on-screen: Build your outbound engine
expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→three-coalescence

Format stack 3 aspects · same scenes[], re-cropped

9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 12 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog

Social captions supplemental published copy · per channel (comp_id level)

tiktokCold outreach fails because it is generic. Here is how to make a thousand emails each feel hand-written (AI-assisted). Define the exact role and trigger worth contacting. Find, enrich, and verify each contact so nothing bounces. Then have the model read a real signal per lead, a recent hire or post, and write one true opening line. Keep the proven body fixed and slot in the researched lines. Warm the inboxes, send from separate domains, and a human closes every deal. Start narrow: one segment, a hundred sends, read the replies. Method at temerarii.xyz.
instagramCold outreach fails because it is generic. Here is how to make each email feel hand-written. The method: Define the exact role and trigger Find, enrich, and verify each contact Research one real signal per lead, then write a true opening line Keep the body fixed, slot in the researched lines Warm inboxes, send from separate domains A human closes every deal Start narrow: one segment, a hundred sends, read the replies. Build yours at temerarii.xyz #outbound #coldemail #sales #leadgen #automation
linkedinCold outreach fails because it is generic. Here is the method to make a thousand emails each feel hand-written, without faking it. The old way: blast one template to ten thousand inboxes, hit the spam folder, and call the silence a strategy. The build: - Define the exact role, company size, and trigger that makes someone worth contacting - Find matching companies, enrich each contact, and verify the email so nothing bounces - For each lead, have the model read a real signal, a recent hire or a post, and write one true opening line - Keep the proven body fixed and slot in the researched lines, so quality holds at volume - Warm the inboxes, drip the sends to stay human-paced, and follow up if they go quiet - Send from separate warmed domains, never your main one, so a campaign can never burn your real reputation - On a reply, stop the sequence and route the lead into the CRM The machine starts the conversation; a person finishes it. Start narrow: one tight segment, a hundred sends, and read the reply rate before you scale. A small relevant list beats a giant blast. The method is yours. If you want the engine built, The Big T-M does that at temerarii.xyz
xCold outreach fails because it is generic. Define the exact target, enrich and verify each contact, then research one real signal per lead and write a true opening line. Keep the body fixed. A human closes. Start with 100 sends. Method: temerarii.xyz
facebookCold outreach fails because it is generic. Here is how to make a thousand emails each feel hand-written. Start with precision: define the exact role and trigger worth contacting. Find, enrich, and verify each contact so nothing bounces. Then have the model read a real signal per lead, a recent hire or a post, and write one true opening line. Keep the proven body fixed and slot the researched lines in. Send from separate warmed domains so a campaign never burns your main reputation, and let a person close every deal. Start narrow: one segment, a hundred sends, read the replies. Want this built? Start at temerarii.xyz
threadsCold outreach fails because it is generic. Here is how to make each email feel hand-written. Define the exact target. Find, enrich, and verify each contact. Research one real signal per lead and write a true opening line. Keep the body fixed. Send from separate warmed domains. A human closes. Start with one segment and a hundred sends. Method at temerarii.xyz
pinterestHow to scale cold outreach that actually gets replies: define your exact target role and trigger, find and enrich and verify each contact so emails do not bounce, then research one real signal per lead and write a personalized opening line while keeping the proven body fixed. Warm separate sending domains and let a person close. Start with one segment and a hundred sends. Evergreen outbound and lead-gen method.
blueskyCold outreach fails because it is generic. Define the exact target, enrich and verify each contact, research one real signal per lead, write a true opening line, keep the body fixed. A human closes. Start with 100 sends. Method: temerarii.xyz
youtubeHow to Scale Personalized Cold Outreach That Gets Replies (Full Method) Cold outreach fails because it is generic. This walkthrough teaches how to make a thousand emails each feel hand-written, end to end, without faking the relationship. What we cover: - Defining the exact role, company size, and trigger worth contacting - Finding matching companies, enriching each contact, and verifying the email so nothing bounces - Reading a real signal per lead, a recent hire or post, and writing one true opening line - Keeping the proven body fixed and slotting in only the researched lines, so quality holds at volume - Warming the inboxes and dripping the sends to stay human-paced - Sending from separate warmed domains, never your main one, so a campaign cannot burn your real reputation - Detecting a reply, stopping the sequence, and routing the lead into the CRM - Letting a person close every deal Start narrow: one tight segment, a hundred sends, and read the reply rate before you scale a single thing. A small relevant list beats a giant blast, because relevance beats volume. The method is yours to keep. If you want the outbound engine built, The Big T-M does that at temerarii.xyz AI-assisted production.

Cross-links every lens is a view on this one record

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view