-
the logo
Inspiration
A lot of agricultural produce does not become waste because it is unusable. Sometimes, it simply fails to reach the right buyer at the right time.
A small farmer may harvest 150–300 kg of tomatoes, pineapple, chillies or other produce. That quantity can be too small for a food processor to procure individually. A nearby processor, meanwhile, may need one or two tonnes of exactly that raw material but has no easy way to discover and coordinate with several small farmers at once.
The problem becomes even more visible with processing-grade produce. A tomato that is not attractive enough for the premium fresh market may still be perfectly suitable for sauce or puree. A slightly irregular mango may still work for pulp, juice or pickle. Yet these alternative uses are often discovered only after the produce has already started losing value.
That led us to one question:
What if fragmented harvests could be combined and matched to processors before they become waste?
That idea became LotMate.
What it does
LotMate is a post-harvest matching and aggregation platform connecting farmers and FPOs with small food processors looking for raw materials.
Farmers can list:
- Crop and variety
- Expected or available quantity
- Harvest window
- Produce grade
- Location
Processors can post:
- Raw material required
- Quantity
- Acceptable grades/specifications
- Procurement date
- Sourcing radius
LotMate then matches compatible demand with available or upcoming harvests.
The key difference is that LotMate does not treat each farmer's listing independently. Its Micro-Lot Builder can combine several smaller quantities into one processor-ready lot.
For example:
Farmer A: 180 kg tomato
Farmer B: 240 kg tomato
Farmer C: 260 kg tomato
Farmer D: 350 kg tomatoProcessor requirement: 1,000 kg
LotMate can aggregate them into a viable procurement lot.
LotMate also includes Rescue Mode. Produce with a shrinking marketable window can be prioritised and matched with alternative processing opportunities such as sauce, juice, pulp, pickle or dehydration depending on its suitability.
Where direct farmer-to-processor movement is impractical, an FPO, trader or collection partner can handle aggregation and transportation. LotMate is not designed to remove every intermediary; it is designed to remove unnecessary information and coordination gaps.
How we built it
We approached LotMate as a software-first coordination system, rather than trying to build a large agricultural marketplace from day one.
The MVP revolves around four components:
- Harvest Forecast – farmers list upcoming harvests before the produce reaches the market.
- Demand Matching – processors publish their future raw-material requirements.
- Micro-Lot Builder – compatible small farmer lots are combined to fulfil larger demand.
- Rescue Mode – time-sensitive produce is prioritised before its marketable window closes.
The planned application uses Flutter for the user-facing experience with a backend storing farmer harvests, processor requirements and generated matches.
The matching logic considers factors such as:
crop + variety + grade + quantity + harvest date + processor requirement + sourcing radius
Instead of hiding everything behind an unexplained AI recommendation, the first version focuses on an explainable matching score, so users can understand why a particular farmer or processor was selected.
Our initial prototype scenario uses a local tomato supply cluster where multiple small farmer lots are combined against a processor requirement. This gives us a controlled way to test the matching, aggregation and Rescue Mode workflows before expanding to more crops.
Challenges we ran into
The first challenge was avoiding the trap of building another digital mandi.
Simply allowing farmers to list produce and processors to browse listings would not solve the main coordination problem. We therefore had to identify the missing layer: forming the right quantity, grade and harvest window into a realistic procurement lot.
Another challenge was keeping the MVP small. Agriculture supply chains involve payments, logistics, grading, certification, traceability, storage, transport and many other components. Trying to solve all of them at once would make the project impossible to validate properly.
We therefore decided to focus first on matching and aggregation.
A third challenge is that agricultural data is uncertain. Expected harvest quantity can change, harvesting dates can shift and produce quality cannot always be predicted perfectly. LotMate therefore needs to treat harvest information as an evolving estimate rather than assuming every listing is exact.
Logistics is another real-world constraint. Combining five farmers on a screen is easy; collecting their produce efficiently is harder. This is why collection partners and geographic clustering are part of the system rather than assuming transport will somehow take care of itself.
Accomplishments that we're proud of
One of the things we are most proud of is narrowing LotMate from a broad marketplace idea into a much clearer problem:
turning fragmented harvests into processor-ready lots.
We have designed a workflow that serves three real participants in the value chain — farmers/FPOs, processors and collection partners — instead of assuming that connecting a buyer and seller automatically solves procurement.
We are also proud of Rescue Mode, because it changes the question from:
"Who will buy this produce?"
to:
"What is the most suitable remaining use for this produce before it loses value?"
Most importantly, the concept has stayed focused. The MVP currently has only four core features, each directly supporting the main problem.
What we learned
The biggest lesson was that agricultural market linkage is not only a problem of discovering buyers.
Timing, quantity, quality and coordination matter together.
A processor may exist nearby but still be unable to procure from a farmer if the quantity is too small. Several farmers may collectively have enough produce but harvest at different times. Produce rejected from one market may still have value in another processing pathway.
We also learned that technology should work with the existing agricultural value chain rather than pretending every intermediary is unnecessary. Aggregators, FPOs and traders often perform real functions such as collection, grading and transportation.
LotMate should make those activities easier to coordinate rather than simply trying to remove them.
What's next for LotMate
The next milestone is a working end-to-end prototype demonstrating one complete flow:
processor posts requirement → compatible farmers are identified → small quantities are aggregated → processor-ready lot is formed → collection plan is generated.
After that, we plan to add:
- Rescue Mode alerts
- Better crop-to-processing suitability rules
- Geographic clustering and pickup optimisation
- Farmer/FPO verification
- Processor requirement forecasting
- Quality and traceability records
- Notifications as harvest and procurement windows approach
Longer term, LotMate could evolve into a coordination infrastructure for local agricultural processing clusters, helping processors discover reliable nearby supply while giving fragmented smallholder harvests more opportunities to enter productive value chains.
Our goal is simple: help every harvest find its most suitable use before it becomes waste.
Log in or sign up for Devpost to join the conversation.