I build workshop management systems for garages, service centres and spares dealers: digital job cards, parts and labour billing, spares inventory with reorder logic, service reminders and insurance-claim paperwork — from two-bay garages to multi-city chains.
Kasa kay, workshop malak?
Here is the day I keep meeting. Job cards on carbon paper. The mechanic’s estimate held in his head until someone asks. Spares issued on trust and reconciled never. The customer calling three times for a status nobody can give quickly. And insurance claims sitting still because one photograph was not taken at intake.
The workshop is skilled — that part is rarely the problem. The paperwork around it is running on 1995, and revenue leaks through three specific gaps: labour that was performed but never billed, spares that left the store without reaching an invoice, and service-due customers nobody reminded, who went somewhere else. Barobar?
What does the system cover?
- Digital job cards. Vehicle in, complaints, photos at intake, estimate, approval on WhatsApp, status the customer can see. The status link alone removes most of the incoming calls.
- Parts and labour billing. Generated from the job card, so work performed and parts issued both reach the invoice by construction rather than by memory.
- Spares inventory. Issued-to-job tracking that closes the trust gap, reorder points, and a dead-stock report that tells you which parts have been sitting since the model went out of production.
- Service reminders. Due-date automation that brings vehicles back — the cheapest revenue in the trade, and the one most consistently skipped.
- Insurance workflow. Photos, estimates and claim documents assembled as one pack from the job card, so claims go out complete.
- Chain view. Utilisation, revenue and spares variance per branch for owners running more than one shop.
What does it recover, concretely?
Three numbers, all measurable within a quarter. Unbilled labour — the hours performed and forgotten between the bay and the counter, which surface immediately once billing is generated from the card rather than reconstructed. Spares gap — the difference between what was issued to jobs and what appeared on invoices, which is uncomfortable the first month and shrinks fast once it is visible, because visibility alone changes behaviour. Returning customers — the service-due list worked automatically instead of never.
I will not put a percentage on any of those, because yours will differ and an invented figure would be worse than none. What I will do is run the audit on one workshop and one month of your real data, and show you the three numbers before you commit to anything.
The manufacturing sibling — BOMs, job-work, batch costing — is /products/manufacturing-erp; the wider systems view is /industries/retail-systems.
Related reading
/products/manufacturing-erp — the factory sibling · /products/field-operations — for pickup-and-drop and roadside teams · /products/whatsapp-automation — estimates, approvals and service reminders · /industries/logistics — fleet-side maintenance
One workshop, one month
Give me a single workshop and last month’s records, and I will show you unbilled labour and the spares gap in numbers you can verify against your own bay. /contact — ekdum barobar hisaab.
Questions I actually get
My mechanics will not type.
They photograph and tap. The job card is buttons and a camera — complaints selected from a list, condition captured in photos, estimate approved on WhatsApp. Labels are available in Marathi and Hindi. Mechanics adopt it fastest once they realise the photo record ends the damage arguments that used to land on them.
Does it handle multi-brand spares catalogues?
Your part numbers, your rates, with OEM lists importable where you have them. The system does not impose a catalogue — most multi-brand workshops have their own naming built over years, and forcing a new one is how software gets abandoned in month two.
We run six workshops. Does it consolidate?
Per-branch job boards with one owner view: utilisation, revenue and spares variance per workshop. The comparison across branches is usually the most uncomfortable and most useful screen — the same job takes different hours and different parts in different places, and now you can see it.
How does the insurance claim workflow help?
Photos, estimate and claim documents assemble as one pack from the job card rather than being gathered afterwards. Claims delayed by a missing photograph are the trade's most common avoidable delay, and the fix is capturing at intake rather than chasing at submission.
What about service reminders?
Due dates by vehicle, sent automatically on WhatsApp. It is the cheapest revenue in the workshop trade and almost nobody does it consistently, because doing it by hand requires someone to work a list on a busy day.
Can it track spares issued against a specific job?
Yes, and that link is the point. Spares issued to a job are matched against what was billed on that job, so the gap between what left the store and what reached the invoice becomes a report instead of a suspicion.