Pilot design

Start with one operating question and one measurable outcome.

A strong Sensorco pilot starts with a clear site question, the right sensing layer, and a review plan that shows what should be measured and what success should look like. This page turns that conversation into a more usable brief.

Begin the brief Review the products

Clear deployment fit Decide whether the first pilot is crop-side, liquid-side, or a combined deployment. Match the question first

Measured pilot objective Define what the team wants to detect, understand, reduce, or improve before rollout. Built for review, not guesswork

Review-ready outcome plan Set how the pilot result will be checked, discussed, and used to decide what expands next. Designed for accountable follow-through

Pilot framing checklist

Choose the deployment model Select Sunbul-Sensor, Mai-Sensor, or a combined pilot based on the operating question. Fit first, not hardware volume first

Define the pilot question Clarify what the team wants to detect earlier, tune better, monitor more clearly, or verify with evidence. Make the brief decision-ready

Set the site scope Start with the zones, lines, reservoirs, tanks, or mobile assets that matter most right now. Keep the first pass focused

Plan the review loop Agree on what will be measured, how often it will be reviewed, and how the outcome will be judged. Close the loop with evidence

Sunbul-Sensor Mai-Sensor Platform Review

The best first pilots are narrow enough to learn quickly and structured enough to answer what should stay, change, or expand next.

Pilot fit

Built for crop-side pilots and liquid-side pilots with real operating stakes.

Sensorco fits sites where plant response, soil condition, liquid behavior, or asset status can materially affect yield, quality, labor, uptime, refill planning, or preventable loss.

Greenhouses

Controlled environments that benefit from earlier crop and irrigation signals.

Strong fit when teams need better visibility into plant condition, soil behavior, and irrigation tuning across actively managed growing zones.

Nurseries

Propagation environments where consistency matters every day.

Useful when irrigation performance, plant response, and zone-to-zone consistency need to be read more clearly across active production batches.

High-value farms

Sites where earlier signals can protect quality, timing, and input efficiency.

Strong fit when irrigation decisions need more context and pilot learning needs to translate into repeatable operating improvements with measurable field relevance.

Liquid operations

Reservoir, tank, tanker, and transfer environments that need cleaner oversight.

Valuable when level visibility, flow review, asset tracking, abnormality detection, or refill planning can reduce reactive work and prevent avoidable loss.

Pilot path

Keep the first pilot simple enough to move and specific enough to prove value.

A strong first deployment should answer a real operating question, make the site easier to read, and end with a clearer decision about what should expand, change, or stay focused.

01

Align on the question

Choose the site challenge that matters most and define what the pilot is expected to clarify.

02

Instrument the right layer

Deploy Sunbul-Sensor, Mai-Sensor, or both together based on the question instead of over-scoping the first pass.

03

Review measurements and actions

Use the shared platform view to review trends, alerts, recommendations, and the operating response they triggered.

04

Decide the next rollout

Translate the pilot result into a clearer deployment decision, not just a one-time insight or interesting chart.

Pilot brief

Share the site, the question, and the success definition.

This intake is designed to capture who is involved, what is being monitored, what the pilot should measure, and how the result should be reviewed if the pilot works.

Stage the pilot brief

Fill in the core details below to define the pilot scope, sensing direction, measurement plan, and review goal.

Full name

Organization

I am reaching out as

Work email

Site type

Pilot focus

Priority zones, assets, or areas in scope

What should the pilot measure or make more visible?

How should the pilot be reviewed?

Current operating challenge

What would make the pilot feel successful?

Preferred timeline

Current local prototype: this form validates and confirms the pilot brief flow in the demo. A real inbox or CRM delivery step can be connected in the next pass.

What to include

Helpful detail for a strong first conversation.

The clearer the starting brief, the easier it is to scope a pilot that produces usable learning instead of broad but ambiguous monitoring.

The zone, line, tank, reservoir, or mobile asset that matters most right now
Whether the priority is crop visibility, liquid monitoring, or a combined operating picture
Which measurements need to be monitored, reviewed, or verified during the pilot
The operating decision the team hopes to make faster or with more confidence
How success will be reviewed at the end of the pilot cycle

Need more context?

Choose the sensing story first, then return to the pilot brief with more clarity.

If the deployment path is still unclear, review the product pages first and decide whether the pilot should focus on plant and soil visibility, liquid monitoring and tracking, or both layers together.

See Sunbul-Sensor See Mai-Sensor