How to validate a business idea in India before investing

Before paying a shop deposit, buying equipment or leaving your job, establish what would make your idea worth testing. A useful feasibility check connects three things: evidence that customers will pay, the money left after serving them, and your ability to deliver enough orders.

This guide uses a hypothetical mobile car-detailing service in Ahmedabad. All amounts and operating assumptions are illustrative, not supplier quotes, local market averages or evidence of demand. Replace them with your own findings.

1. Define one customer and one offer

“Car owners in Ahmedabad” is too broad for a first test. Start with a narrower proposition: a specified detailing package for residents of two nearby housing societies, delivered by appointment on weekends.

Write down the service area, package inclusions, exclusions, proposed price and available slots. Check practical access with the property manager before promising doorstep service. Who supplies water or power? Where can the work happen? What happens when access is refused?

Your first question is whether you can reach and serve this particular customer, not whether car care is a large industry.

2. Ask about actual buying behaviour

Speak with prospective customers outside your immediate supporters. Ten conversations can uncover questions worth testing; ten positive answers do not establish market demand.

Ask:

• When did you last pay for a comparable service, and how much?
• What did you choose instead, including doing it yourself?
• What was inconvenient or disappointing?
• Who chooses the provider, and what would make you switch?

Record recent actions separately from opinions. “I paid last month and waited two hours” is more useful than “Sounds interesting.” Keep identifying details out of your research notes unless necessary and shared with permission.

3. Compare alternatives and collect local costs

Compare a few providers serving the same neighbourhoods. Record package scope, advertised price, travel charges, booking lead time and the date checked. A low headline price may cover a different service. Listings establish that alternatives exist, not how many bookings they receive.

Request current equipment and consumables quotes. Record delivery, warranty, replacement parts and minimum order quantities. Estimate transport for your actual route, not an ideal day with every customer in one building. Separate observed facts, supplier quotes and your assumptions in the model.

Before committing to premises or operating a pilot, investigate applicable permissions. India's National Single Window System provides a Know Your Approvals questionnaire. Its results are indicative and depend on your inputs; confirm requirements with the relevant authorities rather than treating the list as legal clearance. The official NSWS FAQs explain that the issuing authority, not NSWS, grants approvals.

4. Test a specific offer at a specific price

Run a small, clearly described pilot only once you can deliver it safely and appropriately. State the package, price, service date and cancellation terms before accepting a booking. Do not advertise unavailable slots or pretend a test is an established service.

Track the funnel: people who saw the offer, qualified enquiries, bookings, completed paid jobs, cancellations and repeat requests. Separate friends, discounted orders and full-price customers.

Choose a decision rule before starting. For example, require five completed full-price jobs with acceptable delivery time and no unresolved service issues before funding a larger test. This is a proposed learning threshold, not proof that the business can support you.

Keep a one-page evidence log

Give each important assumption its own row in a notebook or spreadsheet. Record the source and date, evidence type (observed, quoted or assumed), result, remaining uncertainty and next action. Update the row when you learn something; a quote is not a paid sale, and an assumption is not an observation.

Example row for the detailing service below—all entries are illustrative, not field research:

• Assumption: One completed job takes 90 minutes, including travel and setup.
• Source and date: Founder’s planning estimate; enter the date you made it.
• Evidence type: Assumed—not an industry benchmark or a measured pilot result.
• Result: No timed pilot jobs yet; 90 minutes is a placeholder in the capacity calculation.
• Uncertainty: Travel between societies, package scope, vehicle condition and rework could change the time needed.
• Next action: Time actual pilot jobs, including travel, setup and rework. Record the range and update capacity before relying on the 39-job income target.

Fill in a small-test worksheet

Use this alongside your evidence log to bound the next test before spending. Fill in your own amounts and dates; the worksheet is a plan, not a promise of validation.

• Main assumption: What one uncertain claim will this test investigate?
• Reachable customers: Who can actually see the offer, through which permitted channel, and how will you record reach?
• Offer and price: What exactly will you deliver, at what ₹ price, with which exclusions?
• Maximum affordable test budget: ₹___, including delivery costs; spend no more than you can afford to lose.
• Review date: ___; allow enough time for this customer’s buying cycle rather than assuming two weeks proves demand.
• Evidence for the next test: Record the result against your decision rule above, including completed paid jobs, costs, time and unresolved issues.
• Change or stop criterion: Which result would make you change the offer or stop spending—for example, a capacity limit or the budget ceiling?

Silence with insufficient reach is inconclusive: it does not establish that customers rejected the offer. Record who actually saw it and whether they had a realistic opportunity to buy before interpreting a lack of bookings.

5. Calculate contribution and check capacity

Here is a simplified teaching model, separate from Feasivo's interactive sample:

Variable cost includes assumed consumables, travel and other per-job costs. Fixed costs cover costs that continue regardless of bookings. The owner's income is separate. The example excludes tax, finance costs, depreciation and setup-cost recovery; add applicable items to your own model.

Contribution = ₹1,500 − ₹500 = ₹1,000 per job.

Covering fixed operating costs requires ₹18,000 ÷ ₹1,000 = 18 jobs a month. Covering those costs plus the owner's ₹21,000 income target requires ₹39,000 ÷ ₹1,000 = 39 jobs a month. Neither threshold means the initial investment has been recovered.

Now test delivery. Assume 20 available hours a week and a four-week planning month: 80 hours. Reserve 16 hours for enquiries, purchasing and administration. At 1.5 hours per job including travel and setup, 64 hours supports at most 42 complete jobs.

Reaching 39 jobs would use about 93% of that capacity, leaving little room for delays or rework. If variable cost rises to ₹650, contribution falls to ₹850. The owner-income threshold becomes ₹39,000 ÷ ₹850, rounded up to 46 jobs, above available capacity. Revise the offer, route, cost or time assumptions before scaling.

6. Keep setup money separate from runway

Buying equipment does not fund the months before enough customers arrive. Keep four lines in your budget: upfront setup, operating reserve, personal living reserve and contingency.

For illustration, ₹1,20,000 setup + three months of ₹18,000 fixed costs + three months of ₹21,000 owner living costs + ₹20,000 contingency totals ₹2,57,000. This is a rough reserve illustration, not a complete funding requirement. Add variable-cost cash needs, deposits and payment delays; avoid counting items twice. A month-by-month cash-flow model is more useful than assuming sales arrive immediately.

See the startup capital and break-even guide for the next calculation.

Before spending more, check these six things

• I can describe one reachable customer and a specific offer.
• I have evidence from buying behaviour, not only compliments.
• I have dated local quotes and comparable competitor offers.
• My contribution remains workable under a downside scenario.
• My required orders fit realistic delivery capacity.
• I have checked permissions and separated setup, runway and living costs.

Proceed with a limited next test when the evidence supports it. Adjust when a specific assumption fails. Pause when the required sales exceed capacity or the cash risk is beyond your budget.

Feasivo reports are AI-assisted planning aids, not guarantees of demand or profitability, bank-certified reports, or substitutes for professional advice. Check important assumptions with customers, current quotes and the relevant authorities before investing.