Multiple intermediaries reduce farmers earnings and increase consumer prices.

The receipts 🧾

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

1. Exhibit A

   Farmer-to-consumer marketplaces are among the most repeatedly submitted ideas at every Indian hackathon, and yours will be judged against a memory of many nearly identical decks

2. It gets worse

   eNAM already runs this nationally with real mandi integration, so the novelty bar is brutal and 'we made the UI better' is not an answer

3. Still reading?

   The hard problems in this space are trust, grading disputes, perishability and last-mile economics, and none of them are software problems — a judge from this ministry knows that and will go straight there

4. And the finisher

   Demand forecasting requires transaction history you do not have, so that module can only be trained on synthetic orders or repurposed price series that are not the same thing

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.

  The marketplace and routing are ordinary engineering with mature libraries, and commodity price data is published daily by Agmarknet so the demand and price side has a real public source, but you have no order history to forecast demand from and no actual farmers or vehicles, so the two-sided liquidity the whole model depends on is simulated.

• Innovation scope

  3/5

  Mildly interesting. The novelty will not carry the room; the build has to.

  Three bullets prescribe a marketplace with logistics and AI forecasting and nothing further, so the aggregation logic, the routing formulation and the forecasting approach are yours, but the product concept is entirely fixed.

• Clarity

  2/5

  Nobody is sure what is being asked, quite possibly including the people who asked it.

  Around 300 characters consisting of three capability bullets and a benefits list — it never says which commodities, which geography, who does the last mile, how payment and quality disputes are handled, or what distinguishes this from the marketplaces that already exist.

• Acceptance potential

  1/5

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

  The farmer-to-consumer marketplace is the single most cloned idea in Indian hackathons and judges have sat through dozens of them, and separately eNAM already operates this at national scale with real trader participation, so you face the crowding penalty and the existing-solution penalty simultaneously.

• Effort

  Heavy

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

  A two-sided marketplace with onboarding, listings, ordering and payments, plus an order aggregation layer, a vehicle routing solver and a forecasting model, is four substantial pieces even though none of them is individually novel.

• Demo-ability

  Medium

  Demoable, if you rehearse it. Nobody rehearses it.

  A marketplace demo is a catalogue and a checkout, which every judge has seen dozens of times, and the only genuinely interesting moment — orders aggregating into an optimised route — needs careful staging to be visible at all.

• 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 220–500 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.

• Agmarknet publishes daily mandi prices for hundreds of commodities, so unlike most marketplace submissions you can ground your price and margin claims in real public data rather than invented numbers
• The order aggregation and routing piece is a genuine optimisation problem and is the one part of this statement where a team can demonstrate something technically real
• The MedTech theme label means agriculture teams browsing by theme will not find it, which slightly thins an otherwise crowded field