How Nova Works | The AI-native Adaptive Layer Above Your TMS

The core idea

Products stay generic. Your process stays yours. Nova connects the two.

Most software makes you bend your process to fit the tool. Nova is the layer in between: it holds your exact process and runs it on the standard product underneath. That is why it adapts to you, and ships in weeks, not years.

Without a configuration layer

✕Approvals run on manual email chains

✕No one knows where an order is stuck

✕Off-platform partners fall through the cracks

✕Data is trapped in disconnected spreadsheets

✕Every change is an engineering project

With Nova

✓Configurable multi-level approvals, with email actions

✓A live milestone tracker for every stakeholder

✓Pulled into the same process with SLA tracking

✓Flows into workflows, screens, and AI agents

✓A configuration change, pushed in days

Five working parts, in the order your process moves through them.

Capability 01 · Workflow Orchestrator

01

We run your process the way you run it. Branches included.

Your process is not a straight line. Critical parts need multiple approvals; routine parts skip them. Most systems flatten that into rigid milestones. Nova models the branches as they actually behave.

Under the hood

A configurable graph of nodes and edges, not hardcoded steps. Six node types cover anything: events, conditions, approvals, actions, service tickets, terminal states. Versioned, audited, and configured per customer without touching the product.

When your process changes, we change a configuration, not the product.

Event Condition Approval Action End

Capability 02 · Service Tickets · the hardest part to copy

02

Your CHA is on WhatsApp. Your broker is on email. Your supplier will never log in. We bring them into one process.

Your Key freight partners live in the gaps between tools, where accountability vanishes. Nova pulls them into the same workflow, with deadlines attached.

Under the hood

Email actions and no-login portals. A customs step becomes a tracked task with an SLA; a document request becomes a portal upload that flows back into the process. The partner never changes how they work; you get a clock on every external handoff.

The gaps nobody owned now have an owner and a deadline.

Inside the workflow

Customs clearance stepnode · awaiting confirmation

Outside the platform

W

CHA on WhatsAppnever logs in

@

Insurer on emailreplies by email only

Service Ticket

Customs confirmation requested

SLA 48h · 12h left

Capability 03 · Data Layer

03

The platform reasons about your business, not a generic model.

A platform is only as smart as the data under it. Nova runs on yours: part catalog, plant schedules, supplier scores, and contract terms become live inputs to every workflow and agent. A delay is judged against the date your plant actually needs the part.

Under the hood

Three sources unified: product data, market data, and your uploads. Ingested and structured automatically so workflows and agents use it without engineering, with freshness tracked so nothing runs on stale data. Role-based access; never blended into a shared model.

The system speaks your business. Your terms, your dates, your numbers.

Capability 04 · AI Agents

04

AI your team trusts, because every answer shows its work.

Most logistics AI is a sidebar chatbot or an unexplained prediction, so teams ignore it. Nova's agents run on your data, fire inside your workflow, and refuse to answer without evidence. No citations, no answer.

Under the hood

Agents are triggered by workflow events, not a chat box. A vessel arrives, a customs agent fires. A shipment slips, a delay-risk agent escalates. Each follows one disciplined pipeline:

Scope→ Context→ Route→ Plan→ Evidence

AI your team acts on, because it earns the action. The plant keeps running. The P&L holds.

delay-risk-monitor · live

▌ DELAY RISK DETECTED

ShipmentSHP-2026-04-08-BOSCH-ECU Current ETA (gate)2026-04-28 Plant required date2026-04-27 Delay1 day (within buffer)

Risk assessment

Vessel: on scheduleOK

Port congestion: normalOK

Customs prediction: 3 to 5 daysOK

Last-mile: booked, standardOK

WATCH Keep monitoring. Escalate to procurement if the vessel slips.

Next check: 2026-04-20 06:00 · 4 sources cited

Capability 05 · App Builder

05

The screens your team uses are built for your process, not a generic dashboard.

Adoption is where platforms quietly die. Hand a team a generic dashboard and they go back to the spreadsheet. Nova attaches purpose-built screens to the exact points where work happens.

Under the hood

Assembled from a reusable component library and attached to specific workflow nodes, so they are tailored without being rebuilt. Each screen is workflow-aware: it knows where it sits and acts on the live data flowing through it.

Screens shaped to the job. The platform gets used. Adoption stops being the risk.

Rate comparison

Document review

Exception queue

Booking node

Customs node

Exception node

See it run

One shipment. Eight countries. Every part of the architecture, working together.

A global automaker imports 500 engine control units from Germany to a plant in India. One shipment: a carrier booking, a customs house that never logs in, an insurer on email, multi-level approval, and a plant line that stops if parts are late. It touches every capability on this page.

1

PO raised, enters workflow

Workflow

2

Critical parts routed to approval

Workflow

3

Carrier booked, rates visible

App Builder

4

Plant date sets the benchmark

Data Layer

5

Customs agent on WhatsApp, tracked

Service Tickets

6

Delay-risk agent watches buffer

AI Agents

7

Invoice matched to contract

Settlement

Before

A three-month engineering project for one custom import workflow. No audit trail. Approvals over email. The plant blind to status until a part was already late.

After

A two-week configuration. The full process in version control. Real-time tracking. Approvals automated. Customs paused on portal feedback. Every stakeholder on the same milestones.

Not described. Running. One process, one business, live across eight countries.

See a process-fit demo

Why it works at scale

Six weeks to first deployment. And it stays adaptable long after.

Everything here is configuration, not custom code. That is why it ships in six weeks: deployment is assembly, not construction. And why it keeps adapting: a process change next quarter is a config update in days, not another project.

Legacy builda new process is a 3-month engineering effort, and every change is another one

Month 1

Month 6

First value, ~month 14

Novaconfigured in about two weeks, then pushed as updates

Week 1

Week 3

Live, week 6 · value compounds

Client A process

Client B process

Client C process

One platform engine

One engine, many configurations.

The same proven product runs under every customer; only the configuration on top differs. That makes customization repeatable, not bespoke.

A product with a configuration layer. Not a services firm. The customization never becomes your lock-in.

Role-based access. Versioned, audited changes. Integrates with your existing systems through APIs and event streams, rather than replacing them.

See it mapped to your process. Live in six weeks.

Book a 30-minute process-fit conversation. We will take one of your real workflows, show how Nova maps it, and walk you through week 1 to week 6.

Book a process-fit conversation →

The AI-Native Adaptive Platform for Global Trade.

Nova: the engine that maps your exact process and runs it.

Orchestrated by Nova. Grounded in your data.

Five deep products, bound together by Nova.

Your process isn't a template. Neither is our platform.

Products stay generic. Your process stays yours. Nova connects the two.

We run your process the way you run it. Branches included.

Your CHA is on WhatsApp. Your broker is on email. Your supplier will never log in. We bring them into one process.

The platform reasons about your business, not a generic model.

AI your team trusts, because every answer shows its work.

The screens your team uses are built for your process, not a generic dashboard.

One shipment. Eight countries. Every part of the architecture, working together.

Before

After

Six weeks to first deployment. And it stays adaptable long after.

See it mapped to your process. Live in six weeks.