Client
Lucky Drive, Bulgaria
Business
Designated-driver service in Sofia, Varna, Plovdiv, Burgas. A sober driver comes to the customer and drives them home in their own car. Orders arrive by phone, website and app.
Starting point
A night-time operation that lives on the phone line, with dispatchers, driver teams, cash and card payments, and payroll kept in spreadsheets.
What we built
Passenger app and driver app (iOS and Android), dispatch API, dispatcher panel with click-to-call, payments and wallet, accounting and payroll system, AWS infrastructure, 2022 and 2026 brand redesign of both apps
Team
A technical lead throughout; up to about four engineers at a time in the build years (backend, Flutter, DevOps); one senior engineer running everything since 2023
In production
Since 2018, continuously delivered and operated by Looming Tech
Since 2018in production, continuously delivered and operated by Looming Tech
~82,000distinct customer phone numbers served and 23.8 million GPS points recorded
−27%AWS spend, from about 262 to about 190 USD a month

Client

Lucky Drive runs a designated-driver service under the slogan "Не карай пил!" (don't drive drunk). A customer who has been out for the evening calls, orders on the website or taps the app; a driver team arrives, and one driver takes the customer home in the customer's own car. The service runs through the night in Sofia, Varna, Plovdiv and Burgas, and the same company also operates Lucky Garage (car service) and Брокерито (insurance brokerage).

Take away the night-out setting and the operation is one that every dispatch business shares: orders arriving through several channels, people on the road, a dispatcher who must be able to override anything, a price that depends on the distance actually driven, and a payroll that depends on who worked which shift.

The Problem

Lucky Drive needed software that fits a business where the phone matters as much as the app. Four things had to work together.

  • Every channel has to land in one place. Phone orders, website orders and app orders all need the same trip record, the same dispatcher view and the same billing rules.
  • The price has to be fair and defensible. The fare depends on kilometres and minutes driven, measured by a phone in a moving car at night. Consumer GPS is noisy, so the measurement has to be cleaned, checked and explained.
  • Dispatchers and drivers need to reach each other and the customer instantly, without exposing personal phone numbers, and managers need to be called when nobody picks up.
  • The money side was manual. Shift reports, fuel and car-wash expenses, cash against card revenue, driver wages and bonuses were reconciled by hand in spreadsheets.
  • Lucky Drive did not want to build and run its own software department to solve this. It wanted one partner who would own the technology for the long term.

    What We Built

    Apps for passengers and drivers

  • Passenger app (Flutter, iOS and Android): order on a map with a price estimate, pay in cash or by card, wallet credit and promo codes, favourite addresses, trip history, ratings and tips, Google, Apple and Facebook sign-in.
  • Live Activities: the passenger follows the trip on the iPhone lock screen, in CarPlay and on Apple Watch, with the driver's arrival time refreshed from live GPS and the final amount shown at the end.
  • Driver app (Flutter, iOS and Android): team trip offers where the first teammate to accept wins, the trip flow, background GPS tracking that keeps running with the phone in a pocket, and a finish screen that puts the amount and payment method front and centre.
  • Driver referral codes: each driver carries a personal promo code with its own app link and QR code, and the platform counts the first rides those codes bring in.
  • A dispatch platform built around the phone line

  • Dispatch API with about 153 endpoints covering the full trip lifecycle, team dispatch, per-city tariffs, promotions, payments, push notifications and reporting.
  • Dispatcher panel with live trips on a map, manual phone orders, automatic matching based on best arrival guess, team and driver management, fixed prices for long routes, wait-time charging, and city-scoped access for regional dispatchers.
  • Telephony: click-to-call from the panel, automatic calls to drivers and passengers, prerecorded messages, and escalation to managers for out-of-hours orders. Integration with VoIP system. Passengers see the operator's number, never a driver's personal phone.
  • Website orders flow straight into the same dispatch queue as app and phone orders.
  • Fares calculated from the road actually driven

    The driver's phone is the trip meter. The platform cleans the GPS trace (dropping inaccurate points and physically impossible jumps), falls back to map routing when the signal is poor, and then applies city tariffs, minimum fares, caps and wait-time charges. A regression suite built from real captured trips checks every change to the calculation against known correct amounts.

    Accounting and payroll that replaced the spreadsheets

    A separate accounting system reads trips from the dispatch platform and owns everything that follows: daily shift reports per team, fuel and car-wash expenses, cash against card revenue, driver wages and shift bonuses, deposits, cars and mileage with oil-change tracking, promo-code tracking and an audit log. A trip forecast built on several years of history, holidays and bridge days helps plan staffing for the weeks ahead. A public application form brings in new driver candidates with a review queue for the team.

    A new brand, carried into the product

    In 2026 both apps were redesigned to Lucky Drive's new brand book, with a shared design system so passenger and driver apps look and behave as one product. New store screenshots followed, and a new marketing site with online ordering was built on the same brand.

    How We Worked

    Looming Tech has been Lucky Drive's technology team since 2016. In the build years a small team (backend engineers, a Flutter developer and a DevOps engineer) worked under the same technical lead. Since 2023 one senior engineer has owned the whole platform: product changes, both app stores, the AWS account, costs and security. In practice this is the fractional CTO and tech-builder model: Lucky Drive has a technical lead who knows every corner of its business without hiring one.

    Three habits kept a ten-year-old production system healthy with one engineer:

  • Tests before big changes. Before moving the API to a current Node.js version, web framework and database layer, we captured real trips and their expected amounts as tests. The migration then shipped in a single release, with no staging environment to hide behind.
  • Platform deadlines turned into a planned review. Database end of support, an ageing cache service and public IP pricing were handled together: the production database was upgraded after a full rehearsal, with under four minutes of downtime; the cache moved to a pay-per-request table; and the database was taken off the public internet. The AWS bill went down by about 27%, from about 262 to about 190 USD a month.
  • Data answers for the owner. When questions came up about how drivers' accounts and shifts were really being used, we answered them from the platform's own session and GPS data. The findings became product rules within weeks: one active session per driver and a daily team reset.
  • The same approach carried the euro changeover through every layer of the business, from the apps and dispatcher panel to card payments, receipts and payroll.

    Tech Stack

    LayerTechnologies
    Mobile appsFlutter, Dart, Swift (iOS Live Activities), Google Maps
    Dispatch APINode.js, Hapi.js, Knex.js
    Dispatcher panelAngularJS, Google Maps
    AccountingReact, TypeScript, Vite, Tailwind CSS, Node.js on AWS Lambda
    DataMySQL and PostgreSQL on Amazon RDS, Amazon DynamoDB
    Cloud and deliveryAWS (ECS Fargate, Lambda, S3, CloudFront, SES), CloudFormation, AWS CDK, CodePipeline, GitHub Actions
    IntegrationsStripe, myPOS, Callflow telephony, Firebase Cloud Messaging, Mapbox, AppsFlyer
    Quality and monitoringJest, Playwright, Amazon CloudWatch, Looming Logger

    Outcome and Impact

  • One platform for the whole business: phone, website and app orders, dispatch, payments, telephony and payroll, built and continuously improved for ten years.
  • Scale: about 82,000 distinct customer phone numbers served and 23.8 million GPS points recorded.
  • Modernised without downtime drama: the API moved from Node.js 8 to 22 in one release, and the production database upgrade took under four minutes of downtime.
  • Lower running cost: AWS spend down by about 27%, from about 262 to about 190 USD a month.
  • No more spreadsheet payroll: wages, bonuses, expenses and cash reconciliation run in one system with an audit trail, alongside a trip forecast for planning.
  • A modern customer experience: Live Activities on the lock screen, CarPlay and Apple Watch, and both apps relaunched on the new brand.
  • What This Looks Like for a Delivery or Field Logistics Operator

    A courier, delivery or field-service business runs the same operation with different nouns. Every building block above carries over:

    At Lucky DriveFor a delivery or field logistics operator
    Phone, website and app orders in one dispatch queueOrders from customer service, a web shop, EDI or a customer portal in one job queue
    Driver teams with "first to accept wins" offersCrews or vans offered jobs by zone, with the first available crew taking it and the dispatcher able to override
    Dispatcher panel with live trips on a mapControl room view of every van, job and delay, with manual assignment for exceptions
    Fares from cleaned GPS distance and waiting timeMileage, waiting time and surcharges billed from the actual route, with a regression test on real jobs
    Click-to-call without exposing personal numbersMasked calls between drivers, dispatch and the recipient, with escalation when nobody answers
    Live Activities with driver arrival timeLive delivery tracking and arrival windows for the recipient
    Shift reports, wages, bonuses and cash reconciliationDriver timesheets, piece-rate or bonus pay, fuel and expenses, cash-on-delivery reconciliation
    Trip forecast from history, holidays and bridge daysVolume forecast per depot to plan crews and vehicles
    Session and GPS data analysis for account integrityProof of who drove which route, shared-login detection and audit trails for disputes

    The difference between packaged dispatch software and a custom build is that the system starts from your channels, your crews and your pay rules, and a technical lead who knows them keeps it running year after year.

    Let's Get Moving!

    If your dispatchers, drivers or office are working around the software rather than with it, we would like to hear how your operation runs. Reach out at blooming@looming.tech and let's talk about what a platform built for your business would look like.

    ~82,000 distinct customer phone numbers served