Design partners
Start with one route and your historical data.
We are working with a small number of freight operators to test whether capacity pressure can be identified early enough to improve real planning decisions. We are also inviting other freight operators to evaluate whether the same approach can create measurable operational value on one of their own routes. Phase 1 is a bounded historical study of one route or corridor. No live integration, workflow change or autonomous action is required.
The evaluation
Three questions we want to answer.
Phase 1 is designed to answer them honestly for one corridor — including when the answer is no.
- 01
Could the capacity problem have been identified earlier?
Using only information available at the time, would the pressure on your corridor have been visible 24–48 hours ahead?
- 02
Would a useful capacity option have been available at that point?
Given your carriers, equipment and departures, was there something worth preparing — and at what cost?
- 03
Would acting earlier have been economically better than waiting?
Compared with what actually happened, would preparing capacity early have paid off — or cost more than it saved?
Example · Ferry and ro-ro operators
How many lane metres per sailing are lost to late cancellations and no-shows, and how early could that have been predicted well enough to safely resell the space?
One example of an operator question, not the only one. Road carriers, forwarders and shippers bring their own: the study is built around the question we agree with you.
Who
Built with the people who plan the capacity.
Road carriers
Recurring cross-border or domestic lanes where equipment is repositioned at short notice.
3PLs & forwarders
Networks that buy and coordinate capacity across several carriers.
Ferry & ro-ro operators
Departures where freight demand and deck space have to meet on time.
Shippers
Regular outbound or inbound flows that depend on capacity being there when needed.
Phase 1 scope
Deliberately narrow.
Phase 1 is designed to be low-effort for your team and low-risk for your operations.
No cost
Private feasibility report for your corridor.
One route or corridor
A single recurring lane, route or sailing you know well.
A bounded historical period
Long enough for the agreed question. How much history that needs depends on the question and the data; the report states what the period can and cannot support.
Pseudonymised identifiers
Shipment and vehicle identifiers are replaced before analysis.
No live integration
A secure file transfer is enough for Phase 1.
No workflow change
Your planners keep working exactly as they do today.
No autonomous action
Nothing is booked, moved or sent on your behalf.
What you share
Typical historical fields.
Where available. We work with what you have: none of these fields is mandatory on its own, and the analysis reports what is possible with the data available.
| Field | Notes |
|---|---|
| Booking ID | pseudonymised |
| Booking created timestamp | when the demand became known |
| Amendment / revision timestamp | where your system keeps one |
| Cancellation timestamp | where recorded |
| Sailing / departure identifier | or trip, lane or slot |
| Planned departure time | date and time |
| Booked lane metres | or an equivalent capacity unit |
| Vehicle / freight class | e.g. trailer type, unit |
| Outcome | shown, no-show or cancelled |
| Final used lane metres | or executed capacity |
| Origin / destination | where relevant |
What you get
A private feasibility report.
Written for your planning and management team, with the evidence class of every finding stated. Historical and modelled findings are never presented as realised savings or ROI.
- Data quality and timestamp provenance
- How bookings and demand evolved before departure
- Cancellation and no-show patterns, where relevant
- Forecast lead time: how early a signal was usable
- Comparison against your current or a simple operating rule
- False-alert burden: how often a signal would have been wrong
- Potential recoverable or resellable capacity, where the data support it (MODELED)
- Lane-metre impact for ferry use cases, where available (MODELED)
- Economic interpretation only where your source data support it — never realised savings
- A clear recommendation: proceed, adjust the scope, or stop
Process
How a design partnership runs.
Before the analysis starts, we agree the decision horizon, baselines, operational success threshold and proceed / stop rule. The threshold is not changed after seeing the result.
- 1
Introductory call
We discuss your route, your planning process and whether the data exist. Nothing to sign.
- 2
Agree the question and route
One operational question on one route or corridor.
- 3
Data sharing agreement
A data sharing agreement, and a DPA where applicable, covering scope, retention and deletion.
- 4
Written next step
A light LOI or written next-step understanding, once both sides want to proceed.
- 5
Secure data transfer
A bounded historical extract into your own isolated tenant.
- 6
Pre-registered test plan
Metrics, baselines and decision thresholds are written down before the analysis.
- 7
Historical feasibility analysis
Captrixa runs the analysis without temporal leakage.
- 8
Private review
We walk your team through the report — including anything that did not work.
- 9
If the agreed gate is passed
We discuss a paid shadow pilot or a funded R&D collaboration.
- 10
Otherwise
We stop, or adjust the scope. No obligation.
Questions
Frequently asked.
Does it cost anything?
No. The Phase 1 historical feasibility evaluation is offered at no cost to design partners.
Do we need an API or integration?
Not for Phase 1. A historical export from your TMS, booking system or spreadsheets is enough.
What if our data are incomplete?
That is common and part of what the analysis measures. The report states clearly what the data can and cannot support.
Who can see our data?
Only authorised users in your own tenant and the Captrixa team working on your evaluation. It is never shown publicly or to other partners.
Do we need to sign anything before the first call?
No. The introductory call comes first. A data sharing agreement (and a DPA where applicable) comes before any data are shared, and a light LOI or written next-step understanding only once both sides want to proceed.
Will you promise savings?
No. Phase 1 measures whether your data contain usable predictive signal. Economic value can only be measured later, from observed outcomes.
Can we stop at any time?
Yes. Every phase ends with a decision point, and your data are deleted according to the agreement.
Have a route in mind?
Tell us about the route and the data you hold. We will tell you honestly whether a feasibility evaluation is worth your time.