
| Channel | Native caption |
|---|---|
| Tiktok | 100 personalized outbound emails sent. Zero written by hand. Mail-merge felt like spam because the same body went to everyone. Real method: research each contact, draft per person, send by API. Personal at scale. (AI-assisted) |
| 100 emails. 0 by hand. Mail-merge felt like spam. Same body, swapped name. Real move: research each contact, draft per person, send by API. Personal at scale. #outbound #sales #automation #AI #email | |
| Receipts: 100 personalized outbound emails sent, none of them written by hand. Mail-merge always felt like spam because the same body went to everyone with a name swapped in. People notice. The method: research each contact, draft a message per person, then send by API. That is outbound that is personal at scale, not a blast. We ran it on our own pipeline first. | |
| X | Receipts: 100 personalized outbound emails, 0 written by hand. Mail-merge felt like spam. Real move: research each contact, draft per person, send by API. Personal at scale. temerarii.xyz |
| Here are the receipts: 100 personalized outbound emails sent, none written by hand. Mail-merge always felt like spam because the same body went to everyone. The method is simpler than it sounds: research each contact, draft a message per person, send by API. See how at temerarii.xyz. | |
| Threads | 100 personalized outbound emails sent. None written by hand. Mail-merge felt like spam because the same body went to everyone with a name swapped in. The real move: research each contact, draft per person, then send by API. Outbound that is personal at scale, not a blast. |
| How to send personalized outbound emails at scale without mail-merge spam: research each contact, draft a unique message per person, then send by API. Receipts from sending 100 personalized cold emails with none written by hand. Outbound sales automation that stays personal. | |
| Bluesky | Receipts: 100 personalized outbound emails, 0 written by hand. Mail-merge felt like spam. Real move: research each contact, draft per person, send by API. Personal at scale. |
| Youtube | Title: 100 Personalized Outbound Emails, Zero Written by Hand Mail-merge always felt like spam because the same body went to everyone. We show the method we actually use: research each contact, draft a message per person, then send by API. That is outbound that stays personal at scale. Cold email, outbound sales, automation. temerarii.xyz. |
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 | ![]() matches intent KpiGrid template | stat | 0–5.1s | receipts-count | icon·liquid-chrome | ♪ node_lock | A hundred personalized outbound emails sent, none of them written by hand. on-screen: 100 emails. 0 by hand. |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape octaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→100 emails. 0 by hand.curate kpis, statsLabels | |||||||
| 2 | ![]() first render · fix pending RankList templatedead_air | proof | 5.1–10.1s | receipts-count | icon·white-knockout | ♪ node_lock | Mail-merge templates felt like spam, since the same body went to everyone with just a name swapped in. on-screen: Merge research + send. |
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape octaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Merge research + send.curate rows, statsLabels | |||||||
| 3 | ![]() matches intent StackTrace template | diff | 10.1–17.2s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Outbound of the future is personal at scale. Research each contact, draft per person, and send by API. on-screen: Personal at scale. |
expected on screen: red ground · a StackTrace panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StackTracevisual codeshape octaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Personal at scale.curate codeLines, errMsg, errType, fix, frames | |||||||
| 4 | ![]() first render · fix pending BlueprintGrid templatedead_airgeneric_scene | step | 17.2–22.2s | kinetic-build | icon·white-knockout | ♪ node_lock | Receipts |
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id BlueprintGridvisual pipelineshape octaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Receiptscurate rows, stages, steps | |||||||
| 5 | ![]() first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 22.2–27.2s | coalescence | icon·white-knockout | ♪ bed_out | Receipts |
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Receipts | |||||||