leafShift

Irrigation runs on one logic. Climate runs on another. The weather forecast lives somewhere else again, and the grower's own experience fills the gaps. Someone has to pull all of that into a single daily decision by hand. When that decision is even slightly wrong, water goes where it wasn't needed, crops are stressed where they shouldn't be, and quality, energy, and labour costs all drift in the wrong direction — on the most valuable land on the farm.

A budgeted cost, not a sustainability slogan

It is tempting to say "agriculture wastes water." That is true, but it is too broad to act on, and no one has a line item for it. The sharper, more honest problem is this: the data already exists, but it does not become coordinated action. That gap is expensive in money the grower already counts — water, pumping and cooling energy, labour hours, and lost crop quality — which is what turns it from an environmental talking point into an operating cost a buyer will pay to remove.

Two facts show why irrigation decisions carry so much financial weight:

Three stages — and the third one is still a person

Every farm operating decision moves through three stages: measure what is happening, predict what is likely to happen, and coordinate the best combined action. Most installed systems do the first stage well. Some do the second. Almost none do the third consistently, across mixed equipment from different vendors. That third stage — turning many signals into one coordinated action — is the job still done by a human, inconsistently, and it is exactly the gap LeafShift fills.

This is not just our view. PwC Middle East (2025) argues the central requirement in irrigation today is better integration across the operating system, not simply more technology. The U.S. Government Accountability Office (2024) found that the absence of common standards actively blocks interoperability between precision-agriculture tools. The pieces exist; the layer that makes them act as one does not.

Concretely, and to start: commercial greenhouse, hydroponic, and vertical-farming operators in the UAE and Saudi Arabia producing high-value fresh produce, who already run irrigation and climate systems. We go to the GCC first because that is where the operating problem is most intense and most funded, not because the region is generically "good for agtech."

Why this buyer — and not the farm that needs help most

LeafShift is a layer. It needs existing sensors, controllers, and data to coordinate. A low-tech farm has nothing to layer onto, so serving it would mean becoming a hardware installer first — which is slow, expensive, and destroys software margins. The operators we target have already done the hard part of buying and connecting equipment. We make that equipment finally act as one system.

The value also has to be large enough to clear an enterprise price, and that only happens where several costs stack up together. In UAE controlled-environment agriculture, cooling alone can account for 55–90% of a greenhouse's freshwater use (Fatnassi et al., 2023). That means water and energy decisions are physically linked — and coordinating exactly those linked decisions is what LeafShift does. So the value pool is the sum of water, energy, labour, and quality, not water alone.

Who signs, who uses, who pays, who blocks

Investors do not ask "who is the customer" so much as "who are the four people around the purchase." For LeafShift: the user is the head grower or operations manager; the payer is the operations director or owner; the blocker is usually the incumbent climate-computer relationship (the grower is locked into a Priva or Ridder system) plus a natural reluctance to trust an unproven system with control. Naming that blocker honestly — and designing around it with shadow mode and explainable decisions — is what makes this a real customer profile rather than a wish.

The category, for direction only

Independent estimates of the global precision-irrigation market cluster around US$5–9 billion in 2024–25, growing to roughly US$10–29 billion by 2033–35, at a high-single to low-double-digit annual growth rate. The research houses disagree on the exact numbers, which we show honestly rather than cherry-picking the largest. The relevant point is directional: this is a real, growing, multi-billion category — a ceiling worth aiming at, not a target we can claim.

There is also a specific regional tailwind. Saudi Arabia attracted over US$9.8 billion in private-sector investment into sustainable agriculture and food projects in 2024, under Vision 2030 — capital actively flowing toward exactly the modernisation LeafShift supports.

How we actually size it

We use a standard three-layer model, but we build the bottom layer from a real list, not a percentage of a report:

In words: the TAM is the global precision-irrigation and decision-software category above. The SAM is the slice of that we can actually serve at entry — medium-to-large CEA and high-value irrigated operators in the UAE and Saudi Arabia who have the infrastructure and budget to buy. The SOM is a countable list of those operators, multiplied by a realistic annual contract value (an implementation fee plus a subscription priced by managed area or number of zones), multiplied by a realistic multi-year adoption rate. Because the SOM is built from a named target-account list — the same 80–100 accounts we work in go-to-market — every euro in it can be defended account by account, which is exactly what an investor wants to test.

Three forces are arriving together, and each one is evidenced rather than asserted:

1 · The infrastructure is already installed

This is the quiet but decisive shift. Autonomous-growing software from Blue Radix already runs in 100 greenhouses across 17 countries, and Priva — whose climate computers LeafShift would sit alongside — operates in more than 100 countries with over 450 installation partners. The hardware and data layer we build on top of is now widespread. Five years ago the substrate for a decision layer barely existed; today it is everywhere our buyer operates.

