Start with the business result you want to improve. We scope the work, delivery responsibilities, and cost so your team can evaluate the investment. The license covers one named workflow, from trigger through approved execution and evidence.
No per-seat meter · No token or model-call meter · Quote changes only when scope materially changes
Another AI team, workflow branch, or improvement within the agreed business responsibility does not automatically create another charge. A separate business process or a material expansion is scoped and agreed before it is added.
A pre-hire workflow can include sourcing, screening, scheduling, and interview coordination across the agreed systems. Adding roles or adjusting those steps stays in scope when it remains within the agreed population, systems, controls, and operating envelope.
For example, a vendor-renewal opportunity is outside that agreed hiring responsibility. Proposing it does not activate a new license or authorize new actions. The business owner agrees the separate scope and quote first.
The agreement turns a business objective into a delivery commitment. It names what Nodes provides, what your team retains, and how the work will be accepted and evaluated.
Your business owner and finance team agree the target outcome, baseline, and measurement period with Nodes. The business case records expected benefit and its assumptions, including the cost of leaving the process unchanged.
The scope names capabilities, systems, population, permitted actions, and acceptance criteria. It identifies available capabilities, any implementation needed, and anything outside the commitment.
Nodes and your team have named responsibilities for implementation, support, monitoring, and exceptions. Approval controls, customer effort, dependencies, and material changes are covered in the agreement.
The agreement specifies how results will be reviewed and which customer-specific evidence, decision history, and artifacts remain usable. Export and transition arrangements are distinct from access to the licensed Nodes runtime.
Review capability availability and delivery scope · Inspect the production evidence
The proposal ties commercial terms to delivered work instead of consumption inside the approved program.
Evaluate the expected benefit against the full cost: license, implementation, infrastructure, third-party services, and the work your team will still own. The proposal identifies included and separately funded items.
Projected benefit and measured results stay distinct. Your finance team can review the assumptions, uncertainty, and full cost alongside the evidence before committing. Build the finance review.
Decision Replay is a separate, read-only evaluation for a repeated decision with usable outcome history. It returns evidence and limitations to inform the business case. You can explore Nodes without starting a Replay or preparing a dataset.
Start with one repeated high-stakes decision and at least two years of linked decisions and outcomes. Nodes confirms sufficient volume, usable join keys, outcome coverage, data quality, and policy overlap before accepting the test.
The 72 hours start only after Nodes accepts the agreed deidentified dataset delivered under a mutual NDA. The customer's finance team defines the written $1M evidence bar and calculation before the Replay runs. The analysis is read-only, touches no live decision, and does not establish future realized value.
If the historical record does not support that written bar, there is no production fee and the customer keeps the analysis, including the limitations. This remedy covers the production deployment fee.
Replay analysis fees are not published here. The written Replay terms must state any production commitment and its scope, whether an analysis fee applies, payment timing, and what happens under each result. Review them before authorizing the work. The production-fee remedy does not mean the Replay analysis is free. Meeting the bar does not itself authorize live actions.
Bring a business process or an outcome you want to improve. No dataset is required for a product walkthrough. If historical validation is the right next step, we will review the separate Replay requirements with you.