From the farmer's phone to the technician's van, one system.
An agritech company serving a large and geographically dispersed farmer base with agri-inputs, advisory services, soil and water testing, and drone spraying.
increase in repeat app users
growth in premium advisory and agri-input sales
accuracy in drone-based spraying patterns
What wasn't working.
Service requests, complaints, and advisory bookings arrived through inconsistent channels with no single source of truth. Field resource allocation was largely manual, which meant inefficient routing and turnaround times that varied by who happened to pick the job up. Farmers had no way to raise a request and then see what had happened to it, so the call centre absorbed the follow-ups. Payment collection and invoicing sat outside service completion entirely, delaying revenue recognition and making reconciliation a separate exercise. The company needed these to become one operating model rather than four disconnected ones.
What we built.
Multi-channel request intake
Farmers and staff raise service requests and complaints from the farmer app, the field app, or Salesforce directly, and every route lands in the same case lifecycle instead of a separate queue.
Scheduling and dispatch
Automatic and manual scheduling through a dispatcher console, optimised for field resource utilisation, so routing stops depending on whoever is doing the allocating that morning.
Entitlements, SLAs and checklists
Milestone-based tracking for time-sensitive services, with mandatory pre and post-service checklists on every work order to cut rework and repeat visits.
Farmer self-service app
Soil, water and leaf testing, drone spray booking, mandi services and complaint registration, alongside daily-use tools like localised weather, a store locator and a tank mix calculator.
Field technician app
Assigned work, customer detail and checklists on the device, with appointment updates and absence and leave submission completed from the field.
Payment and invoicing at closure
Online and cash collection captured at the point of service completion, with invoice generation and dispatch built into closing the job rather than chased afterwards.
Built with.
What powered this build.
Have a system that's holding you back?
Walk us through it. We'll tell you what we'd build, what we'd keep, and what it would take.
Start the conversation