Part Six · Specialized Situations All chapters

If You Operate Multiple Marina Properties

Portfolio reporting, standardization, and finding a vendor that can actually scale to you

Several chapters have been sending you here. Running a portfolio of marinas is not running one marina several times over, and the software decision changes accordingly. Three problems define multi-site: seeing the whole portfolio at once, deciding what to standardize and what to leave local, and finding a vendor that can genuinely handle your property count. This chapter takes each in turn.

A portfolio is not a bigger marina

Twelve marinas is not one marina running twelve times. It's a different problem, and it brings its own class of requirements that a single-site operator never has to think about. The question isn't only "is this good software for a marina," but "is this good software for a group of marinas run as one business."

Three questions decide it. Does the data roll up into a portfolio view, or stay trapped per site? Can you standardize what needs to be uniform without straitjacketing every location? And can the vendor actually operate at your scale, not just their biggest current customer's?

A portfolio rollup: every property in one view, with the ability to drill into any single marina

A portfolio isn't a bigger marina. It's a different problem wearing the same uniform.

See the whole portfolio

Portfolio reporting and rollups

The reporting dimension from Chapter 7 is where multi-site lives or dies. For a group operator, these are non-negotiable:

True rollups. Every property in one view, with the ability to drill down into any single site.
Side-by-side comparison. Occupancy, revenue, and receivables across all sites at once, so you can see which property lags.
Role-based access. Each site manager sees their property; you see all of them. Without this, central oversight becomes central data entry.
BI depth. If you live in Power BI or a data warehouse, the quality of the connector matters more than the built-in dashboards. Ask about the enterprise tier specifically.

Without genuine rollups, "multi-site support" means multiple logins and a spreadsheet where you re-consolidate by hand every month, which is exactly the manual work a portfolio system is supposed to eliminate.

Uniform where it counts

Standardize vs localize

The central multi-site tension is which things should be identical across the portfolio and which must flex per property. Good software lets you enforce the first and allow the second. Get this wrong in either direction and you pay for it.

Standardize across sites

Chart of accounts and billing rules, so the numbers mean the same thing everywhere.
Reporting definitions and KPIs, so sites are actually comparable.
Core pricing logic and financial controls.

Localize per property

Dock geometry, slip maps, and physical layout.
Local rates, promotions, and seasonal patterns.
Staffing and some day-to-day workflow details.

The two failure modes are opposite and equally costly. Too rigid, and every site is forced into one mold until local managers revolt or work around it. Too loose, and every property becomes a snowflake with no comparability, which defeats the point of running them as a portfolio. Ask the vendor, live, how they handle both at once.

Can they handle your count?

Can the vendor actually scale to you?

Here's the question group operators most often skip: can this vendor actually run at your scale? A vendor whose largest customer has three properties may be excellent there and buckle at your eighteen. Impressive at one site is not the same as proven across a portfolio.

What is your largest live deployment, by property count, and can I talk to them?
Is the product built for multi-entity portfolios, or a single-site system with a group view bolted on later?
How do you onboard a new site once we're live, for acquisitions and growth?
What does support look like across a portfolio, not just one marina?
What does the enterprise tier actually include, in specifics, from Chapter 14?

Red flag

No reference customer anywhere near your property count, from the "show me a customer like me" test in Chapter 13, or a portfolio view that's clearly an afterthought stapled onto a single-site product. Either means you'd be the vendor's scaling experiment, at your own expense.

Scale is leverage

Volume leverage and readiness

Your scale is also your leverage. Negotiate at the portfolio level, not site by site: volume rates, a genuine enterprise tier, capped escalation, and one master agreement, using the leverage from Chapter 14 and the clause discipline from Chapter 15. And sequence the rollout: prove the migration on one representative site before you touch the rest.

Interactive · Coming soon

Multi-site readiness calculator

Enter your number of properties, how standardized your operations are today, and your growth plans. Get a portfolio-level scale assessment that flags which scaling questions to prioritize in evaluation, so you spend the demo on what actually breaks at your size.

Takeaway

Judge a vendor as a portfolio operator, not a marina operator. Demand real rollups, the right balance of standardized and local, and proof they run at your scale, then use that scale as leverage in the deal.

Or if you're stuck

Next: Chapter 23

If you inherited or are stuck on legacy software

The next specialized situation: operators trapped on old or failing systems. How to assess how stuck you really are, what your options are, and how to plan an escape without losing your data or your season.

Read Chapter 23 →

References and further reading

Sharper MMS, Map the Switch Migration Assessment
Association of Marina Industries (AMI), industry research and benchmark data. marinaassociation.org
Storable Marine, AMI, and Marina Dock Age, Navigating the Numbers: 2026 Marina Operator Insights & Technology Automation