Pricing

Scope the work around the asset, not a generic seat count.

Osori is currently pricing evaluations and deployments directly. Cost depends on well count, data readiness, update frequency, modeling scope, and the level of engineering support required.

Evaluate

Product and data review

Confirm the operating problem, available production history, data quality, and the Osori workflow that best fits the asset.

Product walkthrough
Data-readiness discussion
No-cost initial conversation
Prove

Focused field pilot

Configure a limited field or well set to validate data mapping, surveillance workflows, and the engineering value of the results.

Defined well and data scope
Guided onboarding
Pilot pricing based on complexity
Operate

Ongoing deployment

Continue with field and well access, scheduled data updates, user roles, and support aligned to the operating team.

Tenant and field access
Refresh and support plan
Custom subscription quote
Quote inputs

What determines pricing.

A short data and workflow review establishes the implementation effort and avoids charging a small operator for enterprise scope it does not need.

01

Number of wells and fields

02

Source systems and data cleanup

03

History depth and refresh frequency

04

Users, roles, and field access

05

Forecasting or scenario scope

06

Onboarding and engineering support

Get a scope that matches your field.

Share the approximate well count, available data sources, and the production question your team needs to answer. Osori will respond with the appropriate next step.

Contact sales