skip to content

In a short founder conversation, which diligence questions earn the slot over the others?

level: principalimportance: nice to knowfreq 30%

answer

  1. Cut before you walk in
  2. Two filters: exclusive, and decision-changing
  3. Open with the risk question
  4. Leave the last slot unallocated
  5. Two deep answers beat five shallow ones

basics

~20 s

Keep only questions that pass two tests: no one else in the loop can answer them, and the answer could change your decision. That usually leaves runway against the next milestone, who pays, and the risk the founder names themselves.

solid answer

~50 s

Rank by two filters. Can only an owner answer it, and would the answer actually change what you do? Runway against the next milestone passes both. Who pays and why competitors cannot copy it usually passes both. Deploy cadence, on-call and interview logistics fail the first filter; anything on the company's public pages fails it too. Then sequence rather than list: open with 'What keeps you up at night about this business?', because the answer often covers several of your items at once and tells you where to spend the rest of the time. Keep one question in reserve to follow whatever they open. The hardest part is deciding what to drop — most candidates carry too many questions and end up with a shallow pass over all of them instead of two answers they can actually reason with.

go deeper

for a junior

Prepare more questions than you can ask, then pick two before you walk in. Make one of them about how long the company is funded for, and leave room to follow whatever the founder actually says.

for a middle

Be able to justify each question by who else could have answered it. Routing process questions to engineers and pay-band questions to the recruiter is what frees the slot for anything worth asking an owner.

for a senior

Show that you re-plan live: when one answer partly resolves two of your items, spend the remaining time going deeper on the tension it exposed rather than continuing down the prepared list.

for a principal

Own the tradeoff between information and relationship. Decide beforehand which answers would actually change your decision, spend your hardest question there, defer the rest to the offer stage, and accept the residual uncertainty deliberately.

## The constraint A founder slot is often short, and the diligence checklist — funding stage and runway, path to revenue, moat, key-person risk, equity context — is longer than the time available. Asking all of it produces a shallow pass: five half-answers, none followed up, and a founder who feels processed. The skill is choosing. ## Two filters, applied in order **Filter one: exclusivity.** Could anyone else in this loop answer it, or could a careful reading of the company's public material? If yes, it does not belong here. Process, tooling and team rhythm belong with the engineers. Stages, timelines and the pay band for the level belong with the recruiter. Anything published belongs to your preparation, and asking it burns credibility as well as time. **Filter two: decision weight.** If you imagine the two most likely answers, would you behave differently? Runway passes easily: fourteen months and a milestone leads somewhere different from seven months and an active raise. 'How big is the market?' fails — you will proceed regardless of the answer, so it is curiosity, not diligence. What typically survives both filters: | Question | Exclusive? | Changes the decision? | |---|---|---| | Months of runway against the next milestone | Yes | Yes | | Who pays today and who pays next | Mostly | Yes | | What slows a well-funded competitor down | Yes | Often | | Which people the product or customers depend on | Partly | Sometimes | | What fraction of the company a grant represents, in shape | Yes | Sometimes | A note on that last row: it is legitimate to ask a founder for the *context* around equity — roughly what share a grant represents and how they expect later financing to affect early employees — but keep it to shape. Plan mechanics differ between companies, and tax and legal treatment varies by country and by personal circumstance, so use the answer as background and get independent advice on your own documents rather than negotiating terms in this conversation. Detailed terms belong with whoever owns the offer. ## Sequencing beats listing Open with the question that is cheapest to ask and richest to answer: **'What keeps you up at night about this business?'** Founders answer it candidly more often than not, and the answer typically lands on one of your checklist rows — the sales cycle, a competitor, a person, the raise. That does two things: it tells you which of your items are already partly answered, and it earns you the right to go deeper on the one they raised rather than switching topics. Then spend the middle on the number: runway against the next milestone. Then keep the last slot **unallocated**, and use it on the strongest thread that opened. A pre-written third question is almost always worse than a live one. ## A worked example Suppose you have a short conversation with a co-founder at an early-stage company selling forecasting models to operations teams. You open with the risk question. They say the models are good but each new customer needs weeks of bespoke data plumbing, so growth is gated on delivery. Your prepared list said: runway, moat, hiring plan, key-person risk. The answer just reshaped it. Moat is partly answered — integration depth is the switching cost, and it is also the drag. So ask the number next: 'How many months does the current plan fund, and what does the next raise depend on?' Say they answer nineteen months, with the raise pinned to a retention milestone. Now your reserved slot has an obvious best use: *is the plumbing cost per customer coming down?* Because if it is not, nineteen months and a retention milestone are in tension, and that tension is the single most decision-relevant thing available to you. Three questions, one of them improvised, and you leave with a coherent picture instead of five fragments. ## The tradeoffs you are actually making - **Depth versus coverage.** Two answers you can reason with beat five you cannot. Coverage feels safer and teaches you less. - **Information versus relationship.** Every hard question spends a little goodwill. Runway is worth it; a fourth financial question usually is not. - **Now versus later.** Some questions are better at the offer stage, when candour rises. Ask now what you need in order to keep going; defer what you need in order to sign. - **What your silence says.** Asking nothing about the business is itself a signal to a founder — it reads as a candidate who has not understood what joining an early-stage company is. ## The failure to avoid The common one is not over-asking. It is treating the founder conversation as a warm culture chat, enjoying it, and walking out without ever asking how long the company is funded for. Whatever else you cut, do not cut the clock.

  • If you only get time for one question with a founder, which one do you spend it on?
    The risk question — what keeps them up at night about the business — because it is the only single question whose answer regularly covers runway, competition and key people at once, and it reveals what the founder themselves weighs most. If you already know the risk they'd name, spend it on months of runway against the next milestone instead.
  • How do you handle a founder who spends the whole slot pitching rather than answering?
    Let the pitch run briefly, then ask one narrow, factual question that cannot be answered with vision — months of runway, or who paid last quarter and for what. Specific questions interrupt a pitch politely. If two specific questions both return pitch, that is itself the finding, and you can stop spending the slot.
  • Which of your prepared questions should you deliberately hold back for the offer stage?
    The ones you need in order to sign rather than to continue: detailed equity context, precise financials, anything requiring documents. Candour generally rises once a company has decided it wants you, and terms are best discussed with whoever owns the offer, with independent advice on your own paperwork.

saying these in an interview costs you the question

  • Reading a prepared list aloud instead of following the answers
  • Spending the slot on questions engineers or recruiters could answer
  • Asking something the company's public pages already answer
  • Covering five topics shallowly instead of two properly
  • Leaving without asking how long the company is funded for
  • Trying to negotiate equity terms during a diligence conversation

context