AI-Driven Hyper-Local Business Advisory and Financial Structuring Assistant for Rural Micro-Entrepreneurs

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   Competitor density and market saturation at village level do not exist as data, so the advisory module will generate plausible-sounding local analysis with nothing behind it — and this output is specifically intended to be acted on by someone taking on debt

2. It gets worse

   The rupee amounts in the description are corrupted by an encoding fault throughout, so read the underlying scheme documents for the real thresholds rather than the figures as printed

3. Still reading?

   The calculator half has zero technical content because the statement writes the branching logic out for you, so it cannot carry the submission

4. And the finisher

   Advising someone into a business that fails leaves them with a loan they cannot repay, so confident generation is a harm here rather than a quality issue — build the abstention behaviour deliberately

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  3/5

  Buildable. Not comfortably. There is a week in here you have not planned for yet.

  The financial module is trivially buildable because the statement supplies every scheme parameter, but the advisory module needs competitor density, market saturation and purchasing power at village or block level, and that data does not exist in any accessible form — village demographics come from a long-outdated census and no local business-density dataset exists.

• Innovation scope

  2/5

  Nothing here is new. Your only edge is execution — and execution is also everyone else's only edge.

  Both modules are specified exhaustively, with the financial logic written out as explicit branching rules and worked arithmetic, so the calculator has no design freedom at all and the advisory module's six sections are prescribed.

• Clarity

  5/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  Extremely detailed, naming both scheme tiers with their cost ceilings, interest rates, tenures and moratorium periods, and setting out the six advisory sections and the routing logic individually — though the rupee figures throughout are visibly mangled by an encoding fault, and the calculator's entire arithmetic depends on reading them correctly.

• Acceptance potential

  2/5

  The numbers do not like you. Bring something the numbers cannot see.

  One module is a calculator with the logic handed to you and no technical content, and the other asks for hyper-local market intelligence that does not exist as data — so the likely submission is a language model generating a confident SWOT for a village it knows nothing about, which a first-time borrower then commits to a nine-lakh loan against.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  The calculator is a day's work, but the advisory module needs data sourcing, retrieval grounding, report generation and multilingual delivery, and building it responsibly rather than letting a language model improvise is where the real time goes.

• Demo-ability

  Easy

  Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

  Entering a capital amount and watching a complete financial roadmap with the right scheme and repayment schedule assemble is clean and works reliably, though what it demonstrates is arithmetic the statement already specified.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 160–360 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• The financial module is fully specified with real scheme parameters, so it can be built correctly and verified against published scheme documents rather than argued about
• Mapping available cash to borrowing capacity is genuinely the thing beneficiaries misunderstand, and a tool that makes the ninety-ten relationship concrete has real value even without the advisory half
• A system that says plainly which of its claims are grounded in data and which are general guidance would be far more defensible than one that presents everything with equal confidence, and almost no competing team will make that distinction