LogiDesk (LogiFreight) — Case Study

1. Executive Summary

LogiDesk (LogiFreight) is a multi-tenant SaaS platform that standardizes freight-forwarding operations end-to-end — from bookings and documentation to milestone tracking, charges, and invoicing — eliminating spreadsheet and chat-driven execution.

Snapshot

Product LogiDesk (LogiFreight) — Freight Forwarding & Logistics Operations Platform
Adoption (Live) 55 companies (20 small, 30 medium, 5 large)
Regions Canada, India, UAE
Scope All modules live in production (operations, documents, charges, invoicing, visibility, controls)
Tech Stack Django (DRF), React, Ant Design (AntD)
Role Founder / Product Lead / Technical Lead (discovery → design → architecture → delivery → adoption)

What problem it solves

Freight forwarding teams often run operations across Excel, email, WhatsApp, and shared drives. That fragmentation produces duplicate data entry, document mistakes, revenue leakage, delayed invoicing, and poor visibility for both customers and management.

Why it matters in Dubai / GCC

GCC logistics operators care heavily about SLA performance, compliance-ready documentation, branch controls, auditability, and fast, predictable invoicing to protect cashflow. LogiDesk is designed around these operational realities.

2. Context and Market Reality

Freight forwarding is a coordination business, not just transportation.

A single shipment touches multiple parties (shipper, consignee, agents, carriers), multiple documents (BL/HAWB, manifests, DO, invoices), multiple cost and revenue lines, and multiple milestones (pickup, gate-in, ETD/ETA, arrival, delivery).

Observed operating patterns in the market

  • Quotes and pricing stored in spreadsheets and forwarded via email.
  • Bookings confirmed via WhatsApp/email threads with unclear ownership.
  • Documents stored in shared drives with inconsistent naming and versions.
  • Billing prepared late because charges are reconstructed after the fact.
  • Status visibility depends on specific employees and tribal knowledge.

3. Problem Statement

Freight teams lose time and money because execution is not system-driven — it is memory-driven. When the system of record is fragmented, mistakes and delays become inevitable.

Core symptoms

  • Duplicate data entry across tools and documents.
  • Wrong or missing documents (especially BL and delivery documents).
  • Revenue leakage from missed charge lines and incorrect billing parties.
  • Delayed invoicing and unpredictable cashflow.
  • Lack of audit trail and accountability for changes/approvals.
  • Inconsistent SOP execution across branches and teams.

Business impact

  • A single pricing mistake can wipe profit on a shipment.
  • Delayed invoices increase working capital pressure.
  • Missing documentation can cause delays, penalties, and customer churn.

4. Goals and Success Metrics

Product goals

  • Standardize shipment execution into repeatable workflows.
  • Reduce manual work while preventing operational mistakes.
  • Improve billing accuracy and speed from operations to finance.
  • Provide real-time visibility for managers and customer service.
  • Scale securely with multi-tenant isolation, branch scoping, RBAC, and audit.

KPI framework (recommended)

North Star Metric: Shipments completed correctly and billed on time.

Driver metrics

  • Average time to create a shipment record (minutes).
  • Document checklist completion rate before ETD/ETA.
  • Invoice turnaround time after a billing milestone (hours/days).
  • Invoice dispute rate (per 100 shipments).
  • Charge leakage rate (missed charge lines).
  • Weekly active users by role (ops, documentation, finance, sales).

Constraint metrics

  • Uptime percentage and incident count.
  • p95 API latency and error rate.
  • Support tickets per 100 shipments and trend over time.
  • Data integrity issues (duplicates, missing mandatory fields, invalid routing).

5. Users, Personas, and Jobs-To-Be-Done

Primary personas

Persona Primary goal Key needs
Operations Executive Execute shipments without surprises Checklists, milestones, assignments, quick updates
Documentation Officer Produce correct documents fast Templates, auto-fill, versioning, controlled sharing
Finance/Billing Invoice quickly and accurately Charge rules, approvals, audit trail, invoice queue
Sales/Pricing Quote fast with margin clarity Saved rates, customer profiles, win/loss notes
Manager/Owner Visibility and profitability control Dashboards, branch comparison, exception reports

