01.1 / Logistics · Technical lead
Built the platform.
Then the team.
RUNNR
I built RUNNR from scratch: the business portal, courier operations, driver app, backend, and infrastructure. It takes deliveries from booking through dispatch and proof of delivery to billing.
Today, I still build across the stack, own the architecture, and turn product ideas into sprints for three engineers I’ve mentored from beginner level.
- Business portalBook & track deliveries
- Courier workspaceDispatch & manage orders
- Driver appDeliver & document
- Billing & accountingFrom completed order to invoice
A closer look: configurable courier pricing
Distance, parcel fees, and a flat rush fee.
Same sample order: 2 parcels · 10 kg total
$Distance + $[Parcel Types] + $[Service Speed]Sample couriers and rates, using RUNNR’s formula syntax. Variables are calculated fees or multipliers from each courier’s service rules.
The engineering behind it
End-to-end ownership
I built the initial platform myself and continue working across the web apps, React Native driver app, backend, and infrastructure. The driver app connects delivery tasks, location tracking, and required proof of delivery to the rest of the order lifecycle.
A language for pricing
One example of the architecture: courier-specific service rules calculate fees and multipliers, then a custom DSL combines them into a quote and line items. A formula editor lets couriers or customer success staff change the equation without changing application code.
Building the team, too
I’ve mentored all three engineers from beginner level. One arrived with no programming experience and has become a strong production contributor. Helping people develop their judgment is a core part of my work.


