Scope the work before pricing the platform.
ORQESTRA does not publish tariffs or offer self-service subscriptions in this build. Use the scope builder to outline your requirements for a discussion of availability, implementation and costs.
Outline your starting point.
Choose the work you want to connect. Your selection becomes an editable enquiry brief. Pricing and availability need a separate discussion.
Understand what shapes the proposal.
The work should be scoped around your business requirements. These are the main areas to settle together.
Implementation
Process mapping, shared records, integration work, configuration, validation and bringing the workflow into use.
Data readiness
Source quality, record matching, field authority, historical information and the effort required to resolve conflicts.
Operating environment
Hosting, identity, organisation and company boundaries, security requirements and support responsibilities.
Recurring and usage costs
Ongoing services, third-party subscriptions, model usage and any consumption-based charges, with their basis made explicit.
Before you commit.
What should a written proposal include?
The initial workflow, included capabilities, systems and actions, delivery responsibilities, acceptance checks, exclusions, recurring services and commercial terms. Usage charges should state how they are measured.
Can we start with one process?
One workflow is the recommended scoping approach. Its feasibility, dependencies and delivery terms must be confirmed before any implementation commitment.
Does the scope builder calculate a price?
No. It prepares a useful brief for the scope discussion. A commercial proposal depends on the actual systems, data, workflow complexity and operating requirements involved.
Clarity on the work. Clarity on the commitment.
Define the first phase, understand its dependencies and request a proposal with explicit inclusions and responsibilities.