askcust develops crop scouting apps: inspection routes by NDVI zones and past hotspots, standard point cards with geotagged photos, a pest, disease and weed reference list with economic thresholds, and tasks for the agronomist when a threshold is exceeded. For agronomy teams and scouts who inspect hundreds of fields a season.
A crop scouting app is a system that organises regular crop inspection as a process: it plans which fields to inspect and when, builds a route through points by field zone, gives scouts the same card for recording pests, diseases and weeds, and compares findings with economic thresholds. Unlike a general agronomist app, it sets the inspection method and checks that it is followed.
The inspection point card is the same for everyone: crop, BBCH stage, organism from the reference list and a measure such as count per plant or square metre, share of affected plants or a score. Reports from different scouts and fields become comparable.
The route follows field zones: areas where NDVI deviates, past hotspots, edges by shelterbelts and neighbouring fields, plus control points. The scout sees the route and covered points on the map.
The agronomy team sets economic thresholds by crop, stage and organism; as soon as a finding exceeds one, the chief agronomist gets a task with the point on the map and a photo, and the treatment decision stays with them.
Pheromone and sticky traps have their own cards with location and installation date; catch records by date show the flight dynamics of a pest across fields and signal when a threshold is getting close.
A crop health report by field, crop and week is built from inspection cards automatically: a hotspot map, organism dynamics, completed and missed inspections against the schedule, with no manual compiling.
The scouts' mobile app works offline; the web part is for settings, thresholds and reports.
Inspection frequency by crop and stage, fields split between scouts, and completion tracking: which fields were inspected this week and which were missed.
Inspection points based on NDVI zones, past hotspots and field edges; a route on the map with navigation from point to point and offline operation.
BBCH stage, organism from the reference list, a density or infection measure, a geotagged photo and a comment; required fields prevent closing a point without data.
Pests, diseases and weeds with photos and symptoms, and thresholds for every crop and stage that the agronomy team, not the developer, sets and changes.
A register of pheromone and sticky traps with coordinates, installation and lure replacement dates, catch records and a chart of flight dynamics by field.
A threshold breach creates a task for the chief agronomist with the field, points and photos; a follow-up inspection after treatment is scheduled automatically to check its result.
Crop health by field and week, hotspot maps and organism dynamics over the season and years, for the agronomist, management and clients if scouting is offered as a service.
Zones for routes come from satellite monitoring and the field map, and findings go to the agronomy software.
| criterion | Off-the-shelf scouting app | Crop scouting app by askcust |
|---|---|---|
| Inspection card | The provider sets the structure and measures; adapting them to your method is hard. | The card follows your agronomy team's method and changes between seasons. |
| Reference list and thresholds | The provider's reference list; your own thresholds by crop and stage are not always possible. | Your own reference list and thresholds for every crop, stage and organism. |
| Routes | The scout places points by hand, or the platform's algorithm does. | Based on NDVI zones, past hotspots and rules the agronomist sets. |
| Link to the agronomist | Notifications inside the app; tasks in other systems are handled separately. | A threshold breach becomes a task in the agronomy software with the point and photo. |
| Data | Inspection history is stored in the provider's service while the subscription lasts. | Hotspot and inspection history for all seasons stays in the farm's database. |
| When to choose | A few scouts, a standard method, no need for a separate system. | A team of scouts, your own method and thresholds, a link to NDVI and agronomy software. |
Together with the agronomy team askcust records what is inspected and how: crops, stages, organisms, measures, thresholds and frequency. The result is an inspection card and reference list that work even on paper.
Scouts test a prototype of the card and route on real fields: how long a point takes, what is unnecessary and what is awkward to enter with one hand.
An offline mobile app, routes by field zone, thresholds and tasks, and a web part for settings and reports; the first season runs on one crop or farm unit.
Connection to NDVI, the field map and the agronomy software, reference list and threshold updates before the season, and new crops and organisms under a support agreement.
examples of askcust's work →not agriculture, but the same kind of task: records, CRM, automation
An agronomist app is a tool for the whole working day in the field: fields, tasks, observations, work acceptance. A crop scouting app organises one process, regular crop inspection by a method: schedule, routes, identical cards and economic thresholds. Both can be combined in one app if the scouts and the agronomists are the same people.
Yes, the reference list belongs to the agronomy team: it sets and changes the pests, diseases and weeds with photos, symptoms and economic thresholds for every crop and stage. Initial content is imported from your spreadsheets or methodological materials; askcust does not substitute its own thresholds for the agronomist's decisions.
Yes, the scouts' mobile app works offline: fields, routes, the reference list and thresholds are downloaded in advance, cards and photos are stored on the phone and sent as soon as there is a network. The threshold check runs on the phone right away, so the scout sees a breach while still in the field, even without coverage.
Yes, areas where NDVI deviates from the rest of the field or from last year's dynamics become inspection points next to past hotspots and control points. An image shows where something is wrong but not what: the cause, whether a pest, a disease, water or nutrition, is established by the scout on the ground.
An economic threshold is the pest density or infection level at which control measures should be taken to prevent economic loss, that is, damage greater than the cost of control. Values depend on the crop, stage, organism and prices, so the agronomy team sets them; the software only compares findings with the threshold and raises a signal.
The cost depends on the number of crops and organisms in the method, the complexity of routes, integrations with NDVI, the field map and agronomy software, and whether scouting is offered to clients as a service. You can start with one crop on one farm unit; askcust estimates the first season with a fixed scope once the method is agreed.
A reply within one business day; a call only if we agree on one.