Custom CRM (Airtable, Claude-run) — social-W31-Fri-2

post social-W31-Fri-2kind threadweek W31date 2026-08-07campaign thread · Fripillar it_devbeat Friasset videoduration 64.6sground blackscenes 9

Checklist the per-video bar — engine/sim

86.6/100

plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness

quantitative quality · weights learn from your reviews (engine.sim.memory review social-W31-Fri-2 good|bad)

⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel

9:16 Reelpending1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending

render pending — silent master not yet on disk

expected output: 0/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 9 scenes · 64.6s · comp_id + rendered still + tier + the script

#	Layer (comp_id · still · tier)	Beat	Timecode	Motion	Logo	Audio	VO / on-screen / caption
1	still pending matches intent shared field signature-3d	open	0–6.6s	spatial-parallax	icon·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
2	still pending matches intent shared field signature-3d	hook	6.6–13.2s	kinetic-build	icon·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
3	still pending matches intent NumberedList template	teach	13.2–20.9s	kinetic-build	icon·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
4	still pending matches intent RankList template	proof	20.9–28.599999999999998s	receipts-count	icon·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
5	still pending matches intent TerminalRun template	diff	28.6–36.300000000000004s	crossfade-8f	icon·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
6	still pending matches intent ChecklistCard template	teach	36.3–43.3s	kinetic-build	icon·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
7	still pending matches intent StatScoreboard template	proof	43.3–51.0s	receipts-count	icon·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
8	still pending matches intent PipelineMap template	step	51.0–57.6s	kinetic-build	icon·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
9	still pending matches intent shared field signature-3d	resolve	57.6–64.6s	coalescence	icon·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

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 9 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky

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

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

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

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