Part Three · Comparing Vendors All chapters

References, Case Studies, and the "Show Me a Customer Like Me" Test

How to check a vendor's story with the people who actually live inside their software

The demo showed you the vendor's best version of their product. References show you the version their customers live with every day, which is the one you'll actually get. But only if you talk to the right customers and ask the questions the vendor didn't prepare them for. This chapter is about doing that well.

A case study is an ad

A vendor case study is a commissioned, mutually approved marketing artifact written to help close deals. That doesn't make it false. It makes it selective. The metrics are the flattering ones, the customer is a happy one, and the season everything went sideways isn't in there.

So read a case study the way you'd read any ad: for what it proves and what it quietly leaves out. A polished case study proves the software can work well for someone, on a good day. It doesn't prove it will work for you. That's the start of your homework, not the end of it.

A published case study, read the way it should be read: as marketing, with the omissions doing as much work as the numbers

A case study tells you the software worked once, for someone, on a good day. Your job is to find out what happens on the other days.

When you do read one, look past the headline number. Notice what's actually measured and what isn't, whether the figures are specific or vague, whose words are being quoted, and, most of all, whether the customer's operation looks anything like yours.

Find your mirror

The "show me a customer like me" test

The single most useful request you can make of a vendor is this: show me a customer like me. Not your biggest logo, not your flashiest install. A marina whose operation actually resembles mine.

"Like me" means comparable on the things that shape how software gets used: size, marina type (transient-heavy, seasonal, dry stack, yacht club), and structure. An independent operator learns almost nothing from a twelve-property enterprise reference, and a multi-property group learns almost nothing from a single eighty-slip marina. The vendor's flagship customer is designed to impress, not to inform your decision.

This is where the two operator types should push in different directions. An independent operator should insist on references that are independent marinas of similar size and revenue mix. A multi-site operator should insist on genuine multi-property references, and use the call to probe rollups, per-site access, and central oversight, the reporting questions from Chapter 7.

A marina that looks like yours: similar size, similar mix. That's the reference worth calling

Red flag

If a vendor can't produce a single reference that looks like your operation, treat that as an answer. Either they don't serve marinas like yours well, or they don't have many. Both are worth knowing before you sign.

Try this

Write your "like me" in one sentence before you ask: size, type, and structure. For example, "a transient-heavy independent marina of roughly 150 slips with a fuel dock." Then hold the vendor to producing a reference that matches it, not one that's merely nearby.

Then get them off-script

What to ask a reference

Vendors coach references, at least lightly. So a reference call is only worth the time if you steer it somewhere the coaching didn't reach. Use the fifteen questions from Chapter 11 as your backbone, but aim each one at lived experience rather than capability.

"What broke in your first season, and how did support actually handle it?"
"What do you still do in a spreadsheet because the software can't?"
"What surprised you after go-live that the demo didn't show?"
"How did the migration really go, honestly?"
"If you were choosing again, would you pick them? What would you check that you didn't?"

The most revealing question is the simplest: what do you wish you'd known before you signed? It gives the reference permission to tell you the thing the case study left out.

Pro tip

Ask to speak with a daily user, the dockmaster or front-desk lead, not only the owner who signed the deal. The owner remembers the sales process; the daily user remembers what it's like at 2pm on a Saturday. That's the person whose answer predicts your experience.

Takeaway

Read case studies as ads, insist on a reference that mirrors your operation, and steer the call to the questions vendors don't prep for. The goal is simple: hear the truth from someone who has no reason to sell you anything.

Part Three is done

Where this goes next

You've now framed your needs, mapped the market, and pressure-tested the vendors. Part Four turns to the commercial conversation: what the software really costs, how the pricing models differ, and which contract clauses are worth negotiating. It starts with Chapter 14.

Next: Chapter 14 · Part Four

Understanding marina software pricing

The commercial conversation begins. The pricing models, what each one really costs at your volume, and how to compare quotes that are built to be hard to compare.

Read Chapter 14 →

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