Back Office · office.temerarii.xyz
One published post, granular — the Social for W32 Sat, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW32-Sat-social-1kindSocialweekW32daySatdate2026-08-15campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Omni-channel revenue funnel
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-W32-Sat-1
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
TiktokHow an omni-channel revenue funnel actually works. Stop running each channel as a separate island. It's ONE path every channel feeds: social earns the first hello, email does the patient closing — each plays its real strength. The trick: carry one shared customer ID across channels so a person is never a stranger twice and you see the whole path. #marketingfunnel #omnichannel #growth
InstagramOne funnel, many doors. Social finds them. Email closes them. Carry one customer ID across channels. See the whole path, not scattered clicks. #marketingfunnel #omnichannel #marketing #growth #strategy
LinkedinWhy most multi-channel marketing isn't a funnel — and how to fix it: For years, each channel ran as its own island. An omni-channel revenue funnel is one path that every channel feeds into together. Map the stages first, then assign each channel the job it does best: social earns the first hello, email does the patient closing. Blasting the same hard sell everywhere just teaches people to tune you out. The connective move: carry one shared customer ID across channels so a person is never a stranger twice. That ID lets you see the whole path instead of a pile of disconnected clicks. Takeaway: one funnel, many doors, all walking to the same sale.
XOmni-channel funnel done right: it's ONE path every channel feeds. Social finds them, email closes them. Carry one shared customer ID across channels so you see the whole path, not scattered clicks. temerarii.com
FacebookFor years each channel ran as its own island. An omni-channel revenue funnel is one path that every channel feeds into together. Map the stages first, then assign each channel the job it does best — social earns the first hello, email does the patient closing. Then carry one shared customer ID across channels so a person is never a stranger twice and you can see the whole path. Here's the blueprint.
ThreadsOmni-channel funnel, done right: it's ONE path every channel feeds. Social earns the first hello, email does the patient closing — each plays its strength. Carry one shared customer ID across channels so a person is never a stranger twice and you see the whole path.
PinterestOmni-channel marketing funnel explained: how to connect social, email, and every channel into one revenue path. A guide to mapping funnel stages, assigning each channel its best job, and using one shared customer ID to track the full journey. Marketing funnel strategy.
BlueskyOmni-channel funnel done right: it's ONE path every channel feeds. Social finds them, email closes them. Carry one shared customer ID across channels so you see the whole path, not scattered clicks. temerarii.com
YoutubeOmni-Channel Revenue Funnel: One Path, Many Doors For years, each channel ran as its own island. This short explains the omni-channel revenue funnel: one path that every channel feeds into together. Map the stages first, then assign each channel the job it does best — social earns the first hello, email does the patient closing. Blasting the same hard sell everywhere just teaches people to tune you out. The connective move: carry one shared customer ID across channels so you see the whole path instead of a pile of disconnected clicks. More at temerarii.com.

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–6.3sspatial-parallaxicon·wireframe♪ bed_in
For years each channel ran as its own island, none of them talking to the others.
on-screen: Channels used to run as separate islands
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Channels used to run as separate islands
2s2
matches intent
shared field
signature-3d
hook6.3–11.5skinetic-buildicon·color♪ node_lock
An omni-channel funnel is one path that every channel quietly feeds into together.
on-screen: One funnel, every channel feeding it
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→One funnel, every channel feeding it
3s3
matches intent
NumberedList
template
teach11.5–17.4skinetic-buildicon·color♪ node_lock
The move is mapping the stages first, then deciding which channel does which job best.
on-screen: Map the stages, then assign channels
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Map the stages, then assign channelscurate items, nodes
4s4
matches intent
RankList
template
proof17.4–23.299999999999997sreceipts-counticon·color♪ node_lock
Social earns the first hello, email does the patient closing; each plays its real strength.
on-screen: Social finds them, email closes them
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape dodecaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Social finds them, email closes themcurate rows, statsLabels
5s5
matches intent
JsonDiff
template
diff23.3–29.200000000000003scrossfade-8ficon·color♪ node_lock
Blasting the same hard sell on every channel just teaches people to tune you out.
on-screen: Same hard sell everywhere repels people
expected on screen: white ground · a JsonDiff panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual codeshape dodecaground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Same hard sell everywhere repels peoplecurate codeLines, fileName, lines
6s6
matches intent
ChecklistCard
template
teach29.2–35.1skinetic-buildicon·color♪ node_lock
Carry one shared customer ID across channels so a person is never a stranger twice.
on-screen: Pass one ID across every channel
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Pass one ID across every channelcurate items, nodes
7s7
matches intent
StatScoreboard
template
proof35.1–41.4sreceipts-counticon·color♪ node_lock
That shared ID lets you see the whole path instead of a pile of disconnected clicks.
on-screen: A shared ID shows the full path
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape dodecaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→A shared ID shows the full pathcurate pillar, stats, statsLabels
8s8
matches intent
FlowSchematic
template
step41.4–47.699999999999996skinetic-buildicon·color♪ node_lock
Map the funnel, assign each channel a job, connect them with one ID, then watch it.
on-screen: Map, assign, connect by ID
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual pipelineshape dodecaground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Map, assign, connect by IDcurate stages, steps
9s9
matches intent
shared field
signature-3d
resolve47.7–53.2scoalescenceicon·wireframe♪ bed_out
Omni-channel is one funnel with many doors, all walking toward the same quiet sale.
on-screen: One funnel, many doors
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→One funnel, many doors

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