labs@atheron:~/industries/automotive$ service --ro 51123 --inspect --charge

Automotive software

From the first service booking to the next EV charge.

Your repair order lives in the DMS, a phone call and a technician's memory. That is hard to explain to the customer waiting on it. We build the systems around the vehicle: apps for the service drive, agents for the phones, shared records of a car's history and apps for the chargers it plugs into.

Start a project See the example projects

// what you are up against

The problems we hear most.

Phones that never stop

Service desks spend the day answering booking, status and recall questions by phone, and customers wait on hold while advisors juggle the drive.

Recommended work nobody approves

Technicians find worn brakes and leaking seals, but a line on an invoice does not convince a customer the way a short video would.

A history spread across many shops

A used vehicle's service and repair history is split between dealers, independents and auctions, and odometer and repair records are easy to dispute.

Chargers drivers cannot trust

Drivers arrive at a charger that is offline or occupied, and support cannot see the station's state to help them.

// example projects

Systems we could build for you.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile app

Service app with video inspections

Hypothetical. Not a client, not a result.

// The problem

A dealer group's service departments write up inspections on paper, and customers decline recommended work they cannot see while advisors chase approvals by phone.

// What we would build

A technician app for multipoint inspections with photos and short videos, a customer link to see and approve work and pay online, and an advisor board showing every repair order's status, connected to the dealer management system.

// What is in it

Multipoint inspections on a tablet, with photos and video per item
Customer link by text to watch, approve or decline each item
Online payment and digital signature at pick-up
Advisor board with every repair order's status and wait time
Sync with the dealer management system for repair orders and parts
Reporting on approved and declined work by advisor and store

// Stack

React Native
Next.js
PostgreSQL
CDK or Reynolds DMS integration
Stripe
AWS

// estimate

Build: ≈ US$137,000 to US$210,000, delivered within 29 weeksCAD 195,200 to 298,600
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 6.9 to 12.4 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
First build on devices: 3.9 to 6.4 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 to 2 weeks
API access approved by your DMS vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 39,040 to 59,720
Discovery 9.2%: CAD 17,958.40 to 27,471.20
Design approved 9.2%: CAD 17,958.40 to 27,471.20
Core features 7.6%: CAD 14,835.20 to 22,693.60
Full build 5%: CAD 9,760 to 14,930
First build on devices 20.1%: CAD 39,235.20 to 60,018.60
Testing and fixes 2.5%: CAD 4,880 to 7,465
Store submission 6.7%: CAD 13,078.40 to 20,006.20
Launch 9.7%: CAD 18,934.40 to 28,964.20
Holdback, 30 days after launch (10%): CAD 19,520 to 29,860

Start from this example

Example projectWeb appAIFrontier model

Advisor agent for calls and chat

Hypothetical. Not a client, not a result.

// The problem

A busy dealership misses calls about bookings, repair status and recalls, and every missed call is a customer who may book somewhere else.

// What we would build

An agent that answers chat, texts and, through a voice service, phone calls: it books appointments in the scheduler, gives repair order status from the DMS and checks open recalls by VIN, handing anything else to an advisor. It runs on a frontier model through its API, which handles conversation well and starts fastest; only what each answer needs is sent.

// What is in it

Bookings made in your service scheduler, with the right time for the job
Repair order status read from the DMS
Open recall checks by VIN against manufacturer data
Hand-off to an advisor with the conversation summarised
Conversations in English and French
Evaluation set of real conversations, run before every change

// Stack

Frontier model API
Twilio voice gateway
Python
Next.js
DMS and scheduler APIs
DigitalOcean

// estimate

Build: ≈ US$102,000 to US$156,000, delivered within 21 weeksCAD 144,900 to 221,600
Hosting: ≈ US$558 a monthCAD 795 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

AI route: Frontier model
Model running cost: ≈ US$383 a monthCAD 545 a month

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Specification and evaluation plan: 0.4 weeks
Design approved: 2.4 to 3.4 weeks
Core features: 1.4 to 1.9 weeks
Full build: 0.9 to 1.4 weeks
Working pilot: 3.9 to 6.4 weeks
Testing and fixes: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks
Production: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access approved by your DMS vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 28,980 to 44,320
Discovery 2%: CAD 2,898 to 4,432
Specification and evaluation plan 10.2%: CAD 14,779.80 to 22,603.20
Design approved 2%: CAD 2,898 to 4,432
Core features 6.2%: CAD 8,983.80 to 13,739.20
Full build 4.1%: CAD 5,940.90 to 9,085.60
Working pilot 30.7%: CAD 44,484.30 to 68,031.20
Testing and fixes 2%: CAD 2,898 to 4,432
Launch 2%: CAD 2,898 to 4,432
Production 10.8%: CAD 15,649.20 to 23,932.80
Holdback, 30 days after launch (10%): CAD 14,490 to 22,160

