The crown jewel: built for a 2GB Android, bright sunlight and one thumb.
The agent app assumes the hardest conditions fieldwork offers — cheap hardware, glare, no signal — and stays out of the agent's way. One primary action per screen.
Offline is the default, not the fallback.
Every visit saves locally the instant the agent taps Save, and is designed to sync in the background when signal returns. Sync state is shown honestly on every record — saved on device, syncing, synced — never faked.
Background sync engine ships with the pilot Android build coming with the pilot
A visit can always be saved.
Every capture field is optional. Missing data lowers the suggested trust score — it never throws an error, and it never traps an agent in a form while a farmer waits.
The commission loop.
Agents earn a flat $9 for every visit the back office verifies. Quality pays, not volume — flagged work earns nothing, so the incentive points at good evidence.
Weekly payouts via bank or mobile money coming with the pilot
The boundary walk
The agent walks the farm's perimeter while the polygon draws itself, vertex by vertex. This shape is the export asset: the geolocation EU buyers are now required to hold.
6.6672, 9.1582 · 5 points · 1.9 haThe queue is the job.
The back office opens straight onto the review queue — pending visits, oldest first, each with everything the agent captured and a trust score suggested from the evidence. Verify or flag with the proof in front of you.
The trust score is computed, then confirmed by a human.
Every visit starts at a base of 40 and earns points per piece of evidence: +15 GPS point, +15 boundary polygon, +10 photos, +10 soil, +5 harvest, +5 farmer linked. A score of 80 or above earns Grade A. Nothing is verified because someone says so.
Verify & list lot · Verify only · Flag for re-visit.
Verify & list lot turns a captured harvest into a marketplace lot in one click, at a suggested price from the crop's farm-gate rate. Verify only confirms the farm without listing. Flag sends weak evidence back to the field.
Missing consent is impossible to miss.
When a farmer has no valid consent on file, the review card carries an amber NDPA warning before anything reaches buyers.
Hard consent gate before listing coming
Verified farms
The registry behind the marketplace: every verified farm with its trust ring, crops, size, verified date, GPS and polygon preview — plus a running count of EUDR-ready polygons.
Sales & wins
Completed GMV against pipeline, lots sold and reserved, and one-click "Mark sold" on reserved lots. Marketplace value by state:
Agents
Per-agent visits, verified count, quality rate (verified vs flagged), commission accrued and last active — the roster that keeps field quality honest and pays the people earning it.
A marketplace where every lot is already proven.
Buyers see verified lots only — nothing pending, nothing flagged. Each card carries the crop, state, trust ring, quantity, grade and price. What it never carries is the farmer's identity.
Initials and a state. Nothing else.
The farmer appears as initials ("Farmer B. E.") with a state — never a name or phone number. GPS is shown as "on file"; coordinates are never displayed to buyers.
The lot detail is the page that sells trust.
Quantity, grade and price tiles; quality notes; the boundary polygon with its EUDR note; and a custody timeline — documented, verified, listed — each step with the actor and the time.
Reservations are free and non-binding.
A buyer reserves a lot to open the conversation; the trade desk arranges inspection, payment and logistics offline.
In-app escrow payments coming with the pilot
Consent is captured from the farmer — never assumed for them.
Under Nigeria's Data Protection Act, the farmer's data is the farmer's decision. The agent can help and translate, but can never tick the box on the farmer's behalf. Consent lives on the farmer record and is updated across visits.
In the farmer's language
The agent reads or plays the privacy notice in the farmer's own language before any farm data is captured.
Recorded in-app audio scripts in development
Three answers, all respected
The farmer decides — and "not yet" is the safe default. A declined farmer's data is not processed.
Suppression list for declines in development
Two separate permissions
Marketplace visibility and international buyer visibility — a cross-border transfer under NDPA — are asked, and stored, separately.
☑ Listing may be visible to buyers outside Nigeria
Evidence, automatically
Every consent record carries its own proof, captured without extra work for the agent:
timestamp · agent ID · GPS · language · methodHard consent gate before any listing coming — today the office sees a soft amber warning.
Every boundary walk is an export asset.
The EUDR requires geolocation for every cocoa plot entering the EU — polygon boundaries for plots larger than 4 hectares — from 30 Dec 2026 for large and medium operators, 30 Jun 2027 for SMEs. HarvestCalc agents walk the polygon on the first visit regardless of plot size, so verified lots already carry the strongest geolocation exporters can be asked to produce.
EUDR export bundle in development
One click per lot: the GeoJSON boundary plus the full evidence pack — the artifact exporters pay for. The data model is polygon-ready today; the bundle generator ships next.
GeoJSON · photos · timestamps · reviewer identityWalk through it yourself.
The demo is the working product — open all three doors, document a visit, verify it, and watch it appear on the marketplace.
Free demo · role-card login, no signup · agent, back office and buyer views included