Field Trial
A paid evaluation around one decision and a limited asset collection.
- Data-readiness review
- Agreed workflow and baseline
- Representative evaluation cases
- Reviewable findings and outcomes
- Expansion or stop recommendation
A scoped pilot should establish whether Neuriya improves one recurring decision. Pricing follows the workload, data, and delivery obligations—not an undefined token count.
Define the customer, asset scope, decision owner, current workflow, and operational constraints.
Review data suitability, rights, historical coverage, and independent verification options.
Document the baseline, representative cases, acceptable errors, review effort, and decision criteria.
Compare findings and costs against the current process. Choose whether to expand, revise, or stop.
A paid evaluation around one decision and a limited asset collection.
A proposed recurring subscription for a validated workflow across an agreed portfolio.
A proposed deployment path for requirements that need a specific architecture or operating model.
| Component | Possible pricing basis | What to clarify |
|---|---|---|
| Platform workflow | Subscription for an agreed scope. | Sites, users, workflow, and standard support. |
| Processing | Scenes, area, jobs, or another defined unit. | Sensor dimensions, frequency, volume, and reprocessing. |
| Imagery | Supplier licensing or customer-provided data. | Access, commercial rights, coverage, and acquisition cost. |
| Integration | Defined implementation work. | Systems, formats, identity, and maintenance obligations. |
| Specialist work | Agreed review or validation effort. | Domain expertise, fieldwork, and ground-truth collection. |
| Dedicated deployment | Architecture and infrastructure scope. | Isolation, regions, resilience, and support commitments. |
Explore the value of time reclaimed from manual review. Change every assumption to reflect your own operation.
18 review hours potentially reclaimed
24 sites × 3 hours × 25% × $65/hour.
A planning estimate, not measured savings, cash savings, or a return-on-investment guarantee. Reclaimed time creates value only if it can be used productively.
Would the reviewer choose a more useful next step? Compare against the existing process with independent expertise.
Measure time per case and the number of alerts requiring investigation. A faster interface does not automatically produce a better decision.
Include imagery, processing, integration, review, fieldwork, and support. Evaluate recurring value against the complete recurring cost.
The product is a concept and the delivery requirements have not been validated. Publishing precise prices before defining imagery, processing, and specialist costs would create misleading expectations.
Yes. The local browser demo requires no account or payment. Its synthetic data demonstrates interaction rather than a commercial AI service.
That would depend on the proposal. Customer-provided imagery and externally licensed observations have different costs and permitted uses.
No unlimited compute promise is made. A production proposal should define workload, processing limits, overages, and service obligations.
The pilot should produce an honest decision: expand, revise the scope, or stop. Evaluation criteria and evidence requirements should be agreed beforehand.
Start with one recurring decision, the data you already have, and a result you can independently verify.
No account required for the demo. No real-world actions are executed.