Scope before subscription

Start focused. Prove value. Scale deliberately.

Begin with a product walkthrough or a guided pilot. We then document the deployment around your products, facilities, users, governance and data readiness — including which integrations are live today.

Ways to start

Product discovery

Focused walkthrough

Your brief · your workflows

A product conversation built around the obligation, deadline or data problem you actually have.

Map the obligation and current data landscape
Walk the relevant product workspace
See live capabilities and planned integrations labelled clearly
Ask technical and methodology questions directly
Leave with a recommended evaluation path

Book a walkthrough

For a defined business case Guided evaluation

Scoped pilot

Tailored · documented with you

A structured evaluation on agreed workflows and representative data, run with the team that builds the product.

Discovery consultation on your obligations and data landscape
A tailored pilot on your own data, with agreed success criteria
Read-out, findings and a documented rollout option
Commercial, data-handling and support terms agreed in writing

Deployment patterns

Three ways to shape the scope.

These patterns are orientation, not pre-written commercial promises. Product availability, facilities, users, support, security and integrations are confirmed in the applicable proposal and order form.

One priority workflow

Focused

Scoped · documented terms

Start with the connected product workspace your most immediate obligation demands, including OrvynLCA when product-footprint evidence is the priority.

One defined product and outcome scope
Organisation and facility context
User and governance model fitted to the workflow
Onboarding and support stated in the proposal
Expansion path documented, not assumed

Discuss a focused scope

Governed reuse where it matters Multiple workflows

Connected

Scoped · documented terms

Two or three products chosen around your obligations — with the platform data fabric moving governed figures between them.

Two or more current connected products
Platform data fabric — share, clear, pull, audit
Cross-product approvals & portfolio pulse
Industry workspace tuned to your sector
Support and future expansion agreed by scope

Discuss a connected scope

Current connected portfolio

Portfolio

Scoped · documented terms

ESG, CDP, CEQ, DPP, LCA and PPWR in one governed operating model.

Six connected products + the data fabric
Six approval layers, audit trail throughout
Multi-entity, multi-site, multi-currency
Security and governance documentation scoped for IT review
Support, security and partner options by agreement

Discuss a portfolio scope

Guided early-customer pilots

A limited number of early-customer pilots may include closer product-team involvement and structured roadmap feedback. Availability, scope and any commercial treatment are documented in the proposal rather than promised on the website.

Discuss a guided pilot

Compare

What each path is designed to resolve.

Comparison of Orvyn360 engagement and deployment patterns
Dimension	Walkthrough	Guided pilot	Focused	Connected	Portfolio
Primary purpose	Understand fit	Test a business case	Run one workflow	Govern reuse	Operate the portfolio
Data used	Reference examples	Representative scope	Production scope	Production scope	Production scope
Products	Relevant tour	Agreed pilot set	One current workspace	Multiple connected	All six connected
Platform data fabric	Demonstrated	Where in scope	Not required	Core to scope	Across six connected workspaces
Governance & audit	Demonstrated	Agreed workflow	Product layer	Product + fabric	Across connected layers
OrvynLCA	Relevant tour	Available in scope	Available	Connected	Included
OrvynPPWR	Relevant tour	Available in scope	Available	Connected	Included
Commercial terms	No deployment	Pilot proposal	Order form	Order form	Order form
Support	Product team	Guided	By agreement	By agreement	By agreement

This table explains the engagement model. The signed proposal and order form define availability, limits, support, data handling and commercial terms.

Questions

The pricing questions people actually ask.

Why don't you print a price on this page?

Because the material cost drivers are scope-specific: products, facilities, users, deployment, support and integration. A written proposal makes those drivers visible instead of disguising assumptions behind a headline number.

What happens to our data if a pilot ends and we don't proceed?

Export format, retention, return and deletion are agreed in the pilot proposal before data is loaded. We will not substitute a marketing-page promise for the signed data-handling terms.

Can we start with one product and add more later?

Yes. Any of the six connected workspaces can be the first step toward a multi-product deployment. Expansion remains subject to technical readiness and the applicable order form.

How are India and Australia engagements handled?

Australian product engagements are led by Blue Leaf Technologies. In India, delivery and advisory support may be coordinated with Key Sustainability, an affiliated partner. The responsible entity and commercial terms are identified in the proposal.

Are partner and branded deployments available?

Partner delivery, tenant branding and white-label options can be discussed where the relevant product supports them. Availability, responsibilities and support boundaries are confirmed case by case.

Scoped with context, documented in writing

Find the first step that fits your reality.

Share the products, facilities, users, deadline and data situation. We'll recommend a walkthrough, pilot or deployment-scoping conversation.

Talk pricing Book a walkthrough

Contact details, locations & regional coverage →