Project type
Business WebsiteSystems
Case study
MV AUTA
A public vehicle offer connected to internal operations.
The website could not simply display the offer. It needed to capture customer interest and create a usable hand-off into the company’s internal workflow.
- Public website
- Enquiries
- Vehicle administration
- Internal workflow
Project at a glance
Status
Live project
What I created
Public vehicle offerEnquiry formsInternal administration
My role
Analysis and designUX/UI and developmentLaunch
System scope
Vehicle and content administrationEnquiries and contactsWorkflow statuses
Project context
The problem was not a new website. It was a broken process.
MV AUTA offers used vehicles, vehicle purchasing and related services. The public site therefore had to present a concrete offer and give customers a clear route to contact.
A new website alone would not solve the follow-up work. The solution had to preserve the selected vehicle, avoid manual contact transcription and manage vehicles, enquiries, statuses and content in a connected system.
Three key decisions
Preserve context
The contact remains linked to the offer that prompted it.
The team immediately understands the enquiry without searching for the context again.Connect the public and internal interfaces
The enquiry moves directly from the public website into the internal register.
The public action and the team’s follow-up work use the same information.Administration under one roof
Enquiries, vehicles, statuses and related data are held in one system.
The team does not need to reconstruct work context from several separate places.How the system works
Showroom on one side. Control room on the other. One system in the middle.
One vehicle record
In stockAudi Q7
4.2 TDI quattro
- Year
- 2015
- Mileage
- 202 300 km
- Price
- 449 900 Kč
- Location
- Showroom MV Auta
Selected vehicle
The customer browses the public offer and selects a specific vehicle or service.
Contact action
The form retains the context of the enquiry and the preferred contact method.
Internal record
The enquiry enters the internal register with all related information.
Enquiry status
The team sees the preferred contact method and updates the status as work progresses.
Next action
Work continues without repeated copying or reconstructing context.
The system in day-to-day work
One large viewport. Three real work situations.
The interface remains readable in the context of the complete process, not as a series of small previews.
One systemCustomer enquiry
The contact form is tied to a specific vehicle and gives the team the information needed to respond.
- The selected vehicle remains part of the enquiry.
- The customer chooses a preferred contact method.
Vehicle workflow
The team sees the contact, related vehicle, message and status in one work overview.
- The preferred contact method is visible directly in the record.
- The orange icon identifies the contact method selected by the customer.
- The enquiry status can be updated during processing.
Inventory administration
The internal overview combines vehicle administration, information, photographs and offer status.
- Vehicles, information and photographs are managed in one place.
- Vehicle status is visible directly in the overview.
Product and technical complexity
What needed to be solved
The project’s complexity was not the number of screens, but making the same context work for customers, internal records and offer administration.
Context preserved
The enquiry had to retain its link to the selected vehicle or service while remaining clear to the customer.
Seamless hand-off
After submission, the preferred contact method, related information and processing status had to be visible.
Unified administration
Vehicles, information, photographs and connected content had to remain manageable in one working environment.
Direct responsibility
I led the project from product design through implementation.
I delivered the project independently, from analysis, information architecture and UX/UI through development, launch and client documentation.
I designed
- Brief analysis and solution design
- Information architecture and UX
- Visual interface for the public and internal areas
I delivered
- Frontend, backend and database
- Administration, forms and email notifications
- Czech/English versions, analytics and SEO setup, and client documentation
Technical layer
Technology and capabilities
React + TypeScript
Interactive frontend for the catalogue, vehicle details and user journeys.
PHP API
Server logic for vehicles, enquiries, purchasing and content administration.
MySQL
Database for vehicles, settings and application operations data.
Custom administration
React/PHP interface for managing application data and content.
Technical SEO
Dynamic canonical and OG tags, sitemap and social preview.
Microsoft Clarity
Consent-controlled visitor behaviour analytics.
The client owns the project accounts and content. Later client-side changes are not assessed in this case study.
Project summary
One vehicle.One record.One system.
The public vehicle offer continues into internal work with contacts, statuses and content.
- Vehicle offer
Public offer for a specific vehicle.
- Enquiry
Customer interest retains its context.
- Internal operations
The team continues in one internal record.
Facing a similar situation?
A project does not need to start with a finished brief. We will first define what the system genuinely needs to solve.