Three-way match
Purchase orders, carrier invoices and bank payments reconciled line by line, so only real discrepancies reach a person. Most freight invoices disagree with the quote in small ways; the Pack surfaces the ones worth disputing.
An Industry Pack is the working knowledge of your sector, assembled and ready to deploy: the definitions, the standards, the processes, the activations and the alerts that a good operation in your field already relies on.
Most data projects spend their first months rebuilding things every operator in the sector already knows. What counts as an order. When a container is late. How margin is really calculated once you account for the messy parts. A Pack carries that knowledge in from the start, so the work begins at your actual problem instead of at first principles. A forward-deployed engineer fits it to how you run, and what does not fit gets built.
Logistics and maritime is the deepest Pack today, drawn from real terminal, forwarding and cold-chain operations. The others share the same foundation and are shaped to your operation by an engineer. Each outcome below is tagged by type: a decision, an automation, an alert or a fix.
Compare packs
Pick up to three sectors and see the differences side by side.
For terminals, forwarders, shipping lines and cold-chain operators.
The numbers that matter in logistics live in systems that were never meant to talk: the TMS, the carrier portals, the customs broker, the ledger, and a great deal of email. A shipment's true cost is knowable only once all of them agree, and by then the margin conversation is weeks late. Free time is the clearest case, a clock nobody watches until the invoice arrives. A Pack puts one definition across those sources and watches the clocks that cost money.
Purchase orders, carrier invoices and bank payments reconciled line by line, so only real discrepancies reach a person. Most freight invoices disagree with the quote in small ways; the Pack surfaces the ones worth disputing.
Free-time clocks tracked per container across carrier portals and flagged days before charges accrue, with the owner who can act.
Revenue minus the fully loaded cost to serve, transport, fuel and BAF, port and handling, under one definition, live per contract and lane.
Committed transit versus actual, per customer and lane, tracked over time so service promises match reality.
Client in your sector: Hudig & Veder · Lineage Logistics
Your problem is probably already on this page.
Six parts, assembled for your sector, that make an outcome trustworthy rather than merely automated.
How the sector actually works, drawn from real operations. The edge cases and the exceptions, not the textbook version.
The norms and frameworks your field already answers to, built in, so the Pack speaks your industry's language from day one.
What each term means, carried with its source and its owner and the date it was set. A number without those three is an opinion.
The steps, the sequence and the decision points, mapped as they run, so the Pack fits the work instead of asking the work to fit it.
The wiring that puts the answer where the work already happens: the exception queue, the report, the alert. Not another screen to open.
The signal when something drifts out of its accepted band, raised to the person who can act, with the context to act on.
Six parts, one foundation, built for your sector.
A gap scan lays the Pack for your sector over how you work today and reads the distance between the two.
It is a diagnosis, not a sales exercise. In one pass it surfaces where your current practice and the industry standard diverge: definitions that disagree between teams, a reconciliation still done by hand, a control that exists on paper but fires for no one, a number three departments calculate three ways. The output is an ordered list of what to close and what closing it is worth, so the first engagement starts on the highest-value gap rather than the loudest one.
A Pack and a forward-deployed engineer come as one engagement, with one promise: a trusted outcome in real use, in weeks. The Pack is the head start, the encoded knowledge of your sector. The engineer fits it to how you actually work, closes the gaps the scan found, and stays until the team uses it. Where no Pack fits your sector yet, the engineer builds from scratch, and what they build becomes the next one.
Three ways to start
A template
Set up fast, fits nowhere exactly, and nobody owns the definitions.
Consulting
Fits your operation, starts from zero every time, and leaves with the knowledge.
One engagement
The Pack as the head start, the engineer for the fit, and the outcome stays yours.
An answer is only worth acting on if you can see where it came from. Every figure a Pack produces is traceable to its source system and record, carries the owner who defined it and the date they did, and runs where you decide: in Europe, your own cloud, or your own hardware. What gets built is yours, contracts and definitions included. Governance here is not a review step at the end. It is the reason the number holds.
Traceable
Every figure followed back to its source system and record.
Owned
The person who set the definition, and the date they set it.
Resident
Runs where you decide: in Europe, your own cloud or your own hardware.
Yours
What gets built is your property, contracts and definitions included.
Trust is the feature. The outcome is the proof.
sectors, and counting
gap scan to start
to a trusted outcome
blank canvas
Read deeper
Where your organisation's knowledge lives: owned meaning, trustworthy data and decisions you dare to act on.
Read the pillarChoose one recurring issue where teams lose time or disagree today. A gap scan shows you the distance. A Pack and an engineer close it, and you own the outcome.
No obligations · Your data stays yours · Built in the Netherlands