q Qwetzal

Operations OS for logistics teams

Delivered a multi-tenant operations fabric that multiplied dispatch throughput while halving infra spend per tenant.

Across South Asia, the GCC, and East Africa, tenants needed isolation auditors could defend — without sacrificing dispatch velocity when peaks hit.

Operations OS for logistics teams

“Dispatch finally behaved like something we could explain to auditors — instead of a story we patched together every quarter.”

VP Operations, Confidential logistics SaaS

The second beat after leadership testimony — reconciliation surfaces and governance finally referencing the same operating ledger dispatch depended on.

01

THE PARTNERSHIP BEGINS

Mandate locked: replace the regional monolith with an Operations OS tenants could trust at compliance depth.

Isolation, economics, and measurable dispatch outcomes were explicit before delivery accelerated.

A modular Laravel + Livewire platform serving 40+ tenants with isolated data, role-based access, and a real-time dispatch console. The programme replaced a brittle regional monolith with an Operations OS tuned for compliance-heavy tenants across South Asia, the GCC, and East Africa.

02

THE PARTNERSHIP EXPANDS

Dispatch broke first — shared operations couldn’t absorb tenant growth, peaks, or auditor scrutiny.

Queues blew past four seconds when it mattered; truth lived in fragments, so reviews became reconstruction projects.

What they needed

Confidential — logistics SaaS — a logistics business operating across multiple regions. Engaged Qwetzal with explicit mandates around isolation, velocity, and predictable economics as tenants scaled.

What stood in the way

The legacy monolith could not handle multi-region dispatch and buckled under tenant data growth. Onboarding a new customer took three weeks of manual setup, and a single noisy tenant degraded response times for everyone else.

  • Legacy PHP monolith with a shared schema across all tenants — every schema migration was a multi-day risk event.
  • Dispatch latency above four seconds during peak hours; dispatchers fell back to phone calls and spreadsheets.
  • Onboarding a new operator required three weeks of manual database setup, branding work, and engineer involvement.
  • No centralised audit trail — compliance reviews were reconstructed manually from server logs.
Operations console and logistics coordination

Field posture

One dispatch surface when peaks stopped forgiving spreadsheets.

Regional operators needed the same truth whether they were in GCC hubs or East African corridors.

We anchored the programme on what dispatch leaders replay during audits — not on slide narratives.

Finance and operations workflow transformation

Governance

Evidence became sequential instead of reconstructed.

Approvals, assignments, and exceptions left fingerprints finance could recognise — shrinking audit prep from days to under an hour.

Mobile logistics companion experience

Last mile

Drivers and hubs stayed aligned without sacrificing isolation.

Tenant branding travelled all the way to proof-of-delivery without leaking neighbour data.

Hypercare watched weekend peaks until operators trusted the fabric on their own.

Multi-tenant operations scaling

Throughput

Six× dispatch volume without trading away tenant boundaries.

Shared services stayed observable per tenant so noisy neighbours could be diagnosed in minutes, not days.

Programme velocity

Delivery rhythm

Shipped increments operators could rehearse before cutover.

Friday demos stayed grounded in production telemetry — not demo-only branches.

Each wave inherited clearer rollback triggers than the last.

03

STRUCTURING THE PLATFORM

We rebuilt how tenants entered the fleet, how dispatch behaved under load, and how evidence accumulated for auditors.

One truthful operating picture for operators; finance and regulators could replay what happened instead of arguing about it.

Tenancy boundaries, dispatch semantics, and replayable evidence were treated as programme risks — not polish deferred to the end.

How we intervened

  • — Isolated each tenant’s operating world so growth in one region did not destabilise neighbours.
  • — Put dispatch and assignments behind one live surface operators could trust during peaks.
  • — Made audit-grade traceability native so compliance stopped depending on forensic reconstruction.
  • — Turned onboarding from weeks of manual setup into a repeatable, operator-led path.
  • — Aligned leadership around reliability signals tied to customer-visible outcomes — not internal jargon.
04

THE PLATFORM REACHES PRODUCTION

Production landed in waves — each tenant proved parity before the wider organisation depended on the new fabric.

Pilot operators ran both worlds side by side until reads matched what dispatch leaders expected; only then did traffic commit. Rollback stayed explicit through hypercare so peaks never became a bet-the-company moment.

Programme delivery momentum

Cutover cadence

Waves stayed reversible until leadership signed the next expansion.

Parallel runs absorbed volatility; rollback stayed boring by design — which is how logistics programmes survive revenue Fridays.

Operator experience on the move

Adoption

Field teams picked up the loop without engineering babysitting.

Self-serve onboarding and branded surfaces meant new tenants looked native from day one.

Executive visibility into operations

Confidence

Leadership stopped debating which spreadsheet was canonical.

One operating narrative ran from dispatch desks through finance reconciliation.

05

TRANSFORMATION AT SCALE

Six× throughput on the same footprint, −52% infra per tenant, onboarding under one day, 99.95% uptime year one.

Support tickets dropped 61% in the first quarter; audit prep shrank from days to under an hour.

The new system handles six times the dispatch volume on half the original infra cost, with 99.95% uptime across the first year and tenant onboarding cut from three weeks to under one day.

6×

Dispatch throughput on the same infra footprint

−52%

Infrastructure cost per tenant

Under 1 day

Tenant onboarding, fully self-serve

99.95%

First-year uptime across all tenants

OPERATING REALITY — BEFORE AND AFTER

Once the Operations OS became authoritative, dispatch and finance stopped debating which spreadsheet reflected reality.

Tenant onboarding

Growth targets depended on operators spinning up without engineering babysitting.

Before

Three-week manual provisioning — branding, databases, and brittle scripts owned by a rotating engineer roster.

After

Under one day, self-serve — tenants inherited isolated schemas, defaults, and white-label surfaces.

Dispatch throughput

Peaks were the credibility event — not a demo staged off production.

Before

Queues punched past four seconds; dispatchers reverted to calls and offline spreadsheets.

After

Six× dispatch volume on the same footprint — sub-500ms latency sustained through measured peaks.

Infrastructure economics

CFO stakeholders demanded proof infra tracked tenants — not ambition.

Before

Cost grew unevenly per tenant as noisy neighbours forced reactive scaling.

After

−52% infra spend per tenant through shared services, sizing discipline, and tenant-aware telemetry.

Support posture

Ticket volume was a proxy for operator frustration — leadership watched it weekly.

Before

High-volume repetitive incidents dominated backlog hours.

After

−61% tickets in the first quarter as provisioning and dispatch anomalies stopped repeating.

Audit & assurance

Reviews couldn’t depend on engineers stitching timelines days before diligence.

Before

Two-to-three-day forensic reconstruction from fragmented logs before each review.

After

Under one hour to authoritative narratives — immutable histories auditors could sample.

THE CONNECTED ECOSYSTEM

Twelve operators landed in Q1 with zero engineering lift; peak load held sub-500ms; two enterprise audits passed on replayable events.

  • Onboarded twelve new logistics operators in the first quarter post-launch without engineering involvement.
  • Sustained sub-500ms dispatch latency at six times the previous peak load.
  • Cut monthly infrastructure spend by 52% per tenant through shared services and right-sized provisioning.
  • Passed two enterprise security audits using the new immutable audit trail.
06

THE CONNECTED OPERATING MODEL

Dispatch console, tenant provisioning, billing metering, analytics embeds, immutable audit — handed to client ops.

White-label domains and themes without engineer tickets; driver mobile and integrations shipped as named capabilities.

Command centre

Dispatch command surface

One live picture for assignments, drivers, and exceptions — tuned so peaks did not force teams back to spreadsheets.

Placeholder imagery — tenant onboarding surfaces

Growth mechanics

Tenant onboarding

Self-serve pathways for new operators with branded experiences — without engineering becoming a bottleneck.

Placeholder imagery — access and governance controls

Trust boundaries

Governed access

Roles and permissions that stayed legible to security reviewers as the roster of tenants grew.

Billing & usage signals

Billing & usage signals

Usage surfaced cleanly for finance and account teams alongside operator workflows.

Operator analytics

Operator analytics

SLA, on-time delivery, and fleet utilisation in views leadership actually reviews.

Evidence-grade history

Evidence-grade history

Immutable trail of decisions and state changes auditors could replay — not rebuild by hand.

Driver experience

Driver experience

Acceptance, navigation handoff, proof of delivery, and resilient offline behaviour in the field.

Brand per tenant

Brand per tenant

Themes, domains, and presentation controlled from operations — not ticket queues.

What they received

  • ✓ Production Operations OS operated by the client team
  • ✓ Self-serve onboarding and tenant administration
  • ✓ Written decision history and operational runbooks
  • ✓ Release discipline with rehearsed rollback
  • ✓ Health visibility aligned to business-critical windows
  • ✓ Thirty-day hypercare with joint coverage
07

INTELLIGENCE

Due diligence we answered for enterprise logistics buyers.

Migration posture, isolation model, and ownership after handover — in the cadence procurement expects.

Could we stage adoption instead of betting everyone at once? +

Yes — tenants moved in waves with parallel validation against legacy behaviour before commits escalated.

How did cutover stay safe for live dispatch? +

Pilots ran dual reads until outcomes matched; writes flipped only after explicit sign-off, with rollback paths rehearsed through hypercare.

How strong was isolation between tenants? +

Strong enough for reviewers who cared about blast radius: operations in one tenant could not silently degrade another.

Who owns the programme now? +

The client’s operators — with narrative documentation, decision records, and runbooks transferred during handover.

Related programmes

All work
TravelFreeby

SAAS

TravelFreeby

Offers, fulfilment, and partner orchestration for travel brands
Guided Outdoors

SAAS

Guided Outdoors

Engineering a vertical SaaS ecosystem for global outfitting
Travel Techiez

SAAS

Travel Techiez

Technology backbone for travel operators scaling digital channels

Next engagement

Have a similar challenge?

Tell us about your product and timelines — we'll respond within one business day with relevant references.

Send a brief