Logistics SaaS · DevOps · CI/CD · Infrastructure as code

From monthly release trains to shipping every day

Executive summary: Cargoline's monthly "release train" was costing them enterprise deals — competitors shipped fixes in days. Over 8 weeks we rebuilt CI/CD across 14 services, codified every environment in Terraform, and trained their engineers to own it. Deploy cycles are 60% faster and failed releases fell 75%.

60%faster deploy cycles

−75%failed releases

20 minto spin up an environment

Client background

Cargoline provides freight-tracking software to 3PLs and shippers in North America. Around 40 engineers work across 14 services — but delivery practices dated from when there were six of them.

The challenge

Releases shipped monthly in a coordinated evening event involving most of the engineering team. Test environments were shared and permanently broken in different ways, so bugs surfaced only in production. A prospective enterprise client made weekly hotfix capability a condition of signing.

What discovery found

!The "monthly release" actually took 9 days end-to-end, including code freeze and manual QA passes.

!Three shared staging environments had drifted so far from production that green tests meant little.

!30% of releases in the prior year had required a same-night hotfix or rollback.

!Environment setup was undocumented — estimated at two weeks of senior-engineer time per new environment.

The solution

We rebuilt delivery from the repo outward: trunk-based development with feature flags, per-service pipelines with automated tests as the gate, and every environment defined in Terraform so ephemeral preview environments spin up per pull request. Deploys became push-button canary releases with automated rollback. Crucially, Cargoline engineers paired with us throughout — the goal was capability, not dependency.

Implementation

Wks 1–2

Pipeline audit & pilot

Value-stream mapping of the release train; pilot pipeline shipped for the highest-churn service.

Wks 3–5

IaC & environments

All environments codified in Terraform; ephemeral per-PR preview environments replaced shared staging.

Wks 6–7

Rollout across services

Pipeline templates rolled out to all 14 services with canary deploys and automated rollback.

Wk 8

Enablement & handover

Runbooks, failure-mode drills, and pairing sessions; Cargoline engineers ran the final week's releases solo.

Results

✓Deploy cycle time down 60%: from a 9-day monthly train to daily per-service releases.

✓Failed releases down 75% year-over-year, measured by rollback and hotfix counts.

✓New environment setup fell from ~2 weeks of engineering time to 20 minutes, self-service.

✓The enterprise deal that triggered the project closed the following quarter.

✓Zero external dependency: Cargoline's own team has run and extended the platform since handover.

“We went from dreading releases to not thinking about them. What sold me was that they trained our own engineers instead of making us dependent.”

S. MensahVP Engineering, Cargoline