Pricing
NexusClaw pricing combines an org base fee, usage metering, and outcome-based pricing. The org base fee covers the operating foundation, usage metering reflects runtime consumption, and outcome-based pricing connects digital labor value to attributable, reviewable, and billable business results.
Pricing model
The model is not organized around software access. It is organized around the operating foundation, runtime consumption, and accountable outcomes required for digital labor in production.
01
Pay an org-level base fee for the operating foundation, base agent quota, governance capabilities, auditability, and support services. This layer is not priced by user count; it gives enterprises a budget baseline for deploying digital labor.
02
Meter runtime records such as agent executions, model calls, voice nodes, automation steps, external tool calls, and writeback actions so teams can review consumption by business workflow.
03
When business results can be recorded, attributed, and reviewed, enterprises can connect part of the fee to agreed outcome events. The model tracks outcome type, attribution method, contribution score, pricing tier, billing status, and dispute review.
Model views
These visuals are designed for the website, customer meetings, and internal sharing. They explain how NexusClaw separates the base fee, runtime consumption, and outcome settlement into a business model.
Enterprises first define orgs, environments, governance boundaries, and deployment scope, then decide which workflows agents can enter.
Runtime consumption is captured through traceable actions so cost can be reviewed by agent execution, model call, voice node, and system writeback.
Outcome events, attribution evidence, settlement status, and dispute review sit in one chain so business results become reviewable and billable.
The org base fee, usage metering, and outcome-based pricing form one enterprise model for budget baseline, runtime consumption, and result delivery.
Settlement logic
NexusClaw does not describe outcomes as a generic value claim. It breaks settlement into events, evidence, contribution, tiers, and review records.
Define which business events qualify for the outcome model, such as qualified lead progression, service request completion, renewal action, or workflow milestone.
Record what context the agent read, which actions it triggered, whether people stepped in, and how the result was written back.
Use contribution score, pricing tier, billing status, and dispute handling to create a review chain for commercial discussions.
Commercial rollout
A mature pricing discussion starts with one business workflow where boundaries, actions, and results can be recorded and reviewed.
Confirm deployment environment, business objects, permission boundaries, audit requirements, and base agent quota.
Confirm how agent executions, model calls, voice nodes, automation steps, tool calls, and writeback actions are recorded.
Define which business results qualify for outcome-based pricing, with attribution method, contribution score, and pricing tier.
Review usage, outcome events, dispute records, and the next workflow expansion scope on a monthly or quarterly basis.
If your team is evaluating how agents enter real business workflows, NexusClaw can begin with one org, one workflow, and a defined set of reviewable outcome events.
We do not publish a context-free unit price table. Pricing discussions are based on deployment scope, runtime consumption, and outcome events.
