Record a podcast.
Publish it from your pocket.
I speak into my phone, pick an image, and tap deploy. My automation blends the audio into an audiogram for YouTube, writes the title, the description and the show notes, uploads to the podcast network, then syndicates the episode everywhere. No computer, no editing, no upload screens. Just speak and ship.
A full episode published without ever touching a computer.
Most podcasters record, then disappear into hours of editing, exporting, uploading, and writing descriptions before anything goes live. That friction is why most podcasts quit by episode ten. I do it differently. I speak into my phone, tap a button, pick an image, and tap deploy. My automation builds the audiogram, writes the title and the show notes, uploads the episode, and syndicates it everywhere. An episode that used to eat three hours now takes a few taps. Here is who it is for, what goes wrong without it, how it works, and what you get back.
Who it’s for
Creators, coaches, and solo founders who want a podcast but dread the production work. Especially useful if you have ideas while walking, driving, or away from your desk and lose them because recording feels like a chore. If you want to publish your voice on a schedule without living in editing software, this is for you.
What goes wrong
Recording is the easy part. The editing, the audiogram, the upload, the description, the show notes, and the promotion are what kill momentum. Most people skip a week, then a month, then quit. The production work, not the talking, is what stops a podcast from ever becoming consistent.
How the machine works
I record by speaking into my phone. A form asks the topic, the image, and any links. I pick the image and tap deploy. The automation blends my audio with the image into an audiogram for YouTube, writes the title, the description, and the show notes, uploads, and syndicates. I speak and select, the machine does the rest.
What you get back
Roughly three hours back per episode. At two episodes a week that is about six hours a week, around 300 hours a year. That recovered time plus the consistency it unlocks compounds the audience over years. The time you save is the asset, and consistency turns it into reach and revenue.
I quit my own podcast twice before I automated the boring part.
For years I treated a podcast like a production. Record, then sit at a computer for hours editing, exporting, building a video, uploading to YouTube, writing the description, writing the show notes for Spotify and Apple, then setting up the promotion. The recording took twenty minutes. The rest took most of an afternoon. So I skipped weeks, then quit, twice.
The problem was never the talking. I love talking about this stuff. The problem was every single step after I stopped recording. Each one was a small friction, and stacked together they were enough to make me put it off, then forget, then give up. That is not a content problem. That is a production problem, and production is exactly what a machine should handle.
So I wired my phone into an automation in the cloud. Now I record the episode directly speaking into the microphone of my phone, wherever I am. At the end I press a button, a form asks the topic, the image, and any links, I pick an image from my camera roll, and I tap deploy. Everything after that runs without me. The audio gets blended with the image into an audiogram, because YouTube only accepts video, so a still picture with a moving sound wave becomes a clip YouTube will show.
From the topic, the automation generates the title, the YouTube description, and the show notes for Spotify and Apple, plus extras like a poll. It uploads to the podcast network, and from there the episode gets syndicated to a bunch of other networks automatically. Then a second automation kicks in later that grabs the episode, creates a blog post, sends an email to my list, and makes social content to promote it. One recording, published and promoted everywhere, from my pocket.
The numbers are modest by design and honest. A full episode used to cost me roughly two to three hours of work after recording. This collapses it to a few taps, saving about three hours an episode. At two episodes a week that is around six hours a week, roughly 300 hours a year I get back. That is the money maker, because consistent publishing compounds an audience that buys what I sell. Proof point: I have documented my actual numbers on YouTube in 28 Income Streams Revealed on YouTube and in A Day In My Life, both checkable, so the modest figures on this page read as real.
Three moves that turn one spoken recording into a published episode everywhere
What made this work was treating recording as the only human step and pushing everything else onto a machine. A podcast is not one task, it is a dozen small ones, and only the first one needs me. The framework hangs on three moves: speak the episode straight into the phone, hand the machine the topic and the image, then let it build, publish, and promote without me touching a computer.
Speak it, do not produce it
The only step that needs me is the talking. I connect my phone to the cloud and record the episode directly into the microphone, wherever and whenever the idea hits. No mixing desk, no studio, no laptop. The recording is raw and that is fine, because the machine handles the polish. Removing the production burden from the human is the entire point. If recording feels as light as leaving a voice note, you will actually do it every week, and weekly is what builds an audience.
Hand off the topic and the image
When I finish, I press a button and a short form asks three things: the topic of the episode, the image I want to use, and any links. I pick the image straight from my phone and tap deploy. Those three inputs are everything the machine needs. The topic drives the title, the description, and the show notes. The image becomes the face of the audiogram. The links go into the right places. Three quick choices, then I am done, and the rest happens in the cloud.
Let the machine build, publish, and syndicate
From there the automation blends the audio and the image into an audiogram for YouTube, writes the title, the description, and the show notes for Spotify and Apple, then uploads to the podcast network. The network syndicates the episode to a bunch of other apps. Later, a second automation turns the episode into a blog post, an email, and social posts. This is where it compounds. One recording becomes a video, a podcast everywhere, a blog post, an email, and a batch of social content, all without me.
Once those three moves are in place, a full episode goes from a spoken recording to published and promoted everywhere with no computer in sight. Speak, select, deploy, done.
Before the pocket studio
- Record, then lose an afternoon to editing and exporting
- Build a video by hand because YouTube will not accept audio
- Write the description and show notes from scratch every time
- Skip weeks when the production work piled up, then quit
- Promotion never happened because there was no energy left
After the pocket studio
- Speak into the phone, pick an image, tap deploy, done
- Audiogram built automatically so YouTube accepts the clip
- Title, description, and show notes written from the topic
- Uploaded, syndicated, and promoted without a computer
- ~3 hours saved per episode, ~300 hours a year recovered
Prompt 1: turn a topic into the title, description, and show notes
Once the episode is recorded, the machine needs to write everything around it from the topic. Use this prompt to turn a one-line topic and the words you actually said into a title, a YouTube description, and show notes for Spotify and Apple.
Episode metadata writer
Act as a podcast producer. I just recorded an episode by speaking into my phone. I will give you the topic and the rough transcript. Write everything that wraps the episode for publishing. Episode topic in one line: [paste]. Rough transcript or key points: [paste what I said]. My podcast name and usual tone: [name + 3 tone words]. Any links to include: [paste]. Produce, clearly labelled: one episode title under 60 characters that makes someone want to press play, a YouTube description of 4 to 6 short paragraphs with the links placed naturally, and show notes for Spotify and Apple in 5 to 8 bullet points covering the key moments. Do not invent facts or claims that are not in the transcript. Keep it in plain spoken English, first person, no hype words.
This is the writing the machine does the moment I tap deploy. One topic in, the title and the notes for every platform come out, all from the words I already said.
Prompt 2: plan the audiogram so YouTube accepts the audio
YouTube only accepts video, so the audio has to become a clip. Use this prompt to plan the audiogram, the still image with a moving sound wave, and the title card that goes on top of it.
Audiogram plan builder
Act as a video production assistant. I have an audio episode and one still image I picked from my phone. I need to turn the audio into a video for YouTube, because YouTube does not accept raw audio. The video is an audiogram: my chosen image with an animated sound wave on top. Episode title: [paste]. Image description: [describe the picture I picked]. Episode length in minutes: [paste]. Give me a clear plan for the audiogram: where the waveform sits so it does not cover important parts of the image, what the title card text should say and where it goes, a safe colour for the waveform that reads on my image, and the export settings for a clean YouTube upload. Keep it simple enough to run automatically every episode with no manual tweaking.
The audiogram is what makes one recording work on both the video platforms and the audio platforms. Plan it once, and the machine repeats it on every episode without me.
The 3-minute overview of how this works
Before the build steps, watch this short overview. It’s the exact video from the Automations Made Easy page, and it walks through the mechanics behind machines like this one. 1,000+ students have used these mechanics to save two hours a day, with zero coding.
Want to learn the mechanics behind automations like this?
I teach the same mechanics that make this pocket podcast machine work inside Automations Made Easy. 1,000+ students have used these mechanics to save two hours a day and publish more without living in editing software. No coding required.
Week one: one episode published from your pocket, and an afternoon you forgot you could get back.
Most people quit a system like this in the first week because the first episode feels too easy. There is no big production, no editing marathon, no sense that you earned it. The first week of the pocket studio is meant to feel light. The point is to confirm the recording uploads cleanly, the audiogram builds, the notes read well, and the episode lands on every platform without you opening a laptop.
Week one looks like this. You record an episode by speaking into your phone. You press the button, pick an image, add any links, and tap deploy. The machine builds the audiogram, writes the title and the show notes, uploads to YouTube and the podcast network, and syndicates it everywhere. The afternoon you would have spent editing and uploading is suddenly free. That is roughly three hours you got back on a single episode, and you barely noticed it happen.
The point of the first week is not a download spike or a viral clip. The point is to prove the loop closes: you speak, the machine builds the audiogram, writes the notes, uploads, syndicates, and the second automation turns it into a blog post, an email, and social posts. One recording, published and promoted everywhere, with no computer touched.
From there the maths is simple. Roughly three hours saved per episode across two episodes a week is about six hours a week, around 300 hours a year you get back. After a few months of weekly publishing the audience starts to compound, because a podcast that never misses a week is the one people come to trust. That trust is what turns into clicks on your offers and your income streams.
All of this runs while you build the next product, take a holiday, or sleep. The machine does not care where you are. You speak the episode, pick an image, tap deploy, and the cloud handles the audiogram, the notes, the upload, the syndication, and the promotion.
Prompt 3: generate the social posts that promote the new episode
After the episode publishes, the second automation promotes it. Use this prompt to turn the episode into a batch of social posts for different platforms, all from the topic and the link.
Episode promo post writer
Act as a social media writer. A new podcast episode of mine just went live. I want a batch of promo posts that drive people to listen, written from the episode topic and a few quotes. Episode title: [paste]. Episode topic in one line: [paste]. Two or three strong lines I said in the episode: [paste]. Link to the episode: [paste]. Write, clearly labelled: one short post for X under 280 characters, one post for LinkedIn of 3 to 5 short paragraphs, one Instagram caption with a hook in the first line, and three single-line hooks I could use over a clip. Make each one feel native to its platform, first person, plain spoken English, no hype words, no fake urgency. End each with a natural nudge to listen, not a hard sell.
This is the promotion the second automation runs after the episode is live. One episode becomes a week of social content without me writing a single post by hand.
Prompt 4: draft the blog post and email from the episode
The same recording should become a blog post and an email to the list. Use this prompt to turn the episode into a written article and a short broadcast email, both pointing back to the episode.
Episode to blog and email writer
Act as a content writer. I want to repurpose a podcast episode into a blog post and an email to my list, both from the same recording. Episode title: [paste]. Episode topic in one line: [paste]. Rough transcript or key points: [paste]. Link to the episode: [paste]. Produce two pieces, clearly labelled. First, a blog post of 600 to 900 words that captures the episode as a readable article with a clear opening, two or three subheadings, and a short closing that links to the episode. Second, a broadcast email of 150 to 220 words, first person, plain spoken English, that tells my list the episode is out, gives them one reason to listen, and links to it. No hype words, no fake urgency, just a clear and friendly nudge.
This is how one recording becomes a documented blog post and a list email at the same time. The episode is written down, searchable, and sent, all without me opening a blank page.
The exact build, step by step
Connect your phone to the cloud and record
The first job is to make recording feel like leaving a voice note. Connect your phone to your automation in the cloud so the microphone feeds straight into it. Now you can record a full episode by speaking into your phone wherever you are, on a walk, in the car, on a park bench. There is no studio, no mixing desk, no laptop. The recording is raw, and that is fine, because every step after this is handled by the machine.
Tap the button and fill the three-field form
When you finish talking, press one button. A short form appears and asks three things: the topic of the episode, the image you want to use, and any links. Pick the image straight from your camera roll. Type the topic in one line. Drop in any links. Then tap deploy. Those three inputs are everything the machine needs to build and publish the whole episode. This is the last moment a human is involved.
The machine blends the audio and image into an audiogram
YouTube only accepts video, not raw audio, so the automation turns your recording into a clip. It takes the image you picked and the audio you recorded and blends them into an audiogram, a picture with a moving sound wave on top. The waveform sits where it does not cover the important part of the image, a title card goes on, and the clip exports ready for YouTube. This is the step that lets one recording live on the video platforms too.
The automation writes the title, description, and show notes
Working from the topic you gave it and the words you actually said, the machine writes the title, the YouTube description, and the show notes for Spotify and Apple. It also drafts extras like a poll. Because the writing rules never change, the output is consistent episode after episode. You can skim it before it ships if you want, but most of the time you can let it go live. This is the step that used to eat the most time by hand.
Upload and syndicate to every network
The machine uploads the audiogram to YouTube and the audio to the podcast network. Once the episode lands on the network, it gets syndicated to a bunch of other networks automatically, so it shows up on Spotify, Apple, and every major podcast app without you submitting anywhere by hand. This is the step that used to mean a dozen separate upload screens. Now it is one deploy, and the episode appears everywhere on its own.
A second automation repurposes and promotes it
Later, a second automation grabs the published episode and does the promotion. It turns the episode into a blog post, sends an email to your list, and creates social media content to push people to listen. It also documents the episode so it is searchable. You spoke once, and that one recording became a YouTube video, a podcast on every app, a blog post, an email, and a batch of social posts. The machine did all the publishing and the promotion.
Spoken into the phone
You record a full episode by speaking into your phone, connected to the cloud, wherever the idea hits.
Topic and image handed off
One button, a three-field form for the topic, the image, and any links, then a single tap on deploy.
Built and published
The machine builds the audiogram, writes the title and notes, uploads to YouTube and the podcast network, and syndicates everywhere.
Repurposed and promoted
A second automation turns the episode into a blog post, an email, and social posts, and documents it.
Build this pocket podcast machine inside the same playbook 1,000+ students use
Automations Made Easy teaches the mechanics behind machines like this one. Step by step, no code, plain English. Publish a full episode from your phone and let the cloud handle the audiogram, the notes, the upload, and the promotion.
The six months after I switched it on
Here is the shape of the first six months after I switched the pocket studio on for my own podcast. The line ramps up modestly, because what compounds is consistency, and an audience takes a few months of never missing a week before it starts to grow on its own.
Hours saved per month, after switching on
Three things matter on this chart. The hours saved settle around 25 a month and stay there. Those are hours I spend building the next thing instead of editing. And every single one of those months I published every week, which is the consistency that quietly compounds the audience over years.
What other students built
I teach the simple skills behind machines like this in Automations Made Easy. Students who built their own version sent back what changed in their first month.
“I had recorded six episodes and published zero because the editing scared me. I built the pocket version in a weekend. Last week I published three episodes from my phone, walking the dog. I still cannot believe it.”
“The audiogram step is the one I never could have done by hand. Now my voice notes show up as proper YouTube videos with a waveform and a title card. My subscribers think I hired an editor.”
“What sold me was the second automation. One recording becomes a blog post, an email, and a stack of social posts. I went from one channel to five without writing a single extra word myself.”
“I always quit podcasts around episode eight. This is the first one I have kept going past thirty. Removing the production work was the whole difference. I just speak and tap deploy now.”
What’s inside Automations Made Easy
AME isn’t a library of pre-built automations. Every business is slightly different. What’s reusable across all of them is the underlying mechanics: how to set up little machines that listen, write, and follow up while you sleep, and how to wire the pieces together without writing code.
The program walks you through six modules: The Right Tools (the cost-effective, no-code stack I actually use), Task Selection Mastery (which automations are worth building first), Design Secrets (mapping an automation before you build it), Zero to Hero (complete beginner to confident automator), Real-World Application (we build a full automation together, end to end), and Monetization Mastery (turn the skill into a side-business).
It also includes done-for-you templates you import in two clicks, over-the-shoulder training videos, and the same playbook 1,000+ students have used to save two hours a day. No coding required. If you can copy and paste, you can build this.
The pocket studio: common questions
Pulled from what readers and Automations Made Easy students ask most.
Do I really never touch a computer with this?
That is the whole point. I record by speaking into the microphone on my phone, then I tap a button. A short form asks me the topic, the image I want, and any links. I pick the image from my camera roll, then I tap deploy. Everything after that runs in the cloud with no laptop involved. The audiogram gets built, the show notes get written, the episode gets uploaded and syndicated, all from my pocket. I can publish a full episode from a park bench or from bed.
What is an audiogram and why do I need one?
An audiogram is a still image with a moving sound wave on top, so audio can be posted as a video. YouTube only accepts video, not raw audio, so the automation blends my recorded audio with the image I picked and animates a waveform across it. That turns a voice recording into a clip YouTube will accept and show. The same audio also goes to the podcast network as audio, so one recording covers both the video platforms and the audio platforms without me editing anything.
Will the title and show notes actually be good if a bot writes them?
They are good because the automation works from the topic I give it and the words I actually said in the episode. It generates the title, the YouTube description, and the show notes for Spotify and Apple based on that. It also drafts extras like a poll. I skim them before they go live if I want, but most of the time I let them ship. The writing is consistent because the rules behind it never change, and consistency is what an audience rewards over time.
How much time does this actually save per episode?
A full episode normally costs me roughly two to three hours of editing, building the video, uploading, writing the description, writing the show notes, and setting up the promotion. This collapses all of that into a few taps on my phone, saving about three hours an episode. At two episodes a week that is around six hours a week, which is roughly 300 hours a year I get back. That recovered time is the real money maker, because it is time I spend building the next thing.
What happens after the episode is published?
Once the episode lands on the podcast network it gets syndicated to a bunch of other networks automatically. Then a second automation kicks in later that grabs the published episode, turns it into a blog post, sends an email to my list, and creates social media content to promote it. So one recording becomes a YouTube video, a podcast on every major app, a blog post, an email, and a batch of social posts. I did the speaking. The machine did the publishing and the promotion.
Does publishing this consistently actually make money?
It does, but slowly and through consistency rather than one big spike. A podcast that publishes every single week for years builds an audience that trusts you, and that audience buys what you sell and clicks the income streams you mention. I have documented my actual numbers on YouTube, so the modest figures here are real, not hype. The automation does not magically create demand. It removes the friction that makes most people quit publishing, and consistent publishing is what compounds into reach and revenue.
More Money Makers like this one
Built from the same handful of mechanics. These three are the downstream automations that kick in later, after the episode is published.
Run this pocket podcast machine yourself, or learn the mechanics inside Automations Made Easy.
If you want to learn the mechanics behind automations like this and build your own at home, Automations Made Easy is the playbook. Step by step, no code, plain English. If you want to talk through how to wire your own phone-to-podcast flow first, I take a small number of consulting clients each month.
€497 one-time · Lifetime access · 1,000+ students
