Marketplace — social-W38-Wed-2 — Temerarii Media Back Office

post social-W38-Wed-2kind threadweek W38date 2026-09-23campaign thread · Wedpillar performancebeat Wedasset videoduration 59.5sground whitescenes 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-W38-Wed-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 · 59.5s · 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·color	♪ bed_in	Old way: SaaS support was a queue of tickets and a cost line everyone wanted to shrink. on-screen: Support was a cost center
	expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→Support was a cost center
2	still pending matches intent shared field signature-3d	hook	6.6–13.2s	kinetic-build	icon·color	♪ node_lock	Here is the miss: every ticket is a confused user telling you exactly where the product breaks. on-screen: Tickets hide the real signal
	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→Tickets hide the real signal
3	still pending matches intent NumberedList template	teach	13.2–20.2s	kinetic-build	icon·color	♪ node_lock	New way: feed your tickets to a model and have it cluster them into the top recurring problems. on-screen: Cluster tickets with a model
	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→Cluster tickets with a modelcurate items, nodes
4	still pending matches intent RankList template	proof	20.2–26.799999999999997s	receipts-count	icon·color	♪ node_lock	Now the loudest cluster points straight at the next fix, so the roadmap stops being a guess. on-screen: The roadmap writes itself
	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→The roadmap writes itselfcurate rows, statsLabels
5	still pending matches intent BuildLog template	diff	26.8–33.1s	crossfade-8f	icon·color	♪ node_lock	Old SaaS chased ticket deflection. Better SaaS chases understanding, because fixing the cause kills the ticket. on-screen: Deflection vs understanding
	expected on screen: white ground · a BuildLog panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape dodecaground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Deflection vs understandingcurate codeLines, lines
6	still pending matches intent ChecklistCard template	teach	33.1–40.4s	kinetic-build	icon·color	♪ node_lock	Teach the team to log the question each new user asks first, since that reveals the broken onboarding step. on-screen: Tag every signup question
	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→Tag every signup questioncurate items, nodes
7	still pending matches intent StatScoreboard template	proof	40.4–45.9s	receipts-count	icon·color	♪ node_lock	The first-question pattern maps the exact place onboarding loses people, in their own words. on-screen: Confusion maps the fix
	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→Confusion maps the fixcurate pillar, stats, statsLabels
8	still pending matches intent ProcessFlow template	step	45.9–52.9s	kinetic-build	icon·color	♪ node_lock	Your step: pull last month of tickets, cluster them, and pick the top three to fix this sprint. on-screen: Cluster last month tickets
	expected on screen: white ground · a ProcessFlow panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual pipelineshape dodecaground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Cluster last month ticketscurate stages, steps
9	still pending matches intent shared field signature-3d	resolve	52.9–59.5s	coalescence	icon·color	♪ bed_out	Now support is product feedback, not a cost. The Big T-M turns the queue into the roadmap. on-screen: Support as product feedback
	expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Support as product feedback

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)

tiktokStop treating SaaS support as a cost center. Cluster your tickets with a model and the top complaint becomes your roadmap. (AI-assisted) #saas #productmanagement #startups

instagramEvery ticket is a user telling you where it breaks. Cluster them. Read the pattern. The roadmap writes itself. #saas #product #startups #customersuccess #tech

linkedinMost SaaS teams treat support as a cost center to shrink. That misses the signal: every ticket is a confused user telling you exactly where the product breaks. The move: feed your tickets to a model, cluster them into the top recurring problems, and let the loudest cluster point at the next fix. Also log the first question each new user asks, because that pattern maps the exact step where onboarding loses people, in their own words. Support is product feedback. Pull last month's tickets and cluster them.

xStop treating SaaS support as a cost center. Cluster your tickets with a model and the top complaint becomes your roadmap. Method:

facebookSaaS teams treat support as a cost to cut, but every ticket shows you where the product breaks. Cluster your tickets with a model and let the biggest complaint shape the roadmap. Comment for the clustering prompt.

threadsSaaS support is not a cost center, it is your roadmap in disguise. Feed your tickets to a model, cluster them into the top recurring problems, and fix the loudest one. Also log the first question every new user asks. That pattern shows exactly where onboarding breaks.

pinterestSaaS product strategy: how to cluster support tickets with an AI model to find the top recurring problems and build your roadmap from real user pain. Log first-questions to fix onboarding. SaaS tips, product management, startups.

blueskySaaS support is not a cost center, it is your roadmap. Cluster your tickets with a model and fix the loudest complaint. Method:

youtubeTurn SaaS Support Into Your Roadmap: Cluster Tickets, Fix the Cause Most teams treat support as a cost to shrink and miss the signal. This shows how to cluster support tickets with a model to surface the top recurring problems, and why logging the first question every new user asks maps the exact step where onboarding loses people. SaaS, product management, customer success. 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