Requests arrive everywhere
Tenants, guests, and vendors reach the desk by phone, text, and walk-up.
Network-led · Destination Network
One operating layer for a marina, harbor, or destination.
MERIDIAN Destination Network gives marinas, harbors, port offices, and multi-property destinations one layer to coordinate tenants, transient guests, vendors, port partners, notices, arrivals, service requests, documents, and local operating rules.
$2,500from / mo per property
Target pricingconfirmed in a written proposal
Guest loginapproval required
Scoped invitesvendors & tenants free
Who it is for
Built for this seat.
- Marinas and waterfront properties
- Harbors and port offices
- Regional yacht-service groups
- Multi-property destinations handling visiting vessels
What it helps coordinate
- Visiting-vessel and transient intake
- Property, berth, and service workflows
- An approved vendor network
- Local authority workflow templates
- Tenant and supplier portals
- Regional reporting
The problem
Common operational problems.
Repeated context
The same vessel and tenant details are collected again at every touch.
No shared picture
Berths, arrivals, permits, and notices live in separate lists.
The change
How MERIDIAN changes the workflow.
- Visiting-vessel and tenant intake into one property file
- Berth, service, and work-order workflows with clear status
- An approved vendor network scoped to each job
- Tenant and supplier portals — respectful and permissioned, not a monitoring feed
- Notices and requirements that reach the right tenants and vessels
Key modules
What this desk runs.
Role access
Who gets a command deck.
Example workflow
One call, start to finish.
Intake the vessel or tenant
One property file for visiting vessels and tenants.
Assign and coordinate
Berths, service requests, and approved vendor access.
Publish notices
Requirements and updates reach the right people.
Report
Regional and property reporting from the live file.
Touchpoints
How other roles connect.
Tenants and guests
A private workspace for requests, notices, and approved access — respectful and permissioned.
Vendors
An approved network, scoped to each property and job.
Port partners
Coordinate arrivals and requirements without a shared inbox.
Trust & control
- Tenants see their own operation, not other tenants or internal operations
- Vendors are scoped to the property and job they are invited to
- Notices and requirements are permissioned by role
Discretion
You see your operation, and only your operation.
Every invite is scoped. Partners see the visit, request, or document you share — never your wider operation, finances, or other clients.
Questions
Frequently asked.
Is this a booking or reservation system?
No. Destination Network is an operating layer for coordination — arrivals, service, tenants, vendors, documents, and notices — not a public reservation widget.
How do tenants get access?
Tenants are invited by the property to a scoped workspace — no public signup — and see only their own slip or vessel.
Can we run more than one property?
Yes. Multi-property and regional networks are supported; larger networks move to an enterprise program.
Do vendors pay to receive jobs?
Vendors join free when invited by a subscribing property; a Vendor Pro upgrade adds their own dispatch workspace.
On screen
Local knowledge, authored once.
The guide studio turns destination knowledge into a reviewed, publishable product: sources gathered, geometry computed, publication gated on a lint pass.
Screens are from the current build, populated with sample data. Vessels, organisations, people, vendors, and figures shown are illustrative and are not those of any client.
Ready
Bring the whole property onto one layer.
Every workspace begins with intake, review, and a written proposal. Guest workspaces are approved manually.