Loading
One moment.
One moment.
NODES does not price per seat. Three ways to buy, sized to where your decision matters most. Start with a diagnostic pilot at $25K and convert to consumption or outcome pricing once the proof lands.
Every tier runs the same platform, the same agents, the same Decision Trace. The difference is how the bill works and where the risk sits.
Published NC costs per action across all 3 pillars and 19 actions, typical monthly volume for a Fortune 500 carrier, and the resulting monthly NC draw. Your final dollar figure depends on commit size and deployment. This is the worksheet, not a summary.
The catalog is the same for every customer. If your NC draw moves, it is because your volume moved, not because a sales conversation moved.
Discounts off the standard NC rate apply automatically as monthly volume crosses each tier. Every customer on the same tier gets the same discount. The curve is published because consumption is the contract. The final rate is set on the commercial call, against your actual volume.
Same platform, same NC catalog, one multiplier on your credit draw. Move from pilot to customer-VPC to on-prem without re-pricing the catalog or renegotiating the contract. The multiplier is the only thing that changes.
Customer-VPC is where most Fortune 500 deployments land. It is the architecture behind 17-day legal reviews. See the Architecture page for the full boundary manifest.
Composite deployments drawn from live customers, redacted. Each breakdown shows the consumption line items, monthly NC draw, and the deployment multiplier applied. Your actual commit and rate come from a commercial call. This is the worksheet, not a brochure.
Security posture, identity, audit, and handoff are part of the platform, not a tier upsell. Consuming a credit for any of these would mean NODES considers it optional. NODES does not.
Annual commits unlock tier 3+ pricing and lock the rate for the term. Quarterly true-ups are non-punitive. Unused NC roll within the commit year, overages bill at the same tier rate. Multi-year commits bank one extra tier.
Answered once, here, in the language your finance team will paste into an SOW. For anything not covered, a 30-min commercial call will produce a worked quote, not a brochure.
Tiered, not retroactive. Your discount on a given month is determined by the tier your monthly NC volume lands in: standard below 250k, -10% from 250k to 1M, -20% from 1M to 5M, -35% above 5M. Every NC in that month draws at that tier's discount. No cumulative recalculation, no year-end settle-ups, no "you crossed 1M in December so the previous month is clawed back." The curve is published; the final rate you commit at is set on the commercial call against your actual volume.
Not within the commit year. NC from an under-consumed quarter roll forward against the annual commit. What does expire is the annual envelope: unused NC at the end of the commit year do not carry into the next term. That is the trade for rate-locked tier pricing. If your consumption is lumpy, the workforce-planning team is the one to talk to; NODES can shape the commit around your cycle rather than calendar months.
One scored evaluation against one success profile, producing one signed decision trace: 2 NC. Re-screening the same candidate against a revised success profile is a new screen, and should be; it is a different decision. Bulk rescoring (pool against a refit profile) is priced separately at 1,800 NC per thousand, because it is a batch operation that runs under different compute guarantees.
At the same tier discount that applied to the quarter they occurred in. If a seasonal surge pushes you through Tier 3 into Tier 4 in Q3, Q3's overage draws at Tier 4's -35% tier, not at standard, not at a punitive uplift. NODES does not run a snap-back clause. If overages persist for two quarters, the commit is re-cut at the new volume rather than leaving you paying overage terms on what is now your baseline.
Yes. The catalog is the catalog regardless of deployment; only the multiplier changes. Migrating from NODES Cloud pilot to Customer VPC in month 4 re-draws every subsequent invoice at the 2.0x multiplier. It does not require a new contract, a new procurement cycle, or a new DPA if your template already permits VPC deployment. The architecture review deliverables from the Customer-VPC path become your enablement package for the switch.
Not to start. Pilots run at Tier 1 standard with no annual commit; you draw credits as you consume, invoiced monthly, NET 45. Tier 3 discounts unlock at 1M NC per month, roughly the volume at which a carrier's first two role families are in production. Tier 4 is 5M NC per month. Below 1M NC per month the math almost never justifies a commit, and it is better to stay flexible.
No. The entire catalog is consumption-priced in Node Credits. Admin and reviewer seats are unlimited; SSO group-mapped RBAC does the access control, not a license key. Per-seat pricing quietly caps how much of the platform actually gets used, which is the opposite of what a decision-intelligence platform should optimize for. NODES deleted the seat SKU and never looked back.
The catalog covers all three pillars. Pricing is consumption-based regardless of pillar. There is no separate SKU for HR Service Delivery, RevOps, or AI Governance. Every action in the ledger draws from the same NC balance, the same volume tiers apply, and the same deployment multipliers hold. If your primary use case is outside Hire & Develop, the diagnostic pilot is scoped to your pillar.
30-day fixed-price engagement, $25K to $45K depending on scope. Agents run in offline analysis mode against 90 days of your data. Named outcomes are defined in the SOW before kickoff. If those outcomes are not delivered, the fee is refunded. If the pilot delivers, 100% of the fee is credited toward your year-one platform commit. The pilot sits below most F500 procurement thresholds by design.
2% or above of validated business impact. The outcome measurement methodology is defined in the SOW before the contract is signed. Impact is measured through customer-side systems, not NODES-reported metrics. Without a defined and signed methodology, the contract defaults to Platform consumption pricing. This protects both sides: NODES shares the upside risk, and the customer retains measurement authority.
Bring last quarter's hiring and headcount numbers. Leave with a line-item NC forecast, the deployment that matches your security review, and a signed-order-form-ready commit. No separate deck. No "circle back with pricing."