Indian founder and colleague sort returned samples and costs during a pre-mortem at a workplace table.

Let AI Interview Your Assumptions

6 min read

Part 31 of 40 in The Crorepati’s Shoestring

This chapter explains how founders can use AI to challenge assumptions instead of seeking flattering confirmation. It helps Indian startup founders test customer needs, costs and delivery realities with small, measurable experiments.

Quick Summary

  • A thoughtful critic is more useful than a flattering chatbot.
  • Test customer behaviour and fulfilment economics before turning uncertainty into a capital request.
  • Use a seven-day experiment to observe customers, make an offer, count costs and decide what to do next.
  • Treat failed tests as acceptable, but treat unmeasured tests as activity.
  • Use AI to simulate objections, then verify them through human interviews and market evidence.

The central argument

A thoughtful critic is more useful than a flattering chatbot.

There is a temptation in the Indian startup ecosystem to turn an uncertainty into a capital request. The founder has not yet learned what the buyer values, how the product will be delivered, or how much it costs to fulfil one promise. A cheque may postpone these questions, but it rarely answers them. The better starting point is a test that forces reality to respond.

Frugality is not miserliness. It is disciplined resource allocation. Spend generously where quality, safety, trust or the customer outcome requires it; challenge spending that merely makes the company look more impressive. This distinction matters in an economy where an extra month of runway, an advance payment, or an honest conversation with a buyer can change a company’s future.

The practical decision in this chapter is specific: ask AI for disconfirming evidence and customer segments that may not care. It asks the founder to trade certainty of appearance for evidence of substance. Evidence may be awkward, disappointing or slower than a press announcement; it is still more useful.

Questions worth asking

  • What would I have to observe to know that “a thoughtful critic is more useful than a flattering chatbot.” applies here?
  • What is the smallest reversible choice I can make this week?
  • Which customer, worker or supplier knows something my spreadsheet does not?

Founder’s margin note: Describe the decision you have postponed because you hoped funding, hiring or a new tool would make it easier.

An Indian story

ILLUSTRATIVE COMPOSITE, a teaching scenario, not a documented account of a named company.

A founder believes every kirana shop needs her app because her uncle likes it.

Imagine meeting this founder on a hot afternoon with three phone calls missed and a supplier waiting for an answer. The problem is not a shortage of ideas. It is a shortage of clear priorities. The founder can buy a tool, hire a consultant or redesign the logo, but none of those actions will automatically uncover the customer’s actual need.

Instead, the founder chooses a modest, observable next step: run a pre-mortem before the next sprint. The purpose is not to win a case-study competition. It is to discover whether people change their behaviour when the offer is made, and what the economics look like after the founder does the work.

The signal to watch is assumptions tested and abandoned. A disappointing result is useful when it rules out an expensive path. A promising result is only a beginning: repeat it with customers who do not know you personally, on ordinary weekdays, without special favours.

Compare with documented Indian founders

The lesson should be tested in your own market rather than borrowed unquestioningly from a celebrated startup. A founder supplying small-town retailers faces different margins, credit terms and trust barriers from a software exporter. Copy a method of learning, not a famous company’s surface features.

Field observation: Who in your district or industry already does this unusually well with limited resources? Ask permission to observe them.

The operating playbook

A seven-day field experiment

Day 1, Define Write the most dangerous assumption behind this chapter: A thoughtful critic is more useful than a flattering chatbot. Name who could prove you wrong.

Day 2, Observe Watch three customers perform the task today; record actions and exact phrases, not your interpretation.

Day 3, Offer Make a concrete offer or test: Run a pre-mortem before the next sprint. Be clear about price, terms and expected delivery.

Day 4, Deliver Personally perform the least scalable part. Observe friction, mistakes and objections before automating.

Day 5, Count Measure assumptions tested and abandoned; include time, cash paid, refunds and all direct costs.

Day 6, Repair Look specifically for this trap: confusing AI-generated critique with market evidence. Change one thing, not the entire system.

Day 7, Decide Continue, modify or stop. State what evidence would reverse your decision next week.

The one-page scorecard

Hypothesis and customer segment: ______________________________

Cash spent / cash collected / money still owed: ____________________

Outcome metric and its baseline: ________________________________

Three observations that surprised us: ____________________________

Decision, owner and date of next review: _________________________

Rule: a failed test is acceptable; an unmeasured test is merely activity.

AI workshop & reflection

What to delegate to AI

Simulate a skeptical buyer and then verify objections in interviews.

Copy-ready founder prompt

Act as a skeptical operating partner to an Indian bootstrapped startup. Our chapter principle is: “A thoughtful critic is more useful than a flattering chatbot.” Our target customer is [segment], budget is ₹[amount], and our available time is [days]. We are considering this experiment: Run a pre-mortem before the next sprint. Identify hidden assumptions, a cheaper test, what evidence would disprove the idea, relevant India-specific customer frictions, and a quality checklist. Do not invent customer facts. Mark every assumption requiring human verification.

Check the output before acting

  • Are all numbers sourced from my own records or clearly labelled assumptions?
  • Have we checked local language, payment habits and distribution realities?
  • Have we excluded customer identifiers and confidential commercial information?
  • Does a human owner review any safety, legal, financial or reputational decision?

Your founder notebook

One belief I am willing to change: ________________________________

One real customer I will speak to: ________________________________

One experiment I will complete: ________________________________

My follow-up date: ________________________________

The point of AI is not to sound more certain. It is to become cheaper, quicker and more rigorous at discovering what is true.

Frequently asked questions

How can founders use AI to challenge startup assumptions?

Ask AI for disconfirming evidence, hidden assumptions, cheaper tests and customer segments that may not care. Verify its objections through interviews and observation.

What is the seven-day field experiment for startups?

Define the dangerous assumption, observe three customers, make a concrete offer, deliver personally, count results, repair one issue and decide whether to continue, modify or stop.

Why should startups test customers before seeking funding?

Funding may postpone questions about customer value, delivery and fulfilment costs, but it rarely answers them. A small test forces reality to respond.

What should founders check before acting on AI output?

Check that numbers come from records or are labelled assumptions, local language and payment habits were considered, confidential information was excluded, and a human reviews important decisions.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top