Jobs-To-Be-Done (examples)

  • When a customer requests a shipment, I want to create a booking in minutes so I can confirm quickly.
  • When documentation is required, I want templates and auto-fill so I do not make mistakes.
  • When milestones occur, I want billing triggered so cashflow stays healthy.
  • When a manager asks for status, I want one screen showing the current truth.

6. Scope and Modules

In-scope modules (all live)

Master Data / Setup

  • Customers, vendors, agents, branches
  • Ports/airports/countries, shipment types, container types
  • Currencies and operational defaults
  • Roles and permissions

Shipment Operations

  • Booking, Direct, Master, Consolidated shipment types
  • Parties, routing, legs, packages/containers
  • Milestones and exception handling
  • Assignments and internal notes

Documents

  • Document checklist per mode/customer/lane
  • Attachments and versioning
  • Controlled sharing and traceability

Charges and Invoicing

  • Cost and sell charge lines
  • Approvals/locks for sensitive actions (optional rules)
  • Invoice generation and invoice queue

Visibility and Audit

  • Operational dashboards and filters
  • Activity timeline (who changed what and when)
  • Branch-level visibility and control

Out-of-scope (for clarity)

  • Full customs declaration system (unless integrated separately).
  • Full ERP accounting replacement (unless explicitly implemented).
  • Carrier EDI integrations (unless implemented).
  • Warehouse/Yard management (WMS/YMS) beyond forwarding operations.

7. Key Product Decisions

Shipment as the single source of truth

A shipment record is the system anchor for parties, routing, milestones, documents, charges, invoices, and audit history. This eliminates multiple competing sources of truth.

Workflow standardization without killing flexibility

  • Minimum viable shipment creation (fast) followed by progressive enrichment (detail later).
  • Structured checklists and milestones provide rails without blocking real-world exceptions.
  • Free-form notes capture operational reality while preserving structured data.

Controls for scale (multi-tenant + branch + RBAC + audit)

  • Tenant isolation ensures company data separation by design.
  • Branch scoping supports regional teams and permissions.
  • Role-based access controls protect sensitive operations and finance actions.
  • Audit logs provide traceability for changes, approvals, and accountability.

8. Functional Requirements

8.1 Shipment lifecycle

Typical states (configurable per business): Draft → Confirmed → In Transit → Arrived → Delivered → Closed

Milestones / events:

  • Pickup
  • Gate-in
  • ETD
  • ETA
  • Arrival
  • Delivery
  • POD received

Rules and validations

  • A shipment cannot be confirmed unless minimum mandatory fields are completed.
  • A shipment cannot be closed if billing is incomplete (optional business rule).
  • All edits to core fields are recorded in activity logs.

8.2 Document management

  • Document requirements vary by mode (air/sea/land), lane, and customer SOP.
  • Templates support auto-fill from shipment master data.
  • Versioning ensures staff and customers receive the correct document version.
  • Sharing actions are traceable (what was sent, by whom, and when).

8.3 Charges and invoicing

  • Charge lines categorized by stage: origin, freight, destination.
  • Support cost vs sell lines to track profitability and margin.
  • Currency handling for multi-country operations.
  • Approvals for discounts, overrides, and margin threshold exceptions (optional).
  • Invoice generation pulls approved billable lines with correct parties.

8.4 Multi-tenant and multi-branch

  • Strict tenant isolation across all queries and file access.
  • Branch-scoped views for operational teams with admin oversight options.
  • Cross-branch reporting for management roles.
  • Configurable defaults per tenant (and optionally per branch).

8.5 Search, filters, and speed

Freight operations depend on fast retrieval. Search and filtering are first-class requirements.

  • Search by customer, booking reference, BL numbers (HBL/MBL), container number, vessel/flight, port pairs.
  • Filter by status, milestone, ETD/ETA date ranges, assigned staff, and branch.
  • Sort by newest, ETA soonest, overdue documents, and exception flags.

