Product walkthrough
Inspect a relevant example and see how a team challenges a recommendation. Bring a business question; no dataset or system access is required.
Request a walkthrough Enterprise pricing
Start with one workflow. Know the cost before work begins.
Your people built what your company knows. Nodes uses it to run one workflow you name, such as following up on incomplete customer applications. Your production license or subscription covers that named workflow, including how it starts, the approved steps and a record of what happened.
Nodes Engine connects your records, documents and the judgment behind past decisions in your context graph, compares what to do and carries out approved work. Nodes Connector connects your systems and verifies each integration. Nodes AI FDE configures and tests each workflow. The three products do not require separate licenses or subscriptions.
No per-seat meter · No token or model-call meter · One published fee: the first decision brief, below
From first conversation to production
Commit to one step at a time.
A walkthrough, paid decision brief and production engagement each have their own scope and agreement.
First decision brief
For US companies with more than 2,000 employees, the fee is $125,000. The question, value threshold and calculation are agreed in writing before payment. Setup typically takes 1-2 weeks.
Within 72 hours of complete agreed data access, you receive a decision brief identifying at least $1M in potential business value over an agreed measurement period. It includes findings, evidence gaps, options and estimated costs of acting or waiting.
If we do not identify the agreed finding in that window, we refund the full $125,000 fee. A successful brief credits the fee toward annual licensing if you proceed. Production implementation is separately scoped and scheduled.
Review the complete offer and finding termsProduction engagement
Agree one named workflow, such as the application workflow above, and who owns each step. Licensing or subscription depends on where Nodes runs.
See the production scopeHistorical Decision Replay
Test one repeated decision against usable historical outcomes. This read-only evaluation has its own eligibility rules, start condition and written evidence bar.
Review Decision Replay terms Deployment and pricing
Choose how you run Nodes.
Service, configuration support and product upgrades are included. Your agreement defines the workflow scope, deployment responsibilities and any separately funded infrastructure or third-party costs.
In a customer VPC or on premises, production data can stay inside the boundary you approve. Nodes is SOC 2 Type II attested. Review deployment boundaries and controls.
Customer VPC
License Nodes in a single-tenant VPC in your cloud.
On premises
License Nodes on infrastructure your team manages.
Nodes Cloud
Subscribe to Nodes Cloud, managed by Nodes.
What the license covers
Workflow-based pricing. No internal-usage meter.
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.
What is not metered
- Seats or users
- Tokens or model calls
- Recommendations, approvals or actions
- Software credits
What sets the quote
Tell us the job, who it serves, the systems involved and how much work it handles.
- Workflow and approved outcome
- Systems, data and integrations
- Operating envelope and controls
- Deployment, implementation and support
Inside one agreed process
The application workflow can include retrieving local guidance, preparing a checklist, drafting a request for missing information and routing an exception. Adjusting those steps stays in scope within the agreed population, systems, controls and operating envelope: the volume and limits set for that workflow.
A new process needs agreement
A field-service scheduling workflow is a separate process from that application workflow. The business owner agrees its scope, permissions and quote before work begins. If Nodes proposes work in another process, the proposal alone does not activate a new license or authorize new actions.
The full investment
How much does enterprise AI cost?
There is no useful universal price. Scope one workflow and count every cost over the same period: license, implementation and integration, AI and infrastructure, third-party services, human review, correction and rework, adoption, governance, monitoring and relevant risk.
A Nodes proposal identifies included and separately funded items. Projected benefit and measured results stay distinct. Time freed, cash saved, revenue and margin have different meanings: an hour freed becomes cash only when a cost goes away. Review supported inputs and labeled assumptions before committing.
Work your team keeps
Someone on your team still owns the business result, grants source access, handles local exceptions, reviews proposed changes and measures outcomes. Estimate that time alongside cash expense.
If you already pay for AI assistant seats
Keep them. A seat gives one person a capable model. A Nodes license or subscription covers one named workflow: the sources it reads, the approved steps, who approves changes and the record your company keeps.
If you plan to build with your own agents
Building fits when the work is distinctive and your team can own what follows launch: integrations, permissions, approval rules, model evaluations, exceptions and the record of each decision. Set that cost beside a Nodes quote for the same period, counting the work your team keeps either way. See build, buy and hybrid compared.
Build the finance review · Test lower-cost options · Review costs beyond the vendor meter · Measure the later result
After analysis · production engagement
Agree what gets delivered and who owns each step.
Implementation follows a separate agreement. It names the scoped work, customer responsibilities, dependencies, acceptance checks and how material changes are agreed.
The business result
Your business owner and finance team agree the starting business measure, current operating cost, team effort and comparison period. For the application workflow, that might be days to a complete application, staff hours spent on follow-up and the next two quarters. Compare estimated impact with the cost of acting, waiting, gathering evidence or leaving the process unchanged. Missing evidence remains a gap.
The delivered scope
Name the workflow, systems, population and acceptance criteria. Your company chooses sources and checking frequency. Agree permitted reads, recommendations and actions for each user and assigned agent. Confirm integration feasibility and implementation dependencies before committing to delivery.
The operating responsibility
Name owners for rollout, guidance, monitoring and exceptions. Agree task quality, supporting evidence, exception limits and total AI and retained human cost. Compare later results, actual operating costs and team effort with the baseline. The owner decides whether to expand, hold or narrow delegated work. Failed and inconclusive results stay in the history, and the owner can pause the work or remove access.
The evidence you retain
Your company retains its context graph, Decision Traces and outcome history. Nodes retains ownership of its applications, updates and platform intellectual property. You control business rules and approvals. Your agreement sets the retention, export and transition arrangements that apply if you leave, separately from licensed runtime access. Review ownership and controls.
One production reference: a Fortune 500 insurance carrier, live since January 2025 across 200+ locations nationwide. That deployment moved from contract to production in 34 days. Your schedule depends on scope and system access. Inspect the production evidence · Review implementation and delivery scope
Optional historical validation · Decision Replay
Test a decision against your history.
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.
Review eligibility, timing and commercial terms
Eligibility and evidence
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. Your 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 evidence bar is not met
If the historical record does not support that written bar, there is no production fee and your company keeps the analysis, including the limitations. This remedy covers the production deployment fee.
Fees and commitments
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.
First conversation
Which decision needs attention?
Bring one business question and its accountable owner. We show how Nodes would approach it, which records it would need and who would approve the work. No company data needed for the first conversation.