Part Three · Comparing Vendors All chapters

The Vendor Landscape

A map of the market, so you can place any vendor before the first demo

You can't compare vendors well until you can see the shape of the market they sit in. This chapter draws that map. Not a list of company names, which go out of date the month you publish them, but the four categories the market sorts into. Learn the categories and you can place any vendor in seconds, and know its likely strengths and blind spots before anyone opens a laptop.

Why think in categories, not brands

A wide marina at work, an operation that four different kinds of software could run

Brand names are a bad way to understand a market. They change. Companies get acquired, rebrand, fold, or pivot, and any chapter that named them would be wrong within a year or two. Categories are different. The underlying shapes the market takes are stable, and almost every vendor you'll meet is a version of one of them.

The payoff is leverage in the demo. When you know a vendor's category, you already know the rough outline of its strengths and its blind spots, so you can spend the demo testing the things that category tends to get wrong instead of being dazzled by the things it always gets right.

The brand names will change. The categories won't. Learn the map and every vendor becomes easy to place.

Four shapes the market takes

The four categories

Marina software sorts into four broad categories. Here they are at a glance, then a word on what each one feels like in an evaluation.

Category	What defines it	Who it fits	Main tradeoff
Legacy desktop systems	Installed on a machine at the marina, often years old, on-premise, little or no cloud or mobile.	Operators who inherited it or have run it for a decade.	Familiar and paid for, but no mobility, weak integrations, and trapped data.
Transactional booking platforms	Built around taking transient bookings online. Booking-first, often per-booking pricing.	Transient-heavy marinas chasing online reach.	Strong at booking and reach, thin on back-office management.
All-in-one cloud platforms	A full module suite (slips, billing, POS, portal, reporting) in the cloud, ideally one system.	Operators who want one system to run the whole marina.	Breadth and integration, but you may pay for modules you don't use.
Niche specialists	Deep in one area: yacht clubs, dry stack, fuel, or multi-site, rather than broad.	Operations with one dominant specialized need.	Excellent at their specialty, weaker on everything around it.

Legacy desktop systems. You're almost always leaving this category, not choosing it. In evaluation, the relevant question isn't whether to pick one, it's how hard your current one will be to escape. If that's you, Chapter 23 is written for it.

Transactional booking platforms. The consumer booking demo will be gorgeous, because that's the whole product. Spend your time on the back office instead: slip management depth, billing, accounting. And run the pricing math, because per-booking models get expensive at scale, as Chapter 6 showed.

All-in-one cloud platforms. The pitch is "everything in one place." Confirm that "all-in-one" means one system rather than a bundle of acquired tools, the distinction from Chapter 2, and test the specific modules you'll actually use rather than admiring the breadth.

Niche specialists. If your operation has a dominant specialized need, these can be the best fit by far. The thing to check is the basics around the edges: does the deep yacht-club or dry-stack tooling come at the cost of weak billing, reporting, or integrations you'll still depend on every day?

Now place the vendors

Placing a vendor, and yourself

Placing a vendor on this map is usually quick, because vendors tell you their category by how they sell. A booking-first pitch is a transactional platform. A module suite is an all-in-one. One deep specialty is a niche specialist. A desktop install is legacy. Within a few minutes of any vendor's website you can pin the category.

Then place yourself. Which category actually fits your operation falls out of the work you've already done: the pains you named in Chapter 1, the modules you mapped in Chapter 2, and the dimensions you ranked in Chapter 4. A transient-heavy marina whose top dimension is customer experience leans one way; a multi-property group whose top dimension is reporting leans another.

Try this

Before any demos, tag each vendor on your shortlist with its category. That one label predicts where each will shine and where to push hard. Then notice whether your shortlist is actually three different categories, or three versions of the same one, which tells you whether you're really comparing options or just comparing logos.

One caution: the categories blur. Some platforms genuinely straddle two, and a few are deliberately repositioning from one to another. The map is a thinking tool, not a filing cabinet. Use it to predict tradeoffs, then verify the specifics with the scorecard.

Takeaway

Place every vendor in one of four categories before you evaluate it, and place your own operation too. The category tells you the tradeoffs to expect, so the demo becomes a test of the specific things that category tends to get wrong, not a tour of what it always gets right.

Categories first, then specifics

Where this goes next

Chapter 11 turns the framework into a 15-question scorecard you run on each vendor specifically, and Chapter 14 covers the pricing patterns that tend to come with each category.

Next: Chapter 11

The 15-question vendor evaluation scorecard

The framework, operationalized. Three questions per dimension, scored side by side, so you can compare the vendors you've now placed on the map.

Read Chapter 11 →

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