Commercial Models Built Around Your Enterprise Scope.
Deploy the CONSOLYX capabilities you need, in the environment and intelligence model that fits your organisation, with implementation and ongoing services scoped transparently around complexity.
A scope-based proposal
Start with your priorities
Deploy one capability, combine several, or build the broader CONSOLYX Enterprise Intelligence environment.
Operational workflows, accounting, local books and operational intelligence.
Consolidation, FP&A, management and financial reporting, and decision intelligence.
ESG, carbon, climate, reporting, risk and assurance according to implemented scope.
Risks, obligations, controls, evidence, findings and remediation according to implemented scope.
Scoped per engagementGoverned AI and executive decision support where selected and technically approved.
OptionalHR, payroll and workforce intelligence is scoped separately.
Choose your deployment model
Deployment architecture is a commercial and technical design decision. Discuss the environment that fits your internal security, infrastructure, data-residency and operating requirements.
Where the approved CONSOLYX architecture supports your environment, with infrastructure, deployment, upgrades, monitoring, backup and support responsibilities set out explicitly.
An approved cloud architecture, with hosting, data, monitoring, identity, consumption and support responsibilities defined in the proposal.
Where supported, customer-controlled systems and data sources combined with approved cloud services or intelligence components.
Each proposal states who owns
Data residency, network isolation and regulatory requirements are validated for each client and jurisdiction, not promised universally. Deployment design is confirmed during solution scoping.
Choose your AI model
AI is not forced into every engagement. The core governed platform is separate from optional AI-enabled intelligence, so adoption can follow your policy, data sensitivity, architecture and business value.
The AI scope of a proposal identifies
Human approval and accountable business decisions remain explicit.
AI in customer-controlled environments depends on validated model hosting, connectivity and data-governance design.
Define enterprise scope
Price is derived from enterprise complexity and delivery requirements rather than a single entity-count threshold.
Modules and intelligence domains selected.
Groups, entities, branches and nodes, operating structures and relevant data volumes.
User populations, roles and governance requirements.
ERP and accounting systems, databases, APIs, files and other approved sources.
Workflows, mappings, reports, planning models, frameworks and localisation requirements.
Customer-controlled or private, cloud or hybrid architecture and the infrastructure responsibility that goes with it.
Selected AI use cases, model and service consumption, and governance requirements.
Migration, testing, enablement and the ongoing service model.
Commercial structure
See what drives upfront implementation effort and what continues as a recurring platform and service commitment. Exact commercial terms are confirmed in the proposal.
Upfront
Discovery, solution design, configuration, data and mapping preparation, integrations, migration as applicable, testing and validation, deployment and enablement.
Ongoing
Agreed licence, subscription or contracted platform entitlement aligned to the selected capabilities and scale.
Agreed support window, updates, maintenance and technical responsibility.
Identified separately where they apply
Included, customer-provided or separately scoped according to the deployment model.
Identified separately where cloud AI, model or service usage introduces variable consumption.
New entities, capabilities, integrations, jurisdictions or material scope changes, through an agreed change process.
Adoption model
Align commercial scope to the way the organisation wants to adopt the platform.
Keep core systems and add CONSOLYX intelligence, reporting, planning, sustainability, GRC or other selected capabilities.
Use CONSOLYX from approved Enterprise Operations scope through local books and downstream intelligence.
Combine CONSOLYX-native and connected environments where the architecture supports the model.
The proposal makes the boundary between CONSOLYX, retained systems, integrations and implementation responsibility explicit.
Implementation journey
Implementation is part of the commercial conversation, because configuration, data readiness and integration complexity materially affect enterprise scope.
Business scope, target architecture, current systems, data and priorities.
Enterprise model, workflows, mappings, reporting, planning and controls.
Approved ERP, databases, APIs, files and other source systems.
Data, workflow, controls, reporting and user acceptance.
Administrators, super users and business users.
Extend capabilities, entities and integrations as requirements mature.
Governance & security
Security, access, traceability and governance are part of the core solution design, while specific controls and architectures are confirmed for each deployment.
Specific certifications, regulatory claims or security service names are stated only after technical validation for your deployment. Advanced architecture requirements may affect scope; governance is never an optional extra.
Extend the scope
Scope grows through an agreed change process, not a list of add-ons.
FAQ
Short answers to the questions enterprise buyers ask before a proposal.
CONSOLYX is scoped around selected capabilities, enterprise complexity, deployment, data and integration requirements, AI scope and implementation needs. A commercial proposal is prepared after the required solution boundary is defined.
Yes, where supported by the selected CONSOLYX capabilities. AI is an adoption choice rather than a mandatory commercial tier.
Yes. Targeted AI use cases can be scoped separately where technically supported and approved for the customer environment.
Customer-controlled, private, cloud and hybrid options are assessed against the approved product architecture and the customer’s infrastructure, security and support requirements before being committed in a proposal.
No. CONSOLYX can be scoped to extend retained systems, operate as an approved end-to-end core, or support a hybrid architecture, depending on the implementation design.
Enterprise delivery can require discovery, configuration, integration, data and mapping preparation, migration, testing, deployment and user enablement. The exact initial scope depends on the customer environment.
Recurring commercials may include agreed platform entitlement, hosting and infrastructure where applicable, support and maintenance, and variable AI or cloud consumption where selected. The proposal states each component clearly.
Yes. The commercial model supports modular adoption and later expansion of capabilities, entities and integrations.
Organisation structure, selected capabilities, data readiness, mappings, reporting and planning requirements, integrations, deployment architecture, localisation, testing and enablement requirements.
No. The core architecture can support multi-country deployment, while country-specific statutory, regulatory, tax, payroll or reporting requirements are validated and scoped separately where relevant.
Next step
Share the capabilities, entities, systems and deployment you have in mind, and we prepare a scope-based commercial proposal around them.