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 social-W24-Sun-1kind threadweek W24date 2026-06-14campaign thread · Sunpillar performancebeat Sunasset videoduration 58.7sground blackscenes 9

Checklist the per-video bar — engine/sim

98.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W24-Sun-1 good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · 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 · 58.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–5.0sspatial-parallaxicon·liquid-chrome♪ bed_in
Most SaaS pricing pages are guesses dressed up as math.
on-screen: Your SaaS pricing page is guessing
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→Your SaaS pricing page is guessing
2s2
matches intent
shared field
signature-3d		hook5.0–11.3skinetic-buildicon·wireframe♪ node_lock
Here is how The Big T-M stops the guessing and lets the data set the price.
on-screen: Stop guessing the price
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→Stop guessing the price
3s3
matches intent
NumberedList
template		teach11.3–19.700000000000003skinetic-buildicon·wireframe♪ node_lock
First, tag every in-app event with PostHog, then feed that usage to a model and ask which feature people pay to keep.
on-screen: Tag every event, then ask AI
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→Tag every event, then ask AIcurate items, nodes
4s4
matches intent
RankList
template		proof19.7–26.7sreceipts-counticon·wireframe♪ node_lock
The proof is in the logs: the feature heavy users touch daily is the one worth charging for.
on-screen: Power features hide in the logs
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Power features hide in the logscurate rows, statsLabels
5s5
matches intent
JsonDiff
template		diff26.7–31.9scrossfade-8ficon·wireframe♪ node_lock
The old way was copying a rival's three tiers and praying nobody noticed.
on-screen: Old way: copy a competitor
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual codeshape dodecaground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Old way: copy a competitorcurate codeLines, fileName, lines
6s6
matches intent
ChecklistCard
template		teach31.9–39.6skinetic-buildicon·wireframe♪ node_lock
Now you price the value metric, the thing that grows when the customer wins, like rows synced or seats activated.
on-screen: Price the value, not the seat
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Price the value, not the seatcurate items, nodes
7s7
matches intent
StatScoreboard
template		proof39.6–46.2sreceipts-counticon·wireframe♪ node_lock
When the price tracks real use, the customer feels fair treatment and stops shopping for the exit.
on-screen: Churn drops when price fits use
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Churn drops when price fits usecurate pillar, stats, statsLabels
8s8
matches intent
StepFlow
template		step46.2–53.5skinetic-buildicon·wireframe♪ node_lock
Ship it as a flag: split new signups, charge two prices, let the revenue per user tell the truth.
on-screen: Run a price test with a feature
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual pipelineshape dodecaground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Run a price test with a feature flagcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve53.5–58.7scoalescenceicon·liquid-chrome♪ bed_out
Build the meter once and the pricing model runs itself while you sleep.
on-screen: Let the meter run the model
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→Let the meter run the model

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)

tiktokYour SaaS pricing is a guess (and the data knows it). AI-assisted: tag every in-app event, ask a model which feature heavy users pay to keep, then price THAT. We test it with a feature flag, not a prayer. Full method below.
instagramStop guessing your SaaS price. Tag the events. Let usage pick the value metric. Test it with a flag. #saas #pricing #productled #startups #temerarii
linkedinMost SaaS pricing pages are competitor copies dressed as strategy. The method we use instead: instrument every in-app event, model which features heavy users won't give up, and price the value metric that grows when the customer wins. Then validate with a feature-flag split test, not a hunch. Takeaway: price what people keep, meter what scales.
xYour SaaS price is a guess. Tag every event → ask AI which feature heavy users pay to keep → price the value metric → flag-test it. The meter runs the model. temerarii.com
facebookMost SaaS pricing pages are a competitor's tiers copied over and prayed about. Here's the move we actually run: tag every in-app event, let a model show which features your heavy users won't quit, and price the value metric that grows when they win. Then test two prices behind a feature flag. Want the playbook? It's on the site.
threadsSaaS pricing is usually a guess in a nice font. The fix: tag every event, find the feature heavy users pay to keep, price the value metric, then flag-test two prices. The meter does the rest.
pinterestSaaS pricing strategy: how to price software using product usage data, value metrics, event tracking, and feature-flag A/B price tests. A plain-language guide to usage-based pricing for startups and product-led growth teams.
blueskyYour SaaS price is a guess. Tag every event, find what heavy users pay to keep, price the value metric, flag-test it. temerarii.com
youtubeHow To Price SaaS With Usage Data (Not Guesswork) Most pricing pages are a competitor's three tiers copied and prayed about. This walkthrough shows the method: instrument every in-app event, use a model to surface the features heavy users won't give up, price the value metric that grows when the customer wins, then validate with a feature-flag split test. AI-assisted production. Plain-language, give-it-away breakdown from The Big T-M. Chapters: the guess · tag the events · find the value metric · flag-test the price · let the meter run.

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

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