9. UX and Information Architecture

Core screens

  • Shipment List — daily operational cockpit with status chips, warnings, quick actions.
  • Shipment Detail — single-pane-of-truth with tabs (overview, routing, docs, milestones, charges, activity).
  • Document Center — templates, uploads, versions, and share logs.
  • Invoice Queue — ready-to-invoice vs exception states for finance.

UX principles

  • Minimum viable data entry first; enrich as operations progress.
  • Progressive disclosure to avoid overwhelming users.
  • Ops-first speed: fast search, few clicks, consistent layouts.
  • Error prevention through validated master data and structured fields.
  • Visible audit timeline to build operational and finance trust.

10. Data Model Overview

Core entities

  • Tenant, Branch, User, Roles/Permissions
  • Customer, Vendor, Agent
  • Shipment, ShipmentLeg, ShipmentPackage/Container
  • MilestoneEvent
  • Document (with versions and types)
  • ChargeLine (cost/sell, currency, tax/charges metadata)
  • Invoice (linked to charge lines)
  • ActivityLog (audit trail)

Key relationships (simplified)

  • Tenant 1-to-many Branch
  • Branch 1-to-many Shipment
  • Shipment 1-to-many Documents, Milestones, ChargeLines
  • Invoice 1-to-many ChargeLines
  • Shipment many-to-1 Customer/Vendor/Agent (by role)

11. System Architecture

Front-end

  • React + Ant Design (admin-grade component library)
  • Reusable CRUD components with server-driven pagination, sorting, filtering
  • Consistent form patterns and validation

Back-end

  • Django + Django REST Framework (DRF)
  • django-filter + Ordering + Search filters
  • JWT authentication
  • Tenant and branch enforcement on every request
  • Audit logging and activity timelines

File storage and documents

  • Secure file storage for shipment documents
  • Per-tenant and per-role access control
  • Versioning and traceable sharing

Security and compliance readiness

  • RBAC for sensitive actions and finance approval flows
  • Audit trail for changes and approvals
  • Branch scoping and admin oversight for multi-branch operators

12. Delivery and Execution

Delivery lifecycle

  • Discovery: interviews, shadowing workflows, mapping shipment lifecycles by mode
  • Definition: PRD, data model, states/milestones, acceptance criteria per module
  • Design: wireframes, permissions matrix, navigation and information architecture
  • Build: backend contracts first; frontend CRUD; seed master data; audit and permissions
  • QA: replay testing using real shipment scenarios; edge cases (consolidation, split billing)
  • Release: phased rollout, onboarding, training artifacts, feedback loop and hotfix pipeline

Risk management (what breaks freight products)

  • Garbage data entry — mitigated by validation and master data dropdowns.
  • Document version errors — mitigated by versioning and checklist enforcement.
  • Finance trust — mitigated by audit logs, approvals, and state locks.
  • Adoption resistance — mitigated by minimal forms and progressive detail capture.

13. Results and Impact (Fill with Verified Metrics)

Use this section to present only verified metrics. If you do not have exact numbers yet, include directional improvements backed by evidence (screenshots, audit logs, support trends, release notes).

Metric Before After
Time to create shipment record [insert baseline] [insert improved]
Document errors / missing docs per month [insert baseline] [insert improved]
Invoice turnaround time after milestone [insert baseline] [insert improved]
Invoice dispute rate (per 100 shipments) [insert baseline] [insert improved]

Adoption and footprint

Segment Count Typical team size Primary value
Small 20 5–20 staff Speed, templates, single system of record
Medium 30 20–100 staff Standard SOP, visibility, faster billing
Large 5 100+ staff Branch controls, audit, approvals, governance

14. Success Stories (Anonymized)

Client stories below use pseudonyms to protect confidentiality.

Om Prakash Singh (India) — Medium forwarder scaling beyond spreadsheets

