Product operator
YAS sp. z o.o. operates the product and handles product, security and commercial contact through [email protected].
Short answer
LaycanMatch was created as a workflow product, not as a generic maritime software brand page.
The product exists because broker desks often have useful cargo and vessel data inside email, but not in a searchable form. LaycanMatch was built to structure that inbox layer, preserve source-email review, and improve cargo-vessel matching without taking commercial control away from the broker.
Who is behind it
Built and operated under a visible legal entity.
LaycanMatch is operated under YAS sp. z o.o., with a public company identity, contact email and registered address visible on the site. The product direction is centered on AI-assisted workflow automation, operational clarity, and broker-controlled review rather than black-box automation claims.
Why this matters
Broker desks need to know which legal entity stands behind a mailbox-facing product before connecting email infrastructure.
Product focus
The product scope is intentionally narrow: broker email parsing, structured offer records, matching, saved positions and review visibility.
Why it was created
The target problem is repetitive inbox work before a deal reaches CRM.
Most maritime software starts too late, after data is already structured. LaycanMatch starts earlier, where desks still lose time scanning broker circulars, comparing laycan windows, checking DWT fit and reopening old threads to verify source text.
Product principles
How the product is intentionally constrained.
This page should make it clear that the operator is not selling artificial certainty. The workflow is designed to help the desk move faster while keeping control and accountability visible.
No automatic broker replies
LaycanMatch does not send replies or negotiate freight terms on behalf of the broker.
No fake certainty
Confidence score and source review are part of the product because extraction can still be ambiguous.
Deployment choice matters
Hosted, dedicated and on-premises paths exist because mailbox sensitivity is part of the buying decision.
Commercial judgment stays human
The broker still decides what to pursue, which counterparty to call and how to position the cargo or vessel.
Legal and contact
Public company details and trust links.
For procurement, compliance or founder-level questions, the site should provide a direct route to the legal entity and supporting trust pages.
| Item | Value |
|---|---|
| Legal entity | YAS sp. z o.o. |
| Address | Prosta 20, 00-850 Warszawa, Poland |
| Contact email | [email protected] |
| Relevant trust pages | About · Security · Methodology · Privacy · Terms |
Related trust pages
Open the pages that explain product scope and operational logic.
A founder/operator page should route users to product, methodology and security context instead of standing alone as a vanity page.
About
Company-level overview and why the product exists for broker desks.
Methodology
How extraction, confidence and matching are interpreted.
Security
Mailbox handling, retention, encryption and deployment options.
Product updates
Evidence that the product is maintained and actively developed.
Talk to the operator
Need a direct answer before connecting a mailbox?
Use the contact page for product, security, deployment or procurement questions.