Australian fleet-leasing company: .NET MVC to Next.js Migration case study
A full redesign of an Australian fleet-leasing company's car-lease platform, moved from .NET MVC to Next.js: lease quotes, lease applications and the driver and customer portal.
The Problem
The company's car-lease platform ran on .NET MVC. Quotes, lease applications and the portal its drivers and fleet customers log in to all lived in the old app, which made design changes slow and the user experience hard to improve.
The Solution
Apex36 worked in a four-person team (two developers, a project manager and a QA engineer) from December 2024 to August 2025 on a full redesign of the platform and its move from .NET MVC to Next.js. The rebuild covered the public site, lease quotes, lease applications and the driver and customer portal. The new front end uses Tailwind CSS and shadcn/ui, with TanStack Query for server data and Storybook for the component library, on PostgreSQL and AWS. The platform is live in production.
Features
Lease quotes
The quote flow customers use to price a lease, rebuilt in Next.js.
Lease applications
The application forms and steps, rebuilt with the new design system.
Driver and customer portal
The logged-in portal for drivers and fleet customers.
A component library in Storybook
Tailwind CSS and shadcn/ui components, documented in Storybook so the team builds pages from the same parts.
Results / Impact
on AWS with PostgreSQL.
public site, quotes, applications and portal.
FAQ
The whole platform: the public site, lease quotes, lease applications and the driver and customer portal, redesigned at the same time.
In steps, not one big switch. We rebuild one area at a time, keep old URLs working with redirects, and move users over once each area is tested.
Four people: two developers, a project manager and a QA engineer. Apex36 worked full stack within that team.
Ready to build something impactful?
Let's discuss your project and how we can help you ship faster and smarter.
Book a Free Strategy Call