AUTOMOTIVE SERVICE CRM
AUTOMOTIVE SERVICE CRM
An automotive service operations platform for work orders, Kanban, scheduling, CRM, fleet, inventory, documents, roles, and a contextual AI agent.
What the business needed?
The GruzRemMotor personal cabinet is a standalone operations product rather than a basic customer portal. It connects the owner, intake staff, mechanics, and administrators across the complete repair lifecycle: appointment, vehicle intake, work order, labor and parts, approval, pickup, and follow-up. The dashboard summarizes workshop state and revenue, the Kanban board exposes operational load, and a contextual Qwen agent understands the current screen, prepares a summary, and proposes a safe action. Every data-changing action requires explicit user confirmation.
What we built
Workshop operations are fragmented
Appointments, work orders, approvals, inventory, and pickup messages lose shared context when spread across sheets and chats.
Owners lack an operational overview
Without one dashboard it is difficult to see workload, vehicles ready for pickup, parts blockers, and the financial picture.
A work order has many stages
From booking to delivery, a vehicle changes statuses, assignees, labor items, parts, approvals, and documents.
Customer, vehicle, and service history are connected
A repeat visit requires one view of contacts, fleet, mileage, previous work, and maintenance recommendations.
Roles require different access
Owners, intake staff, mechanics, accountants, and customers should not have identical visibility or actions.
AI must not change business data silently
An assistant can search and prepare operations, but critical mutations require transparency and confirmation.

How the project was built
01
Created one operations workspace
Dashboard, work orders, scheduling, CRM, fleet, inventory, and reference data share a consistent domain model.
02
Visualized work in progress
A Kanban board exposes each repair stage and makes queues and blockers immediately visible.
03
Connected customers, vehicles, and history
Profiles combine contacts, vehicles, visits, documents, feedback, and service recommendations.
04
Automated documents and accounting flows
The system manages labor, parts, invoices, stock movements, financial indicators, and pickup preparation.
05
Implemented roles and protected actions
Permissions control visibility and mutations while critical operations remain auditable.
06
Added a contextual Qwen agent
The agent understands the open section, summarizes it, finds records, and proposes actions that always require user approval.



Tools
- Next.js
- React
- TypeScript
- Tailwind CSS
- TanStack Query
- PostgreSQL