Part 30 of 40 in The Crorepati’s Shoestring← Part 29Part 31 →
This chapter explains how founders can use AI to remove repetitive work while keeping human judgment responsible for important decisions. It helps Indian startup founders test customer needs, costs and quality with small, measurable experiments instead of relying on funding or impressive appearances.
- Use AI for repetitive, reviewable and reversible tasks, while humans retain judgment.
- Test customer behaviour and delivery economics before spending heavily or seeking more funding.
- Measure hours saved at equal or better quality, including cash, refunds and direct costs.
- Observe customers, perform difficult work manually, then automate only after finding friction and mistakes.
- Protect private records and require human review for safety, legal, financial and reputational decisions.
The central argument
The strongest use of AI is removing low-value work while humans own judgment.
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: pick tasks that are repetitive, reviewable and reversible. 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 “the strongest use of ai is removing low-value work while humans own judgment.” 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 two-person SaaS team uses AI to draft tests and support summaries but reviews every release.
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: automate one weekly task with a manual quality baseline. 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 hours saved at equal or better quality. 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: The strongest use of AI is removing low-value work while humans own judgment. 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: Automate one weekly task with a manual quality baseline. 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 hours saved at equal or better quality; include time, cash paid, refunds and all direct costs.
Day 6, Repair Look specifically for this trap: uploading private records or trusting fabricated answers. 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
Design a human-in-the-loop workflow with acceptance tests.
Copy-ready founder prompt
Act as a skeptical operating partner to an Indian bootstrapped startup. Our chapter principle is: “The strongest use of AI is removing low-value work while humans own judgment.” Our target customer is [segment], budget is ₹[amount], and our available time is [days]. We are considering this experiment: Automate one weekly task with a manual quality baseline. 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
What is the strongest use of AI for a startup?
The chapter says AI is strongest at removing low-value work while humans own judgment. A two-person SaaS team, for example, can use AI to draft tests and support summaries while reviewing every release.
How should a founder test an AI automation idea?
Automate one weekly task with a manual quality baseline. Watch customers, perform the least scalable part personally, measure hours saved at equal or better quality, and then continue, modify or stop.
What should founders measure in an AI experiment?
Measure hours saved at equal or better quality, along with time, cash paid, refunds and all direct costs. Record the outcome baseline and three observations that surprised you.
What risks should founders check before using AI?
Look for uploading private records and trusting fabricated answers. Exclude customer identifiers and confidential commercial information, and have a human review safety, legal, financial or reputational decisions.

