Skip to content
AgriVaultData

Products

Systems we build, configured to each institution.

Six products share one operational record. They are deployed inside a programme — configured to its workflows, roles and administrative geography — rather than sold as standalone licences.

Product architecture

Five modules on one platform and one record.

Programmes deploy the modules they need. Every module writes to the same operational record, so nothing is re-keyed between them.

P1 · Shared platformAgriVault Operations PlatformIdentity, roles, approvals and audit for every module — one operational record from field capture to national reporting.
P1Flagship product

AgriVault Operations Platform

One operational record from field capture through district verification, county approval and national reporting.

The problem it addresses

Programmes run on parallel lists, maps and ledgers that no one can reconcile, so leadership sees activity weeks late and cannot trace a figure back to its source.

Record lineage

Sample

  1. Captured in the fieldField officer · offlineSynced
  2. District verificationDistrict agriculture officerVerified
  3. County approvalCounty officeApproved
  4. National consolidationProgramme teamPending

Workflow

  1. 01Captured in the field
  2. 02District verification
  3. 03County approval
  4. 04National consolidation

Capabilities

  • Approval chain from field to national level, with corrections and escalation
  • Role-based and geography-based access for every user
  • Append-only decision ledger and audit trail
  • Workspaces for field, district, county and national teams
Who uses it
Field officers · District agriculture officers · County coordinators · National programme teams · Auditors
Data in and out
CSV import for registries and ledgers · PDF and CSV exports
Deployment
Configured to the institution's administrative levels and rolled out in phases, starting with a defined area.
P2

Farmer Registry

Farmer and farm profiles registered in the field and verified by district reviewers.

The problem it addresses

Beneficiary lists are duplicated across programmes and cannot be verified, which undermines targeting and subsidy delivery.

Record lineage

Sample

  1. Farmer registeredField officer · assigned areaRegistered
  2. Profile completedField officerReady
  3. Profile verifiedDistrict reviewerVerified
  4. Eligible for programmeProgramme managerPending

Workflow

  1. 01Register
  2. 02Verify
  3. 03Approve
  4. 04Use in programmes

Capabilities

  • Farmer and farm profiles captured by field officers
  • District review and verification workflow
  • Bulk CSV import for existing registries
  • Registry exports
Who uses it
Field officers · District reviewers · Programme managers
Data in and out
Bulk CSV import · Registry exports
Deployment
Deployed with the Operations Platform or as the first module of a wider programme.
P3

GIS & Boundary Intelligence

Plot boundaries walked on the ground, measured, and tied to the farmer record.

The problem it addresses

Plot maps live in separate GIS files that are not linked to farmers, so area, location and eligibility cannot be checked together.

Record lineage

Sample

  1. Corners walkedField officer · GPSCaptured
  2. Outline closedArea estimatedMeasured
  3. Linked to farmerFarmer recordLinked
  4. Reviewed on the mapDistrict reviewerPending

Workflow

  1. 01Walk corners
  2. 02Close outline
  3. 03Link to farmer
  4. 04Review on the map

Capabilities

  • Walk-the-corners boundary capture with recorded GPS accuracy
  • Area estimation in hectares and acres from the captured outline
  • Boundaries linked to the farmer's field visit record
  • County and district geography for every record
Who uses it
Field officers · District reviewers · GIS and programme analysts
Data in and out
GeoJSON boundaries · Mapbox basemaps
Deployment
Boundaries are operational outlines for traceability — approximate, not cadastral survey.
P4

Warehouse & Traceability

Receipts, transfers and custody for inputs and produce, attributed at every step.

The problem it addresses

Stock ledgers are reconciled by hand, and transfers between facilities leave no trail that auditors or donors can follow.

Record lineage

Sample

  1. Transfer requestedWarehouse managerRequested
  2. Transfer approvedCounty coordinatorApproved
  3. DispatchedOrigin warehouseIn transit
  4. Delivery confirmedReceiving warehousePending

Workflow

  1. 01Receive
  2. 02Request transfer
  3. 03Approve and dispatch
  4. 04Confirm delivery

Capabilities

  • Warehouse registry and stock records
  • Transfer lifecycle: requested, approved, dispatched, in transit, delivered
  • Scoped access for assigned warehouse managers
  • Discrepancy and dispute recording
Who uses it
Warehouse managers · County coordinators · National logistics teams
Data in and out
Ledger CSV import · Custody and transfer exports
Deployment
Rolled out facility by facility alongside the programme's input distribution cycle.
P5

Reporting & Executive Intelligence

County, national, donor and executive reporting generated from the operational record.

The problem it addresses

Quarterly reports are compiled from re-keyed spreadsheets and cannot be traced back to what happened in the field.

Record lineage

Sample

  1. Approved recordsOperational recordApproved
  2. Scoped to roleCounty viewScoped
  3. Report generatedProgramme reportGenerated
  4. ReviewedProgramme leadPending

Workflow

  1. 01Approved records
  2. 02Scoped report
  3. 03Export
  4. 04Review

Capabilities

  • Executive, compliance, donor and programme reports
  • PDF reports and CSV exports
  • Reports generated on demand from the operational record
Who uses it
National leadership · Programme managers · Development partners · Auditors
Data in and out
PDF reports · CSV exports
Deployment
Report sets are agreed during design and generated on demand from the live record.
P6

Offline Field Operations

Capture that keeps working without coverage and syncs when it returns.

The problem it addresses

Field teams work where connectivity is intermittent; paper fills the gap and is re-keyed weeks later — if at all.

Record lineage

Sample

  1. Captured offlineField officer · no coverageQueued
  2. Held on deviceCapture queueHeld
  3. Connection returnsDeviceSyncing
  4. Synced for reviewDistrict reviewerPending

Workflow

  1. 01Capture offline
  2. 02Queue on device
  3. 03Reconnect
  4. 04Sync and review

Capabilities

  • Installable field app with an offline capture queue
  • Queued records sync when the connection returns
  • Queue status visible to the officer
Who uses it
Field officers · Extension teams · District supervisors
Data in and out
Installable web app (PWA)
Deployment
Designed for intermittent coverage and shared devices from the first day of deployment.

See the products in the context of your programme.

We walk through the workflows that matter to your institution — registration, verification, custody or reporting — rather than a generic demo.

Start a conversation See engagement models