PILOT PATHS / SCOPE & VALUE

Start with a question.
Earn the next phase.

A scoped pilot should establish whether Neuriya improves one recurring decision. Pricing follows the workload, data, and delivery obligations—not an undefined token count.

01 / YOUR FIRST PILOT

A bounded commitment.
A useful answer.

01

Choose the decision

Define the customer, asset scope, decision owner, current workflow, and operational constraints.

02

Check the evidence

Review data suitability, rights, historical coverage, and independent verification options.

03

Agree the evaluation

Document the baseline, representative cases, acceptable errors, review effort, and decision criteria.

04

Review the result

Compare findings and costs against the current process. Choose whether to expand, revise, or stop.

Pilot scope, delivery schedule, fees, and production terms would be agreed in a proposal. No paid service is purchased through this website.
02 / PROPOSED ENGAGEMENT PATHS

From evaluation
to an operational loop.

PATH 01

Field Trial

A paid evaluation around one decision and a limited asset collection.

SCOPED PROPOSAL
  • Data-readiness review
  • Agreed workflow and baseline
  • Representative evaluation cases
  • Reviewable findings and outcomes
  • Expansion or stop recommendation
Scope a field trial
PATH 02

Portfolio Loop

A proposed recurring subscription for a validated workflow across an agreed portfolio.

SUBSCRIPTION + DEFINED USAGE
  • Agreed sites and observation cadence
  • Repeatable review workflow
  • Budget and priority settings
  • Operational handoff design
  • Usage and outcome reporting
Discuss portfolio scope
PATH 03

Dedicated Orbit

A proposed deployment path for requirements that need a specific architecture or operating model.

CUSTOM DEPLOYMENT SCOPE
  • Data residency assessment
  • Identity and integration requirements
  • Deployment boundary design
  • Retention and resilience planning
  • Separately agreed support terms
Describe requirements
03 / COST DRIVERS

Know what you are paying for.

ComponentPossible pricing basisWhat to clarify
Platform workflowSubscription for an agreed scope.Sites, users, workflow, and standard support.
ProcessingScenes, area, jobs, or another defined unit.Sensor dimensions, frequency, volume, and reprocessing.
ImagerySupplier licensing or customer-provided data.Access, commercial rights, coverage, and acquisition cost.
IntegrationDefined implementation work.Systems, formats, identity, and maintenance obligations.
Specialist workAgreed review or validation effort.Domain expertise, fieldwork, and ground-truth collection.
Dedicated deploymentArchitecture and infrastructure scope.Isolation, regions, resilience, and support commitments.
04 / TRANSPARENT ASSUMPTIONS

Estimate the opportunity.
Then measure it.

Explore the value of time reclaimed from manual review. Change every assumption to reflect your own operation.

ILLUSTRATIVE MONTHLY CAPACITY VALUE
$1,170

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.

05 / SUCCESS MEASURES

Agree what “better”
will mean.

UTILITY

Decision quality

Would the reviewer choose a more useful next step? Compare against the existing process with independent expertise.

EFFORT

Review workload

Measure time per case and the number of alerts requiring investigation. A faster interface does not automatically produce a better decision.

ECONOMICS

Delivery cost

Include imagery, processing, integration, review, fieldwork, and support. Evaluate recurring value against the complete recurring cost.

06 / COMMON QUESTIONS

A clear scope beats
a vague promise.

Why are there no fixed prices?

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.

Is the interactive demo free?

Yes. The local browser demo requires no account or payment. Its synthetic data demonstrates interaction rather than a commercial AI service.

Would imagery be included?

That would depend on the proposal. Customer-provided imagery and externally licensed observations have different costs and permitted uses.

Is throughput unlimited?

No unlimited compute promise is made. A production proposal should define workload, processing limits, overages, and service obligations.

What if the pilot does not establish value?

The pilot should produce an honest decision: expand, revise the scope, or stop. Evaluation criteria and evidence requirements should be agreed beforehand.

YOUR NEXT MOVE

A smaller first step.
A stronger next one.

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.