Prove one work-package flow
Start with one inspection, maintenance, closeout, service order, or reporting process and configure Oculi around the unit of work your team already delivers.
Price the field work being delivered, not the people logging in
Oculi pricing is quote-based and aligned to work packages, inspections, service visits, closeout packages, recurring reports, and program scale, rather than making every login the main pricing driver.
Quote-based pricing aligned to recurring field work
We review the unit of work, reporting outcome, operational volume, and rollout requirements. That keeps the quote tied to the work being delivered while field crews, reviewers, and stakeholders can collaborate.
Scale by work packages, sites, and reports
Expand across recurring visits, sites, reporting packages, and operational roles while keeping usage aligned to the work completed.
Match larger programs to reporting and rollout requirements
Support larger workflows with custom reporting, integrations, governance, exports, and rollout planning tied to program scale.
What affects an Oculi quote
| Factor | What we review | Why it matters |
|---|---|---|
| Workflow scope | Operations and maintenance (O&M) workflows—such as preventive maintenance visits and inspections—plus closeout packages, service orders, safety observations, or other field records | The unit of work determines how forms, statuses, review steps, and reports should be configured |
| Volume and cadence | Work packages, sites, recurring visits, reports, and program growth expectations | Pricing can scale with operational usage instead of seat count alone |
| Reporting needs | Client templates, evidence requirements, photos, open items, approvals, and exports | Report complexity affects configuration, QA, and onboarding effort |
| Implementation support | Existing forms, sites, assets, roles, data import needs, and rollout path | Guided onboarding is part of the product and should match the first workflow |
| Integration needs | Exports, downstream reporting, analytics, operations systems, and governance requirements | Integrations and custom reporting can change delivery scope |
Exact pricing is quote-based because Oculi is configured around the field workflow, reporting outcome, and rollout scope. The fastest way to price it is to share the work package or report your team wants to improve first.
What Oculi pricing includes
Each rollout combines Oculi software with guided setup around one real workflow, rather than starting with a blank tool rollout.
- Mobile field capture for site visits, photos, notes, statuses, and open items
- Portal review workflows for office teams, managers, and reporting roles
- Configured forms, fields, statuses, and work-package structure
- Guided onboarding through the first report or closeout package
- Reporting, export, and integration planning where required
See the workflows Oculi supports
Use a focused workflow page to compare the operational fit, then bring the report or closeout package your team already delivers.
Solar O&M
Explore solar maintenance reporting
Connect the site visit to the client report
Keep photos, equipment details, closeout notes, and open work attached to the maintenance record.
Inspection And Closeout
Explore inspection and closeout reporting
Find evidence gaps before delivery
Review photos, checklist context, deficiencies, status, and sign-offs as one closeout record.
Customer Outcome
Read the customer story
See the Zon Generation workflow
Read how structured maintenance capture supports office review and client reporting.
Questions about Oculi pricing and rollout
The quote starts with the work, report, and rollout requirements your team already has.
Is Oculi priced per user?
Oculi does not make every login the main pricing driver. The quote is based on the field workflow, unit of work, reporting needs, operational volume, onboarding, and any approved integration or export scope.
What do you need to prepare an Oculi quote?
Start with one current work package, inspection, service visit, closeout package, or recurring report. We review the forms, evidence, statuses, review steps, report requirements, cadence, and rollout scope behind it.
Is onboarding included?
Yes. Guided workflow setup is part of the product. Operandi maps the current process, configures the first workflow, and supports the initial rollout.
Can we start with one workflow?
Yes. A focused rollout starts with one practical workflow and its report or closeout package before expanding to more sites, teams, or processes.
Do integrations affect pricing?
They can. Export, downstream reporting, analytics, operations-system, and governance requirements are reviewed during scoping because they can change delivery effort.
Get pricing around the workflow you actually need to improve
Share the field process, report, or closeout package that creates the most manual follow-up today. Oculi can then scope the rollout and quote the work being delivered.