Peagle · Farid Muradov

Peagle is a logistics web app for businesses that run their own deliveries. I co-founded the company in Amsterdam and led product as CPO. Its core is a node-based editor where operations staff build delivery rules without writing code.

Peagle Conditions editor: 'Weight above 50 kg' and 'Pieces above 10' nodes wired into a Join node, with Reset and Publish buttons at the top right.

01Overview

Delivery rules as building blocks

Every delivery business has its own rules: heavy orders need a van, rain changes timing, priority orders go first. In Peagle, a dispatcher picks a condition such as weight, weather or traffic, sets a threshold, and wires conditions together on a canvas. Nothing changes until they press Publish.

Around the editor sits the rest of the operation: a dashboard, an order list, a live map of couriers, and settings for dispatch, routes and branding. All of it shares one dark sidebar and one yellow accent.

02What I designed

One workspace for a delivery team

ConditionsNode-based rule editor
Condition nodes with their own inputs and units, connected through Join nodes, with a searchable picker grouped by category.
DashboardRevenue, profit and expenses at a glance
A date range switcher, a three-line trend chart, live counts of orders and couriers, and top customers.
OrdersA filterable order table
Tabs by state, colour-coded status tags, a late flag, column controls and bulk upload from a spreadsheet.
MapCouriers and orders on one map
Select an order to see its route and ETA, or a courier to see every stop they carry, with a reassign action on each.
SettingsDispatch, route and brand settings
Toggles for auto dispatch and route limits, driver pay, and brand colours and messages for customer notifications.

03Screens

From the overview to a single rule

Dashboard with revenue, profit and expense cards, a line chart of all three by month, counts of active orders and couriers, and a ranked customer list — **Dashboard**Money, volume and courier stats for the selected period.

Order list table with tabs for All, Current, Scheduled, Completed, Failed and Archived, and status tags such as Picked-up, On the way, Delivered and Failed — **Order list**Every order with its fee, ETA, driver and status.

Conditions page with a search menu listing condition types (Weather, Weight, Pieces, Transport type, Traffic, Timeframe, Distance) and a Weather submenu with Rainy, Snowing, Sunny and temperature options — **Condition picker**A searchable menu of condition types, each with its own options.

Map view with courier avatars and coloured order pins spread over city streets, with search and filter controls — **Map**Couriers and open orders in one view.

Map with one order's route drawn from courier to customer, and a card showing the order status 'On the way', a 25 minute ETA, the courier and a Reassign button — **Order on the map**Route, ETA, courier and pickup and drop-off addresses.

Map with a courier's full multi-stop route and a side panel listing their orders with Picked-up, On the way and Delivered tags — **Courier route**All of a courier's stops, with each order reassignable.

Drivers and Dispatch settings with toggles for auto dispatch and online-only dispatch, and a driver payment amount field — **Dispatch settings**How orders get assigned and how drivers are paid.

Route Settings with a route optimization toggle and per-route limits for weight, pieces and revenue — **Route settings**Optimization on or off, and caps for each route.

Brand customizationThe client's colours and messages for customer notifications.

The Figma file also has full login, registration (three steps plus verification) and password reset flows, plus a Users settings page; they are left out here.
Domino's Pizza appears as the sample tenant in the designs. Confirm it is fine to show, or whether it was a real client.
Settings subtitles and the bulk upload copy are still placeholder text, so the page describes structure only.
Confirm which screens shipped and whether you designed every screen yourself or with a team.