Scattered context
Files, email threads and instructions live in different places.
SHIPMENT INTELLIGENCE. WITHOUT
THE GUESSWORK.
Every shipment.
One clear picture.
Documents don’t always tell the same story. FreightMind connects the details, catches the discrepancies, and shows your team what needs attention.
LESS PAPERWORK. MORE PERSPECTIVE.
ORIGINShenzhen
OCEAN FREIGHT
DESTINATIONLagos
Shipment overview
The details that need your attention, all in one place.
Active shipments ▦
5In this sample workspace
Open exceptions ⚑
5 Across 3 shipments
Checks clear ✓
2No document exceptions
| SHIPMENT | ROUTE | DOCUMENTS | STATUS |
|---|
Fictional records. Real-world document challenges.View a shipment to explore ↗
ONE CONNECTED SHIPMENT FILE
▤ Commercial invoices▤ Packing lists▤ Bills of lading▤ Customer instructions
THE PROBLEM IS IN THE GAPS
One shipment.
One shipment.
A dozen versions
of the truth.
An invoice says 1,250 cartons. The bill of lading says 1,200. Your team shouldn’t have to discover the difference at the last minute.
Repeated checks
Teams compare the same fields, one document at a time.
Late surprises
Missing information surfaces when there’s little time to act.
A CLEARER WAY TO WORK
From shipment folder
From shipment folder
to shared understanding.
A focused workflow for checking documents.
Built to support
your existing operations.
↥
Bring the documents
Group the commercial invoice, packing list and bill of lading under one shipment.
COLLECT▤
Structure the details
Turn document content into consistent fields for parties, quantities, weights and references.
NORMALISE⇄
See what doesn’t agree
Compare records and surface missing information and mismatches, with source references.
RECONCILE✓
Review with confidence
Inspect the evidence, add context and decide what needs correcting or escalating.
HUMAN REVIEW
LESS NOISE. MORE SIGNAL.
Don’t just flag a problem.
Don’t just flag a problem.
Show where it starts.
Every finding should lead back to the records that explain it. No black box, and no autonomous trade decisions.
These quantities don’t match.
Review required
DOCUMENTQUANTITYWEIGHT
▤ Commercial invoice1,25018,420 kg
▤ Packing list1,25018,420 kg
▤ Bill of lading1,200 −5017,910 kg
Here’s what needs a closer look
The bill of lading lists 50 fewer cartons and 510 kg less gross weight. Check the source documents before accepting the shipment record.
Invoice · p.1Packing list · p.1B/L · p.1
Illustrative finding · Human review required
One shipment, connected records
See the parties, containers, documents and open exceptions together. Stop rebuilding context from scattered folders.
Checks that understand the context
Use deterministic comparisons for numbers, and AI for ambiguous descriptions, units and document relationships.
Your procedures in the loop
Planned knowledge retrieval brings customer SOPs and carrier instructions into explanations, with evidence for review.
A clear handoff to a person
Log a finding, add a review note and record a decision. Customs, trade and release decisions stay with your team.
FOR THE TEAMS BEHIND THE MOVEMENT
Built around the shipment.
Built around the shipment.
Useful across the handoffs.
Starting with document-intensive freight operations in Africa. Designed for trade across borders.
Freight forwarders
Bring customer, supplier and carrier documents into a single review workflow.
OUR INITIAL FOCUSImporters
Spot inconsistent quantities, weights and references in incoming shipment records.
Exporters
Check that outgoing documents tell a consistent story before the next handoff.
3PL operations
Give operations teams a shared view of documentation gaps and unresolved findings.
INTELLIGENCE WITH A FOUNDATION
Purpose-built workflows.
Purpose-built workflows.
Planned on AWS.
The architecture combines document extraction, structured checks and context-aware reasoning. Each service has a specific job.
Architecture roadmap. No claim of AWS partnership, certification or a live production integration.
Explore our security approach ↗01Read and structureAmazon S3 · Amazon Textract+
S3 is planned for shipment files. Textract will extract text, tables and document structure so the application can validate shipment fields.
02Normalise and explainAmazon Bedrock+
Foundation models will classify documents, normalise ambiguous fields, interpret document relationships and explain exceptions. Ordinary code will compare numeric values.
03Ground in your proceduresAmazon Bedrock Knowledge Bases+
Customer-specific retrieval will bring relevant SOPs, carrier instructions and historical records into the review context. Evidence remains available for human verification.
04Connect and operateLambda · RDS · API Gateway · Cognito · CloudWatch+
Lambda will orchestrate processing; RDS will hold shipment records. API Gateway will serve application APIs, Cognito will support authentication, and CloudWatch will provide monitoring. Tenant access rules will be enforced by the application.
A PLAN FOR EVERY STAGE
Start with a shipment.
Start with a shipment.
Build a better operation.
Proposed monthly launch pricing. Plans and availability will be validated during the pilot.
For a focused operations team.
$99/ month
- 100 shipments per month
- Core shipment document checks
- Evidence-linked exceptions
- Human review workflow
For a busier shipment desk.
$299/ month
- 500 shipments per month
- Everything in Starter
- Shared shipment visibility
- Pilot onboarding support
For more complex workflows.
$799/ month
- Higher volume, scoped together
- Everything in Growth
- Team requirements assessment
- Integration planning
Need a custom setup?
Let’s scope an Enterprise plan.
Illustrative USD pricing from our launch plan, not a final offer. User limits, document allowances, taxes and additional usage will be agreed before any paid engagement.
GOOD QUESTIONS. CLEAR ANSWERS.
Before you
Before you
come aboard.
What does the first version focus on?
Creating a shipment record, collecting commercial invoices, packing lists and bills of lading, structuring their information and flagging missing or conflicting data. Wider document support and operational workflows are part of the roadmap.
Does FreightMind make customs or trade decisions?
No. It is designed to surface information that requires review. Authorised people remain responsible for document corrections, customs decisions, compliance checks and shipment release.
Can we use our existing logistics systems?
The intended role is an intelligence layer alongside your existing TMS or ERP. Specific integrations are not yet promised; requirements will be scoped during pilot discovery.
What happens when units or descriptions differ?
The workflow separates exact numeric comparisons from ambiguous interpretation. A pallet count may differ legitimately from a carton count. Reviewers verify the source context and record corrections instead of treating every difference as an error.
Is the interactive workspace connected to AWS?
No. This website includes a browser-only demonstration with fictional records. It does not upload files, run AI extraction or connect to customer systems. The AWS section describes the planned platform architecture.
Who is the pilot for?
We are initially exploring document-intensive workflows with freight forwarders in Africa, alongside importers, exporters and 3PL teams. Pilot scope, readiness and timing will be discussed individually.
CLARITY BEFORE THE NEXT HANDOFF
Keep the shipment moving.
Keep the shipment moving.
Catch the details that don’t.
Explore what a clearer document workflow could look like for your team.