mocne.aiLet’s talk

Auto repair shop, 5 working days to a working version

Booking and job status system for an auto repair shop

Bookings on scraps of paper, car statuses in the boss's head, the schedule on WhatsApp. Everything moved to one dashboard the whole team can see.

SHORT ANSWER

Repair shops lose jobs because clients call when no one answers and don't know the status of their cars. We build a single screen: vehicle check-ins, service bay calendar, job statuses and daily schedule. Mój warsztat had a working version in 5 business days, and after a month had 31% fewer lost bookings and around 6 fewer hours per week spent on status calls.

The customer searches for this term: „auto repair shop software with a calendar”

Screenshot of Mój warsztat on phones: workshop dashboard with the daily schedule and service bay calendar
The data in the screenshot is sample data.

−31%lost bookings after one month. Around 6 h less on phone calls per week.

Industry
Car repair workshop, team of fewer than 10 people
Delivery time
5 business days to a working version
Scope
Web app and phone version, email/SMS notifications, staff panel, hosting on the client's domain

What actually gets in the way

Customers called, messaged or dropped in — and each channel ended up in a different place. When the mechanic was under a car, the phone rang unanswered, and the customer went to a competitor.

Then there were the daily “is my car ready yet?” calls. A dozen or so of these calls a day pulled people away from work.

What we build

The simplest version that solves the problem: one screen showing what's coming in, which bay it's in and when it's leaving.

  • Vehicle intake: customer, car, issue — in half a minute.
  • Service bay calendar with day and week views.
  • Job statuses: received → diagnosis → repair → ready for pickup.
  • Daily schedule for the whole team, also works on phones.

What changes

After one month, the workshop had 31% fewer lost bookings, and staff saved around 6 hours per week — time previously spent on calls asking about status.

Further features were only built when the team said what they were missing.

„Now I can see everything on one screen, and we haven't forgotten about anyone since.”

Marek Łubik, workshop owner, Kraków
First version
Quick Start from 2 000 PLN excl. VAT
Further development
Ongoing Development from 500 PLN excl. VAT / month
This industry
5 working days to a working version

Questions asked before launch

Does the team have to use a computer?

No. The daily schedule in Mój warsztat also works on phones, and job status notifications are sent by email or SMS. The app runs under your domain, in a browser.

Will it work across multiple locations?

We design systems for repair shop networks with separate locations and isolated data for each one from the outset — we describe this in our note on multi-tenant Postgres RLS.

How much does it cost and how long does it take?

The first working version is Quick Start from 2 000 zł netto. Further development is Ongoing Development from 500 zł netto / mies., with no long-term contract. You get an exact quote after a 20-minute call, before we start work.

What happens after deployment?

We don't disappear. If you want to keep developing the app, choose Ongoing Development — with no long-term contracts and the option to cancel in any month. Otherwise, send requests for fixes to one address: hello@mocne.ai.

How we built it

Describe your situation

A few sentences about what you currently track in a spreadsheet will do. You get a quote after a 20-minute conversation.

Let’s talk