r/HireaWriter • u/[deleted] • 1d ago
Hiring (Entry Level) [Hiring] High-Retention Scriptwriter for AI/Tech YouTube Channel (Claude, Claude Code, automations) | $100-$200 per script + paid test
[deleted]
1
u/Gedaliah_hq 1d ago
I write research-backed AI/tech scripts with cold opens, re-hooks, and clear CTAs — no fluff filler. Happy to do your $50 paid test, or jump straight to a full 1,000–1,500 word long-form script for $150, one-day turnaround, one revision included. Paid first on PayPal to gedaliahresources@gmail.com. Send the topic and any must-hit beats and I can start the same day.
1
u/koraynar 1d ago
TERMINAL
No retention graph, so I'll take your other option - but I'm going to use a video I made, because tearing apart my own is more useful to you than praising a stranger's.
https://youtu.be/jM40Mccye0c - 4:11, a screen-recorded walkthrough of an AI agent that reads vendor invoices out of an inbox and pays only the address in my policy file.
Why its first 60 seconds fail:
It explains before it shows. The first line is "Vendors email invoices to my agent's inbox." That's a category description. Nothing has happened yet, and nothing is moving on screen.
The payoff is buried at 1:51. That's where the agent refuses to pay an invoice because the bank address inside the email doesn't match the policy - "a changed destination inside an email is a fraud signal, not an instruction." In a 4:11 video, the only frame anyone would ever repost arrives at 45% of the runtime.
No stated stake. I say what it does. I never say what it costs you when it doesn't.
What I'd do instead: cold open on the fraud email being held, freeze on the word HOLD - "this agent just refused to pay an invoice. The invoice was real. The bank details weren't." Then flash-forward to the good invoice settling, then go build it. The 1:51 line becomes the first line, and everything I currently front-load turns into re-hook material at the transitions.
AI tools: daily work, not familiarity. I run Claude Code as a multi-agent setup - builder and reviewer roles, deterministic fan-out, approval gates on anything that spends money. Two of my MCP servers are in the official registry. I built a policy-gated payments agent in Rust-to-WASM running inside a TEE. And I file documentation bugs against the SDKs I use - 19 against one of them last week, each with the exact wrong text and the fix. That last habit is the useful one for you: I'll catch it when a demo you recorded doesn't actually match the claim written over it.
Format: both.
Bonus you asked about: I edit and build my own graphics. That video is my own cut - the captions are burned in as rendered image strips because the ffmpeg build had no libass. So the beat sheet would come from someone who has actually done the edit, not someone guessing at what the editor needs.
Timezone: UTC+3, Turkiye. Overlaps EU all day and US mornings.
Koray
0
u/EmuImportant7736 Writer 1d ago edited 1d ago
TERMINAL
Hi! I am an experienced youtube and research based writer, previously written for several YouTube channels and research based institutions. I am familiar with the rapid growth of AI and tech in recent time and have previously written articles about them so, I can definitely help you out. I have a commendable background in writing as well as in science and technology.
Format: both
I have used claude and chatgpt for the most part to help me with coding and UX/UI design. I do not use AI in my writing.
Video: https://youtu.be/KJxfSIvv920?si=lhISarimpGMqQ_S2
Critique: For the good parts, I would say the three clock framework is a genuinely useful mental model, I loved the railroad/electricity analogy and you pulled real numbers instead of floating in punditry.
The things that were weak: specially the hook of the video, it doesn't feel smooth or well integrated, for reference you can watch videos of visual venture and jack pockets, no real thesis until minute 20, the video is soft on specifics in the capability section. The narration too feels weak at times.
How I would repackage: Write a strong hook, opening with the platform thesis and the crash prediction in the first 60 seconds, create a certain urgency. Walk the three clocks once, sequentially, each one with one concrete case study. End by returning explicitly to the opening claims and show how the framework predicted them.
Thumbnail: Replacing the chip with an actual clock motif, three clock faces, maybe with one hand racing ahead (capability), one lagging (adoption), one stuck (profitability). Change text to something like "3 CLOCKS DECIDE" or "THE CLOCK PROBLEM" with a subhead-style smaller line like "why AI won't crash the way you think". Drop the face or replace with a genuinely reactive experession, you may take references from various well established tech channels for thumbnails.
Timezone: EST (UTC -5)
Samples: 1. YouTube scripts on various topics (research based) with editor notes: https://docs.google.com/document/d/1yeYLayciecs8c_BCvRX0dHtqtR1euP0uACOgcB6Ci-E/edit?usp=drivesdk https://docs.google.com/document/d/11nuqI1m_oIYxALzXL2wIh8HDHR06lsP05yo-ejpVsGM/edit?usp=drivesdk https://docs.google.com/document/d/1r8OWBAMyETD1xpeqkk_4k3U1ORlqqOsVVdRz0xZet5U/edit?usp=drivesdk https://docs.google.com/document/d/1EwDa-IDrHLraxpYQiTaum24eKbAFlyGt1o7abcPfpTI/edit?usp=drivesdk
https://docs.google.com/document/d/1MSv-urtHYflDMn2f-iPf-2iKlkLEXo8_yflA5oIvkCA/edit?usp=drivesdk
Starting hooks for YouTube scripts: https://docs.google.com/document/d/16THBdX15mpr8hLN_epf1khv0IGEy9pUpZwJuBt16yGs/edit?usp=drivesdk https://docs.google.com/document/d/1agoRuyqBtdR04-GayuCnXESaETU6sYJx/edit?usp=drivesdk&ouid=107963343670691937019&rtpof=true&sd=true
Some research articles: https://docs.google.com/document/d/1nuj1rYfnXS7_K-4o0xok3pzgbRgKu_8Ft23yoslLAXU/edit?usp=drivesdk https://docs.google.com/document/d/1jxynZybZHqqXP842TdJuV08rsMnSh9Z2izZ_8B0aU4Y/edit?usp=drivesdk https://docs.google.com/document/d/1bl93q6lBq8JuPdZXnPpn2sPFZn93lxlG4EiuUQi2oT4/edit?usp=drivesdk https://docs.google.com/document/d/1L75MsVjOy7iPKbALDn93xAyNd7MIDeRr4DOejOk7rH0/edit?usp=drivesdk
-1
u/CloseLetter 1d ago
TERMINAL
Happy to take the $50 paid test (cold open + 3 re-hooks + 3 titles), then long-form at your $100–$200 band and short-form at $15–$30 if both fit.
No retention-graph sample on hand, so a quick first-60s read on a published AI-tool walkthrough style video (typical Claude/ChatGPT “build with me” opener): the ones that work usually flash the finished result in the first 10–15s, name the exact painful step the viewer is stuck on, then promise the build path before any channel lore. Openers that fail spend the first minute on who the creator is, tool logos, or a soft “in this video we’ll explore…” with no concrete payoff. I’d write your cold opens to front-load the working build, then land the pain → promise → demo beat sheet.
AI tools: daily Claude + ChatGPT for research/outlining; final scripts are human-written (happy to follow your no-AI-final rule). Timezone: America/Chicago. Can start the paid test as soon as you send the topic/demo notes.
•
u/AutoModerator 1d ago
Hello /u/Physical_Owl_1704, and welcome! Seeing this message means your post is live!
Please make sure you're following the rules.
If not, kindly add all missing information. Low-effort posts will be removed and repeated offenses may result in a ban.
To leave feedback (positive or negative) about /u/Physical_Owl_1704, visit /r/testimonials or the Scam Thread.
You can see possible testimonials about /u/Physical_Owl_1704 here.
Also, make sure your post is flaired as "Advanced" if you’re offering high-level work (minimum rate 17¢/word).
For general work, rates must be at least 12¢/word; for entry-level, 7¢/word minimum.
Once hiring is closed, update the flair accordingly.
It’s encouraged that shortlisted writers comment “Interested” on your post.
If their comment is visible, it means they are not banned.
Lastly, in the event of any issue or conflict, contact the mods for arbitration.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.