How PortFlow Overcomes Maritime Agency Trust Barriers with Targeted SaaS Solutions

Supply vessel due Tuesday at 2 pm. Nothing. I follow up, "tomorrow." Still nothing. I'm superintendent on a tanker at Blue Horizon, 2025. We need fuel and water. The agency gave us a supplier contact who took hours to answer, then gave times he didn't keep. You don't know how much fuel you're actually getting until the vessel comes alongside and someone physically counts. The request said one quantity. What arrived was different. Nobody at the agency knew the gap existed until the barge was tied up and we started the transfer. Everything before that was a WhatsApp thread and a guess passed between people who had no system connecting them. I'd been on the supplier side for 20 years at Valema, selling equipment and supplies to port terminals. I'd watched agencies operate like this from the outside and assumed it was just how the industry worked. Sitting on that tanker chasing a supplier who wasn't coming, I realized it wasn't industry culture. It was an unsolved problem. I started sketching the database that night.

Flopped, LinkedIn ads. I spent around $200 targeting maritime agency managers with a product demo. Zero conversions. The audience exists on LinkedIn, but they don't buy software from a sponsored post from someone they've never heard of. Maritime is a trust-first industry. You buy from people you've worked with, not from an ad that appeared in your feed. Worked (sort of), posting in maritime communities on Reddit with real data. Canal de Panama went fully paperless in January 2024. Paris MOU put four countries on the Grey List in July 2024, with detention rates around 4%. I shared those numbers and asked whether anyone was solving the back-office gap in agencies. Real replies from port agents, superintendents, and operations managers who recognized the problem immediately. No paying customer from it yet, but those conversations confirmed the problem is real, and that the people closest to it know exactly what's broken and have been tolerating it for years.

The test tenant I have hasn't complained about the product. They get stuck at the start. Years of crew records sit in Excel files. Vessel history lives in PDF attachments. Supplier contacts are in someone's personal WhatsApp that walks out the door if they quit. Moving all that into a new system feels like a separate job before the actual job. I built a CSV import tool. They still didn't touch it. So, I ran the first migration myself, for free. That got them past it. Doesn't scale, but it works while I figure out a better answer. The friction is switching, not the software. I've also heard this from captains I've shown the platform to, they want it but can't push their agency to adopt it. The buying decision sits with the agency owner, not the end user. My next step is a guided onboarding flow with sample data pre-loaded, so they see the product working before entering anything.

Most people outside maritime assume the industry runs on software because Maersk and MSC do. That's the shipping line. The agency handling your vessel at port, the one coordinating fuel, water, crew changes, port clearances, is a different business entirely. Usually 5 to 20 people. Still on WhatsApp and Excel. The second mistake, people think agencies won't adopt software because they distrust technology. That's a misread. The agencies I've talked to want to change. The problem is that nothing built for them has been specific enough. A generic CRM has no concept of an STCW certificate. A project management tool won't generate an FAL declaration. They tried generic tools, those tools didn't fit, so they went back to WhatsApp. Calling that resistance misses the point. They made the reasonable choice given what was available. The compliance layer is where generic tools fall apart completely. An STCW certificate has an expiry date, a certificate type, and a crew member attached to it. No generic CRM models that.

First paying customers. The product is ready and I'm pre-revenue, so the next six months are about converting interest into contracts. The target is five paying agencies by month three. After that, payments integration so agencies can pay inside the platform, and the PDA/FDA module, which handles port disbursement accounts - the financial layer agencies use to manage what they spend on behalf of ship owners. I've submitted to both YC S2026 and 500 Global. If either comes through, things move faster.

26 modules live. $20/month infrastructure. Zero external funding. Built it solo.

23 years in port supply. I founded Valema Suministros in 2000, selling equipment and supplies to port terminals across Costa Rica and abroad, including clients like Maersk and Del Monte. That gave me 20 years inside the supplier and terminal side of maritime operations. I’d never worked inside a maritime agency. The superintendent role at Blue Horizon put me on the vessel side, which is where you deal with agencies as their customer. That angle was new. On the technical side, I had no CS degree and had never shipped software before. About two years of self-teaching, then I built PortFlow.

I built 26 modules before a single person used the product, the ISM compliance dashboard, the FAL declaration generator, the cryptographic audit log. All complete, tested, documented. Zero users. I kept telling myself the product needed to be production-ready before I showed it to anyone. That was wrong. I was building to feel ready, not to learn anything. The agencies I eventually showed it to didn't care about half of what I built. They cared about tracking supplier deliveries and knowing when crew certs were expiring. I could have learned all of that in week two with a spreadsheet demo.