A
Forwarder copilot
quotes from the history of similar routes, extracts data from an emailed order
Boundary rule
Never sends a quote to the client. It suggests, the forwarder approves.
Solutions
Platform for managing freight forwarding and transport
transport and freight forwarding companies, own fleet or subcontracted carriers
What does not work today
- orders sit in email and spreadsheets, nobody knows how many are in progress
- the client calls to ask where their truck is
- the margin on an order is known after the fact, at settlement
What you get
Three stages, each with its own value and its own price. You buy them in sequence, not all at once.
01 Process mapping
enquiry, quote, order, execution, documents, settlement
02 Panel
- · orders and statuses
- · CMR and transport documents
- · client panel with tracking
- · carrier panel
03 AI support
- · Forwarder copilot
- · Margin guard
- · Availability and ETA forecast
Three AI modules, and what none of them will do on its own
Every module carries a boundary rule, the line beyond which the decision belongs to a person. The rule is part of the build, not a marketing claim.
B
Margin guard
alerts when the rate drops below the threshold for that route and season
Boundary rule
Never blocks an order from being accepted. It warns and shows an alternative.
C
Availability and ETA forecast
forecasts truck availability and gives a realistic ETA instead of a declared one
Boundary rule
Does not confirm a delivery date to the client automatically.
Security and data
The same rules apply in every panel, whatever the industry. They are not an option to be priced separately.
- Row level security at database level
- The access rule lives in the database itself, not in application code. A bug in the application does not expose another client's records.
- Append-only audit log
- Who, what and when. An entry cannot be altered or deleted, not even from an administrator account.
- TOTP multi-factor authentication
- A second login factor from an authenticator app, without SMS codes.
- File links valid for 15 minutes
- A file address expires. Forwarded on or copied from browser history, it stops working.
- Data inside the European Union
- Database and files in an EU region. The sub-processor list is public and kept current.
- Data processing agreement
- Signed before the first data import, not after go-live.
Regulatory risks in this sector
- · driver personal data
- · working time records
- · GDPR in fleet monitoring
Stages and decision gates
After each stage there is a decision on whether to continue. If a stage did not deliver what it was meant to, the next one does not start.
- 01
Process mapping
Gate: continue, or stop at this stage.
- 02
Panel
Gate: continue, or stop at this stage.
- 03
AI support
Gate: continue, or stop at this stage.
Questions that come up most often
- Will the platform replace my current system?
- Usually yes, because it covers the whole flow from enquiry through quote and order to documents and settlement, together with the client and carrier views. What stays on your side is settled during mapping: telematics and accounting usually stay where they are and connect to the platform. We do not force a single-step replacement, because migrating everything at once is the most common reason rollouts fail in this sector.
- Where does the copilot get its rates from?
- Only from your own order history, not from market indices or other companies' data. The model looks for routes similar in direction, distance, cargo type and season, and shows which past orders a suggestion rests on. If there were no similar routes it says there is no basis rather than guessing. A quote does not reach the client until the forwarder approves it.
- Will the margin guard block a cheap order?
- No. The guard shows that the rate has dropped below the threshold for that route and season and offers an alternative, but the decision stays with the forwarder. There are good reasons to take an order below the threshold, a return leg that would otherwise run empty being the obvious one. The system supplies the number behind that decision, it does not take the decision away.
- What about driver data and fleet monitoring?
- Location and working time data are personal data of the driver, so the scope and purpose of collection go into the documentation before launch. The client panel shows a status and an expected arrival time, not a continuous vehicle trail. Performance data is not exposed as a driver ranking, because that is the most common source of conflict in this kind of rollout.
- How many orders a month does this need to pay off?
- The threshold usually sits somewhere around one hundred to one hundred and fifty orders a month, but the count matters less than how often somebody answers a client asking where their freight is. If that happens a dozen times a day, the client panel pays back faster than the AI module. Below that scale we usually propose mapping and a lighter panel.
- Will carriers actually use it?
- The carrier panel is built for a phone and for one action, uploading a document and confirming a status, without asking for an account and a password at first contact. Rollouts that require a carrier to log into yet another system tend to end with photos going back to a messaging app, so this path has to be shorter than sending a photo.
Let us check whether this fits your company
Instead of a contact form we ask for five things. On that basis we come back with a price range and a proposed mapping scope, or with a straight answer that in your case the numbers do not add up.
- sector and line of business
- company size and how many people sit in the process
- systems you use today
- the process that hurts most
- rough budget