Two Indian co-founders discuss a stalled packing machine while a supplier waits at a workshop doorway.

Disagree With Your Co-Founder Early

6 min read

Part 27 of 40 in The Crorepati’s Shoestring

This chapter explains how co-founders can test their partnership through bad news, clear decision rights and written conflict rules. It helps founders replace assumptions, spending and shared enthusiasm with small experiments and evidence.

Quick Summary

  • Bad news tests a partnership more reliably than shared enthusiasm.
  • Write decision rights, vesting and conflict rules while relationships are healthy.
  • Use small, observable tests before requesting capital, hiring or buying tools.
  • Measure decision speed, unresolved conflicts, cash and direct costs.
  • A failed test is acceptable; an unmeasured test is merely activity.

The central argument

The partnership is tested by bad news, not shared enthusiasm.

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: write decision rights, vesting and conflict rules while relationships are healthy. 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 partnership is tested by bad news, not shared enthusiasm.” 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.

Two college friends building in Chennai disagree over who owns engineering decisions.

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 simulated cash crunch and discuss choices in writing. 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 decision speed and unresolved conflicts. 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 partnership is tested by bad news, not shared enthusiasm. 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 simulated cash crunch and discuss choices in writing. 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 decision speed and unresolved conflicts; include time, cash paid, refunds and all direct costs.

Day 6, Repair Look specifically for this trap: using friendship as a substitute for governance. 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

Generate a discussion agenda, not a legal contract.

Copy-ready founder prompt

Act as a skeptical operating partner to an Indian bootstrapped startup. Our chapter principle is: “The partnership is tested by bad news, not shared enthusiasm.” Our target customer is [segment], budget is ₹[amount], and our available time is [days]. We are considering this experiment: Run a simulated cash crunch and discuss choices in writing. 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

Why should co-founders discuss conflict rules early?

Decision rights, vesting and conflict rules should be written while relationships are healthy. This helps reveal how people respond when choices become difficult.

What is the seven-day field experiment?

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

How can founders test a partnership?

Run a simulated cash crunch and discuss choices in writing. Watch decision speed and unresolved conflicts, then use the evidence to guide the next decision.

What should founders measure during the test?

Measure decision speed, unresolved conflicts, time, cash paid, refunds and direct costs. Record observations, the decision, its owner and the next review date.

Leave a Comment

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

Scroll to Top