I Spent ₹10,000 Validating a Startup

Status: Planned experiment — results will be added after the test is actually run.

Hypothesis

A carefully allocated ₹10,000 validation budget can produce enough customer evidence to decide whether a startup idea deserves further investment.

Experiment

Spend no more than ₹10,000 across research, landing-page validation, customer outreach, prototypes, or other clearly defined validation activities.

What we will measure

• Money spent
• People interviewed
• Landing-page visits
• Leads
• Signups
• Preorders or payments
• Customer objections
• Strongest evidence for or against the idea

Results

To be completed after the validation experiment.

What we learned

To be completed from the actual experiment.

A real low-budget validation experiment

A public Indie Hackers experiment demonstrates how little can be required to get meaningful startup evidence.

The founder reported spending $100 on ads and direct outreach.

That produced approximately:

• 100 visits
• 5 booked calls
• 3 people willing to pay for a manual version

Instead of immediately building software, the founder performed the work manually for two weeks.

Source: https://www.indiehackers.com/post/stop-building-start-validating-d10e4bb00a

The exact budget was $100, not ₹10,000. The experiment belongs in this category because it demonstrates the same principle: use a small fixed budget to buy evidence before committing to a large build.

The hypothesis

The hypothesis is:

If people will give money or meaningful commitment for a manual version of a solution, the problem may be strong enough to justify building software.

That is stronger than asking whether people “like” the idea.

A person can like an idea without changing behaviour.

Payment is different.

The first signal

The first test generated 100 visits and five booked calls.

That means the experiment moved beyond passive attention.

Five people gave up time to talk.

Then three people agreed to pay for a manual version.

That is the key signal.

The founder had not yet built the full software product.

The market was already showing willingness to exchange money for the outcome.

Becoming the product

The founder then delivered the service manually for two weeks.

This is one of the strongest parts of the experiment.

Manual delivery reveals the actual workflow.

Instead of guessing what software should automate, the founder sees the customer's process directly.

That creates a list of evidence:

• Which steps happen repeatedly?
• Which steps are painful?
• Which steps customers ignore?
• Which output creates value?
• Which features are unnecessary?
• What would the customer pay to avoid doing manually?

The software can then automate the parts that actually matter.

Hnry provides another real validation example

Hnry began with James Fuller's personal tax problem.

He built spreadsheets to manage contractor tax, shared them with friends, and then created a simple landing page.

A $100 Twitter ad produced 40 early users, according to a public account of the company's founding story.

Source: https://thenudgegroup.com/podcast/were-not-short-on-opportunity-we’re-short-on-capacity-karan-anand-managing-director-aus-hnry

The company eventually grew to serve tens of thousands of customers across New Zealand and Australia.

The important part happened much earlier.

The founders had evidence that the problem was painful before building the full company.

A third validation example

Antler's customer-validation research describes Flyweel founder Matteo Calo using AI to create a visual prototype and then spending $100 on paid ads to test demand.

The purpose was not to prove a huge market.

It was to get a fast signal before committing more resources.

Source: https://www.antler.co/blog/how-to-validate-like-a-vc-backed-founder

This is exactly how a ₹10,000 validation experiment should be viewed.

The money is not the goal.

The evidence is.

How to structure a ₹10,000 test

A founder could set a hard ceiling of ₹10,000.

Start with the cheapest tests:

Phase 1 — problem interviews

Talk to people who actually experience the problem.

Phase 2 — simple offer

Create a landing page or prototype.

Phase 3 — demand test

Use targeted outreach or a small paid traffic test.

Phase 4 — commitment

Ask for a preorder, deposit, paid pilot, or manual-service payment.

Stop when enough evidence exists.

There is no requirement to spend the full ₹10,000.

If ₹2,000 produces strong evidence, keep the remaining budget.

What counts as validation?

Weak evidence:

• Likes
• Compliments
• “Cool idea”
• Friends saying they would use it

Stronger evidence:

• Qualified conversations
• Prototype usage
• Demo requests
• Repeated usage

Strongest evidence:

• Payment
• Preorders
• Deposits
• Paid pilots
• Switching from an existing solution

The closer the signal is to actual economic behaviour, the stronger the validation.

The decision gate

At the end of the experiment, the founder should know:

1. Who has the problem?
2. How painful is it?
3. What do they use today?
4. Did they try the proposed solution?
5. Did anyone pay?
6. Can the economics plausibly work?

If those answers are unclear, building more code is not necessarily the answer.

Run another experiment.

Result summary

The documented $100 Indie Hackers experiment generated 100 visits, five booked calls, and three people willing to pay for a manual service.

Hnry's separate $100 Twitter test generated 40 early users before the formal product was built.

These examples show why low-cost validation works.

Lesson

A ₹10,000 experiment should not be designed to prove that a startup will become a billion-dollar company.

It should answer one expensive question cheaply.

Spend less. Learn faster. Build only after the evidence earns it.

Sources

• https://www.indiehackers.com/post/stop-building-start-validating-d10e4bb00a
• https://thenudgegroup.com/podcast/were-not-short-on-opportunity-we’re-short-on-capacity-karan-anand-managing-director-aus-hnry
• https://www.antler.co/blog/how-to-validate-like-a-vc-backed-founder