2 · Water pressure is acute and funded

In the GCC this is not a future risk, it is a present, budgeted priority. Saudi Vision 2030 and the National Water Strategy make irrigation efficiency a national goal; the FAO and the Saudi Irrigation Organization had established 21 demonstration farms across the Kingdom by mid-2024; and precision systems are already cutting in-region water use by 20–60%. The buyers are actively modernising right now, with public money behind them.

3 · The expert grower is scarce

The whole autonomous-growing category is driven by the shortage of skilled, experienced growers — automation lets one grower manage several times more area. That scarcity is what turns a "nice optimisation" into an "operational necessity": when you cannot hire another expert, software that captures and scales expert decisions stops being optional.

Sequence: UAE first, Saudi second

We enter the UAE first because it is the denser controlled-environment and agritech hub, which means more target accounts close together and faster pilots. Saudi Arabia follows because its irrigation-modernisation programme is larger in scale — bigger contracts, but a longer sales cycle. The order is deliberate: prove the motion where it is fastest, then scale it where it is biggest.

What the customer actually experiences — five stages

We do not ask a grower to hand over control on day one. The product earns trust in steps, and each step produces the proof needed for the next:

Through all five stages the grower can always see why a decision was made. The physics baseline is explainable by its nature, and the machine-learning adjustment on top is attributed — you can see how much each factor contributed. That transparency is what earns a grower's trust, and it also keeps us aligned with European expectations on explainable AI from the start, rather than retrofitting it later.

Not autonomous on day one — on purpose

Handing full control to an unproven system would be a trust and liability mistake, and growers know it. Shadow mode solves this: LeafShift's recommendations run quietly alongside the grower's real decisions, so the farm keeps running exactly as before while we accumulate a daily, side-by-side record of which system would have done better. That record is both the sales proof and the raw material for the data moat described in the next section.

This is not just a slide — the core already runs

The architecture is not theoretical. In a separate applied-research project on a food bed in Beja, Portugal, we have already built and run the core LeafShift pattern in working software: a physics baseline (the FAO-56 crop-water-balance standard, implemented with a peer-reviewed, open-source library maintained by the USDA) plus a bounded machine-learning correction that learns each zone's local quirks and is capped so it can only ever adjust the physics by a small, safe amount. In a full-season simulation, that correction tracked soil moisture to well within sensor accuracy. This proves the architecture works end to end. It is validation infrastructure, not a customer deployment — and the numbers it produces are simulation results, not field-proven performance.

The loop is simple to state: every deployment produces proprietary field data; that data trains better, site-specific corrections; those produce measurably better decisions; better decisions win more deployments; and more deployments produce more data. The technology is the machine that turns customers into a performance advantage — it is the means to the moat, not the moat itself.

Two layers: physics first, then a bounded learner

The system has two layers, in a strict order. Layer one is a deterministic agronomic baseline — the FAO-56 crop-water-balance standard used by irrigation engineers worldwide. It calculates what each zone needs from first principles. It is transparent, explainable, and works on day one with no training data at all. Layer two is a machine-learning correction that learns the things the physics cannot know in advance: a particular bed's microclimate, a sensor that drifts, a neighbouring crop that shades it. Crucially, this correction is bounded — it can only nudge the baseline by a small, capped amount — and it is explainable, so every adjustment can be attributed. Physics always governs; the learner refines.

This ordering is the whole point. A pure "black box" that simply outputs an irrigation command is hard to trust, hard to audit, and a regulatory problem. A transparent physics baseline with a small, bounded, explained correction is trustworthy, auditable, and aligned with EU AI Act expectations by construction.

What is actually defensible — in order

We are honest about what is and isn't proprietary, because an investor will probe exactly here. The physics standard, the open-source library, and the machine-learning method are all public — and we say so proudly, because that is what makes the system explainable and trustworthy. The defensibility sits in four places, strongest first:

1 · The proprietary field-data loop. This is the same moat the serious incumbents actually have — their advantage is years of field data, not a secret algorithm. Ours is captured from day one through shadow-mode logging, drift detection, and continuous retraining, so the architecture is designed to accrue the moat rather than hope for it.

2 · Vendor-neutrality. The leading autonomous-growing products are tied to specific climate computers. A layer that coordinates across mixed infrastructure from different vendors — and picks the best goal per site, whether that is saving water, saving fertiliser, or deliberately stressing a crop to improve quality — is a structurally different and broader position.

3 · Deployment learning and workflow lock-in. The playbooks for installing, calibrating, and integrating into a grower's daily workflow become repeatable assets, and once LeafShift is the decision layer a grower trusts, the switching cost is high.

4 · Explainability as a regulatory moat. As connected, AI-driven control comes under closer regulatory scrutiny in Europe and elsewhere, a transparent, bounded, attributable system is compliant where a black box is not.