The lot is the source of truth
If the yard says sold and the app still shows available, you have a complaint, not a feature. Status changes have to land on mobile and on the dealer desk without a nightly spreadsheet.
Automotive & Mobility
Cars in this market do not sell from a brochure. Official Toyota, Honda, Mercedes-Benz, BMW, Nissan, Hyundai, Volkswagen, and Ford networks sit next to importers, WhatsApp lots, assemblers such as Innoson, and dealer groups such as Stallion, CFAO, and Coscharis. Bolt and Uber run on the same roads. A buyer wants to see the unit, talk to a person, and book an inspection — not download a PDF.
The product has to keep the yard honest. Which VIN is on the lot this morning. Which walkaround matches that VIN. Which lead is waiting, and which inspection slot is free. When the lot and the app disagree, the dealer loses the sale and the buyer goes back to Instagram. NADDC, FRSC, SON, and Customs sit on assembly, the road, standards, and the port. They define that environment. They are not clients.
We build that layer: inventory, media, leads, chat, and booking. We are not a dealer group. We do not import cars. You keep the stock, the sales team, and the repository.
Who this is for
- Dealer groups and lots that still close inventory on WhatsApp and a spreadsheet.
- Marketplaces that have to show used cars honestly — video, not three photos — and get a human to an inspection.
- Ride-hailing and fleet products that need dispatch, driver tools, and a trail of trips, not a landing page.
In this sector
Lots, dealer desks, inspections, and the road.
Dealer inventory
Units, prices, branches, and status that match what is actually on the yard — including when a car moves or sells.
Media a buyer will trust
Walkaround video and stills tied to a VIN, not a folder of unmatched photos.
Leads and inspection slots
Chat, a pipeline, and a calendar so two buyers cannot book the same bay.
Mobility on the same roads
Driver and rider tools, dispatch, and trip history for products that sit next to the dealer trade — Bolt and Uber define that layer, they are not clients.
Areas covered
We build the software a dealer, lot, or mobility product actually runs on. Typical work includes:
01
Buyer app and dealer desk
The feed the buyer scrolls, and the desk the dealer sits in: listings, chats, leads, and the day’s inspections. One product — not a WhatsApp group, a Google Sheet, and a Facebook page that only one person can update.
02
Inventory that matches the yard
Every unit has a status: on lot, reserved, sold, in transit. Price and media follow the VIN. When a car leaves the yard, it leaves the feed. That is the difference between a catalogue and an operation.
03
Walkaround video and listing media
Dealers shoot on a phone, on a bad network. The product has to accept that upload, attach it to the right unit, and play it for a buyer without pretending every lot has a studio.
04
Inspection booking and handover
A slot, a location, a person. No double-booking. After the build, the repository, keys, and hosting sit in your name — same handover as AutoShowroom.ng.
What the software has to survive
A car product is not finished when the listing page looks good. It has to survive a Saturday lot, a sold unit that is still online, and a buyer who will not trust three photos.
Media that can be audited
Walkarounds are evidence. They belong to a VIN. A dealer cannot swap photos onto another unit without a trail. Buyers in this market have been burned; the product has to make that harder.
Leads that do not die in a chat
Interest arrives as a message. Someone has to own it, book an inspection, and close or lose it. A dump of WhatsApp exports is not a pipeline.
Phones and bad networks
Uploads, live video, and booking happen on the lot and on the road. The product has to work when the network is ugly — that is the environment, not an edge case.
Questions a dealer will ask
If the product cannot answer these on a busy Saturday, it is not ready. We design so it can.
- 01
Which VIN is on which lot this morning?
- 02
If a dealer changes the price on the yard, when does the app update?
- 03
Who can publish a listing, and can they do it without a walkaround?
- 04
What happens when two buyers book the same inspection slot?
- 05
If a car sells, does it leave the feed, the dealer desk, and any ads you still run?
How we build it
Automotive software fails in operations, not in the hero image. We build for the lot you actually run.
Lot first
Inventory and status are modelled before the buyer feed. The catalogue is a view of the yard, not the other way around.
Media pipeline
Upload, attach, play. Designed for dealer phones, not a studio brief.
Named roles
Dealer staff, buyers, and platform admins do not share one login. Publishing a listing is not the same permission as deleting a dealer.
Handover
Repo, keys, and hosting in your name. Runbooks for a sold unit, a bad upload, and a double-booked slot.
- A dealer who works the lot sits in discovery — not only the founder.
- We do not ship a feed that cannot be taken down when the car is gone.
- You own the code. We do not keep the lot’s data after handover.
Where we stop
Trust starts with a clear line. We build the system. We do not pretend to be the dealer, the importer, or the ride-hailing company.
- We do not hold stock, run a franchise, or inspect cars for you.
- We do not claim Innoson, Stallion, CFAO, Coscharis, Bolt, or Uber as clients. Those names define the sector.
- We do not hold a NADDC, FRSC, SON, or Customs brief. Those agencies define the sector. They are not clients.
- We do not keep production keys or the repository after handover.
The landscape
Agencies that write the rules, then OEM marks buyers already know, and the mobility apps that sit on the same roads. This is the market — not a list of Emicraft clients. Local groups such as Innoson, Stallion, CFAO, Coscharis, and Autochek belong in that picture even when we do not host their marks.
Regulators & agencies
OEMs
Ride-hailing
Building a lot, a dealer desk, or a mobility product?
Bring how cars actually move through your yard — or how trips actually dispatch. We will say what the software can carry. AutoShowroom.ng, built for Omoiyi Show, is the case in this sector.