CONCORSO - PRESENT
Toronto, CANADA
Overview
Concorso is a mobile-first operations platform for Canadian automotive reconditioning businesses. It brings clients, vehicles, estimates, jobs, scheduling, invoicing, and payroll into one workspace, supporting independent mobile operators, established shops, and teams handling dealership work.
The product addresses a fragmented working day: bookings in messages, job details in notebooks, and payment tracking in spreadsheets. Its design brings these responsibilities together around the vehicle and the job, giving owners and technicians a consistent way to organize work across all three operating models.
Timeline:
February 2026 - Present
Platform:
Web App
Project Goals
01
Unify fragmented automotive workflows into one system that supports daily work across three operating models.
02
Make essential tasks usable on a phone, with clear status and consistent information throughout.
Discovery
Understanding the work behind every vehicle
The product brief identifies two connected audiences: owners coordinating the business and technicians completing the work. Their needs overlap around the same job, but the context changes. An owner needs visibility across schedules, payments, and people; a technician needs the next task and its current status.
The documented operating constraints shape the design problem: phone use between physical tasks, work spread across different locations, and dealership vehicles with firm return deadlines. Together, these requirements point toward a shared operational model that preserves essential differences without creating three disconnected products or competing versions of job information.
Designing
One operational foundation, shaped around the work
The design follows one shared vocabulary across clients, vehicles, services, and jobs. This keeps the product recognizable as an operator moves between in-shop, mobile, and dealership work. Differences belong within the relevant workflow, such as a client address for mobile work or a firm return deadline for a dealership vehicle.
Untitled UI components and shared Tailwind tokens provide the interface foundation. Familiar forms, tables, and navigation patterns establish consistency, while the product brief prioritizes scannable information and brief interactions on a phone.</p><p>The implementation also treats loading, empty, error, and retry states as part of the experience. Forms use structured validation, and component examples live in Storybook. These foundations support a coherent product as operational workflows become more detailed.
One workspace for automotive operations
Three connected workflows supporting the entire working day
Unified Job Management
Jobs connect the client, vehicle, selected services, and assigned team within a single business record. The same core structure supports in-shop, mobile, and dealership operations, while each type captures the context needed to carry out the work.
The application includes desktop job creation and a mobile wizard, giving the workflow an appropriate structure for different screen sizes. Owners can organize work through scheduling, while technicians can follow the status of the jobs they are responsible for.
Design value: A consistent operational language makes the relationship between people, vehicles, and work explicit, supporting coordination without requiring separate systems for each operating model.
Connected Client Records
Client management brings contact details, addresses, and vehicles into the same operational structure as estimates and jobs. Dealerships are represented as clients, keeping the organization paying for the work distinct from the location where that work happens.
This distinction matters when a business handles both individual customers and dealership accounts. A shared client foundation supports familiar navigation and record keeping, while dealership-specific service packages accommodate a different commercial relationship. Estimates and invoicing sit alongside the operational workflow rather than becoming an unrelated administrative task.
Design value: Clear relationships between records give owners a consistent place to manage customer context as work progresses.
Timesheets and Payroll
Concorso includes timesheets, payroll, and transactions alongside its job and scheduling workflows. Bringing these responsibilities into the same application connects the administrative side of a recon business with the work owners and technicians already manage throughout the day.
The documented payroll requirements account for the operator's local calendar: pay-period boundaries follow the browser's local midnight. Team management also recognizes invited staff before their first sign-in, reflecting the practical need to organize a workforce before every member has completed account setup.
Design value: Operational details shape the system around the business's working context, providing a foundation for managing people and payment-related administration together.
Impact
One product. Three operating models. Connected workflows.
Operating models supported
Shared operational workspace
Core user audiences
Operational Clarity
Jobs, clients, vehicles, and scheduling share one operational foundation. Owners can review the people, customer details, and work involved without switching between separate systems for mobile, in-shop, and dealership operations.
Consistent Mobile Workflows
The mobile job wizard breaks creation into manageable steps, while familiar controls keep interactions consistent. This supports technicians checking the app between physical tasks and owners coordinating their daily work on their phones.
Connected Administration
Estimates, invoicing, timesheets, and payroll extend the workspace beyond job tracking. Six connected areas cover clients, jobs, scheduling, storage, transactions, and payroll, bringing daily coordination and administration together.
The goal was to make the business side of automotive work feel as organized as the work itself: one place for the vehicle, the job, the team, and what comes next.
Lemans Detailing
Owner
Concorso Car Care
