FAQ
Questions teams ask before a Sensorco pilot.
This page explains how Sunbul-Sensor, Mai-Sensor, the shared Sensorco platform, and the current pilot flow fit together. It is designed to answer the structural questions first so the next conversation can focus on deployment fit and measurable outcomes.
What this page covers
Sunbul-Sensor
Mai-Sensor
Platform
Pilot
If a question still needs more context after this page, the product pages and About page give the broader company and deployment story before the pilot conversation.
Company + platform
What Sensorco is building.
What is Sensorco building?
Sensorco is building a sensing and intelligence system that combines Sunbul-Sensor, Mai-Sensor, and one shared platform for dashboards, alerts, recommendations, and outcome review.
Is Sensorco only for agriculture?
The current site starts with precision irrigation and crop environments, but Mai-Sensor is also framed for broader liquid operations such as reservoirs, tanks, tankers, and transfer systems.
Is Sensorco a hardware company or a software platform?
It is both. The hardware captures the operating signals, and the platform is where teams monitor conditions, receive alerts, review trends, act on recommendations, and verify outcomes.
Products + fit
How the sensing layers differ.
What is the difference between Sunbul-Sensor and Mai-Sensor?
Sunbul-Sensor is the crop-side layer for plant and soil visibility. Mai-Sensor is the liquid-side layer for level, usage, flow, tracking, and broader liquid operations monitoring.
Do teams need both products to start?
No. A deployment can start with whichever sensing layer matches the operating question. Teams use both together when crop conditions and liquid behavior need to be reviewed in one operating picture.
What kinds of sites fit the first deployments?
The current site is framed around greenhouses, nurseries, high-value farms, reservoirs, tanks, tankers, and transfer systems where earlier visibility has real operating consequences.
Can Mai-Sensor be used beyond water-focused monitoring?
Yes. The current product framing positions Mai-Sensor for broader liquid operations depending on the deployment, not only for water-specific use cases.
Pilots + next steps
How the first pilot is meant to work.
How should a first pilot be scoped?
Start with one site question, one sensing direction, and one measurable success definition. That keeps the first deployment focused enough to learn quickly and structured enough to decide what should expand next.
What happens after the pilot brief is submitted?
Right now the site uses a structured local prototype flow. The brief is there to stage a better conversation and validate the intake structure while backend delivery is planned for a later phase.
What makes a strong success definition?
A strong success definition is specific and reviewable, such as earlier anomaly detection, clearer irrigation tuning, better refill planning, reduced loss, or verified improvement after an operating adjustment.
Can the current site support combined pilots?
Yes. The site already frames combined deployments as the right path when plant and soil signals need to be understood alongside liquid behavior in one shared operating picture.
Next step
Use the FAQ to get oriented, then move into a product review or pilot brief.
Use the FAQ as the orientation layer, then move into the product pages or the pilot brief once the deployment path feels clearer.