IBM Agriculture Global

SupPlant

Real-time Analytics

SupPlant needed to make its irrigation intelligence accessible to smaller farms that could not afford in-field hardware while still delivering personalized, actionable agronomy guidance at scale.

500-1,000 new users joining every day
80% user satisfaction rate
Around 50,000 farmers worldwide

Reported impact

Business outcome

SupPlant launched a lower-friction digital agronomy service that expanded reach to tens of thousands of farmers, increased engagement and supported crop productivity without requiring sensor installation.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

SupPlant used IBM technology to turn its crop and irrigation knowledge into a sensor-less digital agronomy service called Plant ;). The company already had proprietary algorithms and a large agronomic datastore, but it needed a delivery model that would work for farms without field sensors or large technical teams. SupPlant selected IBM watsonx Orchestrate together with DataStax Astra DB within IBM watsonx.data to coordinate the new service. Satellite imagery, weather context and SupPlant’s existing agronomy data are combined to produce personalized irrigation guidance, twice-weekly recommendations and ad hoc alerts for plant stress or extreme weather. The system also supports interactive follow-up from farmers, extending the experience beyond static advice and helping SupPlant scale digital guidance to a much broader market of small and mid-sized farms.

Data flow

Satellite images, weather context and SupPlant’s existing agronomy data flow into the watsonx.data foundation and Astra DB, where orchestrated workflows generate personalized irrigation recommendations, alerts and follow-up interactions for farmers.

Solution architecture

3 components · 2 layers
  1. Storage
    • IBM watsonx.data Provides the data foundation for storing and retrieving the information used by Plant ;).
    • DataStax Astra DB Stores the application’s data so personalized recommendations and alerts can be generated at scale.
  2. Orchestration
    • IBM watsonx Orchestrate Coordinates the workflows that turn SupPlant’s agronomy data and satellite signals into personalized farmer guidance.

Architecture clues

  • Built on SupPlant’s existing proprietary algorithms and datastore
  • Designed specifically for small and medium-sized farms without field hardware
  • Plant ;) delivers recommendations twice a week plus ad hoc alerts

Evidence from the source

Plant ;) uses satellite images of plots to give farmers personalized weather and irrigation information twice a week, as well as ad hoc alerts for extreme weather and plant stress.
SupPlant selected IBM® watsonx Orchestrate® and IBM DataStax® Astra DB within IBM watsonx.data® as the basis for its new offering, called Plant ;).
Today, around 50,000 farmers worldwide are using Plant ;), and SupPlant is seeing 500-1,000 new users joining every day.
Transparency Evidence & methodology 100/100 reference value · 84% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence84%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    SupPlant customer story

    First-party
    https://www.ibm.com/case-studies/supplant
    Source type
    Vendor-published customer story
    Published
    Feb 26, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.