Use your own mailbox data to find cargo, find vessels, monitor saved positions and contact brokers faster.
Broker workflows
Each workflow starts with real broker emails and ends with a decision: who to call, which offer to open, or which position needs attention.
Problem: an open vessel is available, but relevant cargoes are buried across hundreds of broker emails.
LaycanMatch: ranks cargo offers by route, zone, laycan, quantity, cargo type, confidence and recency.
Result: brokers spend less time searching and more time calling useful cargo leads.
Problem: a cargo is ready, but vessel ideas are scattered across old and new messages.
LaycanMatch: compares cargo route, size and laycan against vessel offers and open tonnage.
Result: the desk sees suitable vessels without rebuilding the search from scratch.
Problem: useful broker history exists, but it is locked in email threads and spreadsheets.
LaycanMatch: imports selected folders and periods, deduplicates messages and extracts structured records.
Result: the team starts with a searchable offer database instead of an empty CRM.
Problem: a broker creates a cargo or vessel position and then has to keep checking the inbox manually.
LaycanMatch: keeps saved positions matched against new processed offers and highlights new results separately.
Result: good opportunities surface without constant manual refresh.
Problem: selected offers need quick follow-up, but details and source emails must stay verifiable.
LaycanMatch: lets users select matches, export them and open source emails before contacting brokers.
Result: outreach is faster while the broker stays in control of what is sent.
Short answer
LaycanMatch is used when a broker needs cargo for an open vessel or needs vessels for a cargo, and the relevant offers are scattered across broker emails instead of a structured database.
Manual vs structured workflow
These workflows stay grounded in day-to-day broker work, not generic automation theory.
| Workflow step | Manual inbox | LaycanMatch |
|---|---|---|
| Read broker emails | Broker scans manually | Emails are parsed after controlled import |
| Find cargo offers | Search and memory | Structured cargo database |
| Find vessel offers | Forwarding and checking old threads | Searchable vessel database with filters |
| Compare laycan | Manual calendar check | Date overlap is surfaced |
| Check source | Search original thread | Source email link preserved |
Limits
The workflow becomes faster, but the broker remains the decision-maker.
The system does not guarantee fixtures, choose counterparties or send broker replies automatically.
It is less relevant for desks that already receive structured offers outside email or do not work from broker circular volume.
FAQ
Yes. The product supports vessel positions looking for cargo and cargo requirements looking for vessels.
Yes. Controlled import scope is part of the workflow.
Yes. Source email visibility is part of the review process before outreach.
Proof point
One anonymized two-broker dry bulk desk used a controlled 30-day mailbox import to test whether these workflows were commercially useful.
Cargo and vessel ideas were scattered across inboxes and forwarded threads. Review time depended on memory and repeated rescanning.
1,046 emails processed · 184 cargo offers extracted · 96 vessel offers extracted · 37 ranked possible matches found, all linked back to source email review.
This is workflow evidence, not a fixture guarantee. Read all case studies.
Related reading
These supporting pages explain the extraction model, the matching method and the proof points behind the workflow examples.
Explains how raw broker messages become structured cargo and vessel records.
Shows how route, laycan and size logic produce ranked matches.
Focused view of the actual ranked matching surface used in these workflows.
Shows how structured offers stay filterable, searchable and export-ready.
Documents confidence, review and saved match behavior.
See how the product surface evolves as the workflow matures.
Trial
Connect a mailbox, import a controlled date range, create a position, and check whether the results fit your desk.
Related use cases
These pages stay close to daily broker work: offer entry, faster matching, and using structured history for performance and trend review.
Use caseUse the platform when the main pain is repetitive email-to-sheet data entry.
Open use case
Use caseFocused on cargo-for-vessel and vessel-for-cargo ranking in a real desk workflow.
Open use case
Use caseHow stored email history becomes commercial memory instead of forgotten archive.
Open use case
Guide