This article is the seven questions, with the reasoning behind each one. Use them on yourself with a recorder running, or use them as a script for any founder interview. Either way, they're built to do one job: pull a founder past their rehearsed answers and into the specific, unedited version of their thinking.
Most founders have stories. They cannot see them. The Tuesday sales call that rewrote the pitch. The hire that went sideways in week three. The customer who said something in a renewal meeting that changed the roadmap. The material is there. What's missing is a way to surface it on demand.
This is an extraction problem, not a writing problem. The seven questions are a great starting spot.
Where did these questions come from?
I spent years in political communications, then later working with founders across a variety of startups. Pulling ideas and material out of leaders who are constantly context-switching is hard. When I could get them in a room, the answers often lacked the depth I needed to build a content plan around.
The seven questions below have been through a lot of iterations. They are what I draw from when I start with a founder and want to understand their POV well enough to see the content angles.
What are the seven questions?
Each one is phrased as it gets asked, not as a topic. The phrasing moves the answer from a brand statement to a real observation.
1. Who is your ICP and what do they actually care about?
The question sounds basic. The word that matters is "actually." Most founders have a rehearsed ICP answer written for investors. The real answer, the one that contains content, lives one layer below. What does the buyer say on a Tuesday call when they drop their pitch voice. What are they actually trying to protect, prove, or avoid.
2. What is changing in your space that most people aren't paying attention to?
This question surfaces a founder's point of view on their market. Not the trend everyone is writing about, but the shift the founder notices from their seat that has not made it into the discourse yet. The best answers to this one usually start with "I've been noticing..." and get delivered at half the founder's normal speaking speed.
3. What is the hardest part of your stage right now?
Founders tend to answer this one with the real thing on the second or third attempt. The first answer is usually a version of what they would say in a board update. The second is closer. Whether you are doing this alone or with a content strategist, give it the time. The honest reflection lives past the canned response.
4. Tell me about the team around you. What makes them special?
Team stories are underused because founders worry they will read as self-congratulatory. They do not, if the specifics are there. The question surfaces a specific person, a specific decision, a specific moment when someone on the team did something the founder could not have done alone. Named examples. Real dates.
5. What is one thing you would do differently if starting over?
Hindsight is a content machine. Most founders have one or two regrets they have never written about because regret feels like weakness. In content, it reads as self-awareness, which is the scarcest signal in any founder feed.
6. What do most founders in your space get wrong?
A contrarian question, asked carefully. The answer has to be specific enough to be a real observation, not a sweeping dismissal of the category. The useful framing: a named assumption most founders in the space operate on that the founder disagrees with. That disagreement is a post.
7. How do you do things differently than competitors?
The question is about operational choice, not feature list. What does the founder's team do on a Tuesday that a competitor's team does not. What ritual, what principle, what tradeoff. This is where the company's actual personality comes out, which is usually the last thing a founder thinks to write about and one of the first things a buyer wants to see.
Why these seven questions?
Every founder story sits in one of four buckets: a pattern, a tension, a risk, or a belief. The seven questions are a covering set.
Questions 1 and 2 surface patterns: what the market is actually like, what is shifting underneath the official narrative.
Question 3 surfaces tension: the current pressure the founder is sitting with, which is where most unfiltered material lives.
Questions 4 and 5 surface risk: the team bet that paid off, the decision that did not.
Questions 6 and 7 surface belief: what the founder thinks the category gets wrong, and what they do about it.
Pattern. Tension. Risk. Belief. A call that covers all four produces five to ten story seeds, which is more than enough for a month of posts and a sales narrative that sounds like the founder.
What do you do with the answers?
The answers are raw material, not posts. Extraction is the first part. Shaping and deploying come next, and they are a different craft.
The practical workflow: record the call, pull the extractable moments into a running list, pull out moments that stand out. Step back and be critical: which ones are worth sharing as a clip. Which ones exist better as a quote and which ones should be expanded upon in a future call.
How do you try this on yourself?
Enlist another person, colleague, friend, spouse. It makes a difference.
If you try the seven on yourself, do it with a recorder running and a second person asking them. The founder cannot be both interviewer and interviewed at the same time. That is the point of why the framework exists.
Common questions.
What is a founder story framework?
A repeatable set of questions that pulls real stories out of a founder's week. DUO uses seven questions covering ICP, market change, current pressure, team, hindsight, category mistakes, and differentiation. The questions do the work the founder cannot do alone, which is seeing the material they are sitting on.
Why seven questions and not more?
Seven is the smallest set that covers the four categories a founder story usually lives in: pattern, tension, risk, and belief. Fewer questions and the surface area is too thin. More questions and the conversation stops feeling like a conversation and starts feeling like an interview.
How long does it take to get real stories out of these questions?
A single 60-minute call using the seven questions typically surfaces five to ten extractable stories. Not all of them become posts. The ones that do tend to come from the answers the founder did not expect to give, which is why the questions matter more than the agenda.
Can a founder use this framework on themselves?
Partially. It works better with a second person asking the questions because the founder is too close to their own material. If a content strategist or partner is not available, enlist a colleague, friend, or spouse to ask the questions while you record. Someone else hearing the answers in real time is what makes the difference.
What should a founder do with the answers?
Treat them as raw material, not posts. Pull the moments that stand out from the recording into a running list. Then step back and decide for each one: which deserves a clip, which works better as a quote, which should be expanded in a future call. Extraction is the first step. Shaping comes next.
