A decade of custody, renewed with a full platform replacement — delivered two months early.
How a Florida maritime-logistics operator kept its mission-critical mobile application running through a ten-month replacement, and why the account was renewed in 2026 rather than put out to rebid.
Project-tracking and cargo-management systems that were custom by necessity.
No packaged product fits a dry dock, a project cargo, or a ship agency’s working day. This operator ran its business on project-tracking and cargo-management systems built for exactly how it worked — and a field mobile application its crews depended on every shift. 3 Strand has held custody of those systems for more than a decade: maintaining them, extending them for each new customer and terminal, and documenting them as the business changed.
Then the mobile application reached the end of its platform life. The operating system beneath it, the device fleet, and the frameworks it was built on were all aging out together. A load-bearing system was going to stop being supportable on a date nobody inside the company had chosen.
If the application stopped, the crews stopped.
The system was load-bearing in the plainest sense: cargo movements, job status, and the records that drove billing flowed through it. The operator had no internal development team to rebuild it, a local labor market that could not supply one in time, and every reason to fear the usual outcome of a rebid — months of proposal theatre, a new vendor learning a decade of context from scratch, and a cutover that gambled the operation.
- Rebid the platform and onboard a vendor with no history in the systems
- Hire a development team in a market that doesn’t produce one
- Buy a packaged product that fits none of the work
- Run the aging application until it failed
- Renew the relationship and replace the platform with the team that already held the maps
- Scope the replacement from documentation that already existed
- Keep the legacy application in production until the new one proved itself
- Milestone the build to the operator’s own calendar
Ten months. Planned at twelve. Containers never stopped moving.
Scoped from custody, not a sales estimate
Because 3 Strand already held the only current documentation of the stack, the replacement was specified from what the system actually did — every workflow, every integration, every field exception the crews relied on — rather than from interviews and guesswork.
Built in parallel, cut over in phases
The new platform was built alongside the old one, tested against live operations, and cut over in stages the operator controlled. The legacy application stayed in production the whole way; no crew learned the new system on a day when the old one had already been switched off.
Delivered early, then held
The replacement landed two months ahead of its twelve-month plan and moved straight into the maintain-support-grow relationship it came from. The next internal wish-list item, the next customer requirement, and the next device refresh land on us.
This is the shape of every relationship we build.
The platform replacement is the proof, but the decade of custody before it is the product. An operator that holds its documentation, its integrations, and its roadmap with one accountable department does not face a rebid when a system ages out — it faces a renewal. That is what the diagnostic starts, what the project proves, and what the retainer holds.
- Custody first: one team accountable for the systems that bill the loads
- Documentation that outlasts any single keeper — theirs or ours
- Modernization in phases while operations keep running
- Milestones on your calendar, never hourly billing
Which of your systems is aging out on a date you didn’t choose?
Tell us about the system, the date, and the person who holds the maps. Forty-five minutes with the decision-maker is the first step.