Start from this example

Example projectWeb appBlockchain

Shared vehicle history ledger

Hypothetical. Not a client, not a result.

// The problem

A network of dealers, independent shops and an auto auction each hold part of a vehicle's history, and disputes over odometer readings and undisclosed repairs end up on someone's desk.

// What we would build

A private permissioned ledger where dealers, shops and the auction record odometer readings, services and repairs against the VIN as they happen, so a vehicle's history is one record no member can quietly change. A commercial history report may already cover your need, and a shared database works if one member is trusted by all; we will say which applies.

// What is in it

Odometer readings and services recorded against the VIN at each visit
Repairs recorded with the shop, date and parts, never the owner's personal data
Readings that go backwards flagged at once
History view for members, with a shareable report for buyers
A node per member, or a hosted node for small shops

// Stack

Hyperledger Fabric (private, permissioned)
Node.js
Next.js
PostgreSQL
AWS

// estimate

Build: ≈ US$113,000 to US$173,000, delivered within 23 weeksCAD 160,800 to 246,000
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Architecture: 0.4 weeks
Design approved: 2.9 to 4.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Devnet: 2.9 to 4.4 weeks
Testing and fixes: 0.4 weeks
Testnet: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Mainnet: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access approved by your DMS vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 32,160 to 49,200
Discovery 2.5%: CAD 4,020 to 6,150
Architecture 6.7%: CAD 10,773.60 to 16,482.00
Design approved 2.5%: CAD 4,020 to 6,150
Core features 7.5%: CAD 12,060 to 18,450
Full build 5%: CAD 8,040 to 12,300
Devnet 20.2%: CAD 32,481.60 to 49,692.00
Testing and fixes 2.5%: CAD 4,020 to 6,150
Testnet 13.4%: CAD 21,547.20 to 32,964.00
Launch 2.5%: CAD 4,020 to 6,150
Mainnet 7.2%: CAD 11,577.60 to 17,712.00
Holdback, 30 days after launch (10%): CAD 16,080 to 24,600

Start from this example

Example projectWeb appMobile app

EV charging app, OCPP back office

Hypothetical. Not a client, not a result.

// The problem

A regional charging network runs its stations from a vendor portal drivers never see, so they cannot tell which chargers are free, and payment fails at the worst moment.

// What we would build

An iOS and Android driver app to find, start and pay for a charge with live charger status, and a web back office that talks to the stations over OCPP for status, pricing, remote starts and fault alerts.

// What is in it

Map of stations with live status per connector
Start, stop and pay from the app, with receipts
Back office speaking OCPP to the chargers for status, pricing and remote resets
Fault alerts to the operations team before drivers call
Roaming with other networks through OCPI
English and French throughout

// Stack

React Native
Next.js
OCPP 1.6 and 2.0.1
OCPI
PostgreSQL
Stripe

// estimate

Build: ≈ US$132,000 to US$202,000, delivered within 28 weeksCAD 188,300 to 288,000
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$5,010 a monthCAD 7,135 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 6.9 to 11.9 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
First build on devices: 3.4 to 6.4 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 to 2 weeks

How it is paid

Deposit 20%: CAD 37,660 to 57,600
Discovery 9.2%: CAD 17,323.60 to 26,496.00
Design approved 9.2%: CAD 17,323.60 to 26,496.00
Core features 7.6%: CAD 14,310.80 to 21,888.00
Full build 5%: CAD 9,415 to 14,400
First build on devices 20.1%: CAD 37,848.30 to 57,888.00
Testing and fixes 2.5%: CAD 4,707.50 to 7,200.00
Store submission 6.7%: CAD 12,616.10 to 19,296.00
Launch 9.7%: CAD 18,265.10 to 27,936.00
Holdback, 30 days after launch (10%): CAD 18,830 to 28,800

Start from this example

Example projectWeb appAPI

Dealer systems integration hub

Hypothetical. Not a client, not a result.

// The problem

A dealer group re-keys repair orders, parts orders and warranty claims between its dealer management system, its parts suppliers and the manufacturer's warranty portal.

// What we would build

An integration hub that moves repair orders, parts orders and warranty claims between your dealer management system and the systems around it, checks each record before it is sent, and shows your service team what went through and what needs a person.

// What is in it

Repair orders and parts orders passed between systems
Warranty claims prepared from the repair order
Each record checked before it leaves
A queue of anything that needs a person to look

// Stack

Node.js
PostgreSQL
REST
OpenAPI
DigitalOcean

// estimate

