Every question a customer or client emails me is my next video. I read it, answer it in about 30 seconds, and move on. I keep a running note where I capture questions as they arrive, batch record several answers in one sitting, and always strip out anything that would identify who asked. I never run out of ideas because my audience hands them to me daily.
I used to sit and brainstorm content ideas until the day I realized my inbox was already doing it for me. I'd open a blank note, stare at it, and try to invent a topic out of thin air, as if the well of ideas lived somewhere outside my business instead of directly inside it. Then one afternoon I scrolled back through the week's client emails and counted ten questions I had already half explained, one at a time, to real people who genuinely needed the answer. Ten videos, sitting in my inbox, waiting for me to notice them.
That realization changed how I think about content entirely. I stopped treating idea generation as a separate task I had to sit down and do. It happens automatically now, every time someone emails me a question, because the question itself is the idea.
Why your inbox is a content calendar in disguise
A blank page is intimidating because it asks you to guess what your audience wants to know. An inbox never asks you to guess. Someone already told you, in their own words, exactly what they're confused about or curious about or stuck on. That's not a content idea you invented; it's a content idea your audience handed you, which means it's already proven to matter to at least one real person, and almost always to many more who never bothered to ask.
Once I started seeing it this way, the pressure to "come up with something" disappeared. I don't need a content calendar built three months in advance from guesses. I need a system for noticing the ideas that are already arriving, one email at a time, and turning them into something my whole audience can use instead of just the one person who asked.
A simple system for capturing questions as they arrive
The whole system falls apart if you rely on memory. You will not remember the good question from Tuesday by the time Friday's batch-recording session rolls around; it will blend into everything else that came in that week. So I keep one running note, a single running list, not a folder scattered across apps, where every question worth answering gets captured the moment I see it.
When a client or customer emails something worth answering publicly, I copy the core of the question into that note right then, before I even finish replying to them directly. It takes fifteen seconds. I don't wait until later to decide if it's "good enough," because at this stage the goal is just capture, not curation. I sort through the list later, when I sit down to actually record.
I only copy the question itself into my running note, never my full email reply. The video answer should be written fresh for a camera, in spoken language, not read off a written response that was drafted for one specific person.
Turning one question into a 30-second answer video
The format stays the same every time, which is exactly why it's fast. I don't reinvent the structure for each video; I just plug in a new question. Three parts, in order, and then I stop talking.
The three-part structure
That's it. Restate, answer, tip. It fits comfortably into 30 seconds because it isn't trying to be a tutorial or a deep dive. It's trying to be the answer to one question, well delivered, and nothing more.
Batch recording: turning five questions into one sitting
Recording one 30-second video at a time is where this system would break down if I let it. Setting up the camera, checking the lighting, finding a quiet moment: that's the part that actually takes effort, not the talking. So I never record just one. When I sit down to film, I pull five or ten questions from my running note and go through them back to back, resetting only my answer between takes, not my whole setup.
One batch-recording session, done every so often instead of scrambling for a single idea every time I want to post, produces a stack of finished answer videos I can release over the following weeks. The setup cost happens once. The content comes out in bulk.
I didn't need a better imagination. I needed a better way to notice what my audience was already telling me.
Privacy first: never a real name without permission
This part isn't optional. I never use a real client's name, business name, or identifying detail in an answer video without their explicit permission. The whole point of this system is to make one person's question useful to everyone, not to put that person on display without asking.
In practice, that means every question gets reframed before it becomes a script. I strip out the business name, the specific numbers, and any detail that would let someone recognize who asked. I introduce it generically instead, something like "someone I work with recently asked me" or "a question that came in this week." The question stays exactly as useful to the viewer. The person who asked it stays private.
How this compounds into a real content library
A single 30-second answer video is a small thing. A few months of them, recorded consistently from a running note that never runs dry, is a different thing entirely. Each video answers a real question a real person had, which means each one is genuinely useful to anyone who has ever wondered the same thing and never bothered to ask.
Over time that stack becomes a library you can point people to instead of re-explaining the same thing over and over by hand. New questions keep arriving, so the library keeps growing on its own, without a single brainstorming session. It's the closest thing I've found to content that builds itself, because the raw material was never missing. It was just sitting in my inbox, waiting for me to look at it differently.
Key takeaways
- Every customer or client question is a video idea you did not have to invent; your inbox is a content calendar in disguise.
- Capture questions the moment they arrive in one running note, not from memory, so nothing gets lost by the time you sit down to record.
- Use the same three-part structure every time: restate the question, give the direct answer, close with one practical tip.
- Batch record five or ten answers in one sitting; the setup is the slow part, not the talking.
- Never use a real name or identifying detail without permission. Reframe every question in general terms first.
- Done consistently, this compounds into a real content library built entirely from questions your audience already asked you.
This is hack 18 in a series I never expected to keep going past thirty, because there's always one more piece of the day quietly worth automating. If you've ever stared at a blank content calendar wondering what to post next, check your inbox first. The next video is probably already sitting there, waiting for a 30-second answer.
Frequently Asked Questions
From your inbox. Every question a customer or client emails you is a video idea you did not have to invent. Instead of brainstorming topics from scratch, keep a running note or folder where you capture each question as it arrives, so you always have a stack of real, audience-tested ideas waiting instead of a blank page.
About 30 seconds is enough for one question. The structure is simple: restate the question so anyone watching knows exactly what is being answered, give the direct answer without padding, and close with one practical tip. Keeping it short is what makes the format repeatable; a 30-second video is easy to record and easy to watch.
Never use a real client's name or identifying details without their explicit permission. Strip out the business name, the specific situation, and any detail that would let someone identify who asked. Reframe the question in general terms, such as "someone I work with recently asked me," so the answer is genuinely useful to your audience without exposing the person who asked it.
Yes, and it is the most efficient way to do this. Pull five or ten questions from your running note, set up your camera and lighting once, and record all of them back to back. The setup is the part that takes time, not the talking, so batching turns a recurring chore into one short session instead of five separate interruptions to your week.
