AI & Automation for GTM — topic-st-ai — Temerarii Media Back Office

post topic-st-aikind topicweek —date —campaign staff-training-pillarpillar staff_trainingbeat —asset videoduration 88.6sground blackscenes 14

Checklist the per-video bar — engine/sim

96.5/100

plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness

quantitative quality · weights learn from your reviews (engine.sim.memory review topic-st-ai 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 14 scenes · 88.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.4s	spatial-parallax	icon·liquid-chrome	♪ —	Everyone says add AI to go-to-market. Nobody says where it actually plugs in. Let us show you. on-screen: AI on your GTM team
	expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→three-mark
2	still pending matches intent NodeGraphCard template	legacy	6.4–12.7s	crossfade-8f	icon·ember-fill	♪ —	The old way was one templated email to ten thousand people, and a reply rate that proved they noticed. on-screen: The generic blast
	expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Magister leads · crossfade-8f · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardshape knotground blacktreatment ember-fillmotion crossfade-8fpower morphinstrument decay→three-symboliccurate hub, nodes
3	still pending matches intent ChecklistCard template	teach	12.7–18.5s	kinetic-build	icon·wireframe	♪ —	First an agent reads each prospect's site and news, so the outreach knows who it is talking to. on-screen: Step 1: enrich the lead
	expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4	still pending matches intent NumberedList template	teach	18.5–25.2s	kinetic-build	icon·white-knockout	♪ —	We score every lead on real signals, so the team spends its hours on the prospects most likely to close. on-screen: Step 2: score, don't guess
	expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5	still pending matches intent FlowSchematic template	teach	25.2–31.5s	kinetic-build	icon·liquid-chrome	♪ —	The agent drafts the first-touch message; a human edits the one line that makes it sound like a person. on-screen: Step 3: draft, human edits
	expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual node-graphshape knotground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, stages
6	still pending matches intent AnnotatedDiagram template	teach	31.5–37.5s	kinetic-build	icon·ember-fill	♪ —	Every claim in the message ties back to something true about them, so it never reads like a generated lie. on-screen: Step 4: ground the claims
	expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape knotground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate callouts, nodes
7	still pending matches intent LegacyCard template	teach	37.5–44.2s	kinetic-build	icon·wireframe	♪ —	When they answer, the system tags intent and routes hot replies to a human instantly, not on Monday. on-screen: Step 5: route the reply
	expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id LegacyCardvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes
8	still pending matches intent CodeWindow template	teach	44.2–50.800000000000004s	kinetic-build	icon·white-knockout	♪ —	Every touch writes itself back to the CRM, so the pipeline is the truth and nobody updates it by on-screen: Step 6: log to the CRM
	expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual node-graphshape knotground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate codeLines, nodes, windowTitle
9	still pending matches intent DiffCard template	teach	50.8–57.699999999999996s	kinetic-build	icon·liquid-chrome	♪ —	Before anything sends at scale, a person approves the batch, because automation without a brake is just spam faster. on-screen: Step 7: keep the human gate
	expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual node-graphshape knotground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate lines, nodes
10	still pending matches intent PipelineMap template	teach	57.7–63.6s	kinetic-build	icon·ember-fill	♪ —	We track the metric that matters, real conversations started, not emails fired into the void. on-screen: Step 8: measure replies, not sends
	expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id PipelineMapvisual node-graphshape knotground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, stages
11	still pending matches intent TerminalRun template	teach	63.6–70.1s	kinetic-build	icon·wireframe	♪ —	When a message underperforms we edit the prompt, run a small batch, and compare, so the system learns on on-screen: Step 9: tune the prompt
	expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes
12	still pending matches intent KpiGrid template	proof	70.1–76.69999999999999s	receipts-count	icon·white-knockout	♪ —	That is outreach that researches, drafts, grounds, and routes, with a human on the one judgment call. on-screen: Personal at scale
	expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape knotground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate kpis, statsLabels
13	still pending matches intent shared field signature-3d	futurist	76.7–82.3s	spatial-parallax	icon·liquid-chrome	♪ —	When the busywork is gone, your team does the part AI cannot: the actual relationship. on-screen: What this unlocks
	expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldshape knotground blacktreatment liquid-chromemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
14	still pending matches intent shared field signature-3d	resolve	82.3–88.6s	coalescence	icon·liquid-chrome	♪ swell	Show us your GTM motion and we will mark exactly where AI earns its keep. temerarii.xyz. on-screen: Map your motion
	expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground 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)

tiktokEveryone says add AI to your outreach. Nobody says where it plugs in. (AI-assisted) Here is the real map: an agent reads each prospect's site and news, you score every lead on real signals, the agent drafts the first message, and a human edits the one line that makes it sound like a person. Every claim ties back to something true about them. Hot replies route to a human instantly. Every touch logs to the CRM. And a person approves the batch before it sends at scale, because automation without a brake is just spam faster.

instagramAdd AI to outreach, they say. Where though? Here is the map: Agent reads the prospect's site + news Score leads on real signals Agent drafts, human edits one line Ground every claim in something true Route hot replies to a person now Log every touch to the CRM Human approves the batch. Always. #GTM #SalesOps #AItools #Outreach #Temerarii

linkedinEveryone says add AI to go-to-market. Almost nobody says where it actually plugs in. Here is the map, given away. The old way: one templated email to ten thousand people and a reply rate that proved they noticed. The better way: 1. An agent reads each prospect's site and news, so the outreach knows who it is talking to. 2. Score every lead on real signals, so the team spends hours on the prospects most likely to close. 3. The agent drafts the first message; a human edits the one line that makes it sound like a person. 4. Every claim ties back to something true about them, so it never reads like a generated lie. 5. When they answer, the system tags intent and routes hot replies to a human now, not Monday. 6. Every touch writes itself back to the CRM, so the pipeline is the truth. 7. A person approves the batch before anything sends at scale. Automation without a brake is just spam faster. Track real conversations started, not emails fired into the void. Show us your motion and we will mark where AI earns its keep. temerarii.xyz

xAdd AI to outreach, sure. Where though? Agent reads the prospect Score on real signals Agent drafts, human edits one line Route hot replies now Log to the CRM A person approves before scale. temerarii.xyz

facebookEveryone says add AI to your outreach. Nobody says where it plugs in. Here is the map. An agent reads each prospect's site and news. You score leads on real signals. The agent drafts the first message and a human edits the line that makes it sound like a person. Every claim ties to something true. Hot replies route to a human now, and every touch logs to the CRM. A person still approves the batch, because automation without a brake is just spam faster. Show us your motion at temerarii.xyz.

threadsAdd AI to outreach, they say. Where though? Agent reads each prospect's site and news. Score leads on real signals. Agent drafts, a human edits the one line that sounds human. Ground every claim. Route hot replies now. Log to the CRM. A person approves before scale. Automation without a brake is spam faster.

pinterestWhere AI actually fits in go-to-market outreach: enrich each lead from their site and news, score on real signals, let an agent draft while a human edits one line, ground every claim, route hot replies fast, and log to the CRM. A plain AI sales playbook with a human approval gate.

blueskyAdd AI to outreach, they say. Where though? Agent reads each prospect. Score on real signals. Agent drafts, human edits one line. Route hot replies now. Log to the CRM. A person approves before scale. temerarii.xyz

youtubeWhere AI Actually Plugs Into Your Sales Outreach (The Full Map) Everyone says add AI to go-to-market. Almost nobody says where it actually plugs in. This video walks the whole motion and gives the method away. The old way was one templated email to ten thousand people and a reply rate that proved nobody noticed. The map: 1. An agent reads each prospect's site and news, so the outreach knows who it is talking to. 2. Score every lead on real signals, so the team spends its hours on the prospects most likely to close. 3. The agent drafts the first-touch message; a human edits the one line that makes it sound like a person. 4. Every claim ties back to something true about them, so it never reads like a generated lie. 5. When they answer, the system tags intent and routes hot replies to a human instantly. 6. Every touch writes itself back to the CRM, so the pipeline is the truth. 7. A person approves the batch before anything sends at scale. Track the metric that matters: real conversations started, not emails fired into the void. Automation without a brake is just spam faster. Show us your GTM motion and we will mark exactly where AI earns its keep. temerarii.xyz

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

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