Skip to content
SIH Buddyby Ganeev Singh
Dev

๐Ÿ”ฅ Roast My Pick ยท SIH26092

AI-Driven Scheme Matching for Marginalized Entrepreneurs

Ministry of Social Justice and Empowerment (MoSJE)

Brutal71/100

Bold. Let us find out precisely how bold, in the order a panel will find out.

Proceed with caution. A rule engine and a map dressed as an AI recommender, overlapping heavily with the statement beside it โ€” the one feature that would give it substance depends on partner financial data nobody will give you. Roughly 160โ€“360 teams are expected to go here.

The receipts

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

  1. Exhibit A

    The technical content here is a rule engine and a map, which is a very low ceiling regardless of execution quality

  2. It gets worse

    It substantially duplicates the financial module of the adjacent statement in this same block, so the two will be compared and yours is the smaller one

  3. Still reading?

    Partner fund utilisation and overdue status is internal financial data that is not published, so the filtering requirement that would make the routing genuinely intelligent cannot be implemented

  4. And the finisher

    Calling a deterministic rule lookup an AI recommender invites a judge to ask what the model is actually doing, and the honest answer is nothing

The damage report

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

  • Feasibility

    4/5

    Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

    Scheme rules and eligibility criteria are published, the channel partner network is publicly listed with locations, and mapping and routing are trivial โ€” the only unavailable piece is the partner's current fund utilisation and overdue position, which is internal financial data the statement asks you to filter on.

  • Innovation scope

    2/5

    Nothing here is new. Your only edge is execution โ€” and execution is also everyone else's only edge.

    Three modules are enumerated with their inputs and outputs, and the eligibility logic is externally fixed by scheme rules, so there is essentially no design freedom beyond how you present the result.

  • Clarity

    4/5

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

    The three components are specified clearly with the scheme tiers, interest ranges and moratorium periods given, though nothing states how partner eligibility by fund position is supposed to be determined when that data is not published.

  • Acceptance potential

    2/5

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

    This is a rule engine plus a map with no technical substance, it duplicates the calculator that forms half of the neighbouring statement in the same block, and the one genuinely interesting requirement โ€” routing away from partners who cannot currently lend โ€” depends on financial data that is not public.

  • Effort

    Heavy

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

    A rule engine, an amortisation calculator, a geospatial partner directory with category filtering and a multilingual interface is four straightforward components, none deep, but the partner directory needs assembling by hand from published lists.

  • Demo-ability

    Easy

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

    Profile in, scheme and nearest partner out, works reliably every time โ€” but it demonstrates a lookup and a map, which is not something a panel has any reason to remember.

  • 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.

  • Eligibility here is a deterministic rule set, and a team that recognises this and builds an auditable rule engine rather than dressing it up as AI is making the correct and more defensible engineering choice โ€” an eligibility decision a person cannot contest is worse than no decision
  • The channel partner network is publicly listed, so the locator can work on real partners in real places rather than mock data
  • Showing why an applicant does not qualify for a scheme is more useful than showing what they do qualify for, and almost no competing team will build the negative path

None of that means do not pick it. It means do not walk into that room having heard any of this for the first time from a judge.

The framing is a joke. The findings are not โ€” they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.