Truck'n Bike Case Study
Freight isn't a fixed-price commodity. So we didn't build another ride-hailing clone — we built a marketplace where nearby drivers and trucking companies compete for every load, and back their bids with real money.
Truck-Bike Load (Private) Limited
Logistics & On-Demand Freight
4 Apps (iOS + Android) & Admin Panel
UI/UX, Mobile Apps, Marketplace & Wallet Systems
A Marketplace, Not a Dispatcher
Truck'n Bike is an on-demand logistics platform for parcel and goods transportation. A customer posts what needs moving and picks a vehicle category; nearby drivers and registered trucking companies are notified instantly, and they compete for the job by bidding on it.
That single design decision — bidding rather than auto-assignment — is what separates this platform from the ride-hailing pattern it superficially resembles. Moving a documents envelope across town and moving three tonnes of construction material are not the same transaction, and no pricing table set in an office can fairly price both. Letting the market price each load solves that. But it introduces a harder problem: an open bidding system is worthless if bidders don't honour what they bid.
Wise Hustlers designed and built the platform around that problem. Every bid is backed by a wallet balance, so committing to a price means committing real money. Trucking companies get first-class accounts — they bid as a business, win as a business, then assign the job to one of their own registered drivers. The result is live on both app stores as four separate applications, coordinated by a single operations panel.
Freight Has No Fixed Price
Local goods transport was coordinated over phone calls and WhatsApp. A customer with a load would ring around for quotes; a driver with an empty return leg had no way to find work nearby. Price was whatever the last negotiation landed on, and neither side could tell whether it was fair.
The obvious fix — a fixed rate card, like a taxi app — breaks immediately in freight. Distance alone doesn't price a job. Vehicle class, load weight, loading time, and the driver's own position and return route all move the number. The platform had to let supply and demand find the price, while still making that feel effortless to a customer who just wants something moved.
Core Pain Points Addressed:
- ❌ No price discovery: Customers had no way to compare offers; drivers had no way to compete for work.
- ❌ Manual dispatch delays: Finding a driver meant working the phone for hours, load by load.
- ❌ Mismatched vehicle types: A parcel and a full truckload were booked through the same ad-hoc process.
- ❌ Trucking companies locked out: Fleet operators had no way to participate as a business and route work to their own drivers.
- ❌ No commitment layer: Nothing stopped a hauler from quoting low, winning the job, and walking away from it.
Five Surfaces, One Marketplace
1. Customer App
Post a delivery in under a minute: pickup and drop, load details, and a vehicle category drawn from the catalogue operations maintains. Bids arrive back in-app, side by side, so the customer chooses on price and rating rather than on whoever answered the phone first.
2. Driver App
Independent drivers register against a vehicle category, then receive only the jobs that category can actually carry. Push notifications surface nearby loads; the driver bids, tracks the outcome, navigates the job, and watches earnings and wallet balance in one place.
3. Trucking Company Accounts
Fleet operators register as a business and bid alongside independents. Win a job and the company assigns it to one of its own registered drivers — so the customer deals with an accountable company, while the company keeps control of who actually runs the load.
4. Bidding & Wallet Engine
The core of the platform. Jobs are broadcast to eligible nearby bidders, bids are collected against a live wallet balance, and no bid is accepted from an account that can't cover it. Commitment is enforced by the system, not by good intentions.
5. Central Admin Panel
One console for the whole marketplace: create and manage vehicle categories, approve drivers and trucking companies, oversee wallets and bidding activity, and monitor live platform operations — without a developer in the loop.
The Life of a Load
Six steps from “I need this moved” to a driver on the road — with a commitment check built into the middle of it.
Customer posts the load
Pickup, drop-off, load details, and a vehicle category selected from the admin-managed catalogue.
Nearby eligible haulers are notified
The platform pushes the job to independent drivers and trucking companies whose registered vehicle category matches the request — not to everyone on the platform.
Bids come in, wallet-backed
Drivers and companies submit competing prices. The system checks each bidder holds sufficient wallet balance before the bid is allowed to stand.
Customer picks the winner
Offers are compared side by side on price and hauler reputation. The customer decides — the platform doesn't decide for them.
Companies delegate to their own drivers
If a trucking company won, it assigns the job to one of its registered drivers, who picks it up in the same driver app an independent would use.
Delivery runs and closes out
Live status and navigation through pickup, transit, and drop-off, with the outcome reflected in earnings and platform records.
Key Features at a Glance
🛒 Customer App
- ✓ Book parcels and full loads in one flow
- ✓ Vehicle category selection at booking
- ✓ Competing bids compared side by side
- ✓ Live shipment tracking
- ✓ Rated, verified haulers
🚛 Driver App
- ✓ Vehicle category set at registration
- ✓ Instant notifications for nearby loads
- ✓ Wallet-backed bidding on open jobs
- ✓ Live GPS navigation and job status
- ✓ Earnings and wallet history
🏢 Trucking Company
- ✓ Register and bid as a business
- ✓ Manage a roster of registered drivers
- ✓ Assign won jobs to an in-house driver
- ✓ Company-level wallet and bidding
- ✓ Oversight of fleet job activity
Technical Challenges & Solutions
01. Making bids mean something
An open bidding system collapses the moment bidders can quote a price they never intend to honour. We made commitment a precondition rather than a promise: bidders must hold sufficient wallet balance to participate, and the balance is validated at bid time. A hauler who bids has already put money behind the number, which changes the incentive from 'quote low, decide later' to 'quote what you'll actually run'.
02. Wallet integrity under concurrent bidding
The same wallet can be exposed to several open jobs at once, and balance checks that are merely read-then-write let an account over-commit across simultaneous bids. Balance validation and reservation had to be handled as an atomic operation, so a driver cannot back three jobs with one job's worth of funds.
03. Two classes of bidder, one auction
Independent drivers and trucking companies bid in the same marketplace but are not the same kind of entity. One is a person who drives; the other is a business that dispatches. The data model had to let a company bid, win, and then delegate execution to a registered driver — while the customer still sees a single accountable counterparty and the driver still uses the ordinary driver app.
04. Targeted notification, not broadcast spam
Notifying every hauler about every load trains people to ignore notifications. Jobs are filtered by proximity and by the vehicle category a driver registered against, so a bike courier is never offered a truckload — keeping the notification stream relevant enough that drivers keep responding to it.
05. Operations without engineering
Vehicle categories, driver approvals, and company onboarding all change faster than release cycles. Building these as first-class admin capabilities meant the client's operations team could reshape the marketplace catalogue and approve participants directly, instead of filing a change request against a developer backlog.
06. Reliability across four apps and weak networks
Booking status, bids, and location updates had to stay consistent across four separate applications on two platforms — while delivery work happens in exactly the places mobile coverage is worst. This required deliberate handling of retries, offline states, and live status reconciliation rather than assuming a healthy connection.
Technology Stack
Four applications across two platforms, plus a web console and a real-time bidding backend — delivered on a deliberately consolidated stack so one team could move across every surface.
React Native
One codebase per app shipped to both iOS and Android. This is why four store listings didn't cost four native builds — and why a change to the bidding screen lands on every platform at once.
Node.js
Powers the marketplace core: job broadcasting, bid collection, wallet validation, and the push notification pipeline that has to reach nearby haulers within seconds of a booking.
React.js
The web console where operations manage vehicle categories, approve drivers and trucking companies, and monitor live marketplace activity.
MongoDB
Stores the marketplace's moving parts — jobs, bids, wallets, and the differing shapes of independent-driver and trucking-company accounts — under one flexible document model.
What Shipped
A complete two-sided freight marketplace, live and publicly downloadable on both major app stores.
Customer and driver applications are published under Truck-Bike Load (Private) Limited on both the App Store and Google Play.
Let's Pressure-Test It
Book a free call and tell us what you're building. Worst case, you leave with honest feedback and a clearer plan. Best case, you leave with a team that ships.