1. Home
  2. Case Studies
  3. Ajex
Logistics • Dev Pods • UI/UX

Operating & Shipping AJEX’s Freight OS — From Initial Build to Dev Pods + UI/UX

AJEX engaged Theecode to build a freight-forwarding platform covering quotations, bookings, tracking and invoicing. Post go‑live, we transitioned into Dev Pods for continuous delivery while a standing UI/UX pod maintains the design system and complex ops workflows.

Spring Boot
React.js
API‑centric
CI/CD + QA
Design System
See Measurable Impact ➜ Start a Conversation
AJEX — Ops & Delivery Console (Preview)
To‑Do Snapshot
12
Active sprint tickets
Deploys (30d)
28
Zero failed releases
Incidents (P1/P2)
0 / 1
SLA met
Design Tickets
19
Components & flows
Recommended Actions
  • Archive logs > 90 days
  • Schema migration check in CI
  • Consolidate shipment tracking webhooks
Dev Pod

Frontend

React, UI kit, micro‑frontends

Backend

Spring Boot, REST, caching

QA & Release

Regression, CI/CD, UAT

THEECODE CONTRIBUTION
Built the first release and moved to Dev Pods: FE (React), BE (Spring Boot), Integrations & QA/Release. Our UI/UX pod ships the design system and high-density ops screens for quotations, bookings, tracking and invoicing.
Challenge

Ship a configurable freight OS and sustain velocity

  • API‑centric build with React front‑ends and Spring Boot services
  • Introduce CI/CD, regression packs and release hygiene
  • Keep design system consistent across ops/customer portals

Constraints & Guardrails

  • AJEX retains full IP and cloud infrastructure control; Theecode operates as a Dev Partner under a Pod-based T&M model.
  • All deliverables and access follow AJEX’s infosec and compliance protocols.
  • CI/CD pipelines, credentials, and repositories are owned by AJEX with joint governance.
  • Pods mirror AJEX’s sprint cadence and collaborate directly with internal product owners.

Outcome

  • A stable Freight OS powered by modular Spring Boot services and React portals.
  • Design system and UI/UX track continuously evolving under Theecode’s pod.
  • Zero failed releases, faster iteration cycles, and sustained delivery continuity.
  • Dev Pods remain embedded extensions of AJEX’s engineering team, scaling velocity without disrupting governance.
Theecode Dev Pod Model
Frontend (React)
Ops console + customer portal with reusable components.
Backend (Spring Boot)
Quotation, booking, tracking, billing services.
Integrations
API Gateway, webhooks, third‑party carriers.
QA & Release
Runbooks, regression packs, staging parity, observability.
Platform Snapshot

Client → API/Services → Data → Infra

Ticketech iOS POS session mock: open ticket, tip, close, print receipt
Simple, bank‑grade layering that avoids oversharing internals.
  • React UI, Ops & Customer portals
  • Spring Boot services (Quotation, Booking, Tracking, Billing)
  • Postgres + Redis + Observability
  • CI/CD, Security & Access, Backups & DR
Screens & Flows (Illustrative)
Quotation → Booking
Ticketech iOS POS session mock: open ticket, tip, close, print receipt
Tracking Console
Unified back office dashboard mock: revenue book, per-location revenue, tickets and touchpoints
Billing & Invoicing
Fraud & Bulk Close dashboard mock: risk alerts, stale overrides, bulk close status
Impact
4×
faster onboarding (pods)
100%
delivery continuity
0
failed releases (90d)
2×
design throughput
Need high‑performing pods?

Need high‑performing pods?

Start with a Dev+AI pod. Go live in days, not months.

  • Enterprise‑grade staffing
  • Agile delivery governance
  • Predictable monthly pricing
Book a Working Session View More Case Studies