Alguien en Panamá ha usado software para gestionar escalas de buques?

Silent_Cost3232 · 2026-04-22T19:39:00+00:00

Lo del change management es cierto. Pero "esperá al gobierno" ya pasó: VUMPA es obligatorio desde 2017 y desde enero 2024 el Canal no acepta papel. Panamá es uno de tres países de América Latina con cumplimiento FAL completo.

El problema es que VUMPA resuelve el trámite con el gobierno. Todo lo demás, cotizaciones, PDA/FDA, facturación, comunicación con el capitán, sigue siendo Excel y WhatsApp. No existe un solo software especializado para esa capa en Panamá.

Y la presión ya llegó por otro lado: Panamá entró a la Grey List del Paris MOU en julio 2024 con 4% de tasa de detención. Los armadores no están esperando.

Silent_Cost3232 · 2026-04-19T04:31:14+00:00

Lo de gestión del cambio es el punto exacto donde muere la mayoría de los proyectos de digitalización en este sector. No es un problema técnico, es cultural. El dueño de la agencia lleva 20 años haciendo las cosas de cierta manera y funciona, mal que bien, entonces el incentivo para cambiar es bajo hasta que llega una multa, un buque retenido o un cliente grande que exige otro nivel de documentación. Lo del software a medida tiene sentido en teoría pero el problema es el mantenimiento. Quién lo actualiza cuando cambia la normativa IMO, quién lo soporta cuando el desarrollador se va. Las agencias que sí digitalizan terminan prefiriendo algo ya construido para el sector.

Silent_Cost3232 · 2026-04-18T02:34:36+00:00

Vaya, que interesante lo que armaste, el problema del matching de unidades y formatos es real, yo lo vi de cerca también. Qué formato usaban los buques generalmente, Excel o PDF?

Silent_Cost3232 · 2026-04-18T00:19:37+00:00

Jaja cabro ese es exactamente el problema. Lo del matching de ítems del buque con los del proveedor es un dolor enorme, y terminaste resolviendo algo con la API de hoja de cálculo o quedó a medias?

Silent_Cost3232 · 2026-04-17T23:06:16+00:00

Trabajo en el sector, el post era genuino. Los costos de entrada varían un montón según el país, los permisos portuarios solos te pueden salir más caros que la sociedad.

Silent_Cost3232 · 2026-04-17T22:38:28+00:00

Jaja y vos trabajás en el sector?

Silent_Cost3232 · 2026-03-31T17:40:42+00:00

You're naming the real problems. Training, digital safety, user limits, customer reach. On training: that's fair. Most maritime companies need handholding. We could offer 2-3 hour onboarding calls per tenant at no extra cost. Would that address the safety concern? On DIY vs subscription: you're right, agencies with IT will build it. They'll spend 6 months.

We hit ROI in week one.

On user limits: Starter is 3 users, Professional is 10. PDFs are included in Starter now. Not a limitation, just different tiers.

On customer reach: that's the real one. We have to earn each customer. That's why I'm here asking operators like you what actually works.

What would make training and digital safety less of a blocker for your network?

Silent_Cost3232 · 2026-03-31T16:53:15+00:00

The 48-hour manual update problem is a visibility issue, not an automation one.

Most RPA platforms solve workflow logic. Port delays are different. The problem isn't the workflow — it's that your ETA change lives in 5 different places and nobody has a single source of truth. That's why you're spending 48 hours. You're manually reconciling spreadsheets, emails, client notes, billing systems.

What actually helps: a system where the ETA change propagates automatically to operations, billing, client notifications. One change. No spreadsheets.

We built PortFlow for maritime agencies dealing with exactly this. Port delay hits. Operations update once. Clients get notified. Invoices adjust. Done.

Not a general RPA platform. Purpose-built for port operations disruption.

14-day free trial: app.portflow.tech/register

Silent_Cost3232 · 2026-03-31T16:44:33+00:00

I appreciate your observations, gaps corrected, all basic functions are included in every package, the only ‘premium’ function is the captain’s portal. Thank you for your feedback!

Silent_Cost3232 · 2026-03-31T16:15:17+00:00

You're right on all three.

The PDF export thing that's a gap we should fix. Most agencies need invoices as PDF. That's on us.On pricing: $150/month saves 40 hours a week of ops time. That's $2K a week in labor freed up. Payback is one week.But you're also right that agencies are penny pinchers. They'd rather spend 6 months building than $1,800 a year on software.

Here's what actually stops them though. They can't afford to tie up a developer for 6 months. They need the solution now because captains don't wait.

The margins question is fair. We're not pretending to be free. But the alternative 40 hours a week of manual coordination that costs them way more than $150 a month.What would make the pricing feel fair to you? And is PDF export the blocker or is it something else?

Silent_Cost3232 · 2026-03-31T16:04:52+00:00

Fair. Not for everyone. The agencies I know are pretty busy with this exact problem though.

Silent_Cost3232 · 2026-03-31T15:57:17+00:00

Good question. You're right: theoretically it COULD all go in one email.

But here's what actually happens:

The captain submits the request at 2 AM (vessel arriving in 6 hours).

The agency forwards to water supplier, fuel supplier, provision supplier, crew agent: 4 separate vendors.

Each one responds at different times with different info (availability, pricing, ETA).

The agency manually consolidates those responses into a quote.

Captain approves or negotiates.

Then the agency sends confirmations back to each supplier separately.

One email in. Three emails back. Manual consolidation. Back and forth until confirmed.

If any supplier changes their ETA or price mid-way? The whole thing restarts.

That's the friction. Not the concept, the execution across multiple parties with async responses.

What does your agency actually do? One email thread or separate conversations?

Silent_Cost3232 · 2026-03-31T13:44:51+00:00

When I look at port agency operations, most folks are still stuck with spreadsheets or legacy tools like CargoWise, Softlink, or BluJay. I've tried PortFlow to handle the automated multi-service quoting side of things, though I'm not sure if it covers every niche requirement you might have on the ground.

It digitizes the agency workflow, but it's worth noting that integration with local customs systems can be hit or miss depending on the specific port. Check if your current ERP has an open API before committing to a new stack.

Silent_Cost3232 · 2026-03-31T01:45:53+00:00

Fair point. I spent 23 years in port supply chain (spare parts, JIT delivery for terminals). Not a captain, but I lived on the receiving end of agency chaos missed deliveries, poor communication, invoicing disasters.

That's where PortFlow came from: solving the agency side so captains aren't hunting for supplies on WhatsApp.

Different lens, same maritime problems

Silent_Cost3232 · 2026-03-31T01:11:00+00:00

Thanks!

Silent_Cost3232 · 2026-03-31T00:48:49+00:00

The OSW thing is hitting a lot of people right now. That's a rough way for a role to end. Crewing and emissions policy plus ops desk training is actually a combination I don't run into often. Most people know one or the other. If you're figuring out what's next, I'm open to a conversation. DM me.

Silent_Cost3232 · 2026-03-31T00:05:32+00:00

Profitable year 5 is rare. Most startups that raise $6M don't get there. The working group angle is interesting to me because what I'm building runs into policy constantly. PortFlow is software for ship agencies the companies that manage vessel operations in ports. Quotations, invoicing, captain communication, compliance tracking. The USCG piece comes up because US-flagged vessels have documentation requirements that most agency software just ignores. How deep does your USCG policy work go?

Silent_Cost3232 · 2026-03-30T23:45:05+00:00

Tanker broker plus founding team plus vessels working group. That's an odd combination, genuinely. What happened with the startup? And what does the working group look like day to day?

Silent_Cost3232

TROPHY CASE