We measure it on 500 of your own booking emails in 14 days, scored field by field, before you commit anything to the full build.
Fixed pilot fee. Miss the accuracy threshold we set together and you pay nothing. No licences, no multi-year commitment.
What keying bookings actually costs
Count one week of booking emails, then multiply by what a coordinator hour costs you. Most operations directors stop debating this at that point.
per booking to read the mail, open the attachments and key a shipment, before anyone chases a missing field.
keying error rate on ports, container types and weights. Each one resurfaces as a customs query or an amended bill.
of lag between a booking landing in the inbox and the shipment existing in the system. That gap is where your visibility problem starts.
who knows which shipper abbreviates which port, and takes that with them when they move on.
Three fields. This is what keying bookings costs you per year.
Excludes customs queries, amended bills and the visibility gap while a booking waits in the inbox, so the real number sits higher.
The mechanism
Not a mailbox rule with OCR bolted on. An extraction and validation layer trained on your senders and your trade lanes, writing shipments through the integration with a full audit trail.
The mail body, the packing list, the commercial invoice, the shipper's own spreadsheet. Fields are pulled from all of them and reconciled against each other, not lifted from whichever attachment came first.
Organisation codes, UN/LOCODE ports, container types and Incoterms are checked against your own master data before anything is written. An unrecognised shipper stops the booking; it never gets guessed.
The shipment is created with every value linked back to the line of the document it came from, so a coordinator can audit any field in seconds instead of reopening the email chain.
A shipper's booking request on the left. What the layer extracts on the right. Illustrative example with fictional data.
| Pcs | Description | Gross kg | Cbm |
|---|---|---|---|
| 12 | Frozen fillets, cartons on 4 pallets | 9,480 | 14.2 |
| 1 | 40ft reefer, set to -22C, genset requested | - | - |
| - | Phyto certificate to follow separately | - | - |
S00148223 · NORSEA · NOBOO → NLRTM · 1x40RH · 9,480 kg · CIF · ready 06.08.2026
The offer
One fixed fee. Fourteen days. Your real booking traffic. A number at the end that tells you, and us, whether the full build earns its cost.
Not a workshop. The pilot ends with your bookings written into a test environment and an accuracy number your operations lead can audit.
Against a problem costing most clients €40,000–70,000 a year.
Credited in full against the build if you proceed within 90 days.
No software to install, no workshop series, no project team on your side. Your people keep working; we work on copies.
Before we start, we agree the accuracy threshold that makes this worth deploying. Together, in the engagement letter. If the measured result on your documents comes in below it, the pilot is free. We can offer this because we scope honestly: if we don't think your document mix can hit the number, we decline the pilot and tell you why.
Pilots run one at a time per engineer, so they start in the order requests arrive. Current lead time: about two weeks
Your actual alternatives
| Do nothing | Hire another coordinator | Add-on tool | Braynex pilot → build | |
|---|---|---|---|---|
| Handles your awkward senders | ✕ they stay manual | ✓ until they leave | ✕ the odd formats stay manual | ✓ trained on your sender mix |
| Cost over 3 years | rising with volume | €135–190k+ | €20–45k + the manual remainder | known, fixed, quoted |
| Proof before commitment | - | ✕ | ✕ demo on their sample data | ✓ measured on your bookings |
| Survives staff turnover | ✕ | ✕ | ✓ | ✓ documented end to end |
| Audit trail per field | - | partial | varies | ✓ traced to the source line |
Why believe us
AI that converts medical records into legally defensible timelines. Accuracy-critical, regulated, every extraction traceable to its source page.
Client meeting recordings become compliant advisory documents automatically, adopted across the practice for every client meeting.
Production vision-AI moderation for marketplace listings: real ML in production at volume, not an API wrapper.
Swiss entity (Zug) · EU-region hosting · GDPR & revised FADP compliant · named senior engineers you meet before signing
Fair questions
For your top ten shippers who always send the same template, it probably is. Keep it. The cost we go after is the long tail: the agent who sends the booking in the mail body with no attachment, the shipper whose packing list is a photo, the customer who changed their spreadsheet columns last month. That tail is small in volume and large in handling time.
Writing is the part we prove first, which is why the pilot includes a real batch created end to end in a test environment rather than a video. If your specific configuration blocks it, you learn that in week one for a fixed fee, not in month four of a build.
It stops and goes to your team with the conflict stated in words ("the Incoterm says Rotterdam but the delivery address is inland"). It does not create a half-right shipment that someone finds at the quay. The measure that matters is not just accuracy, it is whether the system reliably knows when it is unsure. The pilot reports that separately.
Sometimes you should, and the pilot will tell you. If the analysis shows an available product covers your sender mix, the report says so and we part as friends. You will have paid a fixed fee for certainty either way. We only recommend a build where the measurements support one.
EU-region hosting, a GDPR-compliant processing agreement, and a contract with our Swiss entity in Zug. Nothing trains a public model. Your own compliance lead can review the setup before the pilot starts, and the pilot sample can be narrowed to a subset you are comfortable sharing.
Because we are structured for exactly this engagement size. The large consultancies staff €60k projects with juniors or decline them; we deliver them with the people you actually meet. That is the trade we have built the company on.
Start here
Tell us your booking volume and where the emails come from. We reply within one business day with an honest read on whether the pilot makes sense for you, including when it does not.
Lead Engineer · runs your pilot
The people on this page are the people on your project. No handover to a delivery team you never met: the engineer who scopes your pilot is the engineer who builds it.
Braynex
Prishtina, Kosovo · Zug, Switzerland
Contact: contact@braynex.ai
Responsible for the content of this page: Braynex. Further statutory details (register entries, VAT identification) are available on request and via the main website at braynex.ai.
The contact form on this page sends your entries directly to contact@braynex.ai by email. We use the data you provide solely to respond to your enquiry; it is not shared with third parties, used for advertising, or added to any mailing list.
This page is hosted in the EU region and sets no marketing cookies. For questions about your data or to request deletion of correspondence, write to contact@braynex.ai.