Most founders I talk to have stories. They cannot see them.
The problem with founder content is almost never a storytelling problem. The founder has lived through the thing that would make the post land. They remember the customer conversation, the hire that went sideways, the quarter that looked like it might end the company. What they lack is a way to pull those moments out on demand and recognize them as content.
This is an extraction problem, not a writing problem. A founder who cannot extract their own material ends up posting generic industry observations, because generic observations are the only thing available when the real material is still buried.
Where these questions came from
I spent years in political communications. The work before a speech, a debate, a media hit, was always the same. You sat with the principal and asked questions until they said something they had not planned to say. That one real answer was the thing you wrote around. Everything else was scaffolding.
Founder work is closer to political-comms discovery than most people realize. A founder, like a politician, spends most of their day inside a system of language they have built to function. The useful material sits in the layer underneath, where the actual observations, tensions, and changes of mind are unused. What politicians taught me about founder branding goes deeper on where this comes from.
The seven questions below are what I bring to a founder call. They pull someone out of their rehearsed pitch and into the specific, unedited version of their thinking.
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. The third sounds like a confession. That third answer is where stories live.
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 unlocks 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
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 to do with the answers
The answers are raw material, not posts. Extraction is the first verb. Shaping and deploying come next, and they are a different craft. Founder storytelling is extract, shape, deploy, in that order, and skipping any of them produces content that reads like it was written by someone who was not in the room.
The practical workflow: record the call, pull the extractable moments into a running list, tag each one with which of the four buckets it falls into, and prioritize based on what the audience cares about this month. Over a year, that list becomes the content bank. Over two years, it becomes the thing that makes the founder's brand defensible. The craft of founder storytelling covers the full arc.
A note on the framework
This is not the only way to pull stories out of a founder. It is the set of questions I have landed on after enough calls that the patterns are stable. They work because they assume the founder already has the material and the job is to help them see it.
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. The questions work better with a second person asking them because the founder is usually too close to their own material. The practical workaround is recording the answers, sending them to a writer or partner, and letting someone else flag the moments that are actually stories.
