Water delivery · Custom software · [X] weeks · [price range]

    Drivers planned routes in their heads. Now the day is planned with one tap.

    AquaFlow, a water delivery company, ran its whole operation on Excel files and gut feeling. I built the system that runs it for them — routes, clients, orders and finances in one place.

    20+ hrs
    saved per driver, every month
    1 h
    earlier finish, every day
    [X]
    drivers · [X × 20 = Y] hrs saved per month, company-wide
    AquaFlow screenshot

    This is your situation if…

    • Your drivers, technicians or sales reps visit several addresses a day and decide the order themselves.
    • Clients, orders and payments live in separate spreadsheets — or in someone's memory.
    • You find out about a late delivery when the customer calls, not before.

    The problem

    Every morning, each driver got an Excel list of addresses — no order, no priorities, no logic. Each one invented a route on the spot. The result: wasted fuel, late deliveries, and an operations team with no idea what was happening in the field until someone complained.

    Routing was only the visible part. There was no single place for clients, orders or money. Everything lived in separate spreadsheets or in someone's head, so answering “who ordered what, and did they pay?” meant asking around.

    What I built

    In the order it happened.

    1. 1
      Mapped the whole operation first.

      From the moment an order comes in to the driver's sign-off — to see exactly where time and money leaked. No tools yet.

    2. 2
      One system, three views.

      The owner sees the whole business. The operator assigns deliveries. Drivers see only their day — and a button that plans it.

    3. 3
      Route planning with one tap.

      The route accounts for where the driver is right now, live traffic, roadworks and each customer's delivery window.

    4. 4
      Clients, orders and money in the same place.

      Every spreadsheet replaced. “Who ordered, who paid, who's due tomorrow” is one screen, not a round of phone calls.

    AquaFlow - additional screenshot

    Driver view: today's deliveries and the one button that plans the route.

    For technical readers: how it's built

    Web app built with Lovable and Claude Code; map and route rendering with Leaflet; route optimisation and background jobs in n8n; role-based access for owner, operator and driver portals. [confirm details]

    Lovable
    Claude Code
    n8n
    Leaflet

    What changed

    Measured [X months] after launch.

    20+ hrs
    saved per driver per month — no more figuring out where to go next
    1 h
    earlier daily finish — more deliveries without hiring another driver
    [X] €
    less fuel per month [Marko mentioned lower gas costs — get the number]
    0
    spreadsheets left in daily use
    Duration:
    [X weeks]
    Investment:
    [price range, or “projects like this: from X €”]
    Team on my side:
    just me
    Runs in:
    AquaFlow's own accounts [confirm]
    “We'd been trying to fix our dispatching manually for over a year. Stefan spent the first meeting just asking questions, and by the next call had already mapped out what was broken. The system saves each driver 20+ hours a month — and honestly, reduced our gas costs.”
    Marko PetrovićMarko Petrović
    Operations Manager, AquaFlow

    Have a similar problem? Let's talk.

    30 minutes, free, no commitment. You talk to me from the first call to delivery. Or write to iveticpf@gmail.com.

    Book a free 30-minute call