PRICING & SCOPE
Price the platform
around your operation.
Your departments, data, integrations, deployment, and support needs shape the proposal. Start with the work you want to connect; we’ll define the scope and commercial terms in writing.
There is no universal published price or implementation promise.

Make the investment
easy to unpack.
Connect the commercial conversation to the work, systems, and responsibilities in your proposed scope.
- 01
Map the operation
Departments, workflows, sites, users, and the systems you need to keep.
- 02
Define the delivery
Data, integration, implementation, training, and acceptance responsibilities.
- 03
Review the written terms
Included costs, exclusions, support, renewal, export, and exit.
YOUR WRITTEN SCOPE
One operation.
A defined commercial scope.
- Platform
- Modules, roles, users, environments
- Implementation
- Configuration, migration, integration, training
- Ongoing services
- Support, infrastructure, third-party costs
- Agreement
- Term, renewal, acceptance, export, exit
Included. Excluded. Assigned.
Confirmed in writing.
What we scope
- Legal customer, sites, users, modules, roles, and environments.
- Data sources, migration, integrations, retention, deletion, and ownership.
- Cloud, private, on-premises, or disconnected architecture where technically available and validated.
- Security, privacy, AI, regulatory, accessibility, and customer-control requirements.
- Implementation phases, customer dependencies, training, support, service levels, and acceptance tests.
What the proposal should show
A proposal should state the subscription or license basis, included and excluded services, implementation fees, usage or infrastructure charges, taxes, invoicing schedule, term, renewal, price-change rules, cancellation and termination rights, data export, support level, and any third-party costs. No website statement changes those written terms.
Timing and availability
Go-live timing and feature availability are estimates only when expressly labeled as estimates in a proposal. A binding commitment exists only in a signed order form or statement of work with assumptions, customer dependencies, milestones, acceptance criteria, and remedies. Regulated or complex integrations may require additional review and validation.
No online purchase or automatic renewal on this site
Cortrova.com does not collect payment, start a free trial, enroll a visitor in an automatically renewing service, or create a product account. Any future purchase or renewal flow must provide its own conspicuous terms and affirmative acceptance record.
Your next step
Start with the work you want to connect.
Bring your departmental priorities, current systems, and deployment requirements. We’ll use them to define a written proposal.