Automotive software development for the fleet, the forecourt and the workshop.
We build inspection, service and aftersales software for dealers, workshops and fleets.
Connect field apps and business systems through a shared vehicle record.
- 150+Projects delivered across 12 countries since 2012
- 100+Senior in-house engineers, six countries
- 2 to 4 weeksTypical time from signature to start
- ISTQBISTQB-certified QA engineers
- ISO 27001Certified security practice, audited by Quay Audit UK
01Overview
Scope the vehicle workflow from real operational data
We map the vehicle workflow with your operational and technical owners, using sample records and the systems they come from. Discovery identifies the data and integration requirements for the first release.
- In the field, at the vehicleGive inspectors a usable record at the vehicle, including when connectivity is limited.
- Inspection and condition capture
- Damage marking and photos
- Offline-tolerant sync
- On the fleet sideTrack the vehicle and the operational events around it.
- Assignment and scheduling
- Telematics and event feeds
- Audit and chain of custody
- On the dealer and aftersales deskConnect the customer's service booking with the work and invoice.
- Service booking
- Customer contact and CRM
- Invoicing and payments
- Vehicle inspection at platform scaleOur vehicle inspection work includes field apps and a central web database for a platform supporting 9M+ vehicles.
02Where it sits
Match the automotive workflow to the software layer
The software layer sets the interfaces, operating constraints and support responsibilities. Use that distinction to scope the business application and its connections.
| Where the software sits | What that decides | What you are actually buying |
|---|---|---|
| Inside the vehicle: ECU, head unit, firmware over the air | Functional safety, homologation and vehicle release cycles | ECU, head-unit and firmware work follows the vehicle’s functional-safety and homologation process. We develop the integration layer that receives vehicle data and makes it usable in fleet and business applications.Platform development and integrationOr book a meeting |
| In the field, next to the vehicle | Photos, damage evidence and connectivity at the vehicle | A cross-platform app an inspector can work from standing at the car: photos attached to the record, damage marked on a vehicle diagram, pushed to one web platform behind it.Vehicle inspection platformOr book a meeting |
| In the workshop and the parts room | Service decisions grounded in condition and history | Condition-based service intelligence over the shop’s own history of parts, lubricants and fluids, delivered through the CRM and warehouse systems it already runs.Service intelligence for vehicle maintenanceOr book a meeting |
| On the dealer’s desk and the customer’s phone | Booking and aftersales connected to the DMS | Use the DMS for the workflows it already serves; develop a custom layer for dealer booking, aftersales contact and invoicing where needed. Define data exchange and upgrade responsibilities before implementation.How we build custom systemsOr book a meeting |
| The system that already runs all of it | Supported frameworks and maintainable integrations | Modernize the existing application module by module, preserving the vehicle data model and documenting its connections so each replacement has an agreed scope.Legacy software modernizationOr book a meeting |
03Solutions
Software for fleet, dealer and workshop operations
Assigned inspections and arrival records, photos attached to the vehicle record and damage marked on a diagram, with a cross-platform app that syncs to a central web platform.
- Right when
- Inspectors need a shared evidence record
Track parts, lubricants and fluids through each vehicle's service history, using its condition and usage to inform service recommendations.
- Right when
- Service advice needs vehicle-specific evidence
Dealer booking, aftersales contact and invoicing connected to the service job, including appointments, between-visit communication and payment records.
- Right when
- Booking and aftersales span several tools
Connect the dealer management system (DMS), shop CRM and warehouse systems through middleware, with supported interfaces, validation and synchronization agreed for each platform.
- Right when
- Your product connects to customer systems
Vehicle and field-device event feeds in one operational data store, with reporting for assignment, audit and chain of custody.
- Right when
- Vehicle records are split across systems
Move a desktop product to multitenant cloud or modernize an unsupported framework module by module, retaining the vehicle data and sequencing the change around live operations.
- Right when
- The application needs a supported platform
04Stack
The application stack behind our automotive systems
Our automotive work includes .NET server applications with web and cross-platform mobile clients. The architecture connects field records and shop data across the platforms the business retains.
JavaScript
TypeScript
Angular
Vue.js
iOS
Android
ASP.NET- .NET
C#
MS SQL
Dealer and fleet systems often outlive their framework's support. So we design a data model that stays unchanged as the framework is upgraded, and we document the integrations. We set up the project so a new engineer can build it on day one.
Oleksandr TrofimovCTO & Co-Founder, unicrew05Proof
Vehicle inspection and maintenance platforms
- Vehicle inspection, at national scaleFor Jack Cooper, a US automotive-logistics provider, we built an inspection platform with iOS and Android field apps and a central web database. The platform supports inventory and inspections across 9M+ vehicles for OEMs, car rental companies, lending institutions, dealerships and auctions. ASP.NET, JavaScript and Xamarin, with Angular in the front end.9M+vehicles the platform supports
- A desktop product rebuilt as multitenant SaaSFor eAutoClub we rebuilt Service Intelligence from a desktop product into a multitenant web application. It connects workshop data to service decisions based on the vehicle's condition and history. Onboarding and supporting new clients took significantly less time.
- Aftermarket and buyback inspection workFor Logic Screen Solutions in Karlsruhe, we developed dynamic Excel imports, Elasticsearch document search and multiparty roles for an aftermarket project database. Its CEO writes: "Close deadlines have always been met so far." Mover Technologies' founder describes a manufacturer buyback app we built: "Our app helps inspectors evaluate minor damages to determine whether vehicles qualify to eventually be pushed to auctions and sold." Both were written under our former Artelogic brand.2verified reviews describing vehicle work
06Client voices
What clients on vehicle and aftermarket software say
They always seem to have a suitable developer on standby when we require an additional skillset and they always respond very quickly and help to work out a solution if e.g. the project requirements are suddenly changing.
I’m consistently humbled by Artelogic’s performance. Projects of this caliber are hard to outsource. Teams come and go, and this type of work almost never gets done. They’ve kept their priorities straight as they’ve grown and always deliver.
07Case studies
Automotive platforms built for the field and workshop
Explore the inspection platform's field-to-web workflow and the service-intelligence product's move from desktop to multitenant cloud.
See all case studies
AutomotiveJack Cooper: Automotive softwareA sophisticated vehicle inspection tool for one of the biggest transportation providers.
AutomotiveService Intelligence: App for vehicle maintenanceunicrew helped eAutoClub move Service Intelligence, an app that works out what service a vehicle needs from how it is actually used, from the desktop to a multitenant cloud platform.
08Questions
Questions about automotive software projects
Fleet and dealer applications manage operational workflows; in-vehicle software handles the vehicle's own control and head-unit functions.
- In the vehicle: ECU, head-unit and firmware functions are scoped against the applicable functional-safety and homologation requirements.
- Fleet and field applications: inspection, telematics, assignment and audit, with connectivity and offline behaviour scoped for field use.
- Dealer and aftersales applications: booking, CRM, service history and invoicing, often connected to the DMS.
We build fleet, dealer and workshop business applications around the vehicle.
- Field inspection and condition capture.
- Vehicle records, service and parts history.
- Dealer booking, aftersales contact and invoicing.
- DMS, shop CRM and warehouse integrations, with fleet and inspection reporting.
We also modernize the applications and frameworks behind these workflows.
Yes. We scope middleware between your product and the dealer management system (DMS), shop CRM and warehouse systems, based on the interfaces and access they provide.
We agree the data flows, synchronization points and validation and transformation rules before building connectors. Where APIs are limited, we determine a feasible route before committing the integration scope.
We quote automotive software development against the vehicle workflow, data and integration scope agreed in discovery.
- Time and materials: billed hourly, quoted per project.
- Fixed price: quoted per project against an agreed outcome.
- Team extension: billed monthly per team member.
A DMS integration and a field inspection platform have different scopes. A post-launch warranty is standard on fixed-scope work, with the length agreed per contract.
Most engagements start within two to four weeks of signature. Delivery dates follow the agreed workflow, vehicle data requirements and integration dependencies.
For inspection platforms, we agree which inspection and client-onboarding rules the operational database must make configurable. The priority workflow goes in front of inspectors or service staff before the remaining scope is committed.
We plan framework upgrades as part of the application's maintenance and modernization.
Upgrades proceed module by module, maintaining the vehicle data model and integration behaviour as components change. A desktop-to-cloud migration can use the same sequencing approach. Delivery includes build and integration documentation for the team maintaining the system.
We scope security and applicable GDPR requirements for the personal data your vehicle application holds.
Inspector locations, owner contact details and service history linked to a vehicle identification number (VIN) inform the access and retention design.
On build engagements, contracts and NDAs come first. Access is least-privilege and agreed with your technical contact, read-only wherever the work allows, with no production write access during discovery.
unicrew has ISTQB-certified QA engineers. Our ISO 27001:2022 and ISO 9001:2015 certifications cover information security and quality management systems, renewed through a multi-stage audit with Quay Audit UK.
Scope your inspection, service or aftersales project
Share the vehicle workflow you want to develop and the systems it depends on. We agree a first scope and the integration or upgrade questions to resolve.
What happens after you contact us
- We reply within one business dayTell us about the vehicle workflow you want to build or connect.
- A call about the vehicle and the deskWe review the vehicle data, field conditions and business systems the work depends on.
- Placement and engagement model, in writingBuild, integrate or modernize, priced as time and materials, fixed price, or team extension.
- NDA, then discoveryMost engagements start within two to four weeks of signature.