Before: Bookings and shipment details tracked in spreadsheets and email threads; documents stored in inconsistent folders with version confusion; invoicing delayed because finance waited for ops confirmations.

What we implemented

  • Shipment lifecycle workflow (draft to closed) with validations
  • Document checklist and versioning to prevent wrong document dispatch
  • Invoice queue connected to shipment readiness (milestones and docs)
  • RBAC and branch scoping to align ops vs finance responsibilities

Outcome

  • Shifted execution from memory-driven to system-driven workflows
  • Reduced document mistakes through versioning and checklist discipline
  • Improved invoice predictability via a dedicated invoice-ready pipeline
  • Improved management visibility through structured filters and search

Narayan Patel (UAE) — Large multi-branch operator needing control and audit

Before: Each branch ran different SOPs; charge capture inconsistent; no reliable audit trail for approvals; margin issues discovered late; management reporting manual.

What we implemented

  • Branch-scoped access with head-office oversight controls
  • Approval flows for sensitive actions (charge edits, invoice approval)
  • Audit timeline as a first-class feature for shipments and finance actions
  • Standardized shipment templates and minimum required fields across branches

Outcome

  • Reduced operational risk through approvals and traceable audit logs
  • Standardized workflows across branches to reduce process variance
  • Improved profitability control due to consistent charge capture
  • Faster cross-branch reporting using unified system data

Devra Kandel (Canada) — Small forwarder needing speed and professionalism

Before: Work fragmented across chats/emails; documents scattered; customers asked for updates and staff manually searched threads; billing delayed because charges were reconstructed later.

What we implemented

  • Minimum viable shipment creation for speed, with progressive enrichment
  • Document center per shipment with structured types and uploads
  • Charges captured throughout operations to avoid end-of-month reconstruction
  • Fast search by customer, reference, BL, container, vessel/flight

Outcome

  • Reduced time spent searching for documents and shipment status
  • Improved customer experience with consistent document handling
  • Faster invoice readiness because charges were captured as work happened
  • More professional, repeatable operations for a small team

15. Learnings

  • Freight operations are a workflow family: mode, lane, and customer SOP change the execution path.
  • Documentation is not a side module; for many forwarders, it is the core value.
  • Finance adoption depends on trust features: audit logs, approvals, and lock states.
  • Fast search and filtering matters more than fancy UI in daily operations.
  • Multi-tenant + branch scoping + RBAC is a strong moat for B2B SaaS at scale.

16. Roadmap

Next 90 days

  • Customer-specific document templates and stricter checklist automation.
  • SLA alerts and overdue milestone detection (exceptions dashboard).
  • Invoice automation triggers based on milestone progression.

6 months

  • Agent collaboration portal (shared milestones, doc exchange, traceability).
  • Rate management and quote-to-book flow with margin visibility.
  • Profitability dashboards per lane, customer, and service type.

12 months

  • Integration layer for carrier APIs and accounting exports (where applicable).
  • AI assist: document extraction and exception detection.
  • Configurable workflow engine per customer SOP.

17. Evidence Pack for Portfolio

  • 8–12 screenshots: shipment list, shipment detail tabs, docs, charges, invoice queue, RBAC, audit timeline, dashboards.
  • One architecture diagram (box-and-arrow is enough).
  • One simplified ERD (shipment-centric).
  • 1–2 demo videos (2–4 minutes).
  • Release notes or changelog page showing iteration and delivery velocity.
  • An anonymized dataset or export snippet (optional) to demonstrate scale and structure.

18. Interview Talk Track (2 minutes)

LogiDesk is a multi-tenant freight operations platform used by 55 companies across Canada, India, and the UAE. I designed it around a shipment-centric single source of truth with milestones, documents, charges, invoices, and audit trails. The key product win was standardizing messy real-world freight workflows into repeatable execution without killing flexibility. On the engineering side, we shipped tenant isolation, branch scoping, RBAC, server-driven filtering, and an audit timeline — which is critical for GCC operators needing control and traceability. I can walk you through the shipment lifecycle, document versioning, and the invoice readiness flow.