NodeFox
Demo

See what an operational workflow can do.

Watch the actual software execute, then explore business examples from incoming orders and invoices to prepared records and resolved exceptions.

Follow the work · 58 seconds

A contract review you can follow from start to finish.

A 30-day renewal notice meets a 60-day internal requirement. Follow extraction, the exact check, a human revision decision and the resulting review packet.
Illustrative contract review with human approval product demonstration
Illustrative workflow · sample data. Product-derived UI; simulated integrations and results.
Transcript and demonstration details

Illustrative execution, not a customer deployment. Narration is AI-generated. Actions and outputs depend on workflow configuration.

  1. 0–11s · A renewal deadline needs review.

    A supplier agreement allows thirty days for renewal notice. The company’s review policy requires at least sixty. Someone needs to resolve the difference.

    Supplier agreement · Example only · Clause 8.2 · Renewal notice · Notice period: 30 days · Agreement ID: AGR-104

  2. 11–21s · Find the term. Keep its source.

    NodeFox uses AI to extract the notice period and its clause reference. A Reader retrieves the approved review criterion.

    Clause 8.2 located · Notice period extracted: 30 days · Source wording kept with the value

  3. 21–30s · An exact rule flags the mismatch.

    Code validates the number and compares thirty with sixty. The mismatch creates a review flag, not a legal conclusion.

    Validate a numeric notice period · 30 < 60: route for review · A policy flag, not a legal conclusion

  4. 30–39s · Carry the evidence into a decision.

    The executable graph connects the document, policy, exact check and human decision. The next action waits for the reviewer.

    Internal review criterion · Minimum notice: 60 days · Policy version: review-example-1

  5. 39–48s · A person requests the revision.

    The authorized reviewer checks clause eight point two and requests a sixty-day notice period. NodeFox records that decision.

    Authorized reviewer checks the clause · Request a 60-day notice revision · Keep negotiation and signing separate

  6. 48–58s · A review packet. No automatic acceptance.

    The output contains the source clause, policy and requested revision. Negotiation and signing remain with the responsible people.

    Review packet · revision requested · Clause 8.2 and policy linked · Decision: request 60-day notice · Signature and acceptance: not performed

Actual product footage · original 20-second execution excerpt

This separate recording shows the real application executing a contract-review graph. It is not footage of the illustrative renewal-policy scenario above.

See the software · recorded execution

AI does its part. The workflow carries it forward.

Watch a real NodeFox network interpret contract information, apply code and select a route. The graph and execution log show what happens between the model response and the next action.
demo / contract-review-execution
Actual product footage · 20-second silent excerpt. A sample contract-review network runs model, code and routing steps; execution logs appear alongside the graph. This is a product demonstration, not a customer result.

Interpret, then check

A model evaluates the extracted information. Code applies the routing logic to its output.

Carry the result forward

The selected branch supplies the next step. Teams define these dependencies in the visual graph.

Inspect the execution

The log identifies active and completed steps. Use the full recording for authoring and setup.
Inspect stills from the full recording: configuration, execution and output

Actual product recording

A review memo with findings and next actions.

The recording shows this memo in a document viewer after execution. It contains identified issues and a recommendation for human review—not an automatic contract acceptance.

A review memo with findings and next actions. Still from the NodeFox contract-review recording at 8:25.
Captured software and sample contract · cropped for readability · select the image for full size. Model names and UI reflect the recording.
Illustrative workflow films

Find the work your team recognizes.

The flagship introduces the platform. Focused business demonstrations explain specific checks and decisions. All films use synthetic data and simulated integrations; actual product footage is identified separately.

From invoice to approved record

Illustrative from invoice to approved record product demonstration
Designed workflow demonstration · sample records and simulated integrations.
Transcript and demonstration details

Illustrative execution, not a customer deployment. Narration is AI-generated. Actions and outputs depend on workflow configuration.

  1. 0–8s · The invoice and receipt disagree.

    The invoice and the warehouse receipt disagree. Before anything moves to accounts payable, someone has to reconcile them.

    INV-2048 · Northstar Supply · PO-7301 · 240 units at $18 · Invoice total · $4,320 · Received · 228 units

  2. 8–17s · Turn the handoffs into a workflow.

    In NodeFox, that work becomes an executable graph. AI reads the invoice while a Reader retrieves the purchasing records.

    INV-2048 · Northstar Supply · PO-7301 · 240 units at $18 · Invoice total · $4,320 · Received · 228 units

  3. 17–25s · Wait for the facts. Apply the rule.

    Both inputs feed an exact check. Twelve units are missing, so two hundred and sixteen dollars needs review.

    Invoice quantity exceeds receipt · 228 × $18 = $4,104 supported · Route remaining $216 to review

  4. 25–32s · A decision with the evidence attached.

    The reviewer gets the discrepancy and its evidence together. The next action waits for that decision.

    AP reviewer sees invoice + receipt · Approve $4,104 for AP preparation · Hold $216 pending receipt

  5. 32–41s · Approval releases the next action.

    Approval releases the configured Writer. It prepares the supported amount for accounts payable, and keeps the balance on hold.

    AP-2048 · review completed · Supported amount: $4,104 · Held amount: $216 · Payment release: separate authorization

  6. 41–49s · An approved result. A visible history.

    The result includes both amounts, the source records and the decision. Payment authorization stays separate.

    AP-2048 · review completed · Supported amount: $4,104 · Held amount: $216 · Payment release: separate authorization

  7. 49–59s · Less coordination. More completed work.

    Use the same approach for orders, onboarding and investigations. Less coordination by hand. A process you can inspect and reuse.

    AP-2048 · review completed · Supported amount: $4,104 · Held amount: $216 · Payment release: separate authorization

16 workflow films · narrated examples

Explore the complete library

Want to see it on your workflow?

Bring a recurring process and its current handoffs. We’ll discuss the systems, decisions and value a first implementation would need to establish.