A recruitment CRM and ATS built around an automotive desk.
Most recruitment software hands you generic fields and expects an automotive desk to bend around them. This is the opposite. A system shaped to how you actually place technicians, service advisors, sales executives and managers into dealer groups, OEMs and the aftermarket. Built on the Microsoft 365 you already pay for. You own the data, there's no per-seat licence, mine or Microsoft's, and another developer can pick it up from the docs if I ever step away.
Why a generic CRM never quite fits automotive.
An automotive desk doesn't move like a generic sales pipeline. Your best technicians aren't sitting on job boards waiting to be found, they're working a ramp and get poached every couple of years. A service advisor won't drive 40 miles for the same money, so location is half the match. And the person who pays your fee is a dealer principal or group HR you've known for years, not a fresh inbound lead. Generic CRMs have no real model for any of that. You end up bolting it on with custom fields and a side spreadsheet, and it falls apart the first busy month.
The value on an automotive desk sits in two places a generic tool can't hold: the candidates you've placed before and will place again, and the dealer relationships you've spent years building. Lose either to a leaver's private spreadsheet and you've lost the business, not just the data.
Built around how automotive recruitment actually works.
Same ownership and Microsoft 365 spine as every Sorapis build. The difference is that the fields, stages and automations come pre-shaped to your sector instead of scoped from a blank page.
Roles your desk actually fills
Technician grade and skill (diagnostic, MOT, EV and hybrid certified), service and aftersales, parts, vehicle sales and business managers, workshop control, body shop, dealer principal. Pipeline stages that match a real automotive process, not generic "lead to close".
Location-aware matching
Most automotive candidates won't relocate far. Match on a commute radius from the site, not just a job title, so a recruiter sees who's actually placeable for a role before picking up the phone.
Dealer-group relationships
Track the group, the sites under it, the people you deal with and every conversation across years. The relationship survives a recruiter leaving, because it lives in the system and not in their head.
Re-placement, built in
A tech you placed two years ago is moving again right now. The system surfaces past placements due to move and candidates who've gone quiet, with the fee still attached, so your own database keeps paying you.
Temp, contract and perm together
Aftersales and event staffing run temp, dealer roles run perm. One system handles both, with timesheet and margin visibility on the contract side so you see profit before month-end, not after.
AI on the busywork, not the decision
AI reads CVs and right-to-work documents and fills the fields, drafts the first message and the client-ready summary. A person confirms every time. It runs in your own environment, so candidate data isn't shipped to a third-party model.
I've been inside it, and I'll tell you when it's not for you.
I worked inside recruitment before I built software for it, so I'm not learning your desk on your budget. I build one system at a time, the whole thing, start to finish. You explain the problem to the person who solves it, not a salesperson who hands it to a junior.
I'm also early, and I won't pretend otherwise. If you're a small desk and an off-the-shelf ATS already fits, I'll tell you to stay on it. If you run hundreds of recruiters across a dozen brands, a mature platform may serve you better, and I'll say so. This is for the automotive firm that has outgrown bending generic software and wants a system that finally fits, on infrastructure it owns.
Worried your data won't survive the move? Migration starts with a feasibility study on your real database. If it shows your data can't be brought to the agreed standard, the study is free.
One monthly number, and a short list of everything else.
Most builds run as one monthly number: a groundwork fee to start, then a fixed monthly payment that covers the build, hosting, support and training. The price is fixed for the whole term, no annual increases, and part of every month banks as credit you can spend on future development. Want to end it early? You settle the balance on the work delivered, the credit counts toward it, and everything stays yours. Bug fixes are free, always.
Beyond my fee you pay for three things. The Microsoft 365 licences you already have, so nothing new. Azure AI usage, billed by Microsoft at consumption in your own tenant, typically tens of euros a month, no markup. And a job-board aggregator subscription if you want multiposting. That's the whole list. Support comes with a guaranteed response time on working days.