Parking Management Platform for Urban Mobilityon Next.js and Python
Parking is a low-engagement product with thin margins per transaction. Kansoft built a multi-tenant platform that handles daily booking and subscription permits in one flow, then added a self-service advertising layer that turns the same user base into a second revenue stream.
A parking product that needed to become a platform.
Park Pay operates in mobile computing software, providing digital parking solutions for urban operators. The core product worked: users found a space, paid, and left.
The commercial problem is that parking is a low-margin, low-engagement transaction. Growing meant either more locations or more value per user, and the client wanted both: subscription permits for recurring revenue and an advertising platform to monetise the audience the parking product already had.
Architecture diagram for this engagement is being drawn.
Four things standing between a booking tool and a platform.
Each one is a separate product problem. Solving them in isolation would have produced three disconnected systems sharing a logo.
Two parking models, one interface
On-demand daily parking and long-term subscription permits have different pricing, billing and availability logic, but users expect one simple experience covering both.
An advertiser ecosystem from scratch
Monetising the user base meant building self-service onboarding, campaign creation, placement management and performance tracking, a significant product expansion well beyond parking.
Concurrency at multiple locations
Growth across locations and users required high-concurrency booking, real-time availability updates and multi-tenant operation without performance falling away.
Engagement in a low-engagement category
Nobody wants to spend time in a parking app. The experience had to be frictionless enough to drive repeat use and subscription uptake while still surfacing advertising content.
Ship parking first, then layer revenue onto it.
Building booking, subscriptions and advertising simultaneously would have delayed everything and risked a platform none of whose three parts was good. Phasing it meant the core product earned its users before the monetisation layer asked anything of them.
Journey mapping
The full experience mapped for three distinct personas — pay-as-you-go drivers, permit holders and advertisers — so each flow serves its user rather than averaging across them.
SaaS architecture
A scalable multi-tenant design with a React and Next.js front end over a Python backend, built for high-concurrency operations and real-time availability data.
Booking and permit engine
A flexible engine covering hourly, daily and subscription parking with dynamic pricing, recurring billing, auto-renewal, grace periods and self-service plan changes.
Advertising layer
A self-contained advertiser module with onboarding, campaign scheduling, targeting, placement management and impression and engagement analytics.
Chosen for concurrency, real-time state and two product surfaces.
The platform serves drivers, operators and advertisers from the same data, which puts the weight on the architecture rather than any one interface.
From a parking transaction to a platform that monetises its own audience.
Four changes between the original booking product and the platform now running parking and advertising together.
Four changes that mattered as much as the numbers.
The parking product did not get bigger. It got a second business attached to it, running on the user base the first one already had.
Recurring revenue alongside transactions
Subscription permits with auto-renewal and self-service management convert occasional users into predictable monthly revenue, without a support queue handling plan changes.
A revenue stream that costs little to run
Self-service advertiser onboarding and campaign management mean ad revenue scales without proportional operational headcount.
Operators run their own locations
Pricing, capacity and revenue are managed by operators through an admin interface, so adding a location is not an engineering task.
Advertising that does not break parking
Ads surface contextually inside the flow rather than interrupting it, which is what keeps engagement from costing the core experience.
How the work was shaped.
Monetisation designed into the product, not bolted onto it.
Advertising layers fail when they are added to a finished product and start competing with it for attention. Designing the parking flow and the ad surface together, with the architecture multi-tenant from the start, is what makes the second revenue stream additive rather than a tax on the first. Phasing delivery mattered as much: core parking shipped and gathered real usage before subscriptions and advertising were built on top of it.
Related Case Studies
Xamarin to .NET MAUI Migration for Manufacturing Mobile Apps
A cement manufacturer moved three business-critical apps from end-of-life Xamarin to .NET MAUI in roughly 15 days each, all at UAT inside four weeks.
Procurement Modernization for Manufacturing on .NET 6 and Angular
A cement manufacturer re-engineered its ASP.NET Web Forms procurement platform into a .NET 6 and Angular stack on Azure, keeping every workflow intact.
Angular Frontend Modernization for Travel Tech from Google Web Toolkit
A travel technology platform moved its back office from Google Web Toolkit to Angular module by module, with both systems live and no disruption.