The Quiet Scribe — Handsfrom The Quiet Scribe
Your first AI worker
It's already running my own channel — not a demo, the actual posting.
Drop your files, let it run. If you don't like what comes out, reply and I'll refund the $7, no questions asked.
You finish the caption in one app. Now you open Instagram, scroll your camera roll to find the right image, paste the caption back in by hand, and set the time yourself. Tomorrow you do the same thing again, in a different app, for a different piece.
That's the whole reason this exists.
The missing piece is what happens after you've decided what to publish: opening the platform's own app, uploading it, pasting the caption back in, hitting publish, and checking it actually went live. Scribe Hands does that part — you tell it which piece, it handles the rest and confirms it worked.
Deciding what goes where and when, across a whole calendar, is a different job — more on that once you're in.
$7 to stop doing that part by hand.
It's been quietly running for a while now — not a rehearsal, the actual posting.
What happens, plainly: you tell Scribe Hands which finished piece to publish — a video, or an image with its caption. It handles the actual posting through your own account. A second command lets you independently confirm it's really live, rather than just trusting what the first one said. No opening the platform's own app, no re-typing what you already wrote.
Reliability
That's the real question underneath "does this actually work unattended" — and it deserves more than "it's been fine so far." Scribe Hands is built around two separate steps on purpose: one command publishes, a second, independent command checks. The second one doesn't ask the first command what it thinks happened — it makes its own live call to your account and looks at what's actually there.
Run that second check and if the two don't match, you'll know exactly that — instead of finding out three days later when you finally open the app yourself. That's the reason verification is its own separate command, not folded silently into "publish": a step that only ever tells you what it wants to be true isn't proof, it's just a louder guess.
The same two-step discipline is what's been running the actual account you saw above — not a demo account, the one currently posting.
Drop your files, let it run. If you don't like what comes out, reply and I'll refund the $7, no questions asked.
He finishes the post the same way he always has. He runs one command with the file's name — he doesn't open Instagram to upload it, paste the caption in again, and hit post.
Finish your piece — a video, or an image and its caption — and name the file.
Tell Scribe Hands which one to publish: one command, one file.
It posts through your own account. Run a second command whenever you want to independently confirm it's really live.
No new login. No dashboard to check. It runs on your own files, in your own accounts.
Scribe Hands currently runs on a Mac.
"Doesn't Metricool already connect to my Drive?"
Connecting to your Drive gets you file access — it doesn't get you publishing. You still open Metricool's own dashboard, browse to the piece, write or confirm the caption there, and click schedule — one dashboard visit per post, every time. Scribe Hands removes that step entirely: finish the piece, then tell it which one to publish. One command, one named file, done — no dashboard in between.
That's a real thing to hand over without a way to check it worked, which is why Scribe Hands doesn't stop at "it should be live." Run a second, separate command and it makes its own live call against your account, not a repeat of what the first command already claimed. Metricool's dashboard shows what it thinks got scheduled. Scribe Hands shows what's actually live, checked independently.
Drop your files, let it run. If you don't like what comes out, reply and I'll refund the $7, no questions asked.
Vs. schedulers
Buffer, Hootsuite, Metricool — connect one, and here's the flow: finish the piece, export or upload it, open the dashboard, find it, confirm the caption, pick the platform, hit schedule. Repeat per piece, every time.
Finish the piece, name the file, tell Scribe Hands to publish it. That's the whole list.
We haven't found another tool that skips that middle step entirely — the dashboard visit is still there even in the tools built to make scheduling easier. Scribe Hands is built to remove the visit, not speed it up.
Skip the dashboard. Not just the wait.
$47 is what Scribe Hands is actually worth once it's finished being built in the open. It isn't finished yet — this is a founding beta, and founding beta access is $7.
That's not a discount on a finished product. It's early access to one still being shaped — which means founding buyers get more of me, not less: hands-on help getting set up, because you're helping me find what's actually confusing before anyone else hits it. Once that's solved, setup calls stop and it ships self-serve at $47.
No countdown. No "X spots left" ticker. The beta itself is the reason this price exists — not a promotion, a stage in getting built.
This is your first AI worker, not the whole toolkit. There's a wider team waiting behind it — what that unlocks gets explained once you're in, not priced here.
Drop your files, let it run. If you don't like what comes out, reply and I'll refund the $7, no questions asked.
The team behind it
It does one job: it publishes what you've already made. Once that's running, the next question answers itself — who makes what gets published? That's a different worker's job, waiting behind this one. Then another question comes after that one. Each of those is a job Scribe Hands doesn't try to do itself — that's not a gap, it's the reason a team is worth hiring one job at a time. More on what's behind it once you're in.
Drop your files, let it run. If you don't like what comes out, reply and I'll refund the $7, no questions asked.