Products
FuroField
Crop enterprise and value-chain management: fields and crop cycles, agronomy with automatic spray holds, season planning, outgrower registries, input credit, harvest lots, offtake and the evidence a buyer or auditor asks for.
01
Built crop-first
Not a livestock system with crops bolted on, and not a generic ERP with an agriculture skin. The unit of work is the block and the season, and the calendar is the crop's.
02
What the record actually holds
A block and a season, and everything either of them carries. An application records the product, the rate and the person who chose it, and starts the interval that follows from it. A harvest is weighed and graded into lots that still name the block they came from. A delivery is netted against the advance that funded it, and a settlement is paid with a statement the grower can read.
None of that is a report built afterwards. It is the operating record of the season, which is why an evidence pack can name what it rests on: a tonnage is the weighbridge entry that produced it, and a product and dose is the application record and the person who chose it.
03
What is not built on the crop side
The honest half. A buyer comparing products should be told this before a security review tells them, and it is the same list published on the obligations page rather than a softened version of it.
- A due diligence statement, for cropNot yet — Not built. The statement's subject today is an animal or a batch — the deforestation work sits on the livestock side and there is no crop equivalent.
- Lot custody and the audit pack, end to endPartial — Lot custody rides the shared workspace register, so two handsets do converge — but it is an untyped store: no custody check that a lot's harvest records exist, no code uniqueness across a tenant, no void history, and no audit trail. The typed route is built and deployed; the client half that would use it is not. Stated the same way on who the platform serves.
- A SIZA exportNot yet — Nothing is built. SIZA appears on this site as industry context, and context is not a capability.
- Issuing a certificate, or a determination that an audit is metRefused — Certificates come from accredited bodies. A system of record that certifies its own output is worth nothing to the party relying on it.