Auto repair shop software built around your bays, slots and prices
We build booking and quoting systems for car service, repair and detailing businesses, then keep them running. Drivers see a price, pick a slot and book; your team gets the booking in its calendar and a message on the phone. We built and run this on a car service and detailing site: online booking in 45-minute slots, a quote page and five driver tools, in three languages.
- 45 minslots drivers book online, without calling
- 3languages: Polish, Ukrainian, English
- Sheetshold prices and services, so staff change them without a developer
- 5free tools for drivers, plus an instant quote page
What goes wrong at the front desk, and what we build for it
Bays get double-booked
Bookings come by phone, Instagram message and walk-in, and they land in three different places.
What we buildOne booking calendar with your slots. Online bookings write into it, and staff add phone and walk-in bookings in the same place.
Quotes are guessed on the phone
Prices sit in someone’s head or an old spreadsheet, so two calls get two answers.
What we buildA quote page that reads your price list from a sheet you edit. Change a price in the sheet and the site follows, as it does on the car-service site.
The shop software can’t book online your way
The off-the-shelf tool has its own slot lengths and packages, not yours.
What we buildOnline booking in your own slot lengths and service packages. If your workshop software has an API, the booking can go there as well.
Car details are typed by hand
Staff copy the make, model and registration from a photo or a phone call.
What we buildA registration-document scan, so the driver’s photo fills in the car’s details.
Customers forget their next service
Nobody sends reminders, so the car goes somewhere else next time.
We would buildReminders by email or message, based on the last visit and the service done. Reminders are not part of the car-service build; they are the next piece we would add.
The website is a brochure
It lists services and says “call us”. It doesn’t answer questions, take bookings or show up in AI assistants.
What we buildService pages, articles on a schedule and tools for drivers, plus an OpenAPI booking API and llms.txt so AI assistants can read the site and book. See AI in your operations.
A second location means starting over
Each site gets its own setup, and the numbers don’t add up across them.
What we buildLocations as data in the same system: one calendar per site, one price list with local changes, one view of all bookings.
How the pieces connect
Relevant case
What we built for a car service
The client is a car servicing and detailing site, a project we built and run. The aim was that drivers see a price, pick a time and book without calling. We built the whole website.
- Online booking in 45-minute slots, written to Google Calendar, with a message to the team.
- A quote page, five driver tools and a registration-document scan.
- Prices and the catalogue in Google Sheets.
- A booking API for AI agents, and a retry every 30 minutes for anything that didn’t arrive.
Taking bookings by phone and message?
We build the booking, the prices and the site as one system, then look after it.
How the work runs
Tell us what happens today
Tell us how bookings and quotes reach you now and which tools your team already uses. We reply within one business day, usually within a few hours.
A free first look
An online call, and an outside check of your site with XRay, our own audit tool. A deeper audit is scoped after the call.
Build, or take over
We build the missing parts, or take over a system someone else built. One team covers analysis, build, testing and DevOps.
Keep it running
Fixes, security updates and new features. Hourly billing, one rate for the whole team, a report every week.
You own the code, the data and every account. More on how we work and the systems we have built.
What this doesn’t do
No replacement for your parts or accounting system. If you have workshop software you like, we connect to it instead of rebuilding it.
No promises about Google rankings. We build pages that search engines and AI assistants can read. Positions are not ours to promise.
No prices before we talk. Billing is hourly with weekly reports, scoped after the call.
Questions we get from workshop owners
Can it work alongside the workshop software we already use?
Usually. If your software has an API, bookings can go into it. If not, the booking system can be the calendar your team works from, and we keep exports for the rest.
Can AI assistants book a visit?
Yes. The car-service site has an OpenAPI booking API that lets AI agents book a slot for a driver, and an llms.txt file that tells AI assistants what the site covers.
What happens if a booking doesn’t reach the calendar?
On the car-service site a job runs every 30 minutes and sends again anything that didn’t get through. Changes go live only after the automated tests pass.
Can drivers book in more than one language?
Yes. The car-service site runs in three languages, with service pages and articles in each.
Who owns the site and the booking data?
You do. You own the code, the data and every account, including the calendar and the sheets.
Where to go from here
Still booking bays by phone?
Phone, messages, walk-ins or a form: tell us how bookings reach you now.
We reply within one business day, Tallinn time (EET), usually within a few hours. No obligation.