bugama
Bugama FleetsThe ERP for drivers, vehicles, workshop and settlements.Bugama DriverThe app for your drivers, on iOS and Android.Bugama CompliancePlanned shifts vs. real activity, every single day.Bugama GPSTelematics powered by Wialon, inside Bugama.AI & AgentsDemand forecasting, event radar and agents at work.
Bugama OSCustomers
Our visionThe team, and why we build Bugama.Case studiesHow operators run on Bugama today.ResearchOur white paper on demand forecasting.About BugamaWhat we build and what we believe.Help centerFeatures, definitions and guides.Book a demo30 minutes with our team.
ENES
Bugama Fleetsfleets.bugama.comBugama Compliancelabs.bugama.com
Request a demo
bugama

Bugama is the operating system for ride-hailing fleets: drivers, vehicles, shifts, compliance and money in one place, with AI agents doing the repetitive work.

All systems operationalhello@bugama.com

Products

  • Bugama Fleets
  • Workshop
  • Recruiting
  • Settlements
  • Bugama Driver
  • Bugama Compliance
  • Bugama GPS
  • AI & Agents

Bugama OS

  • The vision
  • Vehicle inspection
  • Energy & charging
  • Passenger care
  • All eight services

Resources

  • Case studies
  • Help center
  • Research
  • Glossary
  • System status

Company

  • Our vision
  • About Bugama
  • Book a demo
  • Contact
© 2026 Bugama. All rights reserved.
ENESHosted in the EUPrivacyTermsCookie policy
Customer stories

How operators run on Bugama

Real operations in Spain and Portugal, told with the numbers that matter to them. Operator names are kept private; the processes and figures are theirs.

Payroll fleet · Spain

One system for ~1,000 drivers, 90 companies and 8 cities

Read →
Rental fleet · Lisbon

Closing 200+ weekly settlements without a spreadsheet

Read →
Compliance · Madrid

Turning shift rules into daily feedback for every driver

Read →
Market study · A Coruña

Finding the afternoon hours when a third of the city waits

Read →
Payroll fleet · Spain

One system for ~1,000 drivers, 90 companies and 8 cities

A Spanish operator with salaried drivers moved hiring, rosters, workshop, damage claims and payroll inputs out of spreadsheets and into one shared record.

FleetsWorkflowsAgents

The challenge

This operator employs its drivers through around 90 small companies that own the cars and licences, in eight Spanish cities. With 30 to 40 drivers leaving every week, mostly during the trial period, hiring never stops. Each damaged car touched the workshop, the insurer, HR and payroll, and each department kept its own spreadsheet.

What changed

  • One record per person, from candidate to driver to leaver, whichever company employs them.
  • Hiring as a workflow: voice agent for first contact, documents by link, contracts signed on the phone, platform access requested automatically.
  • Damage claims across departments: workshop, insurance, HR and payroll work the same file, with the driver’s share split into signed instalments.
  • Department queues for HR, labour relations, workshop, insurance, accounting and legal.
  • Payroll inputs exported to the external payroll provider instead of retyped.
Workflow · Damage claim DF-2291
  1. InspectionIn progress
    Check-in finds new damage on the rear bumper
    Damage report DF-2291 opened automatically
  2. Workshop
    Estimate €1,340 · 3 days off the road
    Replacement car lent between investor companies
  3. Insurance
    Route chosen: own insurer
    Claim file created with photos and estimate
  4. HR
    Driver share above €1,000
    Four instalments agreed and signed
  5. Payroll
    Instalment 1 of 4
    Posted to the driver ledger, no spreadsheet
~1,000

drivers on payroll

~90

employer companies

8

cities in Spain

30–40

leavers a week, replaced through one hiring flow

Rental fleet · Lisbon

Closing 200+ weekly settlements without a spreadsheet

Rent, fuel, tolls, EV charging and platform earnings are matched to the right driver by plate and day, and every Monday the week closes itself.

FleetsSettlementsConnectors

The challenge

In Portugal, this fleet rents cars to self-employed drivers and settles with each of them every week. Rent, fuel cards, motorway tolls, EV charging and platform earnings arrived from different suppliers at different times. A missing toll meant a wrong statement, and a wrong statement meant a dispute.

What changed

  • Every cost attributed automatically to whoever had the plate at that moment: fuel, tolls, charging and platform earnings.
  • The week waits for the data: settlements close only when every connector has synced.
  • One step to close: statements as PDF, receipts and the SEPA bank batch.
  • Cars reserved until inspected: a new driver only gets the keys after the check-in inspection.
Weekly settlement · Week 41 · Lisbon
Driver 2291 · Toyota C-HR AA-41-RT
Mon 6 – Sun 12 Oct · every line attributed by plate and day
Platform earningsBolt · Uber · 63 trips€ + 812.40
Weekly rentRent + 10% agreement€ − 280.00
FuelPrio card · 3 transactions€ − 64.20
TollsVia Verde · 11 passages€ − 18.45
EV chargingAtlante · 2 sessions€ − 22.10
Damage instalmentDF-2291 · 2 of 4€ − 50.00
Balance to driver€ 377.65
PDF statement SEPA batchRecibo verde issued
Mon–Sun

settlement week, closed every Monday

4

cost connectors: fuel, tolls, charging, earnings

1

click to close the week

PDF + SEPA

statements and bank batch, generated together

Compliance · Madrid

Turning shift rules into daily feedback for every driver

Late starts, time in revenue zones and peak-hour availability are measured for every shift, and drivers hear about it the same evening.

ComplianceGPSVoice agent

The challenge

Salaried drivers in Madrid share each car in 12-hour morning and afternoon shifts, organised by rest-day groups. The rules were clear on paper (start on time, work the revenue zones, be online at peak hours) but checking them meant hours of cross-referencing platform exports with GPS.

What changed

  • Every shift measured about two hours after it ends, with the first GPS movement as the real start.
  • City-specific rules: late start, minutes in revenue zones, peak-hour availability, cancellations and eco-driving.
  • Same-day feedback by SMS and email, and a call from the voice agent when it happens again.
  • Top earners exempt, so the best drivers are never interrupted.
  • Shared cars handled: kilometres split between the morning and afternoon driver.
Feedback to drivers · automatic
Same evening · SMS

“Hi Daniel, yesterday your LM2 shift started 44 min late and you spent 312 of 420 minutes in revenue zones.”

Same evening · Email

The full timeline of the shift, with the rule, the target and the result for every check.

If it repeats · Voice agent

“I can see it happened again today. Is something stopping you from starting on time?” The answer is logged.

Top 10% earners · No message

Drivers in the top decile of their city are exempt. Good results are not interrupted.

≈2 h

after each shift, results are ready

420 min

target inside revenue zones per shift

Top 10%

of earners exempt from messages

3

channels: SMS, email and voice

Market study · A Coruña

Finding the afternoon hours when a third of the city waits

Live data across nine fleets showed 35–38% of cars parked in the afternoon versus about 20% in the morning, so the roster could change accordingly.

ComplianceAI & data

The challenge

In a mid-sized city, more cars do not always mean more trips. The operator wanted to know when the market was saturated before adding or moving cars, using data rather than impressions from the drivers’ chat.

What changed

  • Live states of nine fleets compared hour by hour: cars on a trip, going to a pickup, or parked waiting.
  • Clear pattern: about 20% of cars waiting in the morning, with 8 to 9 minutes between trips, and 35–38% waiting in the afternoon.
  • Decision: trim afternoon shifts, keep the busy mornings untouched.
A Coruña · share of cars parked, waiting for a trip
Morning19–23%
8–9 min average wait
Afternoon35–38%
Most cars parked of the day
0%25%50%

Nine fleets observed over September, from the operator’s own 39 cars to fleets of three.

9

fleets observed in the same city

39

cars from the operator itself

~20%

cars waiting in the morning

35–38%

cars waiting in the afternoon

Get started

Your fleet could be the next story

Show us how your operation works today. In 30 minutes we will show you what Bugama would measure, automate and simplify from the first week.

Request a demoExplore the products