Built in a workshop.
Proven in a workshop.
TorqueOS was not created in a boardroom or by a software house guessing how workshops work. It came from running an independent workshop and needing a better way to keep the whole day moving.
Running a workshop means dealing with constant phone calls, customers chasing updates and suppliers who need chasing too. Parts arrive late, arrive wrong or change the shape of the day. Jobs move. Technicians need answers. Authorisations, paperwork and invoicing all compete for attention while vehicles still need to be fixed and returned on time.
The problem was not a lack of effort. It was the operational noise created when bookings, customers, vehicles, parts, technicians, approvals and money lived in different places or depended on someone remembering the next step.
We started building the system we wished we already had: something that reduces admin, keeps everyone aligned and highlights what needs attention before it becomes another phone call or delay.
TorqueOS — The Operating System for Independent Workshops.
The aim is simple: let workshops spend less time joining information together and more time fixing vehicles, looking after customers, keeping the workshop moving and running profitably.
What the system should do
Make the workshop easier to run.
Reduce the admin
Keep the information around each job together so the team spends less time searching, repeating and chasing.
Keep everyone aligned
Give the front desk, technicians and owner a clearer view of what is happening and what needs to happen next.
Highlight what needs attention
Make delays, missing answers, parts issues and unfinished work easier to spot before they hold up the day.
Protect workshop time
Help the team focus on vehicles, customers, a steady flow of work and profitable jobs rather than operational noise.
Built from the workshop
Why I Built TorqueOS
I was running a busy independent garage, and too much of the day depended on paper, phone calls, WhatsApp messages and things living in my head. People kept having to ask each other what was happening.
I was always moving between the office and the workshop to answer the same questions: What's in today? Who's working on it? What are we waiting for? Has the customer authorised the work? Have the parts arrived? What needs to go out today? What's finished but not invoiced? Keeping everyone up to date took too much chasing.
Existing systems could handle bits of the job, but I wanted one connected system: booking to job, job to technician, parts to progress, inspection to customer authorisation, invoice to payment, and reminders when the next MOT or service is due.
That's why I'm building TorqueOS from inside a working independent garage. It's shaped around how workshops actually operate, not how a software company assumes they do.
Stephen Fagan — Founder, TorqueOS
The aim is simple: build the operating system independent workshops run their business on.
Built around workshop feedback
Real workshop feedback matters.
Feedback from independent workshops helps keep TorqueOS practical for real jobs, real pressure and the pace of a working day. We listen when:
Something takes too many clicks.
A screen does not match the way the workshop actually works.
A change could save time, prevent chasing or reduce mistakes.
That feedback helps us improve TorqueOS around the way independent workshops actually operate—not assumptions about how they should.
See how TorqueOS works in an independent workshop.
See how TorqueOS handles a workshop day and talk through where it could reduce admin, improve visibility and keep your workshop moving.