---
title: "Related founder FAQs"
slug: "do-it-yourself-game-plans/related-founder-faqs"
section: "Do-it-yourself game plans"
description: "How many customer interviews are enough? There is no universal sample for a strategic choice; the suggested 5–10 interviews are a discovery starting point,"
internal_only: false
---

# Related founder FAQs

### How many customer interviews are enough?

There is no universal sample for a strategic choice; the suggested 5–10 interviews are a discovery starting point, not statistical proof. Check observed buying behaviour and recruit contradictory cases. [How To Talk To Users — Y Combinator](https://www.youtube.com/watch?v=z1iF1c8w5Lg)

### How much does the DIY process cost?

Count actual founder, finance, research and legal time and obtain written quotes for specialist work. No verified category median exists for an independent decision review.

### Should the board see the pre-mortem?

Share a decision-grade summary when appropriate and follow your governance duties and confidentiality rules. Do not automatically expose raw confidential interviews or private coaching material.

### What if the team refuses to challenge the CEO?

Collect independent written views before group discussion and record dissent neutrally. Consider a neutral facilitator whose fee is unrelated to the outcome.

### Can I use AI to draft the memo?

Yes, with redacted inputs and independent verification; label AI-generated hypotheses as unverified. NIST provides a voluntary GenAI risk framework for governance questions. [NIST Generative AI Profile, AI RMF](https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence)

### Who should own the final decision?

The authorised founder, CEO, board or other governance body owns it under the company’s arrangements. A paid adviser can recommend, but should not silently assume authority.

### What should trigger a restart?

Specify observable triggers in advance, such as cash below an agreed floor or failed product behaviour. Avoid retroactively moving thresholds to justify persistence.