Most founders don't have a content problem. They have a sourcing problem. They sit down to write, stare at the cursor, and try to invent something insightful — when the best content they could possibly publish was sitting in their inbox, their DMs, and their sales calls the whole time.
We call the fix the question log: a running record of every question a prospect, customer, or peer actually asks you. It's the single highest-leverage content system we set up with new clients, because it inverts the hard part. You're no longer manufacturing ideas from nothing. You're answering questions a real person already cared enough to ask.
This is not an idea bank — that's where you park your own thoughts. The question log captures the demand side: what your market is confused about, skeptical of, or stuck on. Different input, different output, and it tends to outperform because it's anchored to a real human's real friction.
Why questions beat ideas as raw material
Here's the math that makes this worth building. The average founder we work with generates maybe 2–3 usable post ideas a week from their own head before they hit a wall. The same founder fields 15–30 questions a week across sales calls, customer emails, DMs, and Slack communities without even noticing.
You're sitting on 5–10x more raw material than you're using. And question-sourced material converts better on two fronts:
- Relevance is pre-validated. If one prospect asked it, dozens are wondering it. You're not guessing what your audience cares about — they told you.
- The hook writes itself. A question is already a hook. "A founder asked me last week why his hero image gets clicks but no sales" is a stronger opening than anything you'd brainstorm cold.
The best part: questions reveal the gap between what you know and what your market knows. That gap is exactly where authority content lives.
What earns a slot in the log
Not every question is content. The log fills with junk if you log everything, so we use a simple filter. A question earns a slot when it's:
- Recurring — you've answered it more than once. Repetition is the market telling you it's a real pattern, not a one-off.
- Revealing — the question exposes a wrong assumption. "Don't I just need a prettier image?" is gold, because the answer reframes how they think.
- Specific — "how do I improve my listing" is too broad. "Why did my CVR drop after I added lifestyle images" is a post.
- Emotionally charged — questions asked with frustration, fear, or skepticism behind them. Those carry energy you can write into.
Skip the purely tactical "what's the pixel size for a hero image" stuff. That's an FAQ on your site, not a LinkedIn post. The log is for questions where the answer changes how someone thinks, not just what they do.
The capture rule: one destination, 30 seconds
A system you have to maintain will die. So the rule is brutal simplicity: one destination, captured within 30 seconds of the question being asked.
One note. One doc. One channel in your phone's notes app. It does not matter which — it matters that there is only one, and that adding to it takes less effort than ignoring it. The moment capture requires a decision ("which folder?") it stops happening.
When you log a question, write two things: the question in the asker's own words, and a one-line note on why they asked it — the assumption or fear underneath. That second line is what turns a question into a post later, because it gives you the angle, not just the topic.
Your four richest streams:
- Sales calls. Every objection is a question. "How is this different from what an agency would do?" is a post on positioning.
- Customer support / DMs. The confusion that drives a support ticket is confusion your whole market shares.
- Communities and Slack groups. Watch what people ask repeatedly in the spaces your buyers live in. You don't even have to be the one asked.
- The question behind the question. When someone asks "should I lower my price," the real question is usually "why isn't this converting." Log both.
Turning the log into posts
Once you've got 30–50 questions banked, the writing session changes completely. You don't open a blank page. You open the log, pick the question with the most energy behind it, and write the answer you'd give if that person were sitting across from you.
The structure almost always falls out naturally:
- Hook: the question itself, framed as a moment. "A $2M brand owner asked me this last week and the answer surprised him."
- Reframe: name the wrong assumption underneath the question.
- Answer: what's actually true, with a specific number or example.
- Close: a question back to the reader that pulls the same thread.
One good logged question often spawns three or four posts — the direct answer, the contrarian take on why people ask it wrong, a case study where you solved it, and a framework version. That's how a log of 50 questions becomes a quarter of content without a single brainstorm.
This is also why the question log feeds the rest of your content system. The questions that come up most become your content pillars. The sharpest answers become your signature frameworks. The log is the upstream source the whole machine draws from.
How it changes your numbers
We track this with clients, and the pattern is consistent. Founders running on a question log instead of cold brainstorming see:
- Faster production — writing time per post drops because the topic and angle are pre-loaded. A session that used to produce two drafts produces four.
- Higher comment rates — question-sourced posts pull more comments because readers recognize their own confusion in the post. They reply with "I've literally been wondering this."
- More inbound DMs — when you publicly answer the exact question a prospect was about to ask, you collapse their decision timeline. The post does the sales call's first 10 minutes for free.
No magic. Just better raw material feeding the same machine.
FAQ
Isn't this just an FAQ page? No. An FAQ answers tactical, settled questions on your site. The question log captures questions where the answer is a point of view, and routes them to content that builds authority, not just deflects support tickets.
How is this different from an idea bank? An idea bank holds your own thoughts and observations. The question log holds your market's — what they ask, doubt, and misunderstand. Idea banks can drift into navel-gazing. Question logs stay anchored to demand.
What if I'm not in many sales calls? Then mine communities, DMs, podcast comments, and your customers' support tickets. You don't have to be the one asked — you have to be the one paying attention to what your buyers ask anyone.
How big should the log get? Keep a working set of 30–50 live questions. Prune as you publish. A log that grows to 300 stale entries becomes an archive you never open. The point is a feed, not a museum.
If you're an ecommerce founder who knows you should be posting but keeps hitting the blank page, the problem usually isn't that you have nothing to say. It's that you're trying to invent instead of capture. We build the question log — and the system around it — so your content runs on what your market is already telling you. If that sounds like the missing piece, let's talk.