About

Built for the floor, not the boardroom.

OTOLAB started from a simple observation: the software automotive workshops were given had been designed by people who had never stood in one.

Why we built it

Paper sketches and a spreadsheet called final_FINAL_v3.

Walk into most detailing studios, wrapping centres or audio fitment shops and you find the same stack: a paper form for the vehicle inspection, a whiteboard for who is doing what, a spreadsheet for hours, a phone that will not stop ringing with clients asking whether their car is ready, and a WhatsApp group where the real coordination happens.

The generic tools on offer did not fit. Project management software has no concept of a vehicle. Accounting software has no concept of a damage marker on a rear quarter panel. Anything that did fit was priced for a dealership group and configured over six months by a consultant.

So the pieces got built for the work as it is actually done — an order record that knows about vehicles, an inspection that happens on a 3D model instead of a photocopied outline, a task list generated from the services you sell, and a client dashboard so the phone stops ringing.

How we build

Four things we hold to.

The floor decides

If a feature adds a step for a technician holding a polisher, it is wrong. Speed at the point of use beats completeness on a feature list.

Your data is yours

Export it whenever you want. No lock-in, no hostage-taking on the way out, no selling it to anyone.

AI that does the work

Not a chatbot that answers questions about the manual — an assistant with real access that creates the order and assigns the technician.

Priced for real workshops

A three-person detailing studio should be able to afford the same platform a dealership uses. Plans scale with the team, not with ambition.

Come see whether it fits.

Start free, run a week of real jobs through it, and judge it on your own work rather than a demo dataset.