Copy the published post text
Field Notes
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-field-notes-W41-Sat
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 | Field note: your follow-up email was three paragraphs of pressure. The one-liner gets the reply. Cut it to one sentence that ends in an easy yes-or-no question. (AI-assisted) |
| Field note. Your follow-up was a wall of text. The one-liner gets the reply. Cut it to one sentence. End with an easy question. #sales #followup #coldemail #fieldnotes #temerarii | |
| Field note: your follow-up email was three paragraphs of pressure. The one-liner is what gets the reply. Legacy follow-ups restated the whole pitch, which gives the reader a wall of text and a reason to wait. The fix is small. Cut the next follow-up to one sentence that ends in an easy question, the kind someone can answer in a few seconds. Less to read, lower effort to respond, more replies. Shrink the ask. | |
| X | Field note: your follow-up was three paragraphs of pressure. The one-liner gets the reply. Cut it to one sentence ending in an easy question. temerarii.xyz |
| Field note from the trenches: your follow-up email was three paragraphs of pressure, and the one-liner is what actually gets the reply. Legacy follow-ups restate the whole pitch. Instead, cut your next one to a single sentence that ends in an easy question. Try it on your next send. More at temerarii.xyz. | |
| Threads | Field note: your follow-up email was three paragraphs of pressure. The one-liner gets the reply. Legacy follow-ups restated the whole pitch. Cut the next one to one sentence ending in an easy question. Less to read, more replies. |
| Sales follow-up tip: stop restating the whole pitch. A short one-line follow-up that ends in an easy question gets more replies than three paragraphs of pressure. How to shrink your next follow-up email and lower the effort to respond. | |
| Bluesky | Field note: your follow-up was three paragraphs of pressure. The one-liner gets the reply. Cut it to one sentence ending in an easy question. |
| Youtube | Title: Field Note: The One-Line Follow-Up That Gets Replies Your follow-up email was three paragraphs of pressure, and the one-liner is what gets the reply. Legacy follow-ups restate the whole pitch and hand the reader a wall of text. The fix: cut your next follow-up to a single sentence that ends in an easy question someone can answer in seconds. Less to read, lower effort to respond, more replies. |
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–6.3s | kinetic-build | icon·color | ♪ node_lock | Field note. Your follow-up email was three paragraphs of pressure. The one-liner gets the reply. on-screen: Your follow-up was a wall |
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→Your follow-up was a wall | |||||||
| 2 |  first render · fix pending NumberedList templatedead_air | teach | 6.3–11.3s | kinetic-build | icon·color | ♪ node_lock | Old follow-ups restated the whole pitch, so the reader hit a wall of text and a reason to wait. on-screen: One line, easy to answer |
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→One line, easy to answercurate items, nodes | |||||||
| 3 |  matches intent LogStream template | diff | 11.3–16.3s | crossfade-8f | icon·color | ♪ node_lock | Cut your next follow-up to one sentence that ends in an easy yes-or-no question they can answer in seconds. on-screen: Shrink your next follow-up |
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual codeshape dodecaground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Shrink your next follow-upcurate codeLines, rows | |||||||
| 4 |  first render · fix pending FlowSchematic templatedead_airgeneric_scene | proof | 16.3–21.3s | receipts-count | icon·color | ♪ node_lock | Field Notes |
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual receiptsshape dodecaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Field Notescurate stages, statsLabels | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 21.3–26.3s | coalescence | icon·3d-extrude | ♪ bed_out | Field Notes |
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Field Notes | |||||||