Dev

Getting Marine Schedule's First Users — The Reality of B2B Sales

2020-06-08·3min read

Published. Nobody Came.

After completing development and posting to the App Store, the download count stayed at zero.

With consumer apps, there's at least a chance of organic discovery through App Store search. With a B2B app targeting ship repair professionals, that doesn't happen. Nobody searches the App Store for "ship repair project management tool." You have to go find your users.

For an indie developer without industry connections, that's a significant wall.

Finding the First User

Through a mutual contact, I got an introduction to someone at a shipyard.

I showed them the app and explained what problem it addressed. The reaction was positive — "This looks useful." But a positive reaction and an adoption decision are very different things.

"Looks good, but changing how the team communicates..." Organizational inertia is real. People have workflows that have been running for years. Replacing them requires convincing multiple stakeholders, not just one.

The path forward: a small pilot. Run Marine Schedule alongside an active repair project — not replacing the existing workflow, just running in parallel to demonstrate value. Low stakes, low commitment.

What Field Feedback Changed

During the pilot, on-site feedback shifted how I'd built several things.

The original UI was "logical" from a developer's perspective. It wasn't logical from the field. Some shipyard workers weren't heavy smartphone users. Some needed to operate the app on deck wearing work gloves. Tap targets that seemed fine on a desk were too small in real conditions.

I made buttons bigger. I moved the most critical actions to the top of every screen. I cut flows that required more than two taps for common tasks.

"Beautiful" became less important than "can someone use this correctly under pressure without thinking about it."

The Value of a Reference Customer

After the pilot, that project became the first reference case.

"A completed ship repair project managed with this app" — that's concrete. In B2B sales, a reference customer changes the conversation. Instead of "here's what this app could do," I could say "here's what happened on a real project."

The second sale was easier than the first. The third was easier than the second. This is how B2B growth works.

What's Different About B2B

The experience clarified what makes B2B different from consumer apps.

Consumer apps need to convince an individual. B2B apps need to convince a decision-maker, the field users who will actually use it, and sometimes an IT department that has to approve new software. The sales cycle is longer. Contracts are more complex. Support expectations are higher.

The tradeoff: users who adopt tend to stay. Churn is lower. Revenue per customer is higher. Very different economics than chasing consumer downloads.