Parking Platform - Urban Mobility

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.

2 · revenue streams from one platformSelf-service · advertiser onboardingMulti-tenant · SaaS architecture
The Client

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.

The Problem

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.

01

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.

02

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.

03

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.

04

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.

What We Recommended

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.

PHASE 01

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.

PHASE 02

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.

PHASE 03

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.

PHASE 04

Advertising layer

A self-contained advertiser module with onboarding, campaign scheduling, targeting, placement management and impression and engagement analytics.

Technology Stack

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.

React / Next.js
Driver, operator and advertiser interfaces from one component system
Python
Booking engine, subscription billing and campaign delivery services
Multi-tenant design
Location and operator isolation with shared infrastructure
Real-time availability
Space state updated across concurrent booking sessions
Payment integration
Booking transactions, recurring subscription billing and advertiser payments
Unified analytics
Occupancy and revenue for operators, performance metrics for advertisers
Measured Outcomes

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.

2
Revenue streams
Parking fees joined by advertising on the same user base
Unified
Booking and permits
Daily, hourly and subscription parking in one flow
Self-service
Advertiser onboarding
Campaign creation, targeting and analytics without operator involvement
Multi-tenant
Architecture
Multi-location deployment with horizontal scaling built in
What Changed for the Business

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.

Engagement

How the work was shaped.

Practice
SaaS Product Development · Custom Software Development · API & Integration Development · Data Platform & Engineering
Platform & stack
React · Next.js · Python · REST APIs
Industry
SaaS & Digital Platforms
Timeline
Dedicated team, ongoing engagement
Why Kansoft

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.

Running a platform with a user base you are not monetising?

Tell us what your product does today and who uses it. We will map where a second revenue stream fits without degrading the core experience.

Book a Free Call