A SaaS marketplace connecting farmers with licensed drone operators for on-demand aerial pesticide and fertilizer application.
TL;DR
Agricultural drone services are commercially viable — the operators exist, the technology works. But small farmers in India can't access them because there's no discoverable marketplace. AgriDrone closes this gap: farmers submit service requests from their phone, operators accept jobs within their efficient radius, and admins ensure platform quality. The core insight: farmer trust and operator geographic inefficiency are the same problem — information asymmetry.
Booking time target
< 5 min
registration to first request
Fulfillment target
≥ 80%
requests accepted within 48 hrs
Why it exists
For Farmers
For Operators
Core insight
The two biggest barriers — farmer trust and operator geographic inefficiency — are the same problem: information asymmetry about location and credibility. Solve that and the market connects itself.
Who we serve
42 · Rural Maharashtra · Basic smartphone user
Goals
Pain Points
“I've heard of drone spraying but I don't know who to call. And how do I know they won't damage my crop?”
What we're building
Farmers create and manage fields with name, area (hectares), crop type, and GeoJSON polygon coordinates. Fields are private — only the owning farmer can view or edit. Field data attaches to service requests so operators know exactly what they're servicing before accepting.
Key requirements
Booking status state machine
Tech
React SPA communicates exclusively with a Flask backend via REST. Flask proxies weather requests and enforces JWT auth and role checks on all protected endpoints. SQLAlchemy ORM abstracts the database layer.
Frontend
React (TypeScript) via Vite · Leaflet for operator maps · Axios for API calls
Backend
Python Flask · SQLAlchemy ORM · Werkzeug/bcrypt password hashing · JWT Bearer tokens
Database
SQLite (dev) → PostgreSQL (production) · FK constraints and cascading deletes
Security
RBAC on all endpoints · CORS locked to frontend origin · API keys server-side only · Server-side input validation
How we measure success
0%
of pending requests accepted within 48 hrs
0 min
registration to first request (target)
0%
operator profile completion rate target
0.5%
platform uptime target
Delivery plan
Still to resolve