The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
A touchscreen app standing on the showroom floor. Visitors browse the full SsangYong range and compare trims there, on the dealership's own device. Nothing is installed on anybody's phone: walking up to the screen is the whole setup.
A showroom floor holds a few cars and a few consultants. At a busy hour a visitor ends up standing in front of whatever happens to be parked there, with nobody free to explain how the trims differ, while the rest of the range exists only in a brochure that goes stale the moment pricing moves. The kiosk sits on that floor as a screen the dealership owns, and it never touches the visitor’s phone. Its scope was drawn narrow on purpose. This is a display for browsing the range rather than a sales channel, and it asks for no contact details or any other personal data.
We go through how the work runs today and what you expect from the software; the scope comes out of that.
We decide what the system is made of and where its information is kept.
We draw the screens and the flow before any code, and start building once you have approved them.
We write and hand over the software so another team could carry it on.
The app lives on the showroom touchscreen, so a visitor starts using it with no download, no account and no personal data handed over.
Visitors move through the whole model range beyond the cars parked around them, and compare equipment packages on the same screen.
Touch targets, type size and navigation depth were set for a short session on foot rather than a scaled-up phone layout.
The kiosk runs on React Native (Expo); updated equipment details reach every screen from the same codebase, with no brochure reprint involved.
| Challenge | Result |
|---|---|
| A showroom can only display a handful of cars; the rest of the range stays invisible | Floor space no longer decides how many models a visitor can explore |
| At busy hours there is no free consultant to answer questions about trim differences | Trim differences get compared without waiting for a free consultant |
| A printed brochure means a reprint every time pricing or equipment changes | Equipment updates ship to the screen instead of going to a printer |
| The interface meets someone standing up, in a hurry, seeing it for the first time | A short session on foot is what the interface was built for, and nobody installs anything |
Our own workshop software, built around the car on the ramp. A work order, the parts it consumes and the invoice it produces run as one chain, and the accounting side hangs off that same record. Maintenance history lives on the plate and chassis, so it travels with the car.
Our own product for HVAC, boiler and appliance service companies. The customer and device records the office works from are the same ones the technician carries into the field. A job can be opened and closed in a basement with no signal, and service history stays tied to the device.
Our own product, still in development and not yet live. How long an appointment runs, what it is booked against and how bookings stack all differ by trade, so we are keeping those rules configurable inside the product instead of fixing them in code.
Tell us how the work runs today and we will look at which step could move into software.
