Workshop software that knows the vehicle before it reaches the bay.
Service operations lose margin in the gaps: bays idle while a quote waits for approval, a courtesy car goes missing, a part was never ordered. We build the system that closes those gaps, and we bring our own computer vision to the front of it, so the job card opens as the car arrives.
01Bookings & bays02Job cards03Quotes & approvals04Parts & inventory05Technician time06Courtesy fleet07Invoicing & payments08Service reminders
Why they call us
The software stopped being the thing that saves time.
Bays sit idle while paperwork moves
A technician finds extra work, the quote goes to the customer, and the car occupies a hoist until someone approves it. Utilisation drops for reasons nobody is measuring.
The check-in is still a clipboard
Existing damage photographed on a phone, registration typed by hand, and a dispute three days later that nobody can settle from the record.
Parts and courtesy cars run on memory
Backorders discovered on the morning of the booking, and a loan fleet tracked in a diary that only one person can read.
What’s in the platform
Eight modules. Turn on what you need, build what you don’t have.
Every organisation starts from the same core and diverges within weeks. The modules below are the starting point, not the ceiling.
01 / BKGBookings & bays
Capacity-aware scheduling by bay, hoist and skill, with online booking that only offers slots you can actually service.
02 / JOBJob cards
Digital job cards with check-in condition capture, technician notes, photos and video, and a complete history against the vehicle rather than the customer.
03 / QTEQuotes & approvals
Additional work quoted from the bay, sent for approval by SMS with photo and video evidence, and approved with one tap. The clock on the hoist stops guessing.
04 / PRTParts & inventory
Stock by location, supplier catalogues and ordering, backorder visibility against upcoming bookings, and parts reserved to a job before the customer arrives.
05 / TECTechnician time
Clock on and off by job, flat-rate versus actual comparison, efficiency and productivity by technician, and a fair basis for pay structures.
06 / FLTCourtesy fleet
Loan vehicles, bookings, condition records, fuel, tolls and infringements, with availability visible when the service is booked rather than on the day.
07 / INVInvoicing & payments
Invoice from the job card, split billing across warranty, insurer and customer, deposits, terminals and reconciliation into your accounting system.
08 / SVCService reminders
Next-service and inspection reminders driven by date, distance and vehicle history, with declined work resurfacing at the right moment.
Customization
What’s standard, what’s configurable, what we build for you.
Most vendors stay vague about this until you are mid-contract. Here it is up front, so you can price the gap before you commit.
| Area | Standard | Configurable by you | Custom build |
|---|---|---|---|
| Scheduling | Bays, hoists, technicians, capacity rules | Service types, durations, online booking windows | Multi-site load balancing, mobile and roadside jobs |
| Job cards | Digital cards, photos, technician notes | Inspection checklists, required fields, templates | Manufacturer-specific inspection and warranty formats |
| Vehicle intake | Manual registration entry, photo capture | Check-in checklist, damage map, consent wording | PlateSense gate recognition, AutoSense damage analysis |
| Parts | Stock, suppliers, reorder points | Supplier catalogues, markup rules, bin locations | Direct supplier API ordering, superseded part logic |
| Billing | Invoices, deposits, payment terms | Labour rates, menu pricing, discount rules | Warranty and insurer claim formats, fleet contracts |
| Reporting | Utilisation, efficiency, revenue by service | Saved views, targets, scheduled exports | Group dashboards, forecasting, Power BI models |
| Integrations | Accounting, SMS, payments | Credentials, sync frequency, field mapping | DMS bridges, manufacturer systems, telematics |
The AI layer
Where a custom build earns its cost.
Off-the-shelf systems bolt a chatbot onto a decade-old database. We build the intelligence into the workflow, using the same engineering we ship for enterprise clients on Azure AI.
Plate recognition at the gate
PlateSense reads the registration as the vehicle arrives and opens the job card with history attached, so the advisor greets the customer already knowing the car. This is live product, not a roadmap item.
Vehicle image analysis
AutoSense analyses check-in imagery to record existing damage consistently, which settles disputes with evidence rather than recollection.
No-show and overrun prediction
Flags bookings likely to no-show and jobs likely to overrun, so the day is planned against reality instead of the booking sheet.
Demand forecasting
Predicts consumable and common-part demand from your booking mix, cutting both backorders and dead stock.
Quote follow-up agent
Chases unapproved additional work with the photo and video already attached, and escalates to a human when the customer replies with a question.
Ask your data
A grounded assistant over your own operational data. "Which bay lost the most hours to waiting on approval last month?" answered from your records.
Integrations
It has to live with the systems you already bought.
We integrate rather than replace, so what already works keeps working.
Vehicle
- VIN decoding
- Telematics
- Diagnostic tools
- Manufacturer portals
- Tyre & parts catalogues
Money
- Card terminals
- Xero
- MYOB
- QuickBooks
- Finance & warranty providers
Operations
- SMS gateways
- Microsoft 365
- Entra ID single sign-on
- Power BI
- Rostering & payroll
- Booking websites
Compliance & data
Built to survive the questions your adviser will ask.
Repair records that hold up
Immutable job history with photo and video evidence, technician attribution and timestamps. The record you need when a warranty claim or a consumer dispute is raised months later.
Consumer law and warranty
Built to support Australian Consumer Law guarantees and manufacturer warranty documentation, and US state repair-authorisation and estimate-approval requirements. Written authorisation is captured before extra work starts.
Data and imagery handling
Customer and vehicle imagery is stored in your tenancy with retention rules and access logging, which matters once you are capturing number plates and premises footage.
How the build runs
From first call to first live site.
Discovery and workflow mapping
We walk the workshop, time the real intake and approval loop, and audit the data in your current system. You get a written scope and fixed price before we build.
Core configuration
Bookings, job cards, parts and invoicing stood up against your real labour rates, service menus and bay layout.
Integrations and vision layer
Accounting, payments and supplier links connected, and PlateSense or AutoSense installed at check-in if you are taking the vision modules.
Pilot site and training
One workshop goes live with us on the floor, advisors and technicians trained, then a two-week hypercare window before the rest follow.
Support and roadmap
A named engineer, an agreed response SLA, and a quarterly cycle where you decide what gets built next. You own the source code.
Questions
What owners ask us first.
Do we need the camera hardware to use the platform?
No. The vision modules are optional. The platform runs perfectly well with manual check-in, and PlateSense or AutoSense can be added later without rebuilding anything.
How accurate is plate recognition in a real workshop?
Accuracy depends on camera placement, lighting and angle far more than on the model, which is why we survey the site before quoting. Every read is confirmable by the advisor, so a misread is a two-second correction rather than a wrong job card.
Can it work alongside our existing dealer management system?
Yes, and that is often the first step. We integrate at the job and invoice level so you can prove the workflow before deciding whether to replace anything.
Does it handle warranty and insurer billing?
Yes. Split billing across customer, warranty and insurer is standard, and the specific claim formats a manufacturer or insurer requires are a scoped custom item.
How do you handle multi-site groups?
One dataset across sites, with per-site scoping on access and reporting. Load balancing bookings across locations is a custom item because every group prioritises it differently.
What about our historic service history?
Migrated as a defined phase with a reconciliation report. Service history against the vehicle is usually the highest-value data you own, so we treat it as a first-class part of the project rather than an afterthought.
Can we start with one part of it?
Yes. The most common starting point is digital job cards with quote approvals, because that is where the idle-bay time actually goes.
See it running before you decide anything.
Thirty minutes, a working demo build, and an honest answer about whether a custom platform is right for you. If off-the-shelf is the better call, we will say so.
You’ll speak with engineers, not account managers.