Build: ≈ US$89,500 to US$137,000, delivered within 25 weeksCAD 127,500 to 195,000
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 3.4 weeks
API contract agreed: 1.4 to 1.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Core resources built: 2.4 to 4.4 weeks
Security, gateway and connections: 1.9 to 2.9 weeks
Testing and fixes: 0.4 to 0.9 weeks
Docs, SDKs and load tests: 1.4 to 1.9 weeks
Launch: 0.9 to 1.4 weeks
Launch and first callers: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access approved by your DMS vendor: 1 to 4 weeks
App store review: 1 to 2 weeks

How it is paid

Deposit 20%: CAD 25,500 to 39,000
Discovery 2.3%: CAD 2,932.50 to 4,485.00
Design approved 2.3%: CAD 2,932.50 to 4,485.00
API contract agreed 6%: CAD 7,650 to 11,700
Core features 7%: CAD 8,925 to 13,650
Full build 4.7%: CAD 5,992.50 to 9,165.00
Core resources built 18.3%: CAD 23,332.50 to 35,685.00
Security, gateway and connections 12.1%: CAD 15,427.50 to 23,595.00
Testing and fixes 2.3%: CAD 2,932.50 to 4,485.00
Docs, SDKs and load tests 6%: CAD 7,650 to 11,700
Launch 2.3%: CAD 2,932.50 to 4,485.00
Launch and first callers 6.7%: CAD 8,542.50 to 13,065.00
Holdback, 30 days after launch (10%): CAD 12,750 to 19,500

Start from this example

Example projectWeb appMobile app

Service booking app, redesigned

Hypothetical. Not a client, not a result.

// The problem

A dealership's online service booking takes a dozen screens on a phone, and many customers give up and call instead.

// What we would build

A redesign of the booking journey for web and mobile, tested with real customers: pick the vehicle, the work and a time in a few taps, see the estimate, and get reminders and status updates while the car is in the shop.

// What is in it

Research and usability tests with your own customers
A booking flow of a few taps, built to WCAG 2.1 AA
Estimates and status updates on the phone
A design system your team can keep using

// Stack

Figma
Next.js
React Native
PostgreSQL
DigitalOcean

// estimate

Build: ≈ US$113,000 to US$174,000, delivered within 26 weeksCAD 161,600 to 247,200
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 7.4 to 12.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.9 weeks
First build on devices: 2.9 to 4.9 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 to 2 weeks
API access approved by your DMS vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 32,320 to 49,440
Discovery 9.2%: CAD 14,867.20 to 22,742.40
Design approved 9.2%: CAD 14,867.20 to 22,742.40
Core features 7.6%: CAD 12,281.60 to 18,787.20
Full build 5%: CAD 8,080 to 12,360
First build on devices 20.1%: CAD 32,481.60 to 49,687.20
Testing and fixes 2.5%: CAD 4,040 to 6,180
Store submission 6.7%: CAD 10,827.20 to 16,562.40
Launch 9.7%: CAD 15,675.20 to 23,978.40
Holdback, 30 days after launch (10%): CAD 16,160 to 24,720

Start from this example

// by service

Go deeper on one kind of work.

Pages for the services we have the most to say about in this industry.

~/apps

Dealer and EV apps

Custom service drive apps with video inspections and online approvals for dealers and repair shops, and EV charging apps with an OCPP back office for charging operators.

~/ai

AI for dealerships

AI agents that answer calls, texts and chat for the service department: bookings in your scheduler, repair status from the DMS and open recall checks by VIN, with hand-off to an advisor.

~/chains

Vehicle history ledger

A private permissioned ledger shared by dealers, independent shops and auctions that records odometer readings, services and repairs against the VIN, so history is one record nobody can quietly change.

// questions

What buyers in this industry ask us.

Do you work with independent shops too?

Yes. Most of these systems suit an independent shop or a network of them as well as a dealer group, and the estimator prices them at that size.

Can you work with our manufacturer's systems?

Where the manufacturer offers partner APIs, yes, usually with its approval. We plan that approval into the work.

How do payments work?

A deposit to start, then payments at agreed milestones, with 10% held until 30 days after launch. The deposit is a smaller share on larger projects.

Who owns the apps and the code?

You do, once the work is paid for, including the back office and any agent prompts and evaluation sets.

// other industries

Nearby industries.

~/logistics

Logistics

Dispatch boards and driver apps, booking agents for the inbox, shared bills of lading on a private ledger and load bots.

See the examples

~/energy

Energy and utilities

Field inspection and work order apps for your crews, operations assistants on private models, renewable certificate ledgers and feeder load forecasting.

See the examples

~/insurance

Insurance

Claims apps with adjuster portals, damage photo models, wording assistants for brokers and shared subrogation records.

See the examples

All industries

// where we work

Find your market.

We work from Kelowna with clients across Canada, the United States and further afield. Each market page covers working hours, hosting, the privacy law that applies, and prices in your currency.

Every market

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call