What adoption actually looks like.

Your own data, in a session

Bring an export — consignments, customers, whatever you have. We import it in front of you and you look at your own shipments in the product, with your own references. This is worth more than any demonstration of ours, because the thing being tested is whether it fits your data, and that is knowable in an hour rather than a quarter.

You need

One export file and an hour.

What you are actually buying

The core is the whole working platform — consignments, checkpoints, parties, documents, purchase orders, approvals, alerts and the audit trail. Most operators run that and nothing else. Modules sit on top of it and you licence the ones you need: warehouse, manufacturing, fleet and maintenance, tracking, custody, compliance, import, finance, or agency if you are a forwarder acting for clients.

Two things worth knowing before the commercial conversation, because they change how you plan a rollout:

Nothing is per user

Put the warehouse crew, the drivers and your customers' receiving desks in it. A record with half the participants missing is not a record, and pricing that discourages adding them would make the product worse at the thing you bought it for.

Modules are reversible

A module you stop using stops being charged from the next statement, and the data it produced stays where it is. You are not deciding your final shape on day one.

The blockchain part is optional and metered

Anchoring costs nothing to have switched on; you pay only for records you actually anchor. Everything else runs with no chain at all, including on a site with no internet connection — custody handoffs are still signed by the parties and held as proof, publishable later if you ever need an outside party to verify one.

The current figures are on the pricing page. They live in one place deliberately, so a number here could only ever be a second copy going stale.

One lane, one team, running for real

Pick a single trade lane or a single site and run it properly alongside what you do today. Not a pilot in a sandbox — real consignments, real people, with the old process still in place underneath. Your nightly export keeps both in step.

Takes

Days to set up. Weeks to be confident.

You need

One operations person who is allowed to change how their lane works.

Widen it

More lanes, more sites, and the capabilities that the first weeks proved you needed — rather than the ones that sounded good at the start. Most customers license fewer capabilities after a pilot than they expected to before one.

What genuinely takes time

Agreeing what a field means. Two departments will define "delivered" differently and neither will know until the data is side by side. This is the single most common reason a migration takes longer than planned, and it is a conversation inside your organisation rather than work on ours.

Deciding who owns a record. When both systems can edit a shipment, somebody has to say which wins. We make the disagreement visible; we cannot make the decision.

Habits. A scanner in a hand beats a spreadsheet on a desk only once the person holding it trusts that the scan arrived.

What does not

Standing the software up. Importing a file. Adding a site, a location or a device. None of these is a project, and if any of them is being quoted to you as one — by us or by anyone else — ask why.