Copy the published post text
Ask the Operator
copy ready · render pending
Output-policy spec format · dimensions (asset_specs.output_policy)
formatnative cut · 9:16 · 1:1 · 16:9
dims1080×1920 · 1080×1080 · 1920×1080
cadence5/day floor × 9 channels
Channels 9 destinations
TikTokInstagramLinkedInX/TwitterFacebookThreadsPinterestBlueskyYouTube
This post a distinct social asset — its own angle, storyboard, and cuts
thread-ask-the-operator-W49-Tue
5-distinct-social/day · 9:16 master → 1:1 / 16:9 cuts per channel
Channel-cuts this asset → 9 native captions (one master · per-platform aspect+copy)
| Channel | Native caption |
|---|---|
| Tiktok | Outbound question: how many follow-ups before I'm just being annoying? It's not the count, it's the content. Rewrite each follow-up so it hands over something useful, not just a bump. Three is fine if each one gives. (AI-assisted) |
| Ask the operator. "Follow-ups feel spammy." It's not the count, it's the content. Three is fine if each one hands over something useful. Give in every send, don't just bump. #outbound #sales #coldemail #buildinpublic #followup | |
| Ask the operator. The question: how many follow-ups before I am just being annoying? It is not the count, it is the content. Three is fine when each one hands over something useful. Rewrite your follow-ups so every send gives the reader a reason to reply, not just a bump asking if they saw your last note. Value per send beats volume per week. | |
| X | "How many follow-ups before I'm annoying?" It's not the count, it's the content. Three is fine if each one hands over something useful instead of just a bump. temerarii.xyz |
| Ask the operator: how many follow-ups before you are just being annoying? It is not the count, it is the content. Three is fine if each one hands over something useful. Rewrite your follow-ups so every send gives the reader a reason to reply, not just a bump. More at temerarii.xyz. | |
| Threads | Ask the operator. "How many follow-ups before I'm just being annoying?" It's not the count, it's the content. Three is fine if each one hands over something useful. Rewrite your follow-ups so every send gives, instead of just bumping the thread. |
| Outbound sales tip: how many follow-ups are too many? It is not the count, it is the content. Three follow-ups can work fine if each one hands over something useful. Rewrite your sequence so every send gives the reader a reason to reply, instead of just bumping the thread to ask if they saw your last email. | |
| Bluesky | "How many follow-ups before I'm annoying?" It's not the count, it's the content. Three is fine if each one hands over something useful instead of just bumping the thread. |
| Youtube | Title: Ask the Operator: How Many Follow-Ups Before You're Annoying? The outbound question: how many follow-ups before I am just being annoying? It is not the count, it is the content. Three is fine when each one hands over something useful. Rewrite your follow-ups so every send gives the reader a reason to reply, not just a bump. More at temerarii.xyz. |
Composition layer × scene 5 scenes · this post's OWN storyboard (distinct per asset)
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 | matches intent shared field signature-3d | hook | 0–5.0s | kinetic-build | icon·wireframe | ♪ node_lock | Outbound question: how many follow-ups before I'm just being annoying? on-screen: "Follow-ups feel spammy" |
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→"Follow-ups feel spammy" | |||||||
| 2 |  first render · fix pending NumberedList templatedead_air | teach | 5.0–10.0s | kinetic-build | icon·wireframe | ♪ node_lock | It's not the count, it's the content. Three follow-ups are fine if each one hands over something useful to read. on-screen: Three, each with value |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Three, each with valuecurate items, nodes | |||||||
| 3 |  matches intent ComparisonTable template | proof | 10.0–15.0s | receipts-count | icon·wireframe | ♪ node_lock | Rewrite your follow-ups so each one hands over something useful, not just a bump. on-screen: Give in every send |
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape knotground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Give in every sendcurate colA, colB, rows, statsLabels | |||||||
| 4 |  first render · fix pending NodeGraphCard templatedead_airgeneric_scene | step | 15.0–20.0s | kinetic-build | icon·wireframe | ♪ node_lock | Ask the Operator |
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual pipelineshape knotground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Ask the Operatorcurate hub, nodes, stages, steps | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 20.0–25.0s | coalescence | icon·ember-fill | ♪ bed_out | Ask the Operator |
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Ask the Operator | |||||||