AgroNutikas — field record, evidence and compliance risk in one workflow
A field-entry, evidence and rule-checking pilot for Estonian farmers. The 36-rule check and offline use are under pilot validation.
| Type of evidence | Pilot of a studio product. The studio's own product: product lead, design system and software. |
|---|---|
| Whose problem it illustrates | An Estonian farmer whose field records, evidence and rule checks live in different places. |
| What it does not prove | The public introduction site responds; the product itself is in a pilot. Pilot results are not yet evidence of wider use. |
| What you can order from this | Product build · from 12,000 € |
Problem
An Estonian farmer must keep a field record, hold evidence for PRIA inspections and know which job breaks which rule — usually on paper, in Excel or from memory. The mistake surfaces at inspection time, not at the moment of work. Public sources disagree on the Põltsamaa pilot's area and parcel count, so we do not present them as current verified metrics.
System
The AgroNutikas pilot is shaping a field-entry, rule-checking and evidence workflow. According to its public product overview, the 36-rule risk check (20 standard and 16 organic) and offline storage are under pilot validation; the official PRIA/X-tee integration and server-side storage are on the roadmap. The v8.1 rules and V9 pilot screens shown here therefore describe design and pilot work, not verified production behaviour. Mati, the WhatsApp assistant, and the accounting app are related product parts; evidence of their current operating scope must be checked separately.
Decisions
Offline-first, not offline-later — sync is architecture, not a feature. WhatsApp before a custom app — the farmer is already there. Design System V8.1 with Estonian-named tokens (rukkilill, mets, talinisu, oht, muld) so that design and domain speak the same language. Internal design work on the mobile quick-log addressed draft resumption, sync-state clarity, photo context, field-switch data loss and GPS overlay blocking; this is not presented as a public usability-test result. Development runs on Swarm24 — a round-the-clock autonomous engineering swarm.
Metrics
The pilot area and parcel counts conflict across sources; a current metric needs original data, date and definition confirmed. Investor-facing UX audits of agronutikas.ee scored 57/100 across twelve dimensions (source: 2026 audit) and surfaced contradictory funding figures between language versions — fixed before the pilot. Planned: Estonian voice input (Q1 2027) and a fertility score from satellite, soil and weather data (Q4 2026) — both in development, not shipped.
Stack
Next.js + Vercel (web, app, admin, accounting), Railway (Mati), Neon Postgres, Meta Cloud API, Design System V8.1, Swarm24 (Claude Code + Codex CLI, ClaudeOnly 6+6).
Related design system
AgroNutikas Design System v9.0 — Keep field and office workflow states understandable across surfaces.
Product screens
Product screens from the AgroNutikas pilot build (Design System V9 package). Unlike the marketing-site screenshot above, these are not regenerated on every release — a date is shown where it is known.
A product for your field, built the same way
You need a custom application with a separately agreed scope.