Most of what gets called founder interviewing is really founder performance. The founder shows up in content mode, runs through the polished version of their talking points, and leaves. The interviewer got a transcript. The interviewer did not get stories.
Story extraction is a different activity. It runs on how you listen, not what you ask. The questions matter less than you think. The noticing matters more.
Here is how the call actually goes when it works.
The setup
Record everything. Video if you can, audio at minimum. Good mic, good file, transcribed afterward with speaker labels. You will miss things in the moment. The transcript is where the second pass happens.
Block ninety minutes, not sixty. The first twenty are throat-clearing. The founder shows up in performance mode, tells you the version they tell investors, and slowly thaws. The real material starts arriving around minute thirty, once they have stopped curating and started thinking out loud. A sixty-minute call produces thirty minutes of usable extraction at best. A ninety-minute call produces sixty.
The environment matters more than people admit. Zoom is fine. In person is better. Either way, remove the content framing. Do not start by telling them this is for LinkedIn, and do not open the laptop to take notes while they talk. The goal is a conversation, not an interview. The moment they feel interviewed, they go back to performing.
A good opening line is some version of "I want to understand how the business actually works right now. Tell me what is on your mind." Not "let's get some stories for posts."
The question stack
The first questions are wide on purpose. Narrow aggressively once you hear tension.
Four openers that consistently work:
- What has changed in the last ninety days that you did not see coming.
- Walk me through a sales call from the last month that stuck with you. Any call, good or bad.
- What decision are you sitting with right now that you keep going back and forth on.
- What is something a customer said recently that you keep thinking about.
Notice what these do. They ground the founder in the last ninety days, which keeps them in real detail instead of abstract lesson-land. They ask for one specific instance, not a summary. They open a door to a moment with stakes inside it.
The questions that do not work are the big thematic ones. What is your founder story. What is your biggest lesson as a CEO. What is your advice to other founders. Those produce rehearsed language. Rehearsed language does not contain stories.
Once you have a thread, stay on it. Most interviewers ask a good question, get a real answer, and then move to the next prepared question. Do not do that. A single good opener can carry the full ninety minutes if you keep pulling on it.
What to listen for
This is where the craft lives. You are listening for four specific signals.
The half-second hesitation. The founder is mid-sentence, pauses for a beat that is a little too long, and then keeps going in a slightly different direction. That pause is where a real moment got edited out in real time. Stop them. Ask what they almost said.
The "anyway" pivot. The founder gives a concrete detail, feels like it is too granular, and uses "anyway" or "long story short" as a bridge to skip forward. The detail they just skipped is usually the story. "So anyway, we eventually closed the deal" means they did not tell you what actually happened.
The "just" minimizer. "It was just a quick call." "It was just a small thing the customer said." "I just had a gut feeling." The word just is how founders flatten moments they think are too small to matter. Those are the moments that matter most. Minimizers are signal.
The specific detail mentioned once and abandoned. A name, a date, a number, an actual quote. The founder drops it into a summary and keeps moving. Mark it. Come back to it. "You mentioned the call with Sarah last Thursday. What did she actually say."
Four signals, all audible, all trainable. Miss them and the story walks out the door with the founder.
The wait, go back move
When you hear one of those signals, you have to interrupt. Most interviewers are too polite to interrupt and lose the moment. The trick is interrupting in a way that feels like interest rather than correction.
Short. Curious. Name the specific thing.
"Wait, go back to the call with the VP."
"Who said that, exactly."
"What did you do the next morning."
"Can you say more about the Tuesday meeting."
The founder will usually resist for half a sentence, then give you the real thing. The resistance is because they still think the specifics are too small. The pull-back is the move that tells them the specifics are what you are here for.
Founders open up more after a good interrupt, not less. The interrupt signals that you are actually listening, which changes the entire texture of the conversation. After two or three good interrupts, the founder starts self-correcting. They feel the "anyway" coming and stop themselves. That is when the call has shifted from interview to extraction.
What you do after the call
Do not draft anything for forty-eight hours. Let the session sit.
Then transcribe, and read the transcript as a listener, not a writer. Mark every moment that pulled your attention in real time and every moment that surprises you on the reread. A good ninety-minute call produces five to ten of these.
For each moment, write three lines: what happened, what was at stake, what shifted. If you cannot write all three, it is not a story yet. It is a fragment. Park it in a running doc, tagged by pillar and source, and keep moving.
Then decide what to draft first by a simple test. Which moment makes you want to tell someone else. Not the most strategic one, not the most on-brand one. The one with the pull. That pull is the same pull the reader will feel. Trust it.
Coda
The questions are almost interchangeable. The listening is not. A mediocre listener with great questions produces transcript. A great listener with basic questions produces stories. Spend the craft budget on the second one.
Related reading: story extraction: finding the stories inside your business, what founder storytelling actually is, and the pillar guide on founder storytelling.
Common questions.
How long should a founder story-extraction call be?
Ninety minutes is the floor. The first twenty are throat-clearing. The real material starts showing up around minute thirty, after the founder has stopped performing and started thinking out loud. A sixty-minute call produces thirty minutes of usable extraction at best.
What questions open the best founder stories?
Broad, grounded questions about the last ninety days work better than big thematic ones. What surprised you this quarter. What almost went wrong. What did a customer say that stuck with you. Avoid anything that sounds like an interview prompt from a podcast.
What are the audible signals a founder just skipped over a real story?
The half-second hesitation before a pivot. The word anyway used as a bridge. The minimizer just, as in it was just a small thing. A specific detail mentioned and abandoned. Any of these is the story you want. Stop them and go back.
How do you interrupt a founder without killing the conversation?
Short, curious interruptions that name the thing. Wait, go back to the call with the VP. Who said that exactly. What did you do the next morning. The interruption should feel like interest, not correction. Founders open up more after a good interrupt, not less.
