10 Questions Every Founder Must Answer Before Launching a Startup

Before launching, a founder should be able to explain the customer, problem, current alternative, evidence, buying path, distribution channel, economics, delivery risk, decision threshold, and next learning milestone. The answers do not need to be certain; uncertainty must be explicit and connected to a test.

1. Who experiences the problem in which situation?

Define an initial segment using role, organization, workflow, and trigger. “Freelancers” is a category; “independent designers who invoice five or more international clients each month” is a testable starting segment.

Evidence: recruitment criteria plus recent examples from people who match them.

2. What exactly happens when the problem occurs?

Describe an observable sequence and consequence without mentioning your product. Include frequency, current workflow, delay, cost, or risk.

Evidence: behavioral interviews and workflow artifacts. Use these customer discovery questions.

3. How do people solve it today?

Map direct competitors, broad platforms, spreadsheets, manual work, consultants, internal staff, and doing nothing. Document why each option remains acceptable.

Evidence: customer behavior, current product documentation, pricing, and representative reviews.

4. Why would someone switch?

Name an outcome that matters enough to overcome migration effort, retraining, risk, and approval. A missing competitor feature is not sufficient by itself.

Evidence: repeated complaints connected to a consequence, plus a test where target users prefer or adopt the new workflow. See competitive gap.

5. Who uses, owns, buys, and blocks the solution?

These may be four different people. Identify the end user, accountable owner, budget approver, and anyone responsible for procurement, security, legal, or integration review.

Evidence: a buying-path map based on real conversations and at least one introduction beyond the initial user.

6. What proof supports demand?

Separate attention, stated pain, existing behavior, commitment, and payment. Search interest and social engagement can help locate a market, but they do not prove purchase intent.

Google explains that Trends values are normalized relative interest rather than absolute search volume and should be treated as one data point. See the Google Trends data FAQ.

Evidence: multiple independent signal types, with source links and counter-evidence.

7. How will you repeatedly reach qualified buyers?

Choose one initial channel and estimate the sequence from reach to qualified conversation to commitment. Distinguish owned audiences and friendly introductions from repeatable acquisition.

Evidence: a small channel test with actual delivery, response, qualification, meeting, and commitment counts.

8. Can the economics work?

Estimate price, variable delivery cost, acquisition effort, support burden, payment timing, and retention assumptions. Use ranges and show the calculation.

The U.S. Small Business Administration recommends examining pricing, market saturation, demand, and the costs required to launch; its planning guide also provides a break-even formula and calculator. See SBA business planning guidance.

Evidence: customer price conversations, paid tests where possible, supplier quotes, and a transparent model.

9. What could prevent delivery?

List technical, operational, data-access, regulatory, security, and dependency risks. Test the riskiest unknown before polishing secondary features.

Evidence: a manual delivery, technical spike, data sample, expert review, or workflow test that directly addresses the constraint.

10. What result changes the decision?

Define Continue, Revise, and Stop thresholds before launch. Include the qualifying segment, sample source, observation period, target behavior, and cost of the next investment.

Evidence: a written decision rule in the validation brief.

The pre-launch answer sheet

When are you ready to launch?

Launch the smallest version when it is the cheapest credible way to test the next important uncertainty. Do not wait for certainty, but do not use product development to avoid learning that can be obtained through interviews, manual delivery, prototypes, or pilot offers.

For the full operating sequence, use the startup idea validation guide. For a scored preparation tool, use the 15-step business validation checklist.