One decision. 72 hours. A written $1M evidence bar.
Bring one repeated people decision and at least two years of linked decisions and measured outcomes. We confirm data sufficiency first. Your finance team sets the $1M evidence bar in writing. The replay then shows whether your historical record clears it. That finding is historical evidence, not realized savings.
Decision Replay
Describe the decisionStart with the decision and its measured outcome. The first request contains no production data and does not start the 72-hour clock.
Security review
Open the security pathAsk for SOC 2 materials, VPC architecture, data-flow details, or a questionnaire response.
Press and partnerships
Send an inquiryUse this path for analyst briefings, integrations, events, and channel discussions.
Establish fit before anyone shares production data.
We begin with one repeated people decision and at least two years of linked decisions and measured outcomes. The initial exchange is enough to determine whether a historical replay may be feasible.
If the decision fits, Nodes confirms data sufficiency and your finance team sets the $1M evidence bar in writing. The data owners and decision owner then define the evidence boundary under a signed MNDA.
A Decision Replay asks a narrow question: does the historical record clear the $1M evidence bar your finance team approved?
- A repeated decision with a clear owner.
- An outcome the organization already measures.
- At least two years of linked decisions and measured outcomes with sufficient volume and data quality.
- A finance owner who can set the evidence bar in writing.
The boundary is clear before data moves.
The first inquiry establishes fit. Security and data owners control every step that follows.
Questions about the first step.
The request is intentionally small. Its job is to establish whether there is a decision worth replaying.
01What should I send in the first request?+
Your name, work email, company, and role or decision area. Add one sentence of context if useful. Do not send production data through this form.
02What makes a decision a fit for replay?+
The decision repeats, and at least two years of linked decisions and measured outcomes meet the agreed volume, linkage, and data-quality requirements. We confirm that before the clock can start.
03When is production data considered?+
After a signed MNDA and an agreed evidence boundary. The replay uses an accepted deidentified dataset from completed cases, read-only, and leaves live decisions untouched.
04When does the 72-hour clock start?+
Only after Nodes confirms data sufficiency, your finance team sets the $1M evidence bar in writing, and the agreed deidentified dataset is delivered under a signed MNDA and accepted by Nodes. Submitting this form does not start the clock.
05What happens if the record does not clear the $1M bar?+
There is no production fee. You keep the analysis.
06Where does data live after deployment?+
Inside the customer's VPC. The deployment is single-tenant, has zero customer production-data egress, and uses customer-owned weights. Review the architecture and security posture.
07Who makes the final decision?+
A named person. Nodes supplies a recommendation, the evidence behind it, and the value of action or inaction. The human can approve, edit, delay, or decline it.
One decision. 72 hours. A written $1M evidence bar.
Bring one repeated people decision and at least two years of linked decisions and measured outcomes. After the agreed deidentified dataset is delivered under a signed MNDA and accepted by Nodes, the clock starts. Nodes then shows whether the historical record clears the bar. If the record falls short, there is no production fee and you keep the analysis.