Case study · Logistics, ports & trade
Rates, sign-up and tracking without a phone call: a freight line between Florida and the Caribbean
A freight consolidator shipping from Miami to Trinidad, Tobago and Barbados needed a website that does the operation's work: quote, register, track. We built it, we run it in production, and we've been the same team since the first site in 2018.
In numbers
3
destinations quoted and tracked from one platform
2018
first delivery; the same team runs the platform today
1
rate source for the site, the calculator and customer notices
Who this is for
Owners and directors of freight, consolidation and trade businesses on the Florida-Caribbean corridor whose website has quietly become the operation's front door. You will get the design decisions that let a site answer rate, account and tracking questions without a phone call, and an honest account of an outage that a backup alone did not fix.
Key takeaways
- A brochure site stops being enough when it becomes the front door. Once customers quote, register and track on it, an hour of downtime is an operations problem, not a marketing one.
- One rate source. Marketing pages, calculator and customer notices read the same table, so a rate change is made once.
- The client holds the keys. Cloud hosting, DNS and certificates sit under the client's own accounts, documented so another team could take over.
- A backup you have not restored from is a hope, not a control. That line comes from this project, in November 2024, not from a framework.
- Continuity of team is part of the service. The same people have run the platform since 2018; the work widened from a website into the company's technology function.
When does a freight company's website stop being a brochure?
The questions cargo moves on
Cargo between Miami and the Caribbean moves on questions: what does it cost per pound, what are the local handling charges, where is my box. For years those questions arrived by phone and email, and the answers depended on whoever picked up. The first website, in 2018, was a brochure. It described the service; it didn't run it.
What changed by 2024
By 2024 the business had outgrown that. Customers on three islands expected to quote a shipment, open an account, pay online and track a package without calling. Rates changed by route and had to be communicated consistently to everyone. And the site had become the front door of the operation, so an hour of downtime was no longer a marketing problem.
The brief, and where we started
The owner's brief was simple: make the website reflect how the company actually works, and make sure it stays up.
We started with how a package actually moves: received in Miami, consolidated, flown or shipped to Port of Spain, Tobago or Barbados, cleared, handed over. The questions customers ask sit at those steps.
What did we decide, and why those two decisions?
Every customer question becomes a surface
Every step that a customer asks about became a surface on the site: a rate calculator that reads the same rate table the team quotes from, sign-up that creates a real customer account, tracking, and a contact path that lands in a service desk instead of an inbox.
| The question | Where the site answers it |
|---|---|
| What does it cost per pound? | The rate calculator, reading the same table the team quotes from |
| What are the local handling charges? | The rates pages, from the same table |
| Where is my box? | Tracking |
| Can I open an account and pay online? | Sign-up, which creates a real customer account |
| I need to talk to someone | Contact, which lands in a service desk instead of an inbox |
One rate source, and infrastructure the client can hold
Two decisions shaped the rest. One rate source, so marketing pages, calculator and customer notices read the same table and a rate change is made once. And infrastructure the client can hold: cloud hosting, DNS and certificates under the client's own accounts, documented so another team could take over.
Design and engineering in the same room
Design and engineering ran together. The brand, the interface and the code were done by the same people, so the visual work never outran what the platform could deliver.
What did we build?
- Rates, calculator, sign-up, tracking and contact, all reading one rate table.
- Separate staging and production, each with its own container image, so a change is seen before customers see it.
- Cloud hosting, DNS and certificates set up under the client's own accounts and documented.
The platform relaunched in 2024 and has been in production since.
What has held, and what failed?
What the platform carries today
The platform carries the company's customer journeys: rates, calculator, sign-up, tracking and contact all see steady use, and search traffic arrives on the company's own name and on “tracking” queries from Trinidad.
November 2024: the outage a backup did not fix
In November 2024 the site went down. Restoring from backup did not bring it back on its own; the fault was in how the application had been built and shipped, not in the data. We found it, fixed it and changed the deployment so the same failure can't recur. That incident is the reason we now say to every client that a backup you haven't restored from is a hope, not a control.
Eight years with the same team
Production support includes the unglamorous parts: email licences, signatures, monitoring, backups. Eight years on, the client talks to the same people who built the first site. The work has widened from a website into the company's technology function: brand, platform, cloud, corporate tools and support, with the owner deciding what comes next at each step.
Questions readers ask
Customer Success Team
Itaca Technologies
Your question isn't here?
Ask it as you'd ask it across the table. The team that does the work reads it and answers with a concrete next step.