- Author
- Creative Ventures team
- Published
- Read time
- 8 min read
Last-mile logistics software case study: replacing spreadsheets with a realtime dispatch platform
A last-mile logistics case study — how we replaced a spreadsheet-and-WhatsApp dispatch system for a regional carrier, and why shipping alongside the legacy flow was the key to adoption.
RLC moves 4,000 parcels a day across a regional last-mile network. Before us, that meant a shared spreadsheet, three WhatsApp groups and an office whiteboard. Our job: replace the whole contraption without breaking a single day of operations.
What we built for last-mile dispatch
A realtime dispatch console, a driver mobile app with offline-first sync, a customer-side parcel tracker, and a lightweight routing optimiser that respects the very specific constraints of rural roads, mid-day heat and Ramadan hours. The heart of it is a stream of events — every scan, pickup, attempt and exception — flowing through a single pipeline that everyone shares.
Why driver adoption was the hardest problem
The software was the easy half. Drivers had ten years of muscle memory on paper and WhatsApp. We shipped the first version alongside the legacy flow, not replacing it — every feature had a toggle to fall back. Over eight weeks, one by one, drivers noticed the new flow was faster and stopped reaching for paper. The legacy flow died quietly.
Operational numbers after four months
On-time delivery rate moved from 78% to 94%. Average stops per driver per day went up 17%. Dispatcher head-count stayed the same — they simply stopped spending their day reconciling spreadsheets.
“We did not replace the whiteboard. We made the whiteboard unnecessary, and nobody noticed when it came down.”
More builds from the shelf.
Same team, different problems. Recent cases in adjacent industries — each shipped with the senior people who own outcomes.
Notes from people who shipped.
Real reviews from founders, CTOs and PMs we shipped alongside. Not curated soundbites — actual sentences from launch retros.
· Parsewise®
They rebuilt our entire platform in 4 months. Performance improved 3×, and the codebase is finally something our team can maintain on their own.
· Wishboard®
From zero to 50k users in 6 months. The team handled everything — design, development, and launch marketing. We just focused on the product.
· RLC®
We needed 5 senior engineers fast. They embedded with our team, matched our coding standards, and shipped features alongside our full-timers.
· Blured®
The AI agent they built handles 70% of our support tickets. Response time dropped from hours to seconds.
Before we get started — what teams ask us most.
With a discovery phase. We interview stakeholders, audit existing systems, and map the competitive landscape. You get a written roadmap before any code is written.
MANIFESTO
Two-week sprints. Senior engineers from day one. Code that reaches production, products people actually use, and a team that stays through launch.
Stop piloting. Start shipping.
A 30-minute call to clarify your next steps. Zero obligations — bring a brief, a deadline or a half-formed idea, leave with a written plan.
Book a call
A 30-minute call to map the brief, your deadline, and what would actually move the needle.
/02Get an offer
Written estimate within 48 hours — scope, team, milestones and a fixed price you can sign off on.
/03Pay & start
Sign the SOW, pay the first milestone, kick off the same week. No multi-month onboarding theatre.
/04Ship in 2 weeks
First working sprint goes live in 14 days — real demo on a staging URL you can hand to customers.