I Gave My AI Writer a 10-Minute Voice Note. It Handed Back a Tidied Transcript.

Build in Public · #20

I gave the Aha Studio writer a 10-minute voice note and got back a tidied transcript, wrong in 9 ways. The fix was a set of rules it follows every time, because whatever it writes for me is what customers get too. It also reminded me why I keep building tools for my own bottlenecks first: two of them came out of this week.

At one point, 23 of my blog drafts were waiting on one thing: me.

The research was done. The writing was done. The only thing missing was the My Take, the part where I add my own experience in my own words.

Here’s the thing… I can’t type properly. I spend as long fixing typos as I do typing. So anything that needs me to sit down and write becomes the bottleneck.

Talking is easy for me.

So this week I tested something: could the Aha Studio writer take a voice note, recorded off the top of my head with no structure at all, and turn it into a post I’d actually publish?

What I gave it

A 10-minute voice note on how to increase launch sales on WarriorPlus and JVZoo.

No outline. No order. Just everything I could think of: the funnel, the offer bump, affiliate contests, the buyers list, how I come up with product ideas, the lot.

I was hoping the AI would do what a good editor does. Find the hook. Write a proper intro. Put the points in an order that makes sense.

What came back: wrong in 9 ways

It came back as my voice note, tidied up into a list.

1. All 12 tips sat inside one list, so the table of contents in the sidebar had almost nothing to show.
2. No images. Not one.
3. It sounded like a careful consultant. “Here are a few ideas anyone can consider.” That’s not how I write.
4. “Affiliates” became “partners”. In this market, they’re affiliates.
5. Two tips said the same thing.
6. The FAQ was search filler. “What is an example of an affiliate?” Nothing to do with the voice note.
7. The hidden schema didn’t match the page.
8. No slug.
9. Half my points were missing. 11 things I said in the voice note were dropped or watered down, including the line I’d end the whole thing on: the money is in the list.

Was any single one of those a disaster? No.

Together, they made a post I couldn’t publish.

Why the fix had to be rules

I could have edited it myself in 20 minutes.

But this writer is going into Aha Studio. Whatever it produces for me is what a customer gets when they create their own content. If my own site wouldn’t publish it, a customer shouldn’t get it either.

So I wrote down what it should have done, as rules it follows every time:

• A voice note is raw material. List every point first. Find the hook. Write a real intro. Reorder. Then tick every point off at the end, so nothing gets lost.
• Write in the author’s written style. People talk differently from how they write. Strip the “okay” and the “kind of”, then write like the author’s own samples.
• Headings drive the table of contents. Every section is a proper heading, so the sidebar works.
• Images are part of the post, with the headline and the numbers baked into the image itself.
• Facts come from the source or the author’s profile. Nothing else. No made-up numbers, no experiences put in the author’s mouth.
• A My Take in every post, from the author’s own words, or a visible prompt asking them for it. Never invented.
• A self-check before saving, with the results reported back.

One thing I had to correct along the way: most customers won’t dictate anything. They’ll type a topic, run the SERP Gap analysis, and let the AI write. So dictation is optional. You can dictate your raw material, just your My Take, or nothing at all.

What came back the second time

Much better.

It opened on my own line: “3 sales in the bag before a buyer even reaches OTO2.”

8 sections in the sidebar. 7 images. A My Take. And the 12 ways became 17, because this time it kept far more of what I actually said.

Is it perfect? Not yet.

In a later test it wrote “I launch my own products on WarriorPlus, including Skribbly.” Skribbly is my daughter Stephanie’s product. So the rule about never putting experiences in the author’s mouth still needs more teeth. That’s the next fix.

The real fix is a tool I built for myself

All of this pointed me back at something I’d already started.

It’s called Speedwritr.

I had it built with Codex. It’s not finished (things got a bit confused when I wanted it on Railway instead of just Cloudflare), but the idea is simple:

1. You talk. A floating voice widget sits on top of any page, like a Google Doc, and transcribes as you speak. It can be a total brain dump.
2. The AI makes sense of it and maps out an outline.
3. You approve or edit the outline.
4. It writes the article with your My Take already baked in.
5. Then it keeps going: social posts for each platform, video scripts and more.

See what that does?

There’s no waiting for me to do a separate My Take, because the whole thing is my take. The experience and the expertise come straight from me. The content starts from what I actually know.

It’s a perfect candidate for Aha Studio.

And a second one, because people started talking back

Something good happened while I was heads-down. My blog posts and social posts started real two-way conversations. Comments, questions, DMs.

My new X account is at 111 followers (it was 100 on 3 October), and I’ve barely been in there the past few days because I’ve been building.

I don’t want to be rude to anyone. But when I’m in the middle of a launch (Stephanie’s last week, then the Aha Studio build), I don’t focus on much else, and messages were spread across four platforms.

So I built Social Inbox, a ChatGPT plugin that pulls all my messages, comments and chats from YouTube, Threads, X and Facebook into one place. More platforms get added as I get time, and I’ll probably rebuild it with Claude Code as a Railway app.

Same reason as Speedwritr. I needed it.

What else happened this week

• No wifi for 8 days. Two no-shows from the engineers. When they finally turned up, it took them 5 minutes to fix. I worked off a phone hotspot all week, which slowed everything down.
• So the Aha Studio build only really accelerated in the last two days, but we’re in good shape. Two new AI workers went in on 13 October, and Stephanie is testing every one of them in the background and sending over redesigns for the app.
• Aha Studio goes live on Wednesday 14 October at 9:05 PM Bangkok time, on a YouTube livestream, with six AI workers: Neighborhood Pages, Traffic Magnets, SEO Magnets, Site Sniper, BuildMyDirectory and Calculator Sites.
• Stephanie’s Skribbly launch closed at $12,077.45 from 386 sales. I wrote up what the Deal of the Day did for it and the funnel behind it.

My Take: The lesson this week is about building the stuff I need myself, to fix my own work bottlenecks. Speedwritr exists because I can’t type properly and my My Takes were holding up posts. Now I just record myself and brain dump what I know, and the AI organises it and writes the article. There’s no waiting on me for a separate My Take, because the whole thing is my take, coming straight from my own experience and expertise. Social Inbox exists because people started talking to me on four platforms while I was busy building, and I didn’t want to miss them. Every time I’ve fixed my own bottleneck first, I’ve ended up with a tool other people need too. Start with whatever is slowing you down this week.