Back Office · office.temerarii.xyz
One published post, granular — the Social for W31 Fri, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW31-Fri-social-2kindSocialweekW31dayFridate2026-08-07campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Custom CRM (Airtable, Claude-run)
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-W31-Fri-2
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
TiktokA CRM nobody updates is a list of strangers pretending to be warm contacts. Build it in a simple table, let AI read your call notes and log the update, give each record ONE owner. (AI-assisted) #CRM #sales #automation
InstagramBuild it in a simple table. AI logs the call notes. One owner per record. A CRM you actually fill. #CRM #sales #automation #smallbusiness #temerarii
LinkedinA CRM nobody updates is a list of strangers pretending to be your warm contacts. Build it in a plain table with only the fields you'll actually fill, let a model read your call notes and write the update so the boring part does itself, and give each record one owner so leads don't fall in the gap. A small CRM you update beats a fancy one you abandon.
XA CRM nobody updates is a list of strangers. Build it in a simple table. Let AI log the notes. One owner per record. temerarii.com
FacebookBuild a CRM you'll actually use: a simple table, AI that logs your call notes, and one owner per record so no lead slips through. A small one you update beats a fancy one you abandon. Free method on the site.
ThreadsA CRM nobody updates is a list of strangers pretending to be your warm contacts. Build it in a simple table, let the model log the call notes, give each record one owner. A small one you fill beats a fancy one you abandon.
PinterestCustom CRM best practices: build it in a simple table with only fields you'll fill, use AI to log call notes automatically, and assign one owner per record. Lightweight CRM system you actually maintain instead of abandoning.
BlueskyA CRM nobody updates is a list of strangers. Build it in a simple table. Let AI log the notes. One owner per record. temerarii.com
YoutubeA CRM You Actually Fill: Simple Table, AI Logging, One Owner Per Record A CRM nobody updates is a list of strangers pretending to be your warm contacts. Build it in a plain table with only the fields you'll fill, let a model read your call notes and write the update so the boring part does itself, and give each record one owner so leads don't slip through. A small one you update beats a fancy one you abandon. Free 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.6sspatial-parallaxicon·liquid-chrome♪ bed_in
A CRM used to be expensive software you paid for monthly and felt guilty for barely using.
on-screen: CRM as expensive guilt
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→CRM as expensive guilt
2s2
matches intent
shared field
signature-3d
hook6.6–13.2skinetic-buildicon·wireframe♪ node_lock
Dark truth: a CRM nobody updates is a list of strangers pretending to be your warm contacts.
on-screen: A CRM you don't update lies
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→A CRM you don't update lies
3s3
matches intent
NumberedList
template
teach13.2–20.9skinetic-buildicon·wireframe♪ node_lock
So we do it now by building the CRM in a plain table, with the few fields you'll actually fill.
on-screen: Build it in a simple table
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Build it in a simple tablecurate items, nodes
4s4
matches intent
RankList
template
proof20.9–28.599999999999998sreceipts-counticon·wireframe♪ node_lock
Let a model read your call notes and write the update into the table, so the boring part does itself.
on-screen: Let the model log the notes
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Let the model log the notescurate rows, statsLabels
5s5
matches intent
TerminalRun
template
diff28.6–36.300000000000004scrossfade-8ficon·wireframe♪ node_lock
Old way rented a giant tool. The right way owns a small one that fits the work you really do.
on-screen: Old
expected on screen: black 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 blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Old: rent a giant. Now: own a small onecurate codeLines
6s6
matches intent
ChecklistCard
template
teach36.3–43.3skinetic-buildicon·wireframe♪ node_lock
Give each record one owner, so a lead never falls in the gap between two people both assuming.
on-screen: One owner per record
expected on screen: black 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 blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→One owner per recordcurate items, nodes
7s7
matches intent
StatScoreboard
template
proof43.3–51.0sreceipts-counticon·wireframe♪ node_lock
We run this at The Big T-M, and a small CRM you update beats a fancy one you quietly abandon.
on-screen: A CRM you actually fill
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→A CRM you actually fillcurate pillar, stats, statsLabels
8s8
matches intent
PipelineMap
template
step51.0–57.6skinetic-buildicon·wireframe♪ node_lock
Your move: build the simple table, let the model log the notes, give each record one owner.
on-screen: Steps: table, auto-log, owner
expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual pipelineshape boxground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Steps: table, auto-log, ownercurate stages, steps
9s9
matches intent
shared field
signature-3d
resolve57.6–64.6scoalescenceicon·liquid-chrome♪ bed_out
Now the CRM stays true, because the work to keep it honest finally fits inside a normal day.
on-screen: A CRM that stays true
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→A CRM that stays true

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