Sample case study: the client, figures and details are illustrative. Replace with a real project before launch.
Client
A regional shipping agent (sample)
Plates
Web applications, Integrations & APIs
Duration
11 weeks to first release
The problem
Container status lived in carrier websites, customs emails and a shared spreadsheet. Customers called to ask where their cargo was, and the answer took a morning to find.
What we did
- ISurvey
Two days with the operations team, mapping every question a customer asks and where its answer lives.
- IIBuild
A portal that pulls vessel positions, carrier milestones and customs status into one timeline per shipment, with document upload and alerts.
- IIILaunch
Rolled out to ten customers first, then everyone, with the spreadsheet kept read-only for a month.
What changed
- 1 screenfor every shipment, instead of four systems
- Samplefigures go here once a real project replaces this one
Built with
- Next.js
- PostgreSQL
- Carrier and AIS data feeds
- AWS
- Postmark
