Engagement Models

Structure the project around how defined the work really is.

ORVREN can use different commercial and delivery models depending on scope certainty, technical risk, customer operating preferences and the level of ongoing responsibility required.

Discovery / Scoping

A focused engagement to map the process, requirements, risks, architecture and delivery plan before a larger build.

Fixed-Price Project

Best when scope, deliverables, assumptions and acceptance criteria can be defined clearly before development.

Time & Materials

Useful when requirements will evolve, technical uncertainty is material or work is prioritized iteratively.

Phased Delivery

Break a larger program into controlled releases so the customer can validate value and reduce implementation risk.

Managed Application

ORVREN develops and operates an agreed application with hosting, maintenance and support defined commercially.

Ongoing Engineering

A recurring engineering arrangement for approved enhancements, integrations, optimization and support beyond the initial release.

Choosing the model

The right structure depends on the project.

Defined scope

Fixed-price work can be appropriate when deliverables, assumptions and acceptance criteria are stable.

Evolving scope

Time and materials or phased delivery can reduce false precision when requirements will change during discovery.

Operational responsibility

Managed applications make sense when the customer wants ORVREN to own more of hosting, maintenance and support.

Large program

Phase the work so architecture and business value are validated before committing every future module.

Existing system

Integration, modernization or ongoing engineering may be more appropriate than replacing the entire environment.

Not sure

A discovery engagement can define the options before the customer commits to a larger implementation.

Commercial clarity

Separate maintenance from new development.

Support agreements should define the existing functionality being maintained. New modules, new integrations, major workflow redesign and material customer-specific changes should be scoped and approved separately.

Support / maintenanceProtect the agreed solution

Defects, approved maintenance, operations and support within contract boundaries.

New developmentExpand the solution

New functionality, integrations, migrations and significant changes.

Not sure which engagement model fits?

Select “Not sure” in the project request. ORVREN can recommend a structure after reviewing the scope.

Start Project Request