One operational view across farms, fields and teams
Agribusiness managers need consistent records across estates without giving everyone access to every parcel. Mothmr connects parcel boundaries, crop seasons, monitoring history, assigned work and verified completion in one workspace. Integration options depend on the customer's configuration.
How it works
- 01
Unify field records
Import parcels and keep field history, crops, seasons and reporting together.
- 02
Control who sees what
Assign roles and parcels to supervisors and crews, then follow open work and exceptions.
- 03
Review and integrate
Use reports and documented job evidence for oversight; discuss partner API access during onboarding.
What it covers
All your fields, as a list and a map
Search fields by name, reference or crop and filter by crop, or find them on an interactive map. Totals show how many fields and how much area you hold, which already have imagery and which are awaiting their first image. Each field shows its crop and stage, its open tasks and attention items, and its latest satellite reading with its date and the share of the field it could assess.
One record for each field
Overview, Weather, Crop monitoring, Satellite analysis and History — with Field sensors when a device is connected — keep the field’s name, crop, stage, area and season in view on every tab. The overview gathers today’s advice, what needs attention, headline readings and the weather; the history sets the work, its evidence, the satellite passes, recent weather and the season in date order, so a handover starts from what actually happened.
Records you can take away
A report for each field and season — its details, satellite record, weather, work, evidence and attention history — and ten organization reports: crop summary, workforce, portfolio health, supervisor workload, task completion, overdue and blocked work, shift performance, attention response, season progress and parcel exceptions. Download CSV, or print and save as PDF from the browser. Every report carries the parcel scope of whoever asked for it, so nobody downloads a field they could not open.
A home screen for each role
A grower’s home opens on their land and today’s priorities; an owner’s on activity across the organization; a supervisor’s on their fields and the work awaiting review; a worker’s on their own tasks. Due, overdue and blocked work stands out, field priorities come with their reasons, and every figure opens the list of tasks behind it.
Roles, and the fields behind them
An organization workspace holds administrators, supervisors, field workers and viewers, each one scoped to named parcels. A supervisor sees the fields assigned to them and a worker sees the tasks assigned to them — decided on the server, never by hiding a button.
Assignments, crews and workload
Assign a job to one or more people, a crew and a responsible supervisor while seeing what each person already has outstanding. Queues for due today, overdue, blocked and awaiting review sit beside the day’s shifts and the fields they cover, with workload by crew, supervisor or crop. Overlapping assignments and shift conflicts are flagged, and going ahead anyway records the reason. These are counts of recorded work, not hours or payroll.
Evidence from where the work happens
Notes, photos previewed before they are sent, files, measurements with their units, quantities and checklists — and, only with the worker’s consent, the current location. The task shows which required proof is attached and which is still missing, and cannot be completed until it is all there; the supervisor then reviews it beside the original instructions.
Partner API
For customers who work through an integration, a versioned API with scoped credentials reads fields, satellite observations, weather, advice, activity, reports and operational figures, and accepts field imports, seasons, periods, shifts, tasks and attention items. Signed webhooks report tasks, attention, weather, observations and shifts, retrying a bounded number of times. Provisioned with your team; access stays within the organization and its fields.
Questions
A useful tool should be clear about what it can do, and where your judgement still matters.
Can I bring my existing fields?
Yes. Draw boundaries on the map or import CSV, GeoJSON, KML or KMZ files. Review the proposed parcels before saving them. Each new field enters its own processing queue.
Who can see my fields and tasks?
Access follows workspace membership, role and assignment. Supervisors see their assigned fields, and workers see the tasks assigned to them. Organization access is configured with your team.
How do we discuss pricing?
There is no published price list yet. For a team pilot, we agree the fields, workflow, duration and scope with you before discussing the price. Tell us what you need through the enquiry form.
See it on your own fields
Tell us about your farm and the work you want to coordinate, and we will plan a demonstration around your fields and roles.
Request a demo