Fieldin

Fieldin sells an operational system for commercial growers rather than a narrow crop-imaging or input-recommendation product. Its platform connects tractors, sprayers, harvesters, shakers, trucks, ATVs, implements, operators, and field tasks. The company installs smart sensors on existing machinery, including older or mixed-brand equipment, and uses signals such as location, speed, working pace, power-take-off activity, electric-valve activation, implement tags, and optional operator identifiers to distinguish actual work from movement or idling. The cloud application provides a centralized view of equipment and tasks, mobile access for field teams, reporting, alerts, service tracking, and performance benchmarks. This retrofit and integration layer is useful where replacing machinery is uneconomic and where the main management problem is execution visibility rather than a lack of another agronomic model.

The target market is permanent-crop and other high-value agriculture with geographically distributed blocks, seasonal labor, expensive equipment, and strong pressure to document irrigation, spraying, harvesting, and sustainability practices. Fieldin's current site names crops including nuts, wine grapes, citrus, berries, apples, and stone fruit, and reports more than 750,000 acres managed; those are company-reported figures rather than independently audited metrics. Customer materials describe use cases such as remote irrigation monitoring, shift planning, coverage analysis, missed-row or double-spray detection, labor accountability, and fleet-health tracking. A published Zirkle Fruit case study describes real-time monitoring of four-wheelers across a 1,200-acre orchard, while the company's site presents customer-reported productivity outcomes. These examples support practical workflow value, but diligence should separate customer testimonials and marketing claims from contracted recurring revenue, gross retention, and verified savings.

Competition comes from three directions: OEM platforms such as John Deere Operations Center and CNH AFS, broad farm-management suites such as Trimble Ag Software and Climate FieldView, and regional telematics, dispatch, or custom-development providers. OEM systems can offer deeper machine integration and distribution, but are less attractive to farms with mixed fleets or older implements. Broad suites can have more agronomic, financial, or imagery features, while Fieldin's differentiation is the operational detail of what work was performed, by which machine and operator, where, and for how long. That advantage depends on sensor reliability, installation quality, field-service coverage, and the platform's ability to become embedded in seasonal routines. The hardware-plus-services deployment model can create implementation friction and support cost even when software margins are attractive.

The commercial evidence is meaningful but dated in places. Fieldin announced a $30 million Series B led by Fortissimo Capital in September 2021, bringing publicly reported total funding to $55 million, and stated at that time that its system was deployed at five of California's ten largest farms and touched more than 20% of global almond production. The company continues to present active offices or teams in Fresno, Tel Aviv, Yokneam Illit, and Mildura and maintains a live careers and product presence. Those signals support classifying Fieldin as an independent mid-stage startup, but they do not establish current valuation, runway, profitability, customer concentration, churn, or whether the business has raised since 2021. Priority diligence should request current acreage, paid deployments, annual recurring revenue, hardware replacement rates, implementation payback, data ownership terms, and evidence that usage expands beyond a single crop or workflow.

Fieldin has credible but limited dual-use relevance. Its core capabilities—asset telemetry, geospatial activity logs, operator/task accountability, mixed-fleet integration, anomaly alerts, and maintenance-oriented reporting—map to unclassified fleet logistics, base-operations support, disaster-response equipment management, and contractor oversight. However, the product is optimized for agricultural workflows and field connectivity, and public sources provide no evidence of defense customers, secure deployments, export-control work, ruggedized hardware, or classified-system integration. Any defense opportunity would therefore be an adaptation or channel hypothesis, not current traction. Secure communications, cyber hardening, offline operation, identity and access controls, supply-chain assurance, formal testing, and procurement integration would be prerequisites. The strategic case is strongest as an Israeli-founded operations and IoT asset with logistics adjacency, not as a defense company.