Why we built Auto555: what car rentals were missing

Auto555 did not grow out of an idea like "let's build a SaaS". It grew out of repetitive work. We took on several consecutive projects to build accounting systems for companies that rent out cars, and every time we heard roughly the same description of the pain. The cities changed, the fleet sizes changed, the names changed, but the list of problems matched almost word for word. When the same brief arrives for the fourth time, that is no longer custom development — it is a product nobody has assembled yet.

What we saw at rental companies before we wrote any code

The typical picture at a small rental company looked like this: bookings live in a messenger app and in the manager's head, contracts get printed from a template in a text editor, the mechanic remembers the condition of the cars, and the consolidated records sit in a spreadsheet that an accidental sort breaks every so often. That works exactly as long as there is one person and one shift. After that the discrepancies start: a car is rented out twice, an insurance incident is never recorded, a fine arrives two months later and there is no one left to assign it to.

Why the existing systems did not close the question

• General-purpose CRMs handle deals and clients, but they know nothing about a car as an object with mileage, servicing, insurance and an availability status.
• Large foreign rental systems map poorly onto Russian paperwork and onto how money and deposits are actually taken here.
• Homegrown solutions live until the person who wrote them quits.
• Almost nowhere was there a single unbroken chain of "booking → contract → handover → return → fines", and it is exactly at the joints that money is lost.

What we decided to do differently

We started with the car, not with the client. In Auto555 the central object is the vehicle with its own status: available, rented, in for servicing, under repair, sold. Bookings, the availability calendar, the service history, accidents and fines all grow out of it. That ordering looks like a detail, but it determines everything else: if the system knows the real state of the fleet, it can refuse to let you book a car that is physically sitting in the workshop. We put together more on what came out of it on the Auto555 page and in the Auto555 project breakdown.

The contract and the signature — the second reason all of this started

The second block we considered mandatory from day one was documents. The rental agreement and the receipt are generated from the booking data, and the client signs them with a finger right on the tablet at handover. No scanner, no printer, no folder of papers in the boot. We deliberately did not build a contract constructor with a hundred settings: it matters far more that the document is issued in a couple of minutes and contains exactly the data the system already holds.

External requests and what we call the "single window"

A small rental company almost never lives off a single source of clients. Requests come in from its own website, from Localrent, from Wayrent, from Avito. Keeping four tabs open and moving data across by hand is not "extra work" — it is a guaranteed way to eventually rent one car to two people. So requests from the marketplaces and from the website land in one shared list and turn into bookings from there. You can look at the live product at auto555.ru.

What we chose not to promise

We do not write that Auto555 will increase revenue by some percentage — we have no such data, and any figure like that would be made up. The system does not bring in clients and does not fix cars. It does something else: it keeps information from getting lost between shifts and between stages of a deal. Deposits, corporate clients with invoices, roles and access rights, an audit log, two-factor protection, multiple branches — all of it is about the same thing, about control over who did what and where the money and the car are right now. We described data protection separately on the cybersecurity page.

Why the free plan is not a marketing trick

The Standard plan is free: up to five cars and one user. This is not a "two-week trial" but a working mode for those who are just starting out. We did it deliberately — a rental company with three cars objectively has nothing to pay for an ERP for, but it is better to get used to keeping proper records right away rather than after the first double booking. Beyond that there is Premium at 2 990 ₽ a month and Corporate at 10 990 ₽, if the fleet and the team have grown. If you need not a ready-made product but your own system built around specific processes — that is our CRM and ERP development, and you can discuss it through contacts.