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-perf-saaskind topicweek date campaign performance-pillarpillar performancebeat asset videoduration 54.7sground blackscenes 9

Checklist the per-video bar — engine/sim

95.7/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-perf-saas 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 9 scenes · 54.7s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–6.1sspatial-parallaxicon·liquid-chrome♪ —
For SaaS the whole game is the trial: the first week decides whether someone pays or vanishes.
on-screen: SaaS lives or dies on the trial
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
ComparisonTable
template
legacy6.1–11.5scrossfade-8ficon·ember-fill♪ —
The old way gave every new signup the same tour, whether they were a founder or a finance lead.
on-screen: Old way: same onboarding for everyone
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · crossfade-8f · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ComparisonTableshape dodecaground blacktreatment ember-fillmotion crossfade-8fpower morphinstrument decay→three-symboliccurate colA, colB, rows
3s3
matches intent
NumberedList
template
teach11.5–17.9skinetic-buildicon·wireframe♪ —
Step one, we read the signup details and route each user toward the feature their role actually needs first.
on-screen: Step 1
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4s4
matches intent
ChecklistCard
template
teach17.9–24.7skinetic-buildicon·white-knockout♪ —
Step two, the model writes a specific in-app nudge for the moment a user stalls, not a generic banner.
on-screen: Step 2: model writes the in-app nudge
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5s5
matches intent
BlueprintGrid
template
teach24.7–31.2skinetic-buildicon·liquid-chrome♪ —
Step three, a model scores usage patterns and flags the accounts quietly drifting toward cancellation.
on-screen: Step 3
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape dodecaground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, rows
6s6
matches intent
LegacyCard
template
teach31.2–37.6skinetic-buildicon·ember-fill♪ —
Step four, a flagged account triggers a tailored win-back through the API, fired the day risk spikes.
on-screen: Step 4: trigger the save, via API
expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual node-graphshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes
7s7
matches intent
KpiGrid
template
proof37.6–43.6sreceipts-counticon·wireframe♪ —
The trial-to-paid rate before and after the changes is right there, plain numbers, no rounding up.
on-screen: Receipts: trial-to-paid moved [receipt: conversion]
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate kpis, statsLabels
8s8
matches intent
shared field
signature-3d
futurist43.6–48.800000000000004sspatial-parallaxicon·white-knockout♪ —
Soon the onboarding rewrites its own steps from what last week's users actually clicked.
on-screen: Next: onboarding that builds itself
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape dodecaground blacktreatment white-knockoutmotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
9s9
matches intent
shared field
signature-3d
resolve48.8–54.699999999999996scoalescenceicon·liquid-chrome♪ swell
Pick one onboarding step and split it by role this week. Smallest change, biggest leak fixed.
on-screen: Tailor one onboarding step by role
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment liquid-chromemotion 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)

tiktokFor SaaS the whole game is the trial. The first week decides who pays and who vanishes. (AI-assisted) The method: read the signup details and route each user to the feature their role needs first. The model writes a specific in-app nudge for the moment they stall, not a generic banner. Score usage patterns to flag accounts drifting toward cancel. Fire a tailored win-back through the API the day risk spikes. Do one thing: pick one onboarding step and split it by role this week.
instagramFor SaaS, the trial is the whole game. The method: Route new users by their role, not a generic tour Write the nudge for the moment they stall Score usage to flag quiet churn Fire a win-back via API when risk spikes The trial-to-paid rate sits right there, no rounding up. #saas #productled #onboarding #aimarketing #temerarii
linkedinFor SaaS, the whole game is the trial. The first week decides whether someone pays or vanishes. Here is how we run trial conversion now, in full: 1. Read the signup details and route each user toward the feature their role actually needs first. 2. The model writes a specific in-app nudge for the moment a user stalls, not a generic banner. 3. A model scores usage patterns and flags the accounts quietly drifting toward cancellation. 4. A flagged account triggers a tailored win-back through the API, fired the day risk spikes. The takeaway: stop giving every signup the same tour. Route by role and act on stall signals. The trial-to-paid rate before and after the changes is right there, plain numbers, no rounding up. This week: pick one onboarding step and split it by role. Smallest change, biggest leak fixed.
xFor SaaS the whole game is the trial. Route new users by role, not a generic tour. Write the nudge for the moment they stall. Score usage to flag quiet churn. Fire a win-back via API when risk spikes. Split one onboarding step by role this week. Biggest leak fixed.
facebookFor SaaS, the whole game is the trial. The first week decides whether someone pays or vanishes. The full method: read the signup details and route each user to the feature their role needs first. Let the model write a specific in-app nudge for the moment they stall, not a generic banner. Score usage patterns to flag accounts drifting toward cancel. Fire a tailored win-back through the API the day risk spikes. This week: pick one onboarding step and split it by role.
threadsFor SaaS the whole game is the trial. The first week decides who pays and who vanishes. Route new users by role, not a generic tour. Write the nudge for the moment they stall. Score usage to flag quiet churn. Fire a win-back via API when risk spikes. Split one onboarding step by role this week.
pinterestSaaS trial conversion method: route new signups by their role, write in-app nudges for the moment users stall, score usage to flag quiet churn, and fire tailored win-backs through an API. A give-it-away guide to lifting trial-to-paid conversion in product-led SaaS.
blueskyFor SaaS the whole game is the trial. Route new users by role, not a generic tour. Write the nudge for the moment they stall. Score usage to flag quiet churn. Fire a win-back via API when risk spikes. Split one onboarding step by role this week. Biggest leak fixed.
youtubeSaaS Trial Conversion: Role Routing, Stall Nudges, Churn Scoring, API Win-Backs For SaaS, the whole game is the trial. The first week decides whether someone pays or vanishes. Here is the full method, given away. The steps: 1. Read the signup details and route each user toward the feature their role actually needs first. 2. The model writes a specific in-app nudge for the moment a user stalls, not a generic banner. 3. A model scores usage patterns and flags the accounts quietly drifting toward cancellation. 4. A flagged account triggers a tailored win-back through the API, fired the day risk spikes. The trial-to-paid rate before and after the changes is right there, plain numbers, no rounding up. What is coming: onboarding that rewrites its own steps from what last week's users actually clicked. Your one next step: pick one onboarding step and split it by role this week. Smallest change, biggest leak fixed. Method over hype. Receipts over claims.

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