RAIN / Software

Define the use before the terms.

A starting point for discussing pilot scope, deployment responsibilities, software access, and future commercial arrangements.

Commercial scope to define

INTELLIGENCE BELONGS WHERE THE DATA LIVES.

01 / THE IDEA

Terms should follow a clear engagement.

RAIN has not published software pricing, license tiers, or production support commitments. A prospective pilot needs an agreed task, deployment boundary, responsibilities, and success criteria before commercial terms can be meaningfully defined.

01

Deployment scope

Describe the site, intended workloads, users, and evaluation period rather than assuming a standard package covers every use.

02

Data and responsibilities

Identify source ownership, permitted access, operating responsibilities, and how evaluation outputs will be handled.

03

Support and continuation

Discuss assistance during the pilot and what evidence would justify a later production arrangement.

02 / IN PRACTICE

Put the thinking into practice.

Define the scope, preserve the boundary, and make the outcome something a person can inspect.

  1. 01

    Describe the evaluation

    Specify the operational question, system boundary, and outcomes the participating team wants to assess.

  2. 02

    Clarify obligations

    Identify the access, infrastructure, people, and review effort each participant would provide.

  3. 03

    Agree written terms

    Document any actual engagement separately from the information and planning materials on this website.

03 / A FEW DETAILS

Worth understanding.

What does RAIN software cost?

Pricing and license tiers have not been published. Scope, deployment requirements, and support needs would inform a commercial discussion.

Does downloading a pilot brief start a subscription?

No. The website creates a local planning document. It does not submit an order, start a subscription, or establish a deployment agreement.

BUILD WITH RAIN

One site. One question.
A useful next step.

RAIN is preparing for its first field pilot. Start by defining the environment, the data boundary, and what success should look like.

Build